P5113 / a0 core failure? [fixed: missing file]

[Foxery]

[15:13:29] CoreStatus = C0000135 (-1073741515)
[15:13:29] Client-core communications error: ERROR 0xc0000135
[15:13:29] This is a sign of more serious problems, shutting down.

Same CPU has crunched several p5113 units already, and has now continued working away on an Amber unit. I had to rename queue.dat and \work myself, as the client did not attempt to discard the unit and retried a new one on its own. Might try running it on another box later today just for kicks...

Code: Select all

# Windows CPU Console Edition #################################################
###############################################################################

                       Folding@Home Client Version 6.20

                          http://folding.stanford.edu

###############################################################################
###############################################################################

Launch directory: C:\Folding2
Service: C:\Folding2\fah620-console
Arguments: -svcstart -d C:\Folding2 -verbosity 9 

Launched as a service.
Entered C:\Folding2 to do work.

[15:13:24] - Ask before connecting: No
[15:13:24] - User name: Foxery (Team 198)
[15:13:24] - User ID: 2EF36F2C736A6C19
[15:13:24] - Machine ID: 2
[15:13:24] 
[15:13:24] Loaded queue successfully.
[15:13:24] 
[15:13:24] + Processing work unit
[15:13:24] Core required: FahCore_a0.exe
[15:13:24] - Autosending finished units... [15:13:24]
[15:13:24] Trying to send all finished work units
[15:13:24] + No unsent completed units remaining.
[15:13:24] - Autosend completed
[15:13:24] Core found.
[15:13:24] Working on queue slot 04 [September 15 15:13:24 UTC]
[15:13:24] + Working ...
[15:13:24] - Calling '.\FahCore_a0.exe -dir work/ -suffix 04 -checkpoint 15 -service -verbose -lifeline 2028 -version 620'

[15:13:29] CoreStatus = C0000135 (-1073741515)
[15:13:29] Client-core communications error: ERROR 0xc0000135
[15:13:29] This is a sign of more serious problems, shutting down.
[15:14:52] Service stop request received.
[15:14:52] ***** Got a SIGTERM signal (2)
[15:14:52] Killing all core threads

Folding@Home Client Shutdown.

[kasson]

Ugh--nasty-looking error message. What processor was this on? (Although if it's worked fine with previous 5113's, that's less of an issue.)

[Foxery]

It's a brand new Core2/E5200, built last week. I left it running F@H all weekend, so I'm fairly confident it's stable.

Why would it throw this error before even entering the run, though? I tried stopping/restarting the client a few times to be sure, and it looked exactly the same each time. It never displayed the usual "Files Status OK" or "Entering M.D." messages.

I should be able to copy the data files to a machine with completely different hardware later in the day, if I don't get too backed up. I'll keep ya posted.

[kasson]

The C0000135 error is a windows unable to locate DLL error. So I bet it's having trouble finding the fftw dll that comes with the A0 core. Is that in your working directory?

[codysluder]

There's help in the WIKI: http://fahwiki.net/index.php/CoreStatus_codes#C0000135

EDIT: Opps. Too slow.

[Foxery]

Eureka. I hadn't noticed the DLL file before... Seems the other copy of F@H (on this dual-core machine) downloaded it, but this instance did not. Fixed!