WU Error - Need some Help

[EvilAlchemist]

I have gotten a few "Quit 101 - NaN detected: (ener[0])" on my Q6600.

All on project 3060. Will complete 5 WU's ... then error ... then 5-7 WU's ...then error

Does this sound like a Hardware Issue or WU's issue....
Q6600 G0 = 3.0Ghz
Vcore=1.350
DDR2-1.90
MCH=1.350

Linux - Folding CD
F@H Log from Event

[21:59:23] Project: 3060 (Run 4, Clone 21, Gen 25)
[21:59:23]
[21:59:23] Assembly optimizations on if available.
[21:59:23] Entering M.D.
[21:59:23] optimizations on if available.
[21:59:23] Entering M.D.
[21:59:29] ra SSE boost OK.
[21:59:29]
[21:59:29] Extra SSE boost OK.
[21:59:29] Writing local files
[21:59:29] Completed 0 out of 20000000 steps (0 percent)
[22:11:45] Writing local files
[22:11:45] Completed 200000 out of 20000000 steps (1 percent)
[22:24:14] Writing local files
[22:24:14] Completed 400000 out of 20000000 steps (2 percent)
[22:36:41] Writing local files
[22:36:41] Completed 600000 out of 20000000 steps (3 percent)
[22:48:38] Writing local files
[22:48:38] Completed 800000 out of 20000000 steps (4 percent)
[23:00:33] Writing local files
[23:00:33] Completed 1000000 out of 20000000 steps (5 percent)
[23:12:47] Writing local files
[23:12:47] Completed 1200000 out of 20000000 steps (6 percent)
[23:25:12] Writing local files
[23:25:12] Completed 1400000 out of 20000000 steps (7 percent)
[23:25:50] Quit 101 - NaN detected: (ener[0])
[23:25:50]
[23:25:50] Simulation instability has been encountered. The run has entered a
[23:25:50] state from which no further progress can be made.
[23:25:50] This may be the correct result of the simulation, however if you
[23:25:50] often see other project units terminating early like this
[23:25:50] too, you may wish to check the stability of your computer (issues
[23:25:50] such as high temperature, overclocking, etc.).
[23:25:50] Going to send back what have done.
[23:25:50] logfile size: 137789
[23:25:50] - Writing 138338 bytes of core data to disk...
[23:25:50] ... Done.
[23:25:50]
[23:25:50] Folding@home Core Shutdown: EARLY_UNIT_END
[23:25:54] CoreStatus = 72 (114)
[23:25:54] Sending work to server

 

[schenks]

I've personally had exactly 0 of those in 6 months of running SMP, so I can't tell you one way or another if it's a generally bad WU. What I can tell you is that from experience, the NaN error for me has been bad WUs. Hardware related errors are usually floating point imprecision for me.

 

[EvilAlchemist]

I just now checked the bios and I had "EIST" @ C1E still enabled.
Been reading that is can cause some stability issues ... causes some vdroop
I disabled both.

I am hoping someone else has had this happen ... i am baffled....

I wanna think it is WU related due to the fact that the system can complete so many WU's in a row ... and complete many more afterward ....

.

 

[Kendrak]

When I have gotten an error on the Fold CD it told me it was hardware. Mostly from me pushing that poor 2160 too too far

 

[EvilAlchemist]

When I have gotten an error on the Fold CD it told me it was hardware. Mostly from me pushing that poor 2160 too too far

An E2160 will go 3Ghz with no problem. Maybe 3.2 with effort....

 

[BillR]

I just now checked the bios and I had "EIST" @ C1E still enabled.
Been reading that is can cause some stability issues ... causes some vdroop
I disabled both.

I am hoping someone else has had this happen ... i am baffled....

I wanna think it is WU related due to the fact that the system can complete so many WU's in a row ... and complete many more afterward ....

.

No need to be baffled on an early end. We used to get a lot more then we are seeing now. As a rule it’s not a hardware issue and Stanford has acknowledged they happen from time to time and sometimes it is actually the result they expected/wanted.

3060’s are really chewy and do put extra stress on the CPU, make sure your temps are in range and double check the vcore; you might have to go up a notch.

At least you were only at 7%, it stings like hell when you see one at 99%