• 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.

Bad Core File error?

M

MasterOfPupets

Limp Gawd
Joined
Jun 22, 2004
Messages
235
Got a strange error today, haven't seen anyone else complaining about it. This is running a single SMP client on a Q6600 in WinXP. Newest client version.

After the program shut itself down I tried starting it again, and got the same error. It's the same WU I've done 3/4 of the completed WU's I've gotten since I got this box up and running. Log File:

Code: 
[17:41:19] + Attempting to send results [August 2 17:41:19 UTC]
[17:45:51] + Results successfully sent
[17:45:51] Thank you for your contribution to Folding@Home.
[17:45:51] + Number of Units Completed: 4

[17:45:52] Using generic mpiexec calls
[17:47:58] - Preparing to get new work unit...
[17:47:58] + Attempting to get work packet
[17:47:58] - Connecting to assignment server
[17:47:59] - Successful: assigned to (171.64.65.64).
[17:47:59] + News From Folding@Home: Welcome to Folding@Home
[17:47:59] Loaded queue successfully.
[17:48:43] + Closed connections
[17:48:43] 
[17:48:43] + Processing work unit
[17:48:43] Work type a1 not eligible for variable processors
[17:48:43] Core required: FahCore_a1.exe
[17:48:43] Core found.
[17:48:43] Using generic mpiexec calls
[17:48:43] Working on queue slot 05 [August 2 17:48:43 UTC]
[17:48:43] + Working ...
[17:48:44] 
[17:48:44] *------------------------------*
[17:48:44] Folding@Home Gromacs SMP Core
[17:48:44] Version 1.74 (March 10, 2007)
[17:48:44] 
[17:48:44] Preparing to commence simulation
[17:48:44] - Ensuring status. Please wait.
[17:48:49] - Starting from initial work packet
[17:48:49] 
[17:48:49] Project: 2665 (Run 0, Clone 50, Gen 6)
[17:48:49] 
[17:48:49] Assembly optimizations on if available.
[17:48:49] Entering M.D.
[17:49:13] .2 percent)
[17:49:13] cket
[17:49:13] 
[17:49:13] Project: 2665 (Run 0, Clone 50, Gen 6)
[17:49:13] 
[17:49:13] 2665 (Run 0, Clone 50, Gen 6)
[17:49:13] 
[17:49:15] Entering M.D.
[17:49:21] Rejecting checkpoint
[17:49:22] NaN detected: x[11415][0]=5.19565 v[11415][0]=NaN
[17:49:22] utdown: BAD_CORE_FILES
[17:49:22] Finalizing output
[17:51:22] ES
[17:51:22] 
[17:51:22] Folding@home Core Shutdown: BAD_CORE_FILES
[17:51:23] aN
[17:51:23] 
[17:51:23] Folding@home Core Shutdown: BAD_CORE_FILES
[17:51:23] Finalizing output
[17:53:26] CoreStatus = 1 (1)
[17:53:26] Client-core communications error: ERROR 0x1
[17:53:26] This is a sign of more serious problems, shutting down.

And after the restart:

Code: 
[20:09:32] - Ask before connecting: No
[20:09:32] - User name: MasterOfPupets (Team 33)
[20:09:32] - User ID: B2F8EA406DE076
[20:09:32] - Machine ID: 1
[20:09:32] 
[20:09:32] Loaded queue successfully.
[20:09:32] 
[20:09:32] + Processing work unit
[20:09:32] Work type a1 not eligible for variable processors
[20:09:32] Core required: FahCore_a1.exe
[20:09:32] Core found.
[20:09:32] Using generic mpiexec calls
[20:09:32] Working on queue slot 05 [August 2 20:09:32 UTC]
[20:09:32] + Working ...
[20:09:32] 
[20:09:32] *------------------------------*
[20:09:32] Folding@Home Gromacs SMP Core
[20:09:32] Version 1.74 (March 10, 2007)
[20:09:32] 
[20:09:32] Preparing to commence simulation
[20:09:32] - Ensuring status. Please wait.
[20:09:37] - Starting from initial work packet
[20:09:37] 
[20:09:37] Project: 2665 (Run 0, Clone 50, Gen 6)
[20:09:37] 
[20:09:38] Assembly optimizations on if available.
[20:09:38] Entering M.D.
[20:10:01] .2 percent)
[20:10:01] - Starting from initial work packet
[20:10:01] 
[20:10:01] Project: 2665 (Run 0, Clone 50, Gen 6)
[20:10:01] 
[20:10:03] Entering M.D.
[20:10:09] Rejecting checkpoint
[20:10:10] NaN detected: x[11415][0]=5.19565 v[11415][0]=NaN
[20:10:10] utdown: BAD_CORE_FILES
[20:10:10] Finalizing output
[20:12:10] ES
[20:12:10] 
[20:12:10] Folding@home Core Shutdown: BAD_CORE_FILES
[20:12:11] aN
[20:12:11] 
[20:12:11] Folding@home Core Shutdown: BAD_CORE_FILES
[20:12:11] Finalizing output

Folding@Home Client Shutdown at user request.

Folding@Home Client Shutdown.

Any help?
 
Welcome to another weekend:p

Yes, it would seem Stanford has not only some server issues but on all my machines today I get the right core, then it completes a WU but can't send it and next it down loads a new core which seems to be the old core and rejects that several times.

If that sounds like you, welcome to the club;)

 
Just delete any 2665 WU you receive, in my experience they rarely run correctly on the new 6.22 client.

If you delete the queue.dat file and the files in the work directory you'll get a new WU, if it's a 2665, just delete again and retry until you get a different project.
 
Well, I deleted the core, queue, and work 4 times, everytime getting a 2665 and a bad core error. I don't have time to babysit this right now. I'm clearing the core/work/queue and shutting down for the weekend. Hopefully it will be fixed monday.
 
relic said:
Just delete any 2665 WU you receive, in my experience they rarely run correctly on the new 6.22 client.

If you delete the queue.dat file and the files in the work directory you'll get a new WU, if it's a 2665, just delete again and retry until you get a different project.
Click to expand...

meanwhile, the severs are running out of work to be done, have a huge backlog of 2665 wu that are not getting compleated.. wash rince repeat.

im sure someone is watching .. wheather they care or not is a different question.

 
thore said:
meanwhile, the severs are running out of work to be done, have a huge backlog of 2665 wu that are not getting compleated.. wash rince repeat.

im sure someone is watching .. wheather they care or not is a different question.
Click to expand...

Yep, but if no one will run the 2665s they'll have to listen, now won't they?
 
hehe..

Yep, but that was last nights drama....I'm sure we'll be provided with a different 'entertainment' over the weekend.
 
thore said:
meanwhile, the severs are running out of work to be done, have a huge backlog of 2665 wu that are not getting compleated.. wash rince repeat.

im sure someone is watching .. wheather they care or not is a different question.

Click to expand...

I have no problem letting the client crunch the 2665s, but I do have a problem with having to babysit the damn client to try and get it to work. I don't have time for that. I'll let it go, maybe turn it on tomorrow and see if it works itself out. If not, let it go til they fix it.
 
MasterOfPupets said:
I have no problem letting the client crunch the 2665s, but I do have a problem with having to babysit the damn client to try and get it to work. I don't have time for that. I'll let it go, maybe turn it on tomorrow and see if it works itself out. If not, let it go til they fix it.
Click to expand...

dont get me wrong, i totally understand the logic. why spin your wheels on something that is taking forever, needs constant attention, and refuses to do what you want it to.. (wait.. i swear im not posting about women.. really) dump the core, and cruch something in the mean time.. i know these WU's need to be done.. but if they are unstable and time consuming, might as well move on to something you can make some headway on.
 
Send 2665 my way, I have 7 boxens at work all crunching those WU 99% of the time without issues :rolleyes:

 
Xilikon said:
Send 2665 my way, I have 7 boxens at work all crunching those WU 99% of the time without issues :rolleyes:

Click to expand...


What version/OS are you running?

I'm still getting the error and am getting very frustrated by this. Like I said earlier, I already crunched 3 of these WUs since I got this Q6600 up and running, but now all of a sudden I get this error.
 
Windows 2000 Professional or Windows XP Professional at work. Also, none is overclocked so this may have to do with my lack of issues.

 
You must log in or register to reply here.
Back
Top