Author |
Message |
GDFVolunteer moderator Project administrator Project developer Project tester Volunteer developer Volunteer tester Project scientist Send message
Joined: 14 Mar 07 Posts: 1957 Credit: 629,356 RAC: 0 Level
Scientific publications
|
It is NOW available.
Tested on Windows XP SP2, driver 177.84, 8600GT
gdf |
|
|
|
It is not available.
Tested on Windows XP SP2, driver 177.84, 8600GT
gdf
I assume you mean NOW available.
I'm quite busy today and my hosts still have some 6.30 to finish. I set No New Work for now and will let them finish up what they have, maybe by that time I will have some time to upgrade drivers. I need to try that before work hours. After hours I'm usually beat dead. Trying to upgrade with only 1 brain cell left usually causes problems ;)
Will let you know results probably tomorrow or Wednesday.
|
|
|
|
Hi
Thank you GDF, this application works fine on vista64 + 6.3.10 + 177.84, it seems faster than other application, fast as linux application ;) |
|
|
|
Hi,
I made a try with these software installed:
- Vista64 SP1
- BOINC V6.3.10
- nVidia driver V177.84
Hardware:
- Intel Q9450
- nVidia 8800GTS
Messages during BOINC initialisation:
25/08/2008 18:38:06||CUDA devices found
25/08/2008 18:38:06||Coprocessor: Device Emulation (CPU) (1)
All work units failed at begining: result 46974
____________
|
|
|
GDFVolunteer moderator Project administrator Project developer Project tester Volunteer developer Volunteer tester Project scientist Send message
Joined: 14 Mar 07 Posts: 1957 Credit: 629,356 RAC: 0 Level
Scientific publications
|
I think that you have a driver problem for your card.
What is it?
stefan had a similar problem with BOINC 6.3.10, but others are running fine.
gdf |
|
|
|
C'est une 8800GTS 320/640mo ThierryH? si oui, elles ne fonctionnent plus sur GPUgrid avec la nouvelle application
Si c'est la 8800GTS 512, le problème est ailleur
Is it a 8800GTS 320/640mo ThierryH? if yes, they don't work anymore on GPUgrid with the new application
If it's the 8800GTS 512, the problem is somewhere else |
|
|
|
It's a 8800GTS 320 Mo.
Why it's not longer running on GPUGrid ??
____________
|
|
|
|
Read this http://www.ps3grid.net/forum_thread.php?id=303&nowrap=true#1658 :)
Sorry |
|
|
|
I bought this card only for CUDA because I'm not a gamer. I think nVidia will wait a long time before I buy something else...
____________
|
|
|
|
You didn't choose the good graphic card :) |
|
|
|
I think that you have a driver problem for your card.
What is it?
stefan had a similar problem with BOINC 6.3.10, but others are running fine.
gdf
Yep, I still have the problem.
I already tried to uninstall/reinstall the 177.84 driver for Vista64, uninstall/reinstall BOINC 6.3.10 x86_64, but the BOINC Manager still shows the device emulation.
On a GTX 260... :(
____________
pixelicious.at - my little photoblog |
|
|
|
It's a 8800GTS 320 Mo.
Why it's not longer running on GPUGrid ??
Regrettably we are no longer able to support the first generation of 8800 cards (those with 320 or 640MB of memory) because the latest application needs to use a feature that that hardware lacks.
At the moment we have no way to prevent clients with those GPUs from receiving work even though the application will immediately crash. Hopefully this will be fixed soon.
MJH |
|
|
|
Driver 177.84 and the new app don't work for me. 177.35 & 6.30 were running fine. I have: XP32, SP2, Boinc 6.3.10 and a 9800GTX+ (55 nm chip).
- set BOINC to "no network", stopped it, made a copy of the entire folder
- updated driver from 177.35 to 177.84
- restarted, launched BOINC
- it resumed the 6.30 tasks
- I aborted them manually
- a 6.41 task started and errored immediately, but with a standard windows message box instead of a BOINC-error; I don't know the equivalent message in english, should be something like "the operation read could not be performed on the memory (location xxxxxx), press abort to debug or OK to quit"
- I restored BOINC and watched the 6.30 tasks - they errored within one minute each, giving some messages in the BOINC manager:
25/08/2008 21:38:44|PS3GRID|Computation for task nC18076-GPUTEST2-2-10-acemd_3 finished
25/08/2008 21:38:44|PS3GRID|Output file nC18076-GPUTEST2-2-10-acemd_3_1 for task nC18076-GPUTEST2-2-10-acemd_3 absent
25/08/2008 21:38:44|PS3GRID|Output file nC18076-GPUTEST2-2-10-acemd_3_2 for task nC18076-GPUTEST2-2-10-acemd_3 absent
25/08/2008 21:38:44|PS3GRID|Output file nC18076-GPUTEST2-2-10-acemd_3_3 for task nC18076-GPUTEST2-2-10-acemd_3 absent
25/08/2008 21:38:44|PS3GRID|Restarting task MS15844-GPUTEST2-3-10-acemd_1 using acemd version 630
25/08/2008 21:38:45|PS3GRID|Computation for task MS15844-GPUTEST2-3-10-acemd_1 finished
25/08/2008 21:38:45|PS3GRID|Output file MS15844-GPUTEST2-3-10-acemd_1_0 for task MS15844-GPUTEST2-3-10-acemd_1 absent
25/08/2008 21:38:45|PS3GRID|Output file MS15844-GPUTEST2-3-10-acemd_1_1 for task MS15844-GPUTEST2-3-10-acemd_1 absent
25/08/2008 21:38:45|PS3GRID|Output file MS15844-GPUTEST2-3-10-acemd_1_2 for task MS15844-GPUTEST2-3-10-acemd_1 absent
25/08/2008 21:38:45|PS3GRID|Output file MS15844-GPUTEST2-3-10-acemd_1_3 for task MS15844-GPUTEST2-3-10-acemd_1 absent
25/08/2008 21:38:45|PS3GRID|Starting If19084-GPUTEST2-2-10-acemd_1
25/08/2008 21:38:45|PS3GRID|Starting task If19084-GPUTEST2-2-10-acemd_1 using acemd version 630
25/08/2008 21:38:46|PS3GRID|Started upload of nC18076-GPUTEST2-2-10-acemd_3_0
25/08/2008 21:38:49|PS3GRID|Finished upload of nC18076-GPUTEST2-2-10-acemd_3_0
25/08/2008 21:38:51||Suspending network activity - user request
25/08/2008 21:39:29|PS3GRID|Computation for task If19084-GPUTEST2-2-10-acemd_1 finished
25/08/2008 21:39:29|PS3GRID|Output file If19084-GPUTEST2-2-10-acemd_1_1 for task If19084-GPUTEST2-2-10-acemd_1 absent
25/08/2008 21:39:29|PS3GRID|Output file If19084-GPUTEST2-2-10-acemd_1_2 for task If19084-GPUTEST2-2-10-acemd_1 absent
25/08/2008 21:39:29|PS3GRID|Output file If19084-GPUTEST2-2-10-acemd_1_3 for task If19084-GPUTEST2-2-10-acemd_1 absent
25/08/2008 21:39:29|PS3GRID|Starting HG18769-GPUTEST2-5-10-acemd_3
25/08/2008 21:39:29|PS3GRID|Starting task HG18769-GPUTEST2-5-10-acemd_3 using acemd version 641
25/08/2008 21:39:44|PS3GRID|Computation for task HG18769-GPUTEST2-5-10-acemd_3 finished
25/08/2008 21:39:44|PS3GRID|Output file HG18769-GPUTEST2-5-10-acemd_3_0 for task HG18769-GPUTEST2-5-10-acemd_3 absent
25/08/2008 21:39:44|PS3GRID|Output file HG18769-GPUTEST2-5-10-acemd_3_1 for task HG18769-GPUTEST2-5-10-acemd_3 absent
25/08/2008 21:39:44|PS3GRID|Output file HG18769-GPUTEST2-5-10-acemd_3_2 for task HG18769-GPUTEST2-5-10-acemd_3 absent
25/08/2008 21:39:44|PS3GRID|Output file HG18769-GPUTEST2-5-10-acemd_3_3 for task HG18769-GPUTEST2-5-10-acemd_3 absent
(note that the last one is the 6.41, it errored with the same windows message box but I also caught this BOINC manager output)
- I restored BOINC, went back to 177.35 drivers and restarted
- the 6.41 app still crashed in the same way, but the 6.30 are fine again
- I restored again and have 40 hours of 6.30 goodness left ;)
Any ideas, suggestions, wishes?
MrS
____________
Scanning for our furry friends since Jan 2002 |
|
|
|
One of my other Team members was also having crashes with 6.41.
He detached from the project, and re-attached and now it works.
Mind you he did also go back to Boinc 6.3.8, so i dunno if it was changing Boinc versions or the detach re-attach that fixed it...
____________
Down with the Kredit Kops!!! |
|
|
|
Thanks, that's a good idea. Will give it a try, definitely when my 6.30 WUs are completed. Still debating with myself if I should do it earlier and risk running dry..
MrS
____________
Scanning for our furry friends since Jan 2002 |
|
|
|
Thanks, that's a good idea. Will give it a try, definitely when my 6.30 WUs are completed. Still debating with myself if I should do it earlier and risk running dry..
MrS
I done the driver update thing, detached from PS3GRID, and re-attached.
All is working fine (sofar) and using Boinc v6.3.10, since I have 2 8800GT's in this system :)
____________
Down with the Kredit Kops!!! |
|
|
|
Resetting the project helped! *doing some crazy happy dance*
It's running now with 177.35 and projected time is about 12h, down from previous 15h with 6.30.
MrS
____________
Scanning for our furry friends since Jan 2002 |
|
|
GDFVolunteer moderator Project administrator Project developer Project tester Volunteer developer Volunteer tester Project scientist Send message
Joined: 14 Mar 07 Posts: 1957 Credit: 629,356 RAC: 0 Level
Scientific publications
|
Resetting the project helped! *doing some crazy happy dance*
It's running now with 177.35 and projected time is about 12h, down from previous 15h with 6.30.
MrS
Everybody should reset the project when getting the new application for cuda2 for the FIRST time.
This is due to the fact that cudart.dll for 1.0 and for 2.0 are called in the same way, so your client probably thinks it has it already.
g |
|
|
kuarlSend message
Joined: 5 Mar 08 Posts: 5 Credit: 16,971,567 RAC: 0 Level
Scientific publications
|
not working for me.
boinc 6.3.10
application 6.41
windows vista 64 sp1
driver 177.84
gpu nvidia 8800gts 640mb with 92sp.
26/08/2008 15.00.45|PS3GRID|Starting LS29352-GPUTEST2-0-10-acemd_0
26/08/2008 15.00.46|PS3GRID|Starting task LS29352-GPUTEST2-0-10-acemd_0 using acemd version 641
26/08/2008 15.00.47|PS3GRID|Computation for task LS29352-GPUTEST2-0-10-acemd_0 finished
26/08/2008 15.00.47|PS3GRID|Output file LS29352-GPUTEST2-0-10-acemd_0_1 for task LS29352-GPUTEST2-0-10-acemd_0 absent
26/08/2008 15.00.47|PS3GRID|Output file LS29352-GPUTEST2-0-10-acemd_0_2 for task LS29352-GPUTEST2-0-10-acemd_0 absent
26/08/2008 15.00.47|PS3GRID|Output file LS29352-GPUTEST2-0-10-acemd_0_3 for task LS29352-GPUTEST2-0-10-acemd_0 absent
this is how boinc recognize my system:
26/08/2008 14.39.41||Processor: 4 GenuineIntel Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz [Intel64 Family 6 Model 15 Stepping 11]
26/08/2008 14.39.41||Processor features: fpu tsc pae nx sse sse2 pni
26/08/2008 14.39.41||OS: Microsoft Windows Vista: Ultimate x64 Editon, Service Pack 1, (06.00.6001.00)
26/08/2008 14.39.41||Memory: 2.00 GB physical, 4.23 GB virtual
26/08/2008 14.39.41||Disk: 244.14 GB total, 21.86 GB free
26/08/2008 14.39.41||Local time is UTC +2 hours
26/08/2008 14.39.41||Not using a proxy
26/08/2008 14.39.42||CUDA devices found
26/08/2008 14.39.42||Coprocessor: Device Emulation (CPU) (1)
26/08/2008 14.39.43||Version change (5.10.45 -> 6.3.10)
|
|
|
GDFVolunteer moderator Project administrator Project developer Project tester Volunteer developer Volunteer tester Project scientist Send message
Joined: 14 Mar 07 Posts: 1957 Credit: 629,356 RAC: 0 Level
Scientific publications
|
You should not get the message "Device Emulation", but the name of your graphics card. Have you installed the driver correctly from Nvidia CUDA website as indicated in the gpugrid home page?
best, gdf |
|
|
|
You should not get the message "Device Emulation", but the name of your graphics card. Have you installed the driver correctly from Nvidia CUDA website as indicated in the gpugrid home page?
best, gdf
I got also this message. I have a 8400GS and it crashes directly after downlod and start.
26.08.2008 10:58:57||CUDA devices found
26.08.2008 10:58:57||Coprocessor: Device Emulation (CPU) (1)
Wolfram
|
|
|
koschi Send message
Joined: 14 Aug 08 Posts: 124 Credit: 792,979,198 RAC: 11,592 Level
Scientific publications
|
Geforce 8800 GTS with 640MB is a G80 Chip, same with the 320MB Version. Only the 8800GTS with 512 and 1024MB are G92 Versions that support Cuda 1.1... |
|
|
TemujinSend message
Joined: 12 Jul 07 Posts: 100 Credit: 21,848,502 RAC: 0 Level
Scientific publications
|
Can someone clarify what makes a card cuda2 compatible please.
We all do this as a hobby/passion/obsession and it isn't cheap.
I would hate for someone to spend hard earned cash on a card that is immediately made obsolete by the introduction of cuda2.
Some 8800GT's are cuda2 compatible, some are not. Is it just the amount of memory?
The previous post mentions G80 & G92 architectures, is it that? If so, are all G92s ok?
Something along the lines of "if your card supports xyz you're ok for cuda2" and an indication of where we can find if our cards support xyz would be good.
Your project has certainly gained a lot of interest since you introduced GPU processing but these things cost money so anything that would help future proof users spending would be beneficial to both you and your users. |
|
|
kuarlSend message
Joined: 5 Mar 08 Posts: 5 Credit: 16,971,567 RAC: 0 Level
Scientific publications
|
You should not get the message "Device Emulation", but the name of your graphics card. Have you installed the driver correctly from Nvidia CUDA website as indicated in the gpugrid home page?
best, gdf
certainly. On foldin home, my gpu work without problems.
Cuda 1.0 vs cuda 2.0? compatible device? i think that you should make your software compatible with all cuda graphics card. If some operation can't be performed on gpu, then do it on cpu or whatever. It's unbelivable that nvidia creates these differences in its api...
|
|
|
GDFVolunteer moderator Project administrator Project developer Project tester Volunteer developer Volunteer tester Project scientist Send message
Joined: 14 Mar 07 Posts: 1957 Credit: 629,356 RAC: 0 Level
Scientific publications
|
The problem is simply that our code had two different ways of performing a part of the calculation. For running on old GPUs and on more recent one. However, when compiled with the cuda2.0 toolkit the old GPU code crashes, so we had to default to the simpler code based on more recent GPU devices.
This does NOT have to be a problem with the compiler, CUDA or anything. It could well be a problem with the old code.
Fact is that we can now only support devices with 1.1 compute capability. We are updating the scheduler to take this into account.
Geforce 8800GT 512, all 9000 and GT200 series will work on it for sure. Others might work too (for instance at least some 8600).
gdf |
|
|
|
Thanks for the information, GDF. So it seems very unfortunate and frustrating for users, but solving it would require you to put serious effort into finding the bug / cause of the error, with uncertain outcome.
And a side note: my first WU with 6.41 and 177.35 completed fine, now I'm running with 177.84. Seems to work but won't be faster.
MrS
____________
Scanning for our furry friends since Jan 2002 |
|
|
|
So far so good.
On WindowsXP with 8800GT-512MB
I got ready to install 6.3.10, made a backup, then realized I already had that installed. Told you my brain gets fried after a day of work. So Upgraded NVIDIA drivers to 177.84. Rebooted. After startup, Enabled work and reset project. I got a 6.41 and has been running about 30 minutes.
I'll update 2 work computers tomorrow with 6.3.10 and 177.84. They should have finished all current work by then. |
|
|
|
Is anyone else running 6.3.10 and crunching a CPU project as well as a CPU project? Have you encountered any GPU WU errors?
I swapped my rather temperamental 8800GT card to a P4 HT 3GHz running 32 bit Vista. Using drivers 177.79 and Ntune to force standard 600/900MHz clocks all seems very stable......until that is the parallel CPU WU for another project reports its' result. At the very second the CPU WU completes and starts upload, the GPU WU crashes with an error: Cuda error: Kernel [frc_sum_kernel_angle] failed in file 'force.cu' in line 487 : unknown error.
I've lost two WU on this box as a result of this behaviour, the first was after 13.5 hours crunch time (just 30 minutes from completion, the second after 5 hours.
I can't see any signs of instability on the clocks now, so I've suspended the CPU project while the GPU crunches away. Perhaps the P4 HT is not servicing the GPU in a timely manner when it is busy with the other WU from the CPU project?
____________
|
|
|
|
Running 3 instances of QMC fine along GPU-Grid on a Q6600 with XP32 SP2 and BOINC 6.3.10, 9 and 8, driver 177.35 and 177.84.
MrS
____________
Scanning for our furry friends since Jan 2002 |
|
|
|
I got also this message. I have a 8400GS and it crashes directly after downlod and start.
26.08.2008 10:58:57||CUDA devices found
26.08.2008 10:58:57||Coprocessor: Device Emulation (CPU) (1)
Same problem on the 8800GT of my team mate, what can we do to resolve this? |
|
|
|
Is anyone else running 6.3.10 and crunching a CPU project as well as a CPU project? Have you encountered any GPU WU errors?
I swapped my rather temperamental 8800GT card to a P4 HT 3GHz running 32 bit Vista. Using drivers 177.79 and Ntune to force standard 600/900MHz clocks all seems very stable......until that is the parallel CPU WU for another project reports its' result. At the very second the CPU WU completes and starts upload, the GPU WU crashes with an error: Cuda error: Kernel [frc_sum_kernel_angle] failed in file 'force.cu' in line 487 : unknown error.
I've lost two WU on this box as a result of this behaviour, the first was after 13.5 hours crunch time (just 30 minutes from completion, the second after 5 hours.
I can't see any signs of instability on the clocks now, so I've suspended the CPU project while the GPU crunches away. Perhaps the P4 HT is not servicing the GPU in a timely manner when it is busy with the other WU from the CPU project?
Try upgradeing to driver 177.84
I've only been running that driver only a few hours, but in previous testing on 3 P4-HT's under heavy use and running 1 each CPU + 1 GPU I've not had errors like that. But then again I do not run VISTA. |
|
|
|
It's a 8800GTS 320 Mo.
Why it's not longer running on GPUGrid ??
Regrettably we are no longer able to support the first generation of 8800 cards (those with 320 or 640MB of memory) because the latest application needs to use a feature that that hardware lacks.
MJH
If you desperately want to do science with your 8800GTS, join Folding @ Home by the Pande Group. Their science is very similar to the GPUGrid project and they do support first generation chips (G80 with compute capability 1.0)
|
|
|
|
I got also this message. I have a 8400GS and it crashes directly after downlod and start.
26.08.2008 10:58:57||CUDA devices found
26.08.2008 10:58:57||Coprocessor: Device Emulation (CPU) (1)
Same problem on the 8800GT of my team mate, what can we do to resolve this?
I tried it once more and got the error:
<core_client_version>6.3.10</core_client_version>
<![CDATA[
<message>
Unzul�ssige Funktion. (0x1) - exit code 1 (0x1)
</message>
<stderr_txt>
# Using CUDA device 0
Cuda error in file 'deviceQuery.cu' in line 59 : initialization error.
</stderr_txt>
]]>
I have vista 64 SP1, boinc 6.3.10, |PS3GRID|Starting task ldj8613-GPUTEST2-0-10-acemd_0 using acemd version 641, Nvidia-driver 177.92, 8400GS
Any idee what I can do?
Thx for every help
|
|
|
|
He is on vista64 SP1 with boinc 6.3.10 too, he uses 177.84 but I an too on vista64 SP1 + boinc 6.3.10 and 177.84 ... it works fine for me :/ I don't understand |
|
|
|
He is on vista64 SP1 with boinc 6.3.10 too, he uses 177.84 but I an too on vista64 SP1 + boinc 6.3.10 and 177.84 ... it works fine for me :/ I don't understand
That's odd...
I also use Vista64 (SP1), BOINC 6.3.10, and the 177.84 drivers, but have the same problem with the device emulation... (But on a GTX260) :(
AFAIK you are the only one with Vista 64 who does not get the device emulation message...
Come on - tell us what you did to make it work! ;-)
____________
pixelicious.at - my little photoblog |
|
|
|
AFAIK you are the only one with Vista 64 who does not get the device emulation message...
Ah :O , I didn't know that, I didn't do anything special, I installed the good driver with the good boinc, that's all :/
|
|
|
|
I got also this message. I have a 8400GS and it crashes directly after downlod and start.
26.08.2008 10:58:57||CUDA devices found
26.08.2008 10:58:57||Coprocessor: Device Emulation (CPU) (1)
Same problem on the 8800GT of my team mate, what can we do to resolve this?
I tried it once more and got the error:
<core_client_version>6.3.10</core_client_version>
<![CDATA[
<message>
Unzul�ssige Funktion. (0x1) - exit code 1 (0x1)
</message>
<stderr_txt>
# Using CUDA device 0
Cuda error in file 'deviceQuery.cu' in line 59 : initialization error.
</stderr_txt>
]]>
I have vista 64 SP1, boinc 6.3.10, |PS3GRID|Starting task ldj8613-GPUTEST2-0-10-acemd_0 using acemd version 641, Nvidia-driver 177.92, 8400GS
Any idee what I can do?
Thx for every help
Whre did you get 177.92 driver from ?
The only ones on the cuda download page are 177.84. Did you try 177.84. Most (not all) people here running 177.84 are working OK. |
|
|
|
177.92 is a beta driver which was released yesterday. You can get it from nvidia.com ...
I´ll give it a try if it works on my PC.
____________
pixelicious.at - my little photoblog |
|
|
|
Whre did you get 177.92 driver from ?
The only ones on the cuda download page are 177.84. Did you try 177.84. Most (not all) people here running 177.84 are working OK.
I got the 177.92 from the nvidia-forum. It is beta but with cuda-support. I tried the 177.84 befor and it crashes.
What can I do? |
|
|
|
I forgot:
Folding@home runs fine on my system.
|
|
|
GDFVolunteer moderator Project administrator Project developer Project tester Volunteer developer Volunteer tester Project scientist Send message
Joined: 14 Mar 07 Posts: 1957 Credit: 629,356 RAC: 0 Level
Scientific publications
|
From what I see all 177 drivers are fine once BOINC recognizes your device.
It should report the name of your card as coprocessor, not CPU emulation.
If F@H works then your drivers are probably installed well, so I don't know why it does not recognize it.
gdf |
|
|
|
Still no joy with 177.92 - BOINC still shows the device emulation...
Weird, but Folding runs fine with every driver since 177.35. :(
____________
pixelicious.at - my little photoblog |
|
|
|
177.92 is a beta driver which was released yesterday. You can get it from nvidia.com ...
I´ll give it a try if it works on my PC.
OK, I found the beta drivers.
I too will test, but it will be tomorrow. I want to run the current 177.84 I installed this morning for at least 1 task on each host, to see if they complete and how slow. I will then update one of my two twins first and see what happens, especially if there is a speed increase. |
|
|
|
The 177.92 drivers can be found here:
http://www.nvidia.com/object/winvista_x64_177.92_beta.html
I also keep getting the error on Vista 64 bit, and have Folding@Home running fine.
|
|
|
|
OK, I've got an error on 1 of 2 hosts, on the first attempt using 6.41 with 177.84 drivers on Windows XP. I do not know what happened, I think this was after I left work, although I did not check before I left if all was running fine.
<core_client_version>6.3.10</core_client_version>
<![CDATA[
<message>
Incorrect function. (0x1) - exit code 1 (0x1)
</message>
<stderr_txt>
# Using CUDA device 0
# Device 0: "GeForce 8800 GT"
# Clock rate: 1512000 kilohertz
MDIO ERROR: cannot open file "restart.coor"
Cuda error: Kernel [frc_sum_kernel_dihed] failed in file 'force.cu' in line 516 : unspecified launch failure.
</stderr_txt>
]]>
I can not tell from home at the moment if they are still running OK.
But my home computer with Windows XP did complete its first 6.41 under 177.84 driver, its still in ready to report state, but it was 100% finished at 15:31:57 cpu time. The 2nd one has been running for 5.5 hours so far. |
|
|
|
The 177.92 drivers can be found here:
http://www.nvidia.com/object/winvista_x64_177.92_beta.html
I also keep getting the error on Vista 64 bit, and have Folding@Home running fine.
I've had this error on a P4 HT box. It seems more stable by reducing the clocks on teh card and preventing another CPU project from running at the same time.
____________
|
|
|
|
It is NOW available.
Tested on Windows XP SP2, driver 177.84, 8600GT
gdf
THANX finally on: 177.84 8800GTS512 6.3.10 6.41 Succes!
but:
time: 50775.02 OMG
and:
"
<core_client_version>6.3.10</core_client_version>
<![CDATA[
<stderr_txt>
# Using CUDA device 0
# Device 0: "GeForce 8800 GTS 512"
# Clock rate: 1620000 kilohertz
MDIO ERROR: cannot open file "restart.coor"
# Using CUDA device 0
# Device 0: "GeForce 8800 GTS 512"
# Clock rate: 1620000 kilohertz
# Using CUDA device 0
# Device 0: "GeForce 8800 GTS 512"
# Clock rate: 1620000 kilohertz
called boinc_finish
</stderr_txt>
]]>
"
hmmm.... MDIO ERROR: cannot open file "restart.coor" ?
and when my Computer crunch ps3grid on CUDA all works slowly than when it crunch for e.g. rosetta@home on all 4 cores..... especialy GUI XP, and it is noticeable drop on fps during 3D....
http://www.ps3grid.net/result.php?resultid=47604
It is My first WU :) |
|
|
koschi Send message
Joined: 14 Aug 08 Posts: 124 Credit: 792,979,198 RAC: 11,592 Level
Scientific publications
|
http://www.ps3grid.net/forum_thread.php?id=281
You are not the only one, me and others are having the same problem :-/
For now I put the card that crunches the project to some other pc. Using the computer was really no fun while PS3GRID was running.
Once the problem is solved (assuming that it will be handled in future releases) I'm ready to buy one more card for my normal workstation. |
|
|
GDFVolunteer moderator Project administrator Project developer Project tester Volunteer developer Volunteer tester Project scientist Send message
Joined: 14 Mar 07 Posts: 1957 Credit: 629,356 RAC: 0 Level
Scientific publications
|
It is NOW available.
Tested on Windows XP SP2, driver 177.84, 8600GT
gdf
THANX finally on: 177.84 8800GTS512 6.3.10 6.41 Succes!
but:
time: 50775.02 OMG
and:
"
<core_client_version>6.3.10</core_client_version>
<![CDATA[
<stderr_txt>
# Using CUDA device 0
# Device 0: "GeForce 8800 GTS 512"
# Clock rate: 1620000 kilohertz
MDIO ERROR: cannot open file "restart.coor"
# Using CUDA device 0
# Device 0: "GeForce 8800 GTS 512"
# Clock rate: 1620000 kilohertz
# Using CUDA device 0
# Device 0: "GeForce 8800 GTS 512"
# Clock rate: 1620000 kilohertz
called boinc_finish
</stderr_txt>
]]>
"
hmmm.... MDIO ERROR: cannot open file "restart.coor" ?
and when my Computer crunch ps3grid on CUDA all works slowly than when it crunch for e.g. rosetta@home on all 4 cores..... especialy GUI XP, and it is noticeable drop on fps during 3D....
http://www.ps3grid.net/result.php?resultid=47604
It is My first WU :)
This is all correct and expected.
gdf |
|
|