Project 5903 just went up on advmethods. This is an extension of project 5902 to correct for my own mistake in not making enough of those WUs . Since 5902's already been through the whole testing cycle and this project is an extension of that, we'll be moving through the usual testing regime more quickly than normal.

Please note, the behavior of this core is different from what you may expect. The following behaviors are NORMAL, and the points credit takes it into consideration:

The Project: 5903 (Run 5, Clone 605, Gen 2) appears to be rejecting on a checkpoint that shouldn't exist. Then it starts over and seems to be able to run. I'm showing the previous WU's also, to show that there shouldn't be a checkpoint.

Well after a month of zero errors at 1890mhz shaders, I've gotten two failures already with the 5903. I returned my GTX+ to stock shaders (it was already stock for core and memory) and I guess we'll see how it does. It seems these new units are either more sensitive to error or the on/off/on/off pulsing is actually causing more instability. You know how metals fatigue when they are repeatedly heated and cooled? Perhaps that's what the new WU's are doing - causing fatigue by repeatedly heating and cooling the GPU instead of heating to a constant temperature and leaving it there. I start to wonder like db597 above said, if it isn't worse to have millions of heat cycles instead of a nice steady temperature without cycling up and down every 2 seconds.

AZBrandon wrote:It seems these new units are either more sensitive to error

That's quite possible, especially for the 5902/5903 series. Remember that these WUs take longer to execute (hence the larger # of points). If overclocked shaders only occasionally make mistakes, and it takes a few to crash out a WU, it's more likely that a WU will pick up enough errors to crash over a longer execution.

It's also possible that the core itself has some crashiness, but many of the problems I've seen so far can be attributed to hardware.

From what I have seen now 3 times, p 5903's on core 14 hate being paused and then resumed at anytime later. I've now had to restart the gpu client 3 times because of pausing the folding and then resuming it later and having it just hang there but still do the core checkpoints. Any word on maybe why this would be happening? Is there any chance that the core may hate being paused during doing work before resting again or vise versa?

50KALKILLER wrote:From what I have seen now 3 times, p 5903's on core 14 hate being paused and then resumed at anytime later. I've now had to restart the gpu client 3 times because of pausing the folding and then resuming it later and having it just hang there but still do the core checkpoints. Any word on maybe why this would be happening? Is there any chance that the core may hate being paused during doing work before resting again or vise versa?

It's hard for me to say, because I can't consistently reproduce the issue on my machine here - checkpointing seems to be working fine for me. However, I'm running on XP32, so I wonder if there's some interaction on Vista or 64-bit that's causing problems.