This is a new eVGA mobo and 9800GT, new as in yesterday. As soon as I start seti it crashes the disp driver and the task gets labeled as computation error. What could the source of this be?

I have the newest drivers since cuda is working. The mobo and gpu are new, the rest of the system is a carry-over. I tried each dimm separately and they both had this same error.

This is a new eVGA mobo and 9800GT, new as in yesterday. As soon as I start seti it crashes the disp driver and the task gets labeled as computation error. What could the source of this be?

I have the newest drivers since cuda is working. The mobo and gpu are new, the rest of the system is a carry-over. I tried each dimm separately and they both had this same error.

Um, this should be posted at the SaH boards ...

But, this is a known problem with the SaH application that when it crashes, at times, it will farble up the display driver. In that neither the display driver nor the SaH application are part of this project I don't think that they will be able to help you much here ...

But, this is a known problem with the SaH application that when it crashes, at times, it will farble up the display driver. In that neither the display driver nor the SaH application are part of this project I don't think that they will be able to help you much here ...

Interesting observation.

And here is my GPUGRID post!

Not that I'm complaining, but I've noticed on occasions, my times per steps varies between 20 ms per unit up to 40 ms per unit.

Also on occasion, when I suspend or exit boinc and run a game, the performance of the game slightly degrades. Nothing drastic and I can live with the slight, almost unoticable stutter.

A good old hard restart after a few days of continuous uptime usually puts everything back on track.

Interesting observation.

And here is my GPUGRID post!

[...]

A good old hard restart after a few days of continuous uptime usually puts everything back on track.

Without named OS and game, running BM version and used GPU this is not a usable information.

On a GTX260 or above you will have no problems playing Grid or Need for Speed but you can't play this games on a GT8600 while crunching for GPUGrid. Between this 2 statements are a wide spread. Somewhere in the middle is the GT8800 or GT9800. Everything else you have find for your own.

---

But, this is a known problem with the SaH application that when it crashes, at times, it will farble up the display driver. In that neither the display driver nor the SaH application are part of this project I don't think that they will be able to help you much here ...

Interesting observation.

And here is my GPUGRID post!

Not that I'm complaining, but I've noticed on occasions, my times per steps varies between 20 ms per unit up to 40 ms per unit.

Also on occasion, when I suspend or exit boinc and run a game, the performance of the game slightly degrades. Nothing drastic and I can live with the slight, almost unoticable stutter.

A good old hard restart after a few days of continuous uptime usually puts everything back on track.

I noticed this and realized it was because in 'advanced' > 'preferences' > 'disk and memory usage' I had checked 'leave applications in memory while suspended'. For some reason even though i right clicked in the BOINC tray and clicked suspend i still found that after a while it would suddenly take itself off suspend and suddenly cause my game to have a huge reduction in performance.

So now if i want to stop it for good i goto 'advanced' and click on 'shut down connected client' and then close the BOINC manager by right clicking on the icon in the system tray and selecting 'exit'. That will then stop BOINC completely until you start BOINC again.

Hope that helps

---

@Carl: as Paul said, you'Re talking about seti. We can't see the error message here, so we can't help. Maybe you want to try GPU-Grid? It's much more stable than the current CUDA-seti ;)

@Ben: when I play anything else than Civ 4 I have to stop GPU-Grid. I just suspend the active WU and that has always worked for me, no strange switching on again. The advantage is that my CPU can keep crunching along in the background.

@Thamir: the reported ms/step is not an average, it's measured at the last step. So the occasional inaccuracy is expected, especially under interactive use of the machine.

MrS

---

Scanning for our furry friends since Jan 2002