So, after finally getting the server to send me work, the next units go down with compute errors. They all failed in <5-10 seconds after starting and gave me an on-screen error message. I didn't get a chance to copy it down but an exe was failing to start. The units came from a few different subprojects (KASHIF, IBUCH, etc.). After running so smoothly for over a month it's weird to suddenly have so many problems. I'll try to capture the error when the server tries to send more work units. It won't now saying i exceeded my quota and that the server has no work.

Does anyone know if BOINC has another GPU intensive application other than SETI? Milkyway never seems to have any work. any other projects?

So, after finally getting the server to send me work, the next units go down with compute errors. They all failed in <5-10 seconds after starting and gave me an on-screen error message. I didn't get a chance to copy it down but an exe was failing to start. The units came from a few different subprojects (KASHIF, IBUCH, etc.). After running so smoothly for over a month it's weird to suddenly have so many problems. I'll try to capture the error when the server tries to send more work units. It won't now saying i exceeded my quota and that the server has no work.

Does anyone know if BOINC has another GPU intensive application other than SETI? Milkyway never seems to have any work. any other projects?

Well there is another project "folding@home" , they make their own application and runs on many videocards and does support also smp meaning 4 cpu can work on 1 unit, i am not sure if the gpu-client also uses the cpu's but it probably will.
The client runs on ATI,Nvidia GPU, SMP and normal so in anyway impressive build sadly they turned their back towards boinc, so its not a boinc project anymore.
They reported boinc a much to unstable platform :D

Yeah, and the last time I tried to install the GPU verison of the Folding At Home client (few weeks ago) it was an impressively complicated install. I've been using computers since I was 4 so I know I can do it, but the effort involved and the amount of changes made to my computer, and this rig is actually important for some other things, means I"m not gonna do it.

Hmm, I'm still getting the No-work available error from GPUgrid so can't tell if the situation is fixed or not.

Yeah, and the last time I tried to install the GPU verison of the Folding At Home client (few weeks ago) it was an impressively complicated install. I've been using computers since I was 4 so I know I can do it, but the effort involved and the amount of changes made to my computer, and this rig is actually important for some other things, means I"m not gonna do it.

Hmm, I'm still getting the No-work available error from GPUgrid so can't tell if the situation is fixed or not.

Sorry about that. This was originally a thread about a related problem to the main one, but when the second problem croped up, seemingly unrelated to the first, I started a new thread on it, and got different help in each one. It's finally working.

I have one GPU that has a runtime error every week or so. It kills one running WU then kills the next 5 or 6. After a reboot, it runs fine for the next week.

Any ideas why this one machine has this problem and how I can fix it??

I have one GPU that has a runtime error every week or so. It kills one running WU then kills the next 5 or 6. After a reboot, it runs fine for the next week.

Any ideas why this one machine has this problem and how I can fix it??

This one GPU does run hotter than my other 3, but I have increased the fan to 90%.

Is runtime an OS program or Nvidia or Cuda??

This MSI card is factory OC'ed. I have not done any overclocking myself. In fact, EVGA Precision shows it at less than MSI claims, 648 to 655 respectively.

I did OC the entire system and have cut that back a bit. Maybe that might help.

This one GPU does run hotter than my other 3, but I have increased the fan to 90%.

The last errored out WU also errored the Docking WU's being done by the CPU. This tends to tell me that it isn't the GPU that is causing this problem. I will continue to watch it, but I think it may be the OS causing the errors.