Moderators: Site Moderators , FAHC Science Team
Zagen30
Posts: 823 Joined: Tue Mar 25, 2008 12:45 am
Hardware configuration: Core i7 3770K @3.5 GHz (not folding), 8 GB DDR3 @2133 MHz, 2xGTX 780 @1215 MHz, Windows 7 Pro 64-bit running 7.3.6 w/ 1xSMP, 2xGPU 4P E5-4650 @3.1 GHz, 64 GB DDR3 @1333MHz, Ubuntu Desktop 13.10 64-bit
Post
by Zagen30 » Mon Oct 04, 2010 8:11 pm
On an otherwise stable computer, this one fails immediately upon startup:
Code: Select all
--- Opening Log file [October 4 17:46:34 UTC]
# Windows CPU Console Edition #################################################
###############################################################################
Folding@Home Client Version 6.23
http://folding.stanford.edu
###############################################################################
###############################################################################
Launch directory: C:\Folding@home
Executable: C:\Folding@home\Folding@home-Win32-x86.exe
[17:46:34] - Ask before connecting: No
[17:46:34] - User name: Zagen30 (Team 46301)
[17:46:34] - User ID: XXXXXXXXXXXXXXXXX
[17:46:34] - Machine ID: 1
[17:46:34]
[17:46:34] Loaded queue successfully.
[17:46:34]
[17:46:34] + Processing work unit
[17:46:34] Core required: FahCore_78.exe
[17:46:34] Core found.
[17:46:34] Working on queue slot 05 [October 4 17:46:34 UTC]
[17:46:34] + Working ...
[17:46:34]
[17:46:34] *------------------------------*
[17:46:34] Folding@Home Gromacs Core
[17:46:34] Version 1.90 (March 8, 2006)
[17:46:34]
[17:46:34] Preparing to commence simulation
[17:46:34] - Ensuring status. Please wait.
[17:46:51] - Looking at optimizations...
[17:46:51] - Working with standard loops on this execution.
[17:46:51] - Created dyn
[17:46:51] - Files status OK
[17:46:52] - Expanded 420293 -> 2017421 (decompressed 480.0 percent)
[17:46:52] - Starting from initial work packet
[17:46:52]
[17:46:52] Project: 6512 (Run 9, Clone 59, Gen 56)
[17:46:52]
[17:46:52] Entering M.D.
[17:46:58] Gromacs error.
[17:46:58]
[17:46:58] Folding@home Core Shutdown: UNKNOWN_ERROR
[17:47:00] CoreStatus = 79 (121)
[17:47:00] Client-core communications error: ERROR 0x79
[17:47:00] This is a sign of more serious problems, shutting down.
I was able to move on to a new WU after several deletions of queue.dat and the work folder.
Last edited by
Zagen30 on Fri Oct 08, 2010 5:16 pm, edited 3 times in total.
sortofageek
Site Admin
Posts: 3110 Joined: Fri Nov 30, 2007 8:06 pm
Location: Team Helix
Contact:
Post
by sortofageek » Mon Oct 04, 2010 8:36 pm
Thanks for your report. No data back yet, but we'll keep an eye on this one and let you know if/when we can see something. Sometimes it takes awhile, though, depending on how fast the equipment is to which it gets reassigned.
bruce
Posts: 20824 Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.
Post
by bruce » Mon Oct 04, 2010 8:38 pm
Please post more of the FAHlog. Was anything uploaded?
Zagen30
Posts: 823 Joined: Tue Mar 25, 2008 12:45 am
Hardware configuration: Core i7 3770K @3.5 GHz (not folding), 8 GB DDR3 @2133 MHz, 2xGTX 780 @1215 MHz, Windows 7 Pro 64-bit running 7.3.6 w/ 1xSMP, 2xGPU 4P E5-4650 @3.1 GHz, 64 GB DDR3 @1333MHz, Ubuntu Desktop 13.10 64-bit
Post
by Zagen30 » Mon Oct 04, 2010 9:28 pm
I've updated the posted log section to include literally everything that occurred upon one of the client restarts (it kept grabbing that WU even after deleting queue.dat + work folder until I tried a few hours later; it's moved on now). Nothing was uploaded. A Windows error box would pop up with the only option being to say OK and shut down the client.
Zagen30
Posts: 823 Joined: Tue Mar 25, 2008 12:45 am
Hardware configuration: Core i7 3770K @3.5 GHz (not folding), 8 GB DDR3 @2133 MHz, 2xGTX 780 @1215 MHz, Windows 7 Pro 64-bit running 7.3.6 w/ 1xSMP, 2xGPU 4P E5-4650 @3.1 GHz, 64 GB DDR3 @1333MHz, Ubuntu Desktop 13.10 64-bit
Post
by Zagen30 » Fri Oct 08, 2010 4:59 pm
Got this one again. I know it won't be pulled until other people get it and report errors, but I figured I'd report it anyway.
Code: Select all
[15:14:35] - Preparing to get new work unit...
[15:14:35] + Attempting to get work packet
[15:14:35] - Connecting to assignment server
[15:14:36] - Successful: assigned to (171.64.65.62).
[15:14:36] + News From Folding@Home: Welcome to Folding@Home
[15:14:36] Loaded queue successfully.
[15:14:45] + Closed connections
[15:14:45]
[15:14:45] + Processing work unit
[15:14:45] Core required: FahCore_78.exe
[15:14:45] Core found.
[15:14:45] Working on queue slot 02 [October 8 15:14:45 UTC]
[15:14:45] + Working ...
[15:14:45]
[15:14:45] *------------------------------*
[15:14:45] Folding@Home Gromacs Core
[15:14:45] Version 1.90 (March 8, 2006)
[15:14:45]
[15:14:45] Preparing to commence simulation
[15:14:45] - Looking at optimizations...
[15:14:45] - Created dyn
[15:14:45] - Files status OK
[15:14:45] - Expanded 420293 -> 2017421 (decompressed 480.0 percent)
[15:14:45] - Starting from initial work packet
[15:14:45]
[15:14:45] Project: 6512 (Run 9, Clone 59, Gen 56)
[15:14:45]
[15:14:45] Assembly optimizations on if available.
[15:14:45] Entering M.D.
[15:14:51] Gromacs error.
[15:14:51]
[15:14:51] Folding@home Core Shutdown: UNKNOWN_ERROR
[15:14:55] CoreStatus = 79 (121)
[15:14:55] Client-core communications error: ERROR 0x79
[15:14:55] This is a sign of more serious problems, shutting down.
Oh, and here's a screenshot of the error window that pops up:
sortofageek
Site Admin
Posts: 3110 Joined: Fri Nov 30, 2007 8:06 pm
Location: Team Helix
Contact:
Post
by sortofageek » Fri Oct 08, 2010 5:35 pm
When I see a message complaining about problems with the core, I tend to shut down the client, delete the core and let the client download another. Sometimes it is due to a core file which has become corrupted.
Still
No data back from query
for this WU.
Zagen30
Posts: 823 Joined: Tue Mar 25, 2008 12:45 am
Hardware configuration: Core i7 3770K @3.5 GHz (not folding), 8 GB DDR3 @2133 MHz, 2xGTX 780 @1215 MHz, Windows 7 Pro 64-bit running 7.3.6 w/ 1xSMP, 2xGPU 4P E5-4650 @3.1 GHz, 64 GB DDR3 @1333MHz, Ubuntu Desktop 13.10 64-bit
Post
by Zagen30 » Fri Oct 08, 2010 5:44 pm
Oh, I've shut it down, deleted the core, queue.dat, and the work folder, and it still grabs the same WU and fails with the same error. In fact, I just did that very process about a minute ago, same results.
sortofageek
Site Admin
Posts: 3110 Joined: Fri Nov 30, 2007 8:06 pm
Location: Team Helix
Contact:
Post
by sortofageek » Fri Oct 08, 2010 5:46 pm
Since you can't complete that WU with that client, you might want to try changing the machine ID# so you are recognized as a different client.
sortofageek
Site Admin
Posts: 3110 Joined: Fri Nov 30, 2007 8:06 pm
Location: Team Helix
Contact:
Post
by sortofageek » Tue Oct 12, 2010 4:01 am
Still no data back on Project: 6512 (Run 9, Clone 59, Gen 56).