Well, it's certainly a high Oc, but not an extreme one. And you finished one WU. But is it good? If it's stable then "yes", otherwise "no". How did you test stability?

MrS

---

Scanning for our furry friends since Jan 2002

How did you test stability?

stress gpu during 48 hours with furemark in "extreme mode" (1280X1024)with 16X anisotropic filtering(average 17 fps).max temp:81°c(gpu crash at 83°c)
-6 hours using 3dmark 2006 (74°c)

---

So the answer is a big fat "yes"!

MrS

---

Scanning for our furry friends since Jan 2002

So the answer is a big fat "yes"!

I think the answer is maybe, and that's final!

hello all,

Ive tried o/c-ing my 9800gtx card. got it up about 15%, and its stable everywhere else but gpugrid is not liking it very much. temps at full load are around 60deg.
I can only complete maybe 1 out of 5 wus issued by gpugrid. Any idea why this might be the case? as i said the card is perfectly stable in other apps.

Cheers

Had the same experience like you: my card errored out each & every WU on GG and when I switched to SETI it ran without any probs...
If you want to continue to crunch GPUGrid-WUs you have to lower your OCing until you get no more computation errors...

Had the same experience like you: my card errored out each & every WU on GG and when I switched to SETI it ran without any probs...
If you want to continue to crunch GPUGrid-WUs you have to lower your OCing until you get no more computation errors...

I believe something has changed in the Application's myself. I have a 8800GT OC that was running the WU's just fine then a few days ago started erring out every WU after 3 Seconds. Like other people I can run the SETI GPU WU's just fine though.

I've even under clocked the 8800GT OC & it still errors out the WU's, so lowering your clock speed isn't necessarily a cure for the errors, at least it wasn't in my case.

The 8800GT OC runs perfectly fine though for everything else @ it's Stock or the Overclocked Speed it came with except for running the GPUGrid WU's so like I said I think it's something in the Application's that's changed ... ???

Tixx, how do you determine that it's stable everywhere else?

MrS

---

Scanning for our furry friends since Jan 2002

Ive ran benchmarks on 3d mark, stressed on sisoft sandra, several games, and seti wus.

they are all fine.

also like i said 1 out of every 5 gg wus will calculate fine, the rest error out.

strange

Ive ran benchmarks on 3d mark, stressed on sisoft sandra, several games, and seti wus.

they are all fine.

also like i said 1 out of every 5 gg wus will calculate fine, the rest error out.

strange

I get the same thing with my 8800GT OC, every so often it will actually run & finish a Wu, the rest error out after just 3 seconds ...

Had the same experience like you: my card errored out each & every WU on GG and when I switched to SETI it ran without any probs...
If you want to continue to crunch GPUGrid-WUs you have to lower your OCing until you get no more computation errors...

I believe something has changed in the Application's myself. I have a 8800GT OC that was running the WU's just fine then a few days ago started erring out every WU after 3 Seconds. Like other people I can run the SETI GPU WU's just fine though.

I've even under clocked the 8800GT OC & it still errors out the WU's, so lowering your clock speed isn't necessarily a cure for the errors, at least it wasn't in my case.

The 8800GT OC runs perfectly fine though for everything else @ it's Stock or the Overclocked Speed it came with except for running the GPUGrid WU's so like I said I think it's something in the Application's that's changed ... ???

I must say that I am seeing the same basic effect with my Asus 8800GT. I run 3x 8800GS and 1x 8800GT. The GS's are running fine as usual. The GT collected dust for several months, but is now back up and running--and kicking out 1 compute error after another. This particular card has always been the biggest pita out of the 4 (even on F@H). I just lowered my OC a bit once again, but I expect it to start throwing errors again...maybe not though. I thought it was the card and/or OC....however, after reading this: I'm wondering if there is an 8800GT issue. It's a G92 card.....

Had the same experience like you: my card errored out each & every WU on GG and when I switched to SETI it ran without any probs...
If you want to continue to crunch GPUGrid-WUs you have to lower your OCing until you get no more computation errors...

I believe something has changed in the Application's myself. I have a 8800GT OC that was running the WU's just fine then a few days ago started erring out every WU after 3 Seconds. Like other people I can run the SETI GPU WU's just fine though.

I've even under clocked the 8800GT OC & it still errors out the WU's, so lowering your clock speed isn't necessarily a cure for the errors, at least it wasn't in my case.

The 8800GT OC runs perfectly fine though for everything else @ it's Stock or the Overclocked Speed it came with except for running the GPUGrid WU's so like I said I think it's something in the Application's that's changed ... ???

I must say that I am seeing the same basic effect with my Asus 8800GT. I run 3x 8800GS and 1x 8800GT. The GS's are running fine as usual. The GT collected dust for several months, but is now back up and running--and kicking out 1 compute error after another. This particular card has always been the biggest pita out of the 4 (even on F@H). I just lowered my OC a bit once again, but I expect it to start throwing errors again...maybe not though. I thought it was the card and/or OC....however, after reading this: I'm wondering if there is an 8800GT issue. It's a G92 card.....

I run 5 8800gt's (all o/c'ed) from three differnt manufactures and have the extremeely rare work unit have a problem...I am still running 6.5.0 on all my machines so maybe the problem is with the 6.6.xx application............

Some programs are more sensitive to errors than others. Aside from occasional errors I have been running for two months with very few errors. The system may pass all tests, yet not run a specific application. If you bring down the OC and the application begins to run without errors, then regardless of other tests the OC was at fault.

Another cause can be the amount of memory on the card.

A third cause can be other events on the system that the system as a whole does not react well to and causes tasks to error out...

There is also a slight amount of evidence that some of the tasks issued here may not run well or at all on the lower end cards.

At SaH one of the error modes is that once tasks fail, all will fail until the system is rebooted. There are dozens of reasons that this can happen with the simplest being that the API does not properly initialize the GPU after certain errors so that the error on one task will contaminate all other tasks started.

I run 5 8800gt's (all o/c'ed) from three differnt manufactures and have the extremeely rare work unit have a problem...I am still running 6.5.0 on all my machines so maybe the problem is with the 6.6.xx application

I'm running the 6.5.0 Client too & not the 6.6.xx Client which I think you meant ... ??? If you meant the 6.62 Application I've already surmised that & brought that point up ...

@Paul D.B:

If you bring down the OC and the application begins to run without errors, then regardless of other tests the OC was at fault.

I've already stated that I've Under-clocked the 8800GT with the same results. Took the Card all the way down to 550 Core Speed which is 100 below it's Stock Speed Setting & the WU's still erred out 3 Seconds after starting. That consistent 3 Second Failure is what leads me to believe the Application is at fault & not the Card.

Another cause can be the amount of memory on the card

That's a distinct possibility but up until a week or so ago the Card ran the WU's just fine, so it must have had enough memory up until then if that's the reason. The Card does have 512mb of Memory & only uses about 79mb of it when running the WU's so I don't think that's the reason.

A third cause can be other events on the system that the system as a whole does not react well to and causes tasks to error out

I've put the 8800GT OC in 4 different Systems with the same results, the Systems were already running GTX 260's just fine before trying the 8800GT in them.

At SaH one of the error modes is that once tasks fail, all will fail until the system is rebooted. There are dozens of reasons that this can happen with the simplest being that the API does not properly initialize the GPU after certain errors so that the error on one task will contaminate all other tasks started

I've tried the Re-Boot trick already but the WU's still error out after Re-Booting.

Basically I've retired the 8800GT from running GPU WU's either here or the SETI Project because it won't run the WU's here anymore and is just creating a lot of erred out WU's & to me it's just a waste of Electricity to run the SETI ones for the Credit it gets from them.

I have 2 ATI 4780's coming which should be here either today or tomorrow at the latest & 1 on of them is going to go into the Box the 8800GT is in now and the other in a Box that doesn't have a GPU capable Video Card in it already.

The 8800GT will just become a spare card in the event I need it for backup for one of the 200 Series Cards if one goes bad that I have until I can get a replacement for it. It won't be able to run the WU's but it still can be used for Display only purposes ...

I must say that I am seeing the same basic effect with my Asus 8800GT. I run 3x 8800GS and 1x 8800GT. The GS's are running fine as usual. The GT collected dust for several months, but is now back up and running--and kicking out 1 compute error after another. This particular card has always been the biggest pita out of the 4 (even on F@H). I just lowered my OC a bit once again, but I expect it to start throwing errors again...maybe not though. I thought it was the card and/or OC....however, after reading this: I'm wondering if there is an 8800GT issue. It's a G92 card.....

Don't get me wrong with my earlier post...I'm not discounting it being the card. This particular card has always been the most...uh,..."sensitive". I like Asus MBs, but I won't be buying any more of their vid cards. I can set the OC on this card and it will run fine...then start throwing errors left and right for no reason. Lowering the OC usually helps, but really just starts the cycle all over again. Then eventually it will OC back up....just to start the eventual spiral back downward. This isn't the only MB/system that it's been in, but seems to be starting once again. And You're right, Paul...there's many possible reasons why this can happen. It's simply that when I read the previous post...it seemed very familiar....very familiar. So, if there's any kind of "GT" issue with the app, wus, etc...It would be nice to know.

Just trying to brainstorm ...

I hate it when we cannot find reasons for things ... like why one of my computers all of a sudden seems to want to run the hard drive all the time to the point where nothing gets done ...

Indexing is off, computer is only used for BOINC ... no AV installed ...

PoorBoy,

you're seeing a different issue. If the WUs always fail after 3s that's very systematic and is not one of the usual "too much OC" cases. I don't know what it may be, though.

Naja,

as far as I can remember the (newer?) 8800GS also use G92 chips and are clocked quite a bit slower than an 8800GT. So if the initial clock speed isn't pushed as hard you'll get more OC headroom. I'm sure there's no 8800GT-issue, as many of these cards just run fine. It's just that there are many of them out there, so if x% of all cards fail then it's quite probable that y% of these will be 8800GT, with y denoting some surprisingly high number.

Tixx,

Paul is absolutely right about different applications reacting / failing in different ways.
When you run GPU-Grid: you crunch through these numbers for 12h or longer, calculating an overall ~0.8 Mio time steps. Each step uses the results of the previous one, and the simulated atoms are coupled to each other via chemical bonds. So if you get an error in some calculation, it will be passed onto the next iteration. And either be dampened by the (correct) force calculations or be amplified and trigger an error detection mechanism. Errors are critical here.

Now consider what happens when you run 3D Mark. If you push the clock speed to high it will likely crash, maybe you can see some artefacts prior to this point. But what happens below this threshold clock? What happens, when a calculation in a pixel shader is wrong? Well.. one out of several Mio pixels has a wrong color for one frame. Will 3D Mark detect this or are you going to see it? I don't think so. That's why running games and 3D Mark succesfully can not guarantee you that your card is still calculating correctly. Don't know about Sandra, but generally I never found them to be useful. And seti@gpu is less stressful for the card than GPU-Grid and the WUs are shorter, reducing the "time for failures" per WU. Additionally I think their calculations are largely independent of each other, so errors won't be passed along like in GPU-Grid.

Could also be that GPU-Grid uses different functions of the chips, one of which may be more timing-critical than others. E.g. an addition may actually need 0.5 clocks, whereas a muliplication may need 0.95 clocks. So if all you do is running adds, you could OC by 100% before you see any errors. but as soon as you put a single mul in, you'll get errors. [In a real chip the mul-operation would probably be split into more pipeline steps, so that the clock speed limit for operations would be comparable. Well, in a fast chip ;) ]

BTW: 6.5.0 and 6.6.x are the BOINC-versions.. they're not crunching, just launching the apps. I'm quite sure these are not causing your problems.

MrS

---

Scanning for our furry friends since Jan 2002

ATItool is a small free app that's very useful for testing video overclocks. It contains a "scan for artifacts" function that can catch things the naked eye cannot. My usual arsenal of apps for testing the stability of my system is:

Prime95 - 64 bit, multi core version. Run on all cores using Small FFTs, Round Off Checking enabled
FurMark - Stability Test, Xtreme Burning Mode, non-fullscreen, set resolution to match desktop resolution and minimize to get it out of the way
ATItool - set to "scan for artifacts"
SpeedFan - temps calibrated for accuracy

Prime + Fur will put more heat and load into your system than almost anything else. The Round Off Checking in Prime95 will check for CPU computation errors, the Scan for Artifacts tool in ATItool will check for GPU computation errors. Let it run for a few hours. If no errors present, your overclock isn't causing issues. If you also have a system memory/FSB overclock going, run Prime95 on "Blend" to test for memory errors. Typically, I'll find the max stable overclock, then reduce clocks one step down from that level to ensure stability.

Happy overclocking!

Hmm lol i am not really a hero in this area called oc.
But i finally decided to oc my EVGA 9600 GT
And found it running nice at 725/1800/1100 real(2200).
Now lets wait and see if it really gains me some speed ;)
Untill now most units did :
2478 / 139-143 ms
3718 / 117-131 ms
3848 / 187-206 ms

UPDATE, just in case anybody was using the stability test I encouraged earlier in this thread. CPU testing with Prime95 small FFTs is NOT sufficient unless you let it run for around 40 hours.

Instead, I'm now using a program called "Intel Burn Test". It'll tell you if you're CPU is operating within spec in 30 minutes.