WTF - "Folding@home Core Shutdown: EARLY_UNIT_END" ??

Jathanis

[H]ard|DCer of the Month - Feb. 2013
Joined
Apr 22, 2008
Messages
985
Okay, I've had my share of EUE errors and 24 hour limits, but when I got home from work today, I found a whole string of Early Unit Ends between two successful WU's - what gives? Here's an example from the log, FYI:

Code:
[03:17:34] - Preparing to get new work unit...
[03:17:34] + Attempting to get work packet
[03:17:34] - Will indicate memory of 2046 MB
[03:17:34] - Connecting to assignment server
[03:17:34] Connecting to http://assign-GPU.stanford.edu:8080/
[03:17:34] Posted data.
[03:17:34] Initial: 40AB; - Successful: assigned to (171.64.65.106).
[03:17:34] + News From Folding@Home: GPU folding beta
[03:17:34] Loaded queue successfully.
[03:17:34] Connecting to http://171.64.65.106:8080/
[03:17:34] Posted data.
[03:17:34] Initial: 0000; - Receiving payload (expected size: 85235)
[03:17:35] - Downloaded at ~83 kB/s
[03:17:35] - Averaged speed for that direction ~92 kB/s
[03:17:35] + Received work.
[03:17:35] Trying to send all finished work units
[03:17:35] + No unsent completed units remaining.
[03:17:35] + Closed connections
[03:17:35] 
[03:17:35] + Processing work unit
[03:17:35] Core required: FahCore_11.exe
[03:17:35] Core found.
[03:17:35] Working on queue slot 01 [September 11 03:17:35 UTC]
[03:17:35] + Working ...
[03:17:35] - Calling '.\FahCore_11.exe -dir work/ -suffix 01 -priority 96 -checkpoint 15 -verbose -lifeline 4448 -version 620'

[03:17:35] 
[03:17:35] *------------------------------*
[03:17:35] Folding@Home GPU Core - Beta
[03:17:35] Version 1.09 (Fri Aug 1 11:46:54 PDT 2008)
[03:17:35] 
[03:17:35] Compiler  : Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 14.00.50727.762 for 80x86 
[03:17:35] Build host: amoeba
[03:17:35] Board Type: Nvidia
[03:17:35] Core      : 
[03:17:35] Preparing to commence simulation
[03:17:35] - Looking at optimizations...
[03:17:35] - Created dyn
[03:17:35] - Files status OK
[03:17:35] - Expanded 84723 -> 447228 (decompressed 527.8 percent)
[03:17:35] Called DecompressByteArray: compressed_data_size=84723 data_size=447228, decompressed_data_size=447228 diff=0
[03:17:35] - Digital signature verified
[03:17:35] 
[03:17:35] Project: 5512 (Run 8, Clone 11, Gen 0)
[03:17:35] 
[03:17:35] Assembly optimizations on if available.
[03:17:35] Entering M.D.
[03:17:42] Working on p5512_lam5w_330K_g1
[03:17:44] Client config found, loading data.
[03:17:45] Starting GUI Server
[03:17:45] mdrun_gpu returned -1
[03:17:45] Going to send back what have done.
[03:17:46] logfile size: 11113 info=11113 bed=0 hdr=25
[03:17:46] - Writing 11651 bytes of core data to disk...
[03:17:46] Done: 11139 -> 4051 (compressed to 36.3 percent)
[03:17:46]   ... Done.
[03:17:46] 
[03:17:46] Folding@home Core Shutdown: EARLY_UNIT_END
[03:17:49] CoreStatus = 72 (114)
[03:17:49] Sending work to server
[03:17:49] Project: 5512 (Run 8, Clone 11, Gen 0)
[03:17:49] - Read packet limit of 540015616... Set to 524286976.


[03:17:49] + Attempting to send results [September 11 03:17:49 UTC]
[03:17:49] - Reading file work/wuresults_01.dat from core
[03:17:49]   (Read 4563 bytes from disk)
[03:17:49] Connecting to http://171.64.65.106:8080/
[03:17:50] Posted data.
[03:17:50] Initial: 0000; - Uploaded at ~5 kB/s
[03:17:50] - Averaged speed for that direction ~33 kB/s
[03:17:50] + Results successfully sent
[03:17:50] Thank you for your contribution to Folding@Home.
[03:17:54] Trying to send all finished work units
[03:17:54] + No unsent completed units remaining.
What really confuses me is the "mdrun_gpu returned -1" - "normally" I'd get 3-5 successful GPU work units, then one would return that with an EUE, then after 4 more, I'd get the 24 hour warning and need to restart the client.

If it matters, the last successful one was a 5506 WU, followed by early ends of: 2x5512 WU, 1x5513 WU, & 2x5511WU. But then it started a 5509 WU just fine, and looks like it will finish it without issue. This is on a 9600GSO with the shaders at 1596, and GPU-Z is reporting the temp as only 58C/51C (depends on which GPU temp sensor line you read), so I don't think heat is the issue. Is this just part of the standard "issues" with the newer 430 pernt WU's? Sorry if I'm just rehashing the same issue, but It's driving me nuts!

And BTW, what exactly does "mdrun_gpu returned -1" mean??? That phrase is becoming the bane of my existence! :mad:

 
Back your shaders and core off if you have them OC-ed.

Let it run. My guess is that will fix it.

Some of these new WU are brutal on cards and wont work with the OCz that did with other WU.

 
Back your shaders and core off if you have them OC-ed.

Let it run. My guess is that will fix it.

Some of these new WU are brutal on cards and wont work with the OCz that did with other WU.


+1 This should solve most EUE problems with the GPU client. Also you might try cranking up your fans a bit more. Shaders are the key though.

 
5511's and 5512's EUE immediately for me on my laptop with everything at stock, so it's not an uncommon problem.



 
Back
Top