Folding Forum

Posted: **Mon Mar 02, 2009 4:47 am**

EUE on Big Red.

[19:24:53] + Closed connections
[19:24:53] 
[19:24:53] + Processing work unit
[19:24:53] Core required: FahCore_11.exe
[19:24:53] Core found.
[19:24:53] Working on queue slot 02 [February 28 19:24:53 UTC]
[19:24:53] + Working ...
[19:24:53] - Calling '.\FahCore_11.exe -dir work/ -suffix 02 -priority 96 -checkpoint 15 -verbose -lifeline 132 -version 620'

[19:24:54] 
[19:24:54] *------------------------------*
[19:24:54] Folding@Home GPU Core - Beta
[19:24:54] Version 1.19 (Mon Nov 3 09:34:13 PST 2008)
[19:24:54] 
[19:24:54] Compiler  : Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 14.00.50727.762 for 80x86 
[19:24:54] Build host: amoeba
[19:24:54] Board Type: Nvidia
[19:24:54] Core      : 
[19:24:54] Preparing to commence simulation
[19:24:54] - Looking at optimizations...
[19:24:54] - Created dyn
[19:24:54] - Files status OK
[19:24:54] - Expanded 98710 -> 492276 (decompressed 498.7 percent)
[19:24:54] Called DecompressByteArray: compressed_data_size=98710 data_size=492276, decompressed_data_size=492276 diff=0
[19:24:54] - Digital signature verified
[19:24:54] 
[19:24:54] Project: 5750 (Run 4, Clone 150, Gen 149)
[19:24:54] 
[19:24:54] Assembly optimizations on if available.
[19:24:54] Entering M.D.
[19:25:00] Working on Protein
[19:25:03] Client config found, loading data.
[19:25:03] Starting GUI Server
        {snip}
[20:50:04] Completed 44%
[20:50:49] Run: exception thrown during GuardedRun
[20:50:49] Run: exception thrown in GuardedRun -- Gromacs cannot continue further.
[20:50:49] Going to send back what have done -- stepsTotalG=10000000
[20:50:49] Work fraction=0.4440 steps=10000000.
[20:50:53] logfile size=17842 infoLength=17842 edr=0 trr=23
[20:50:53] - Writing 18378 bytes of core data to disk...
[20:50:53] Done: 17866 -> 4852 (compressed to 27.1 percent)
[20:50:53]   ... Done.
[20:50:53] 
[20:50:53] Folding@home Core Shutdown: EARLY_UNIT_END
[20:50:56] CoreStatus = 72 (114)
[20:50:56] Sending work to server
[20:50:56] Project: 5750 (Run 4, Clone 150, Gen 149)
[20:50:56] - Read packet limit of 540015616... Set to 524286976.


[20:50:56] + Attempting to send results [February 28 20:50:56 UTC]
[20:50:56] - Reading file work/wuresults_02.dat from core
[20:50:56]   (Read 5364 bytes from disk)
[20:50:56] Connecting to http://171.67.108.11:8080/
[20:50:56] Posted data.
[20:50:56] Initial: 0000; Conversation time very short, giving reduced weight in bandwidth avg
[20:50:56] - Uploaded at ~12 kB/s
[20:50:56] - Averaged speed for that direction ~104 kB/s
[20:50:56] + Results successfully sent
[20:50:56] Thank you for your contribution to Folding@Home.

Posted: **Mon Mar 02, 2009 8:26 am**

You received partial credit for this WU. It was successfully completed by others. You probably need to check your hardware.

Hi anko1 (team 47815),
Your WU (P5750 R4 C150 G149) was added to the stats database on 2009-02-28 15:50:01 for 226.88 points of credit.

Posted: **Mon Mar 02, 2009 7:39 pm**

Thanks for checking, Bruce. This is a rare exception for the GPU client, most WUs complete successfully. However, I've been having that strange core status issue (7B) on completing SMP units, so maybe the hardware is the issue (even though it's only about a year old). What would you recommend first? The memory stress test?

Posted: **Mon Mar 02, 2009 7:49 pm**

FAHWIKI source link
7B
CoreStatus = 7B (123)
Client-core communications error: ERROR 0x7b
Deleting current work unit & continuing...
This is an unknown error from the fahlog of SMP clients. Because 0x7b is not defined in the F@h client or SMP fahcore, it is believed to be a Windows or SMPD/MPICH error code. Known causes are unstable systems from too much overclocking, changing network settings while the client is running, or stopping restarting the client. The error is also caused by Windows updates that need to restart your machine. See the List of Known Issues.

Folding-community: Error 0x7b
Folding-community: Kasson' post in Error 0x7b
Folding-community: List of known issues - SMP Windows Client

Here's one more possiblity:
(0X7B Problem with Windows SMP Client solved by MichaelO)
The 0X7B Error that many folks have gotten when using the Windows SMP client is not an error from the Folding Client, but rather from Windows itself according to the Folding Forums, Wiki, etc. I had increasingly started having this problem on one of my machines. This morning I was notified that my Acronis backups had failed in the Verify Step. Upon researching this error in the Acronis forums, it was suggested that the Acronis error was caused by a memory fault. I found this a little hard to swallow at first but after having 0X7B problems this morning after rebooting to try and solve my backup issue I decided to start changing the memory, and sure enough, once I replace my 2 x 1024 memory Pair the problems in both Acronis and the Folding Client disappeared.

Based on this, I would suggest that if you start getting errors on the folding client, you should first try testing your installed memory thoroughly. Windows XP is fairly forgiving about memory faults but Vista is more stringent, and the SMP Client, especially on a dual core is also not very forgiving once the memory starts to go bad.

Seems a good recommodation I would say.

Posted: **Mon Mar 02, 2009 8:07 pm**

Thanks, MtM.

Folding Forum

Project: 5750 (Run 4, Clone 150, Gen 149)

Project: 5750 (Run 4, Clone 150, Gen 149)

Re: Project: 5750 (Run 4, Clone 150, Gen 149)

Re: Project: 5750 (Run 4, Clone 150, Gen 149)

Re: Project: 5750 (Run 4, Clone 150, Gen 149)

Re: Project: 5750 (Run 4, Clone 150, Gen 149)