Forum > GPU crunching

x38g reports

<< < (6/58) > >>

_heinz:
Hi Jason,
with my ION R3600 I'm going back to driver 270.32
21.06.2011 10:06:40      NVIDIA GPU 0: ION (driver version 27032, CUDA version 4000, compute capability 1.1, 242MB, 35 GFLOPS peak)
If I'm lookink up with "AIDA64 Extreme Edition" it shows:
Informationsliste   Wert
Video Adapter Eigenschaften   
Gerätebeschreibung   NVIDIA ION
Adapterserie   ION
BIOS Version   Version 62.79.63.0.1
Chiptyp   ION
DAC Typ   Integrated RAMDAC
Treiberdatum   20.02.2011
Treiberversion   8.17.12.7032 - nVIDIA ForceWare 270.32
Treiberanbieter   NVIDIA
Speichergröße   256 MB
   
Installierter Treiber   
nvd3dum   8.17.12.7032 - nVIDIA ForceWare 270.32
nvwgf2um   8.17.12.7032
nvwgf2um   8.17.12.7032
   
Video Adapter Hersteller   
Firmenname   NVIDIA Corporation
Produktinformation   http://www.nvidia.com/page/products.html
Treiberdownload   http://www.nvidia.com/content/drivers/drivers.asp
Treiberupdate   http://www.aida64.com/driver-updates
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Now I will try x38g again
edit:
x38g is running on GPU now. Report result as soon as ready.

heinz

_heinz:
What we learn from this:
270.32 is not a WDDM driver and BOINC shows 242MB
The newer WDDM driver will not detected properly by BOINC and does not show correct values of VRAM on any of my systems(ION R3600, and I3 Geforce GT540M)
BOINC on I3 shows:
20.06.2011 22:23:06 |  | NVIDIA GPU 0: GeForce GT 540M (driver version unknown, CUDA version 4000, compute capability 2.1, 962MB, 172 GFLOPS peak)
~~~~~~~~~~~~~~~~~~~~~~~~~~~
"AIDA64 Extreme Edition" shows on my I3:
Informationsliste   Wert
Grafikprozessor Eigenschaften   
Grafikkarte   nVIDIA GeForce GT 540M (Medion)
GPU Codename   GF108M
PCI-Geräte   10DE-0DF4 / 17C0-10E2  (Rev A1)
Transistoren   585 Mio.
Fertigungstechnologie   40 nm
Gehäusefläche   114 mm2
Bustyp   PCI Express 2.0 x16 @ x16
Speichergröße   1 GB
GPU Takt (Geometric Domain)   750 MHz
GPU Takt (Shader Domain)   1500 MHz
RAMDAC Takt   400 MHz
Pixel Pipelines   8
Texturen Mapping Einheiten   16
Unified Shaders   96  (v5.0)
DirectX Hardwareunterstützung   DirectX v11
Pixel Füllrate   6000 MPixel/s
Texel Füllrate   12000 MTexel/s
   
Speicherbus-Eigenschaften   
Bustyp   DDR3
Busbreite   128 Bit
Tatsächlicher Takt   450 MHz (DDR)
Effektiver Takt   900 MHz
Bandbreite   14.1 GB/s
   
Auslastung   
Grafikprozessor (GPU)   99%
Speichercontroller   0%
Video Engine   0%
   
nVIDIA ForceWare Clocks   
Standard 2D   Grafikprozessor (GPU): 50 MHz, Shader: 101 MHz, Speicher: 135 MHz
Low-Power 3D   Grafikprozessor (GPU): 202 MHz, Shader: 405 MHz, Speicher: 324 MHz
Performance 3D   Grafikprozessor (GPU): 750 MHz, Shader: 1500 MHz, Speicher: 900 MHz
   
Grafikprozessorhersteller   
Firmenname   NVIDIA Corporation
Produktinformation   http://www.nvidia.com/page/products.html
Treiberdownload   http://www.nvidia.com/content/drivers/drivers.asp
Treiberupdate   http://www.aida64.com/driver-updates
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Pepi:

--- Quote from: _heinz on 20 Jun 2011, 04:40:19 pm ---hi Jason,
I installed latest nvidia beta driver on my laptop, 275.50-notebook-win7-winvista-64bit-international-beta
BOINC 6.12.26 shows:
20.06.2011 22:23:06 |  | NVIDIA GPU 0: GeForce GT 540M (driver version unknown, CUDA version 4000, compute capability 2.1, 962MB, 172 GFLOPS peak)

275.33-notebook-win7-winvista-64bit-international-whql has the same issue.
in general, there must be something wrong in the driver detection of BOINC.

Although,   I can run primegrid.

heinz


--- End quote ---

On my desktop  MB have GPU also. I use MB GPU for usually work, and GTX 560TI only for crunching. When nothing is attached to 560 TI then I have same message as you: driver version unknown
but 560TI works without problem in SETI.

_heinz:
Hi Jason,
all 3 wu's are done now on the ION (driver 270.32)
hostid=5510631
resultid=1956143932
resultid=1956143934
resultid=1956143936

Cuda Active: All 15 paranoid early cuFft plans succeeded.

what does it mean ? all can be used ?

woundering about
<core_client_version>6.10.58</core_client_version>
reports:
SETI@Home Informational message -9 result_overflow
NOTE: The number of results detected exceeds the storage space allocated.

Flopcounter: 42371081878.117691

Spike count:    30
Pulse count:    0
Triplet count:  0
Gaussian count: 0
called boinc_finish
~~~~~~~~~~~~~~~~~~~~~~~~~~~

x38g reports:
Multibeam x38g Preview, Cuda 3.20

Legacy setiathome_enhanced V6 mode.
Work Unit Info:
...............
WU true angle range is :  2.720454

Flopcounter: 10431952929543.820000

Spike count:    2
Pulse count:    0
Triplet count:  1
Gaussian count: 0
Worker preemptively acknowledging a normal exit.->
called boinc_finish
boinc_exit(): requesting safe worker shutdown ->
boinc_exit(): received safe worker shutdown acknowledge ->

So no validation will happen for me.

heinz

Mike:
So far i can see your results looks O.K.
Your winman using fermi app and produces -9 errors.
So the unit will be sent to third host.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version