Author |
Message |
|
There is new driver.
I'll test them. Because 185.66 or 185.66 make always errors.
I hope it's good driver with this project. |
|
|
zpm Send message
Joined: 2 Mar 09 Posts: 159 Credit: 13,639,818 RAC: 0 Level
Scientific publications
|
it seem to work fine on my sys. with gtx 260. |
|
|
|
I test, and I have again the same errors, like 185.66, 185.68.
08/05/2009 19:27:31 GPUGRID Starting task 21-KASHIF_HIVPR_dim_ba2-4-100-RND7086_0 using acemd version 664
08/05/2009 19:28:04 GPUGRID Computation for task 21-KASHIF_HIVPR_dim_ba2-4-100-RND7086_0 finished
08/05/2009 19:28:04 GPUGRID Output file 21-KASHIF_HIVPR_dim_ba2-4-100-RND7086_0_1 for task 21-KASHIF_HIVPR_dim_ba2-4-100-RND7086_0 absent
08/05/2009 19:28:04 GPUGRID Output file 21-KASHIF_HIVPR_dim_ba2-4-100-RND7086_0_2 for task 21-KASHIF_HIVPR_dim_ba2-4-100-RND7086_0 absent
08/05/2009 19:28:04 GPUGRID Output file 21-KASHIF_HIVPR_dim_ba2-4-100-RND7086_0_3 for task 21-KASHIF_HIVPR_dim_ba2-4-100-RND7086_0 absent
08/05/2009 19:28:08 GPUGRID Finished upload of 21-KASHIF_HIVPR_dim_ba2-4-100-RND7086_0_4
<core_client_version>6.6.20</core_client_version>
<![CDATA[
<message>
- exit code 98 (0x62)
</message>
<stderr_txt>
# Using CUDA device 0
# Device 0: "GeForce GTX 260"
# Clock rate: 1404000 kilohertz
# Total amount of global memory: 939524096 bytes
# Number of multiprocessors: 27
# Number of cores: 216
# Device 1: "GeForce 8800 GT"
# Clock rate: 1500000 kilohertz
# Total amount of global memory: 536870912 bytes
# Number of multiprocessors: 14
# Number of cores: 112
# Amber: readparm : Reading parm file parameters
# PARM file in AMBER 7 format
# Encounter 10-12 H-bond term
WARNING: parameters.cu, line 568: Found zero 10-12 H-bond term.
WARNING: parameters.cu, line 568: Found zero 10-12 H-bond term.
MDIO ERROR: cannot open file "restart.coor"
ERROR: c:\cygwin\home\speechserver\gpumd2\src\pme\CPME_cufft.cu, line 104: cufftExecC2R (gridcalc3)
called boinc_finish
</stderr_txt>
I use boinc 6.6.20 on vista 64, and I have 1 GTX260 and one 8800GT.
It works good with ancient driver official 182.50. |
|
|
naja002 Send message
Joined: 25 Sep 08 Posts: 111 Credit: 10,352,599 RAC: 0 Level
Scientific publications
|
Rivatuner cannot detect the 185.85 driver for some people--others it does..go figure. I've lost RT in the 1 rig running 185.85. I've DLed Nvidia System Tools....looks simple enough....can't get the damn thing to work though....:(
EDIT: Seem to have it going atm....pretty whacked, but what else can be expected from Nvidia these days...sheesh.
EDIT 2: Switched to Precision tool...a bit more intuitive... |
|
|
|
I have been using Precision for a while, pretty easy although if you set the fan on auto *sometimes* it forgets and temps start to rise. I have not narrowed it down to exactly when, and there certainly is the possibility that it was me that screwed up and not the tool :am:
____________
Thanks - Steve |
|
|
|
Works good on Win. XP64 with Boinc 6.6.20 with gtx260 and gt9800. |
|
|
naja002 Send message
Joined: 25 Sep 08 Posts: 111 Credit: 10,352,599 RAC: 0 Level
Scientific publications
|
I have been using Precision for a while, pretty easy although if you set the fan on auto *sometimes* it forgets and temps start to rise. I have not narrowed it down to exactly when, and there certainly is the possibility that it was me that screwed up and not the tool :am:
I'm WCed, but it's always good to know when something doesn't work 100% the way it should.....;) One thing that I like about Precision tool is that it will OC all Gpus on startup--that doesn't work with RT....
Works good on Win. XP64 with Boinc 6.6.20 with gtx260 and gt9800.
Vista 64 here...6.6.28, 2x 8800GS |
|
|
jrobbioSend message
Joined: 13 Mar 09 Posts: 59 Credit: 324,366 RAC: 0 Level
Scientific publications
|
I've just finished my first WU on Windows XP Home with 185.85 WHQL and Boinc 6.6.28 with a GTS250 here (and the most recent beta 185.81 here) and my timestep has dramatically reduced to 47.36ms (42.65ms for the latest beta 185.81), which is the lowest I have ever had.
I'll have to see some other results in the next coming days, but I had been averaging about 65-70ms before on most WU's.
Anyone else seen such improvements?
Rob |
|
|
|
185.85, Vista 64, BOINC 6.6.28, GTX295
18 hours GPUGrid, GPUZ, EVGA Precision, no errors.
____________
Thanks - Steve |
|
|
uBronan Send message
Joined: 1 Feb 09 Posts: 139 Credit: 575,023 RAC: 0 Level
Scientific publications
|
The problems with the units only involve the cards not being a 2XX.
So if your card is based on 9xxx or similar it will probably error out on these famous units.
Seems all 2X5 cards run these units without issues on many different drivers, and in fact the newest drivers will give them some performance gains.
The reason why this units fails seems to be a mistery since some do finish but most will crash on our cards.
I also use this 185.85 driver for some time now and seems darn stable, so for me looks like a winner untill now. |
|
|
naja002 Send message
Joined: 25 Sep 08 Posts: 111 Credit: 10,352,599 RAC: 0 Level
Scientific publications
|
I've just finished my first WU on Windows XP Home with 185.85 WHQL and Boinc 6.6.28 with a GTS250 here (and the most recent beta 185.81 here) and my timestep has dramatically reduced to 47.36ms (42.65ms for the latest beta 185.81), which is the lowest I have ever had.
I'll have to see some other results in the next coming days, but I had been averaging about 65-70ms before on most WU's.
Anyone else seen such improvements?
Rob
The 185.xx drivers offer enhanced crunching/folding performance, but I wasn't aware that there maybe a bit of an increase with these 185.85 drivers. Lately I've been busy with the crashing/hanging WUs, so I haven't had the opportunity to check much else out.
On my i7 rig the 185.xx have been a nightmare. This 185.85 driver runs and the only issue that I am having is it always resets the display to 12??x??? instead of the 1024x768 that I use (still on a 19" LCD here). Still an improvement in performance over the pre-185.xx drivers. I'm just hoping something shows up soon that will run 100% on this rig. My other rigs (775) don't have any issues with 185.xx drivers.... |
|
|
naja002 Send message
Joined: 25 Sep 08 Posts: 111 Credit: 10,352,599 RAC: 0 Level
Scientific publications
|
The problems with the units only involve the cards not being a 2XX.
So if your card is based on 9xxx or similar it will probably error out on these famous units.
Seems all 2X5 cards run these units without issues on many different drivers, and in fact the newest drivers will give them some performance gains.
The reason why this units fails seems to be a mistery since some do finish but most will crash on our cards.
I also use this 185.85 driver for some time now and seems darn stable, so for me looks like a winner untill now.
It's not these drivers that are causing the crashing that you are refering to....
It may be the WUs or the insufficient memory of the lower end cards....they don't know, but those WUs are crashing regardless of which driver is used.... |
|
|
|
.. and my timestep has dramatically reduced to 47.36ms (42.65ms for the latest beta 185.81), which is the lowest I have ever had.
I'll have to see some other results in the next coming days, but I had been averaging about 65-70ms before on most WU's.
WUs with different names and different credits likely feature different complexity (i.e. number of atoms) and differ in the time per step. A bit less than 50 ms used to be pretty normal for my 9800GTX+ last autumn. Now most WUs take longer, but not all of them.
MrS
____________
Scanning for our furry friends since Jan 2002 |
|
|
|
Always errors for me...
http://www.gpugrid.net/results.php?userid=8645 |
|
|
|
I only have a few lags on my Hauppauge TV card, picture and sound stopped for 2sec after that running in slow motion, not seen this on 182.50. |
|
|
Beyond Send message
Joined: 23 Nov 08 Posts: 1112 Credit: 6,162,416,256 RAC: 0 Level
Scientific publications
|
Anyone else seeing a 2-3% slowdown on v185.85 compared with v185.66?
This is happening on both my ASUS and PNY 9600 GSO cards. |
|
|
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
|
There seems to be a driver issue with old cards and new cuda 2.2 drivers. Maybe an incompatibility with the 2.1 toolkit.
If you have an old card, stay away from new drivers for a little while.
This is unrelated to the problem with KASHIF workunits. The driver problem happens with all workunits.
gdf |
|
|
|
Thanks for the information, this may very well explain some of the recently unusually high failure rates.
So which is the last known good one, 182.50?
MrS
____________
Scanning for our furry friends since Jan 2002 |
|
|
Beyond Send message
Joined: 23 Nov 08 Posts: 1112 Credit: 6,162,416,256 RAC: 0 Level
Scientific publications
|
Thanks for the information, this may very well explain some of the recently unusually high failure rates.
So which is the last known good one, 182.50?
MrS
See this recent post:
http://www.gpugrid.net/forum_thread.php?id=1034&nowrap=true#9655
Failed WUs and he is indeed using driver v182.50...
|
|
|
|
You're right, that seems like the error. So we'd have to search for an older driver (too bad NV does not just say which CUDA version they support.. or, not that I could find it easily) or just wait it out. Since the project team removed the questionable WUs I didn't get any further errors. But then I only run 2 a day, hardly representative.
MrS
____________
Scanning for our furry friends since Jan 2002 |
|
|
uBronan Send message
Joined: 1 Feb 09 Posts: 139 Credit: 575,023 RAC: 0 Level
Scientific publications
|
Well i have received a test unit so we gonna see if the driver is the issue.
I had rebooted and was to be honest not expecting to see gpugrid downloaded new units, but since it did i thought ill let it finish and see what happens.
Those 2 i got both with ended without issue
Lets see if this test errors out.
Still want to remind you guys that, according to boinc my card seems only to be able todo 1.0 Cuda, what strikes me is why nvidia does not inform which cards benefit from this new cuda 2.X versions or is it again boinc which does not see the right cuda version. |
|
|
MarkJ Volunteer moderator Volunteer tester Send message
Joined: 24 Dec 08 Posts: 738 Credit: 200,909,904 RAC: 0 Level
Scientific publications
|
Well i have received a test unit so we gonna see if the driver is the issue.
I had rebooted and was to be honest not expecting to see gpugrid downloaded new units, but since it did i thought ill let it finish and see what happens.
Those 2 i got both with ended without issue
Lets see if this test errors out.
Still want to remind you guys that, according to boinc my card seems only to be able todo 1.0 Cuda, what strikes me is why nvidia does not inform which cards benefit from this new cuda 2.X versions or is it again boinc which does not see the right cuda version.
The version reported by BOINC is the compute capability of the card, not the cuda version. They have reworded it from 6.6.24 onwards. What sort of card is it?
____________
BOINC blog |
|
|
uBronan Send message
Joined: 1 Feb 09 Posts: 139 Credit: 575,023 RAC: 0 Level
Scientific publications
|
9600 GT haven't found info anywhere what version of cuda is supported by it. |
|
|
|
Hardware capabilities should be, right out of my head:
G80 - 1.0
>G80 & <G200 - 1.1
G200 - 1.3
MrS
____________
Scanning for our furry friends since Jan 2002 |
|
|
uBronan Send message
Joined: 1 Feb 09 Posts: 139 Credit: 575,023 RAC: 0 Level
Scientific publications
|
Yea i forgot indeed is 1.1
Sadly many hours lost again with broken units, rebooted back into win XP
I reinstalled old driver set 182.50 and reversed back to cuda 2.1 with 6.6.28
if i probably change back to 6.5.0 but ill try this a few days more because its time estimates really are ok.
Now back to sleep ill see tommorow if the units still fail |
|
|
MarkJ Volunteer moderator Volunteer tester Send message
Joined: 24 Dec 08 Posts: 738 Credit: 200,909,904 RAC: 0 Level
Scientific publications
|
You might want to go into the Nvida control panel -> Help -> System information and just check what version it thinks it is. Apparently when I upgraded, while it went through the motions and rebooted it still thought it had the old drivers.
To do the upgrade properly I had to uninstall the old drivers and then install new ones before it came up as 185.85 drivers.
____________
BOINC blog |
|
|
|
Whell, I was using 182.08 and it works grat.
I have 6.6.20 and I upgrade to 6.6.28.
You say that 185.85 works on GTX26x and up, so I try and:
<core_client_version>6.6.28</core_client_version>
<![CDATA[
<message>
- exit code 98 (0x62)
</message>
<stderr_txt>
# Using CUDA device 0
# Device 0: "GeForce GTX 260"
# Clock rate: 1242000 kilohertz
# Total amount of global memory: 939196416 bytes
# Number of multiprocessors: 24
# Number of cores: 192
MDIO ERROR: cannot open file "restart.coor"
ERROR: c:\cygwin\home\speechserver\gpumd2\src\pme\CPME_cufft.cu, line 104: cufftExecC2R (gridcalc3)
called boinc_finish
</stderr_txt>
]]>
next:
<core_client_version>6.6.28</core_client_version>
<![CDATA[
<message>
- exit code 98 (0x62)
</message>
<stderr_txt>
# Using CUDA device 0
# Device 0: "GeForce GTX 260"
# Clock rate: 1242000 kilohertz
# Total amount of global memory: 939196416 bytes
# Number of multiprocessors: 24
# Number of cores: 192
# Amber: readparm : Reading parm file parameters
# PARM file in AMBER 7 format
# Encounter 10-12 H-bond term
WARNING: parameters.cu, line 568: Found zero 10-12 H-bond term.
WARNING: parameters.cu, line 568: Found zero 10-12 H-bond term.
MDIO ERROR: cannot open file "restart.coor"
ERROR: c:\cygwin\home\speechserver\gpumd2\src\pme\CPME_cufft.cu, line 50: cufftExecC2C (gridcalc2.1)
called boinc_finish
</stderr_txt>
]]>
next:
<core_client_version>6.6.28</core_client_version>
<![CDATA[
<message>
Niepoprawna funkcja. (0x1) - exit code 1 (0x1)
</message>
<stderr_txt>
# Using CUDA device 0
# Device 0: "GeForce GTX 260"
# Clock rate: 1242000 kilohertz
# Total amount of global memory: 939196416 bytes
# Number of multiprocessors: 24
# Number of cores: 192
MDIO ERROR: cannot open file "restart.coor"
# Using CUDA device 0
# Device 0: "GeForce GTX 260"
# Clock rate: 1242000 kilohertz
# Total amount of global memory: 939196416 bytes
# Number of multiprocessors: 24
# Number of cores: 192
MDIO ERROR: cannot open file "restart.coor"
Cuda error: Kernel [langevin_thermostat] failed in file 'thermostat.cu' in line 34 : unspecified launch failure.
</stderr_txt>
]]>
<core_client_version>6.6.28</core_client_version>
<![CDATA[
<message>
- exit code 98 (0x62)
</message>
<stderr_txt>
# Using CUDA device 0
# Device 0: "GeForce GTX 260"
# Clock rate: 1242000 kilohertz
# Total amount of global memory: 939196416 bytes
# Number of multiprocessors: 24
# Number of cores: 192
MDIO ERROR: cannot open file "restart.coor"
# Using CUDA device 0
# Device 0: "GeForce GTX 260"
# Clock rate: 1242000 kilohertz
# Total amount of global memory: 939196416 bytes
# Number of multiprocessors: 24
# Number of cores: 192
# Using CUDA device 0
# Device 0: "GeForce GTX 260"
# Clock rate: 1404000 kilohertz
# Total amount of global memory: 939196416 bytes
# Number of multiprocessors: 24
# Number of cores: 192
# Using CUDA device 0
# Device 0: "GeForce GTX 260"
# Clock rate: 1404000 kilohertz
# Total amount of global memory: 939196416 bytes
# Number of multiprocessors: 24
# Number of cores: 192
# Using CUDA device 0
# Device 0: "GeForce GTX 260"
# Clock rate: 1242000 kilohertz
# Total amount of global memory: 939196416 bytes
# Number of multiprocessors: 24
# Number of cores: 192
# Using CUDA device 0
# Device 0: "GeForce GTX 260"
# Clock rate: 1242000 kilohertz
# Total amount of global memory: 939196416 bytes
# Number of multiprocessors: 24
# Number of cores: 192
ERROR: c:\cygwin\home\speechserver\gpumd2\src\pme\CPME_cufft.cu, line 104: cufftExecC2R (gridcalc3)
called boinc_finish
</stderr_txt>
]]>
So I will try now 182.50 - like testing :) If it also fails I will go back to 182.08...
____________
POLISH NATIONAL TEAM - Join! Crunch! Win! |
|
|
|
I come back with new problems :
Remember my host : 8400 + 1 GTX 260 + 1 8800 GT on vista 64.
It work good with boinc 6.6.2 and Nvidia 182.5.
I upgrade boinc to 6.6.28
First i have :
22/05/2009 01:17:16 Starting BOINC client version 6.6.28 for windows_x86_64
22/05/2009 01:17:16 Processor: 2 GenuineIntel Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz [Intel64 Family 6 Model 23 Stepping 6]
22/05/2009 01:17:16 OS: Microsoft Windows Vista: Home Premium x64 Edition, Service Pack 1, (06.00.6001.00)
22/05/2009 01:17:16 Memory: 4.00 GB physical, 8.17 GB virtual
22/05/2009 01:17:16 CUDA device: GeForce 8800 GT (driver version 18585, compute capability 1.1, 512MB, est. 60GFLOPS)
22/05/2009 01:17:16 CUDA device (not used): GeForce 8800 GT (driver version 18585, compute capability 1.1, 512MB, est. 60GFLOPS)
22/05/2009 01:17:16 Not using a proxy
The GTX260 don't appear (and only one thread run)
and all my wus go in errors like
22/05/2009 09:42:02 GPUGRID Computation for task p1270000-IBUCH_pYIpYVk1_2105-0-10-RND0895_1 finished
22/05/2009 09:42:02 GPUGRID Output file p1270000-IBUCH_pYIpYVk1_2105-0-10-RND0895_1_1 for task p1270000-IBUCH_pYIpYVk1_2105-0-10-RND0895_1 absent
22/05/2009 09:42:02 GPUGRID Output file p1270000-IBUCH_pYIpYVk1_2105-0-10-RND0895_1_2 for task p1270000-IBUCH_pYIpYVk1_2105-0-10-RND0895_1 absent
22/05/2009 09:42:02 GPUGRID Output file p1270000-IBUCH_pYIpYVk1_2105-0-10-RND0895_1_3 for task p1270000-IBUCH_pYIpYVk1_2105-0-10-RND0895_1 absent
Then I upgrade driver Nvidia to 185.85, and I have still the pb. |
|
|
|
- you used 6.6.20, not 6.6.2 ;)
- the messages you quote say nothing, you have to look into the individual task outputs (e.g. here) .. but currently this probably won't tell you much more
- regarding the cards being used: in the newer clients you have to add an option in the cc_config if you want all GPUs being used.. sorry, don't know the exact details
- one of your WUs finished with 6.6.28, but I don't know why you suddenly get so many errors. The WUs run on GTX 260 and 8800GT, despite of the 260 missing in the messages.
MrS
____________
Scanning for our furry friends since Jan 2002 |
|
|
|
- regarding the cards being used: in the newer clients you have to add an option in the cc_config if you want all GPUs being used.. sorry, don't know the exact details
MrS
That would be
<cc_config>
<options>
<use_all_gpus>1</use_all_gpus>
</options>
</cc_config>
____________
pixelicious.at - my little photoblog |
|
|
|
Thanks, but i don't find a cc_config. :/
I notice an another bug :
I work for an other project (µfluid) and Gpugrid stay in waiting.
So with boinc 6.6.20, the 2 projects work in same time.
2 threads for µfluid, and 2 threads for GPUgridµ. |
|
|
|
You have to create it yourself...just text, but save it as...
cc_config.xml
It goes in the Boinc folder....
____________
Consciousness: That annoying time between naps......
Experience is a wonderful thing: it enables you to recognize a mistake every time you repeat it. |
|
|
|
You have to create it yourself...just text, but save it as...
cc_config.xml
It goes in the Boinc folder....
Yes it does ... |
|
|
|
and Gpugrid stay in waiting.
What's the exact message why it is waiting?
MrS
____________
Scanning for our furry friends since Jan 2002 |
|
|
|
Look :
with boinc 6.6.20, the four wus run in same time. |
|
|
|
I find the solution :
in advanced option : Use GPU while computer in use.
But i run with 182.5. With 185.85 I still have errors. |
|
|
|
In the sticky thread regarding this "problem" paul says that from 6.6.20 up you have to manually switch this settign (if you want you GPU to run when you work).. so I assumed you already knew about this, since you've been using 6.6.20. Was the change introduced later on?
MrS
____________
Scanning for our furry friends since Jan 2002 |
|
|
|
In the sticky thread regarding this "problem" paul says that from 6.6.20 up you have to manually switch this settign (if you want you GPU to run when you work).. so I assumed you already knew about this, since you've been using 6.6.20. Was the change introduced later on?
MrS
In 6.6.20 I don't see this message. |
|
|
|
Yes, but did you have to set the preference manually? Is it there at all? (sorry, I'd take a look myself if I'd use 6.6.20)
MrS
____________
Scanning for our furry friends since Jan 2002 |
|
|
|
on this version their are 2 really nasty bugs
once affect display settiing and another wont let you access the control for nivida |
|
|
|
|
|
|
|
Sorry that I have to ask again: is this 6.6.20 or 6.6.28? I know it should look like this in 6.6.28, but I thought it would also have to look like this in 6.6.20. And in this case you would have had to switch the "use GPU while computer is in use" before and forgot about it when you upgraded.
MrS
____________
Scanning for our furry friends since Jan 2002 |
|
|
|
It's boinc 6.6.28. |
|
|
|
I've updated to the new 185.85 WHPQL driver and my GTX 260 works fine.
Does someone have an idea of the size of the performance improvement over the elder 182.x driver? (mine is running 2 degrees hotter now, so I suggest it is performing a lot more work)
____________
|
|
|
|
I'd say a few percent.
MrS
____________
Scanning for our furry friends since Jan 2002 |
|
|
MarkJ Volunteer moderator Volunteer tester Send message
Joined: 24 Dec 08 Posts: 738 Credit: 200,909,904 RAC: 0 Level
Scientific publications
|
Sorry that I have to ask again: is this 6.6.20 or 6.6.28? I know it should look like this in 6.6.28, but I thought it would also have to look like this in 6.6.20. And in this case you would have had to switch the "use GPU while computer is in use" before and forgot about it when you upgraded.
MrS
Actually 6.6.20 had it as well. The difference was it defaulted to being ticked up to and including 20. From 6.6.21 it defaulted to blank.
____________
BOINC blog |
|
|
|
Actually 6.6.20 had it as well. The difference was it defaulted to being ticked up to and including 20. From 6.6.21 it defaulted to blank.
Ah thanks, that exactly what I wanted to hear. So instead of
Note that for 6.6.20 and up, GPU users have the toggle "use gpu while computer is in use", disabled by default in 6.6.2.0 and up
the text in the sticky should read
Note that for 6.6.21 and up, GPU users have the toggle "use gpu while computer is in use", disabled by default in 6.6.21 and up
EDIT: ah, that's actually just what you said in the 3rd post in that thread..
MrS
____________
Scanning for our furry friends since Jan 2002 |
|
|
|
i hav nvidia 158.85...how can i upgrade it to 185.85?? |
|
|
|
... how can i upgrade ...
You start simply a downloaded driver package, opt in the right product and operating system:
http://www.nvidia.com/Download/index.aspx?lang=en-us
If you have problems with the newest WHQL-driver, download an older package and try it again.
Did you check whether your NVIDIA card is listed in the FAQs ?
Overview of cards that run the GPUGRID application
|
|
|
|
I test, and I have again the same errors, like 185.66, 185.68.
08/05/2009 19:27:31 GPUGRID Starting task 21-KASHIF_HIVPR_dim_ba2-4-100-RND7086_0 using acemd version 664
08/05/2009 19:28:04 GPUGRID Computation for task 21-KASHIF_HIVPR_dim_ba2-4-100-RND7086_0 finished
08/05/2009 19:28:04 GPUGRID Output file 21-KASHIF_HIVPR_dim_ba2-4-100-RND7086_0_1 for task 21-KASHIF_HIVPR_dim_ba2-4-100-RND7086_0 absent
08/05/2009 19:28:04 GPUGRID Output file 21-KASHIF_HIVPR_dim_ba2-4-100-RND7086_0_2 for task 21-KASHIF_HIVPR_dim_ba2-4-100-RND7086_0 absent
08/05/2009 19:28:04 GPUGRID Output file 21-KASHIF_HIVPR_dim_ba2-4-100-RND7086_0_3 for task 21-KASHIF_HIVPR_dim_ba2-4-100-RND7086_0 absent
08/05/2009 19:28:08 GPUGRID Finished upload of 21-KASHIF_HIVPR_dim_ba2-4-100-RND7086_0_4
<core_client_version>6.6.20</core_client_version>
<![CDATA[
<message>
- exit code 98 (0x62)
</message>
<stderr_txt>
# Using CUDA device 0
# Device 0: "GeForce GTX 260"
# Clock rate: 1404000 kilohertz
# Total amount of global memory: 939524096 bytes
# Number of multiprocessors: 27
# Number of cores: 216
# Device 1: "GeForce 8800 GT"
# Clock rate: 1500000 kilohertz
# Total amount of global memory: 536870912 bytes
# Number of multiprocessors: 14
# Number of cores: 112
# Amber: readparm : Reading parm file parameters
# PARM file in AMBER 7 format
# Encounter 10-12 H-bond term
WARNING: parameters.cu, line 568: Found zero 10-12 H-bond term.
WARNING: parameters.cu, line 568: Found zero 10-12 H-bond term.
MDIO ERROR: cannot open file "restart.coor"
ERROR: c:\cygwin\home\speechserver\gpumd2\src\pme\CPME_cufft.cu, line 104: cufftExecC2R (gridcalc3)
called boinc_finish
</stderr_txt>
I use boinc 6.6.20 on vista 64, and I have 1 GTX260 and one 8800GT.
It works good with ancient driver official 182.50.
Same problem with 186.18. :/ |
|
|