7504 - Client Core Communications Error

Sgraffite

Supreme [H]ardness
Joined
Jan 10, 2006
Messages
4,405
I keep a client core communications error on project 7504. I ran Intel Burn Test for 30 iterations to verify stability, and it passed. I was also able to delete my work folder the other day and I got a 6099, which it chewed through just fine.

I googled the error, and I saw multiple thread titles similar to mine on foldingforum.com with timestamps from today, but all threads were deleted when I clicked on them.

Is anyone else getting this error?

I'm not really sure what steps I need to take to troubleshoot this, or if it is a problem on Stanford's end.

Here is an example of the error from my log:
Code:
[16:10:31] Loaded queue successfully.
[16:10:31] 
[16:10:31] + Processing work unit
[16:10:31] Core required: FahCore_a3.exe
[16:10:31] Core found.
[16:10:31] Working on queue slot 05 [November 9 16:10:31 UTC]
[16:10:31] + Working ...
[16:10:31] 
[16:10:31] *------------------------------*
[16:10:31] Folding@Home Gromacs SMP Core
[16:10:31] Version 2.27 (Dec. 15, 2010)
[16:10:31] 
[16:10:31] Preparing to commence simulation
[16:10:31] - Ensuring status. Please wait.
[16:10:41] - Looking at optimizations...
[16:10:41] - Working with standard loops on this execution.
[16:10:41] - Previous termination of core was improper.
[16:10:41] - Files status OK
[16:10:41] - Expanded 1510051 -> 2700832 (decompressed 178.8 percent)
[16:10:41] Called DecompressByteArray: compressed_data_size=1510051 data_size=2700832, decompressed_data_size=2700832 diff=0
[16:10:41] - Digital signature verified
[16:10:41] 
[16:10:41] Project: 7504 (Run 19, Clone 134, Gen 0)
[16:10:41] 
[16:10:41] Entering M.D.
[16:10:47] Mapping NT from 8 to 8 
[16:10:48] Completed 0 out of 500000 steps  (0%)
[16:10:56] CoreStatus = C0000029 (-1073741783)
[16:10:56] Client-core communications error: ERROR 0xc0000029
[16:10:56] Deleting current work unit & continuing...
 
Judging by the problems reported on FF (something I've been watching), it looks like a bad WU.
 
It seems, generally, when the WU crashes immediately upon entering the run, it's a problem with the WU (not always of course, but usually from what I've seen on my machines).
 
Thanks for the quick response. Hopefully they stop sending it soon, it took like 10+ tries before it assigned me a different WU... Between this and the lack of bigadv my laptop has been doing a whole lot of nothing for a few days.
 
Filter and I had a similar problem. I deleted the work folder and the queue.dat files, went into configonly and changed the Machine ID.
 
Multiple users are reporting instant crashes of 7504 project work units. You're in good company.
 
The 7504 is a crud batch. Lots of problems with them. Those threads over in FF consolidated into one thread, thats probably why you couldn't find them. they are here

I've also had a couple of reports of peoples CPU's running hot (+15-20c) on these units as well :eek:
 
Back
Top