The machine's here

http://www.gpugrid.net/results.php?hostid=24557

Originally I could do workunits. Some would still fail. After upgrading to any driver later than 182.02, nothing will run. Every workunit runs for several seconds before erroring out. I don't believe it's hardware related, as I've been able to run units before. I've also tried dropping the clock rates by about 20%, and still the same. No games show any errors or instability either. Any suggestions would be very welcome as a lot of potential work is going undone.

The machine's here

http://www.gpugrid.net/results.php?hostid=24557

Originally I could do workunits. Some would still fail. After upgrading to any driver later than 182.02, nothing will run. Every workunit runs for several seconds before erroring out. I don't believe it's hardware related, as I've been able to run units before. I've also tried dropping the clock rates by about 20%, and still the same. No games show any errors or instability either. Any suggestions would be very welcome as a lot of potential work is going undone.

First suggestion, down-level the drivers to the ones that used to work ... see if they still work ...

This is really tough, as you already tried quite a few things.

- it looks like it's not hardware-related, as you already downclocked and the tasks fail immediately at the beginning, so it can't be heat either. Just to make sure: did you downclock everything, core, shader and memory?

- if it was only the new drivers, downgrading them should help. Maybe try to use "Driver cleaner" before installing the one again which is known to work? Or do you ave a system restore point prior to the new drivers?

- and just to be sure: did you try powering off and removing the power cord for >10 mins?

- does 3D Mark still run?

It really sounds like the new driver changed something permanently, which is not undone by the driver downgrade. Now I remember, I think we had a similar report before.. not sure though, if the guy used a 295 or a 9800GX2. And I can't remember if the problem was solved..

You could try this or something similar to remove the NV driver completely (more "completely" than by just overwriting things with the older version).

MrS

I'm inclined to think it's something in the software environment as well. I'm going to drain my work cache, and clean out the BOINC installation completely and install afresh. As it stands now, the current folder has been inherited from an older XP 64 machine, then a Vista 64 machine, then the current machine, not to mention various development versions.

If you are going to that extent, you might want to consider a fresh install of the OS.

This plan is OK, but I don't think it's the BOINC install. First argument: BOINC only launches GPU-Grid.. there's not much it could do to make the tasks error out, even if it wanted to. And the 2nd: it happened when you upgraded the vid driver, not when you upgraded BOINC, right?

MrS

I've uninstalled anything nVidia related and ran the driver cleaner. Reinstalled afterwards, and still no improvement.


I did find this small app to perform CUDA based memory checks on the card.

http://www.softpedia.com/progDownload/CUDA-MemTest-Download-121066.html

Though my card passes the tests.

I'm not too sure it's something inherent to the operating system. I can run the Distributed.net CUDA client without issue.

Removed BOINC completely, including wiping the folders and all the cruft they'd accummulated. I also turned off SLI.

And now I've two units running simultaneously and correctly.

When I tried without the SLI before, they would still break. So I'm not sure if it's the combo of reinstall and non-SLI or not that fixed it.

The last post that suggested it was working was premature. It actually errored on one core, though this time after more than a minute, rather than the prior 8 seconds. I do now have it fixed. A combination of 6.6.25 and the newest 185.81 drivers works.

The last post that suggested it was working was premature. It actually errored on one core, though this time after more than a minute, rather than the prior 8 seconds. I do now have it fixed. A combination of 6.6.25 and the newest 185.81 drivers works.

I did find this small app to perform CUDA based memory checks on the card.

http://www.softpedia.com/progDownload/CUDA-MemTest-Download-121066.html

Though my card passes the tests.

NOt sure why one or the other ...

Could be related to ressource share and the number of attached projects [which get either their cpu or gpu debts whacked].