• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Eeep! Core Shutdown: UNSTABLE_MACHINE

tedkj

[H]ard|DCer of the Month - July 2008
Joined
Jun 25, 2008
Messages
138
Turns out my brother logged onto the computer, causing 'the system' to no longer have access to the folder where work and cores are stored. This happens even if my user is still logged in. Weird, but anyways, that's it. :)

My GPU2 client on the 8800GT has started to go idle with the following message;

[xx:xx:xx] EUE limit exceeded. Pausing 24 hours.

A workunit goes to 100%, then it sends the results, get a thank_you, and attempts to load new work. It then dumps an error;

[xx:xx:xx] Folding@home Core Shutdown: UNSTABLE_MACHINE

It doesn't happen during a workunit, but in between when it tries to fetch new work. What's the reason for this? I lowered the 8800GT to stock, and it still happens. If I restart the client, all is good until the first or second work unit is done and sent.

Any suggestions? :confused:

Complete log;

[16:45:28] Completed 99%
[16:47:01] Completed 100%
[16:48:02]
[16:48:02] Finished Work Unit:
[16:48:02] - Reading up to 3550680 from "work/wudata_07.trr": Read 3550680
[16:48:02] trr file hash check passed.
[16:48:02] - Reading up to 1139276 from "work/wudata_07.xtc": Read 1139276
[16:48:02] xtc file hash check passed.
[16:48:02] edr file hash check passed.
[16:48:02] logfile size: 129849
[16:48:02] Leaving Run
[16:48:06] - Writing 4820877 bytes of core data to disk...
[16:48:08] Done: 4820365 -> 4046975 (compressed to 83.9 percent)
[16:48:08] ... Done.
[16:48:08] - Shutting down core
[16:48:08]
[16:48:08] Folding@home Core Shutdown: FINISHED_UNIT
[16:48:11] CoreStatus = 64 (100)
[16:48:11] Sending work to server

[16:48:11] + Attempting to send results
[16:49:38] + Results successfully sent
[16:49:38] Thank you for your contribution to Folding@Home.
[16:49:38] + Number of Units Completed: 32

[16:49:42] - Preparing to get new work unit...
[16:49:42] + Attempting to get work packet
[16:49:42] - Connecting to assignment server
[16:49:43] - Successful: assigned to (171.64.65.20).
[16:49:43] + News From Folding@Home: GPU folding beta
[16:49:43] Loaded queue successfully.
[16:49:45] + Closed connections
[16:49:45]
[16:49:45] + Processing work unit
[16:49:45] Core required: FahCore_11.exe
[16:49:45] Core found.
[16:49:45] Working on queue slot 08 [June 30 16:49:45]
[16:49:45] + Working ...
[16:49:45]
[16:49:45] *------------------------------*
[16:49:45] Folding@Home GPU Core - Beta
[16:49:45] Version 1.06 (Mon Jun 23 10:53:13 PDT 2008)
[16:49:45]
[16:49:45] Compiler :
[16:49:45] Build host: amoeba
[16:49:45] Preparing to commence simulation
[16:49:45] - Looking at optimizations...
[16:49:45] - Created dyn
[16:49:45] - Files status OK
[16:49:45] - Expanded 43264 -> 246249 (decompressed 569.1 percent)
[16:49:45] Called DecompressByteArray: compressed_data_size=43264 data_size=246249, decompressed_data_size=246249 diff=0
[16:49:45] - Digital signature verified
[16:49:45]
[16:49:45] Project: 5004 (Run 8, Clone 159, Gen 21)
[16:49:45]
[16:49:45] Assembly optimizations on if available.
[16:49:45] Entering M.D.
[16:49:52] mdrun_gpu returned -1
[16:49:52] Going to send back what have done.
[16:49:53] logfile size: 5533 info=5533 bed=25 hdr=1
[16:49:53] - Writing 6071 bytes of core data to disk...
[16:49:53] Done: 5559 -> 2064 (compressed to 37.1 percent)
[16:49:53] ... Done.
[16:49:53]
[16:49:53] Folding@home Core Shutdown: UNSTABLE_MACHINE
[16:49:55] CoreStatus = 7A (122)

UNSTABLE_MACHINE and the rest of the spam continues 5-6 times and dumps out in the EUE limit exceeded.
 
I've seen that happen when the clocks are set too high. I don't know why this error would remain at stock frequencies. Try doing something else with the card that's GPU-intensive like playing a game or watching high-def video and see if other problems surface.

 
I have had this problem on a Dell box. I cannot get it stable running with 1 or 2 SMP clients + the GPU client. I have settled to just having a GPU client and a standard FAH running and it seems to be ok. My guess is it is a heat issue, one of the things that tipped me off is when touching the back of the PC by the video card, I received a mild burn! :D
 
I was getting this a little while back and fixed it by dropping my OC down a bit. Now that the heat has hit full blast, I realized that I got that error again a few times last night. I'm dropping the clocks a little more to see if I can't get the heat down enough.
 
I was getting this a little while back and fixed it by dropping my OC down a bit. Now that the heat has hit full blast, I realized that I got that error again a few times last night. I'm dropping the clocks a little more to see if I can't get the heat down enough.

FAH will push your machine beyond what any other stability test will.

 
With the GPU2, it could also happen that the client became borked and it will always do that no matter what. A full uninstall and reinstall usually fix this.

 
Back
Top