I checked both the Box's I mentioned in the other Thread and they both were running at 1/2 speed which I know from past experience leads to continual errors until fixed.

I Uninstalled the Drivers on both Box's and reinstalled them, after rebooting both Box's were running @ full speed. They may not stay running like that though because I have 1 Card now (GTX 260) being RMA'ed for the same reason. Apparently there is a fix or work around for that problem and if the 2 Box's continue to drop back to half speed I'll have to try it rather than have to try & RMA 2 more Cards.

All 4 Cards in the 2 Box's are GTX 260's FYI ... All the Wu's on both Box's got Trashed too doing the Reinstalling of the Drivers even though I suspend GPUGrid & the Wu's, Didn't matter, they were gone after BOINC Started back up & had to download fresh ones.

Poorboy, read my post. " Link to prevent Nvidia 200 Downclocking" I believe that could be the problem. The 200 goes into power saving mode by design.

Poorboy, read my post. " Link to prevent Nvidia 200 Downclocking" I believe that could be the problem. The 200 goes into power saving mode by design. I thought my 1st 200 series card was bad also, but it was not. 3d performance mode has to be forced via. software, Riva Tuner is what I use.
I have been trying to get the word out as a LOT of people have been posting Boinc wide, thinking their cards are bad.
Maybe this is not your problem but it sounds just like my experience.

I checked both the Box's I mentioned in the other Thread and they both were running at 1/2 speed which I know from past experience leads to continual errors until fixed.

I Uninstalled the Drivers on both Box's and reinstalled them, after rebooting both Box's were running @ full speed. They may not stay running like that though because I have 1 Card now (GTX 260) being RMA'ed for the same reason. Apparently there is a fix or work around for that problem and if the 2 Box's continue to drop back to half speed I'll have to try it rather than have to try & RMA 2 more Cards.

All 4 Cards in the 2 Box's are GTX 260's FYI ... All the Wu's on both Box's got Trashed too doing the Reinstalling of the Drivers even though I suspend GPUGrid & the Wu's, Didn't matter, they were gone after BOINC Started back up & had to download fresh ones.

Joining this tread:
wuid=653971
I think i's a server problem?


On one of my xp32 with 260:

<core_client_version>6.4.7</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: 27
# Number of cores: 216
# 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>
]]>

and

CPU time 280.4531
stderr out
<core_client_version>6.4.7</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: 27
# Number of cores: 216
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>
]]>
____________
"Silakka"
Hello from Turku > Åbo.

Poorboy, read my post. " Link to prevent Nvidia 200 Downclocking" I believe that could be the problem. The 200 goes into power saving mode by design.

hostid=35303


Try to install drivers again, It seems ok now, with my trouble host and
all others 4 gpu computers are working fine with 190.38. It seems like over gigs of drivers can go wrong some time?
____________
"Silakka"
Hello from Turku > Åbo.

hostid=35303


Try to install drivers again, It seems ok now, with my trouble host and
all others 4 gpu computers are working fine with 190.38. It seems like over gigs of drivers can go wrong some time?

I've installed 190.38 on 2 dual gpu rigs.

The Q6600--no problems.

The i7 920 was nothing but problems. I upgraded to 6.6.37 and that seemed to fix the issue. I reinstalled the driver. I've switched back to RT, forced the driver and forced 3D performance. It has been running for a couple of days now error free.

6.6.37

Force Driver in RT--Post #9

Force 3D Performance

I've switched back to RT, forced the driver and forced 3D performance. It has been running for a couple of days now error free.

6.6.37

Force Driver in RT--Post #9

Force 3D Performance

hostid=35303


Try to install drivers again, It seems ok now, with my trouble host and
all others 4 gpu computers are working fine with 190.38. It seems like over gigs of drivers can go wrong some time?

Already tried that and within a few hours both Box's had Trashed 4 more Wu's each.

hostid=35303

Almost 10 years ago I started with seti, with a Pentium MMX 166 MHz, and It seems like my boinc career will end with seti, this 260 won't work with gpugrid anymore after update to 190.38.

"not yet format the hard drive, anything else is done"
____________
"Silakka"
Hello from Turku > Åbo.

hostid=35303

Almost 10 years ago I started with seti, with a Pentium MMX 166 MHz, and It seems like my boinc career will end with seti, this 260 won't work with gpugrid anymore after update to 190.38.

"not yet format the hard drive, anything else is done"

Are you all uninstalling the old Nvidia driver first from add remove programs, then uninstall Pxysx, and then running " Driver Sweeper " in safe mode after reboot to remove all the old remnants before updating Nvidia drivers?
I would suggest this if it has't already been tried.
I take this long route and seldom have problems.

Don't uninstall Physx before Nvidia drivers, I messed up doing that. Nvidia first and then Physx.

Tried that yesterday, same result. Hostid=35303 is now on NNW.
Seti is running fine on that host. (one error in 24h)
Something is strange with that computer, now it's running one seti gpu and 2 mc on double core amd 5600. Nice :), nothing is oc.
http://setiathome.berkeley.edu/results.php?hostid=4914727
and
Hostid=35303 cpuz.txt



http://personal.inet.fi/surf/tbymark/boinc/cpuz.txt
Tried that too:
Are you all uninstalling the old Nvidia driver first from add remove programs, then uninstall Pxysx, and then running " Driver Sweeper " in safe mode after reboot to remove all the old remnants before updating Nvidia drivers?
I would suggest this if it has't already been tried.
I take this long route and seldom have problems.

Don't uninstall Physx before Nvidia drivers, I messed up doing that. Nvidia first and then Physx.

Roll back to 185.xx, there seem to be problems with 190.xx over some hardware.
185.xx will be fine for gpugrid for quite a while.

gdf

Roll back to 185.xx, there seem to be problems with 190.xx over some hardware.
185.xx will be fine for gpugrid for quite a while.

gdf

My 9800GTX+ has been ok with 190.38 - no failures or blips of any kind.

Regards
Zy

Question, possibly for PoorBoy. The GTX 260 cards - are they the Core 216 version? I'm having the same problems as everyone else getting GPUGRID wu to run on this card (XP Home 32-bit, Q6600, stock everything). I've tried to roll back to previous versions of the driver (currently running 185.XX) with no positive results. I'm not showing a downclocking problem using GPU-Z.

Question, possibly for PoorBoy. The GTX 260 cards - are they the Core 216 version? I'm having the same problems as everyone else getting GPUGRID wu to run on this card (XP Home 32-bit, Q6600, stock everything). I've tried to roll back to previous versions of the driver (currently running 185.XX) with no positive results. I'm not showing a downclocking problem using GPU-Z.

Am I right that there's not a single reported failure with G9x cards, only G200 are affected? But some of them still run fine with 190.xx?

MrS

PoorBoy,
My GTX 260 Core 216 shows clock rates of 576MHz GPU clock, 999MHz Memory clock, and 1242 MHz Shader clock (GPU-Z values). These are also shown as the default clock values. Am I right in my interpretation of your problem that one or all of these clock values are 1/2 of my clock values, or am I running at 1/2 speed and don't know it :)

PoorBoy,
My GTX 260 Core 216 shows clock rates of 576MHz GPU clock, 999MHz Memory clock, and 1242 MHz Shader clock (GPU-Z values). These are also shown as the default clock values. Am I right in my interpretation of your problem that one or all of these clock values are 1/2 of my clock values, or am I running at 1/2 speed and don't know it :)

GTX 260 - 216 SP - Xp SP3

185.xx driver: 10 WUs, 10 error while computing

190.38 driver: 10 WUs, 9 error while computing


sorry, bye bye

Same here, my gpus went to Collatz and with no errors yet, waiting for a new nvidia driver and if it work then maybe coming back!
____________
"Silakka"
Hello from Turku > Åbo.

100% Wus exiting with error after 1 or 2 hours of processing. Win7 Ultimate x64, 6.6.36-6.6.38 BM (have no try 6.6.37 yet, snd I have a doubts it will be helpful), 190.38, certainly, nVidia driver. GTX260 with 192 shader blocks.

p.s. SETI gpu Wus are being processed well (with only few errors).
____________
From Siberia with love!

I hopethey will fix all the problems at last. I really like this project and I want to participate in it, but I still should only crunch SETI and Collatz project's Wus, 'cause there are almost no errors on these projects...
____________
From Siberia with love!

It looks like that the failure rate on >=GTX260 is increasing. I have no problems with collatz Wus or the older 182.50 driver. All WUs crashing with exit code 1 not at start but after 8h :(. I will test some seti WUs. Cannot run this project anymore as long as this issue will be solved. Too much waste time...

I have a GTX 260 (192) that worked fine under 182.50 but errors 100% on any driver higher. This one now runs F@H.
I have a GTX 260 (216) that works perfectly with 190.38 on GPUGrid.

I have a GTX 260 (192) that worked fine under 182.50 but errors 100% on any driver higher. This one now runs F@H.
I have a GTX 260 (216) that works perfectly with 190.38 on GPUGrid.

We don't have any error on 190.xx. However, we cannot test on 260 because all our cards are 280, 275 or 8800GT.

gdf

Its starting to sound like its limited to the GTX260 cards then if other G200 based cards seem to work. Have there been any reports of other cards having similar failure rates?

You're assuming that the errors you are seeing on your systems upon clock changes are caused by the clock changes.. which may very well be the case. but you're also assuming that all 190.38 problems are related to this similar cause - which I'm not so sure about. GDF said the errors (most?) with 190.38 happen in the FFT part.. which doesn't mix well with assuming downclocking as the reason.

MrS

It's a case of which came first, the Chicken or the egg, in this case it's the Error or the Re-set. In other words did the Card Re-set itself & then the error occurs or did the error occur & then the card re-set it's self ???

Could we say that, since after an error the card stays clocked down and subsequent WUs fail (if I remember correctly), the downclocking causes the error? I don't think so: it could also be that the driver detects no GPU activity (since the WUs fail) and therefore keeps it clocked down. Due to some reason this downclocking could be forced in newer drivers.

What if you change clocks manually during computation? Does that work? I know it did on my 9800GTX+ when I tried last time.

Can you set 2D clocks manually, maybe in the power profile? And see if you get an error. If not I'd say the downclocking is really "just" a symptom and not the cause.

MrS

Did you connect the card's 6 and 8pin pwoer connectors? the card requires those connectors to be connected in order for the card to function properly.

Maybe the poor guy wanted to make sure that by the term "using" you didn't refer to having replaced your old paper weight with some new shiny and very green thing ;)

MrS

I told him I knew where he lived and would be visiting him if he didn't give me a RMA#, he asked me to provide a copy of the purchase receipt ... :P

I told him I knew where he lived and would be visiting him if he didn't give me a RMA#, he asked me to provide a copy of the purchase receipt ... :P

Ahh, you have the same problem ... :(. The people from Galaxytech also ask me for a purchase receipt. I have 3 years warranty and the card is less than one year at the market. Why they need now a proof by the purchase receipt?

Do we have some solution yet to this 260 cards issue?
What has happened, if something?

____________
"Silakka"
Hello from Turku > Åbo.

Do we have some solution yet to this 260 cards issue?
What has happened, if something?