F@H serious error
Moderators: Site Moderators, FAHC Science Team
F@H serious error
I have been running F@H for months on my computer and all of sudden I keep getting a message and can not fold any more. the message is "Folding@home has run into a serious error running the core and will shut down". I erased the program and downloaded it again and I still get the same thing. Any help appreciated.
Re: F@H serious error
What were the Project/Run/Clone/Gen numbers of the WU being worked on? After you replaced the program, did you get a different P/R/C/G? If not, you probably need to erase the work directory and let it build it again. Then recheck to see if you get the same WU again or a new one.
Posting FAH's log:
How to provide enough info to get helpful support.
How to provide enough info to get helpful support.
-
- Site Moderator
- Posts: 6394
- Joined: Sun Dec 02, 2007 10:38 am
- Location: Bordeaux, France
- Contact:
Re: F@H serious error
Log file please ? ©
-
- Posts: 174
- Joined: Sun Nov 16, 2008 6:41 am
Re: F@H serious error
i had this same thing happen with an error, even after i deleted the folder before reinstalling. let them get the log here before you do get rid of it all so they can correct the problem, but i had to go through proper uninstall, then delete the left over program folder, and the other remnants in the appdata roaming folder, restart, then reinstall
Re: F@H serious error
Code: Select all
# Windows CPU Systray Edition #################################################
###############################################################################
Folding@Home Client Version 6.23
http://folding.stanford.edu
###############################################################################
###############################################################################
Launch directory: C:\Users\Charles\AppData\Roaming\Folding@home-x86
[04:04:02] - Ask before connecting: No
[04:04:02] - User name: Charles_Zimmerman (Team 147178)
[04:04:02] - User ID: 6BD73DC84324A3CA
[04:04:02] - Machine ID: 1
[04:04:02]
[04:04:02] Loaded queue successfully.
[04:04:02] Initialization complete
[04:04:02]
[04:04:02] + Processing work unit
[04:04:02] Core required: FahCore_78.exe
[04:04:02] Core found.
[04:04:02] Working on queue slot 03 [January 29 04:04:02 UTC]
[04:04:02] + Working ...
[04:04:02]
[04:04:02] *------------------------------*
[04:04:02] Folding@Home Gromacs Core
[04:04:02] Version 1.90 (March 8, 2006)
[04:04:02]
[04:04:02] Preparing to commence simulation
[04:04:02] - Ensuring status. Please wait.
[04:04:19] - Looking at optimizations...
[04:04:19] - Working with standard loops on this execution.
[04:04:19] - Created dyn
[04:04:19] - Files status OK
[04:04:19] - Expanded 356949 -> 3006825 (decompressed 842.3 percent)
[04:04:19] - Starting from initial work packet
[04:04:19]
[04:04:19] Project: 2620 (Run 32, Clone 19, Gen 17)
[04:04:19]
[04:04:19] Entering M.D.
[04:04:29] Protein: p2620_p1475_tet1_03_1 t= 20000.00000
[04:04:29]
[04:04:29] Writing local files
[04:04:29] Gromacs error.
[04:04:29]
[04:04:29] Folding@home Core Shutdown: UNKNOWN_ERROR
[04:04:32] CoreStatus = 79 (121)
[04:04:32] Client-core communications error: ERROR 0x79
[04:04:32] This is a sign of more serious problems, shutting down.
-
- Site Moderator
- Posts: 6394
- Joined: Sun Dec 02, 2007 10:38 am
- Location: Bordeaux, France
- Contact:
Re: F@H serious error
Delete the WU until you get something else. I've reported the one giving you issues as bad.
-
- Posts: 522
- Joined: Mon Dec 03, 2007 4:33 am
- Location: Australia
Re: F@H serious error
Stop the client; delete the work directory, queue.dat, and unitinfo.txt. As toTOW has reported this WU as bad, you should get a new WU.
The directory can be found at C:\Users\Charles\AppData\Roaming\Folding@home-x86
PS. Welcome to the forum
The directory can be found at C:\Users\Charles\AppData\Roaming\Folding@home-x86
PS. Welcome to the forum
-
- Posts: 289
- Joined: Sun Dec 02, 2007 4:31 am
- Location: Carrizo Plain National Monument, California
- Contact:
Re: F@H serious error
From your log :[04:04:19] - Working with standard loops on this execution.
I would add the -foreasm flag, otherwise if you work with standard loops (that is without SSE) it will work really slowly. See the Wiki if you need to know how to.
I would add the -foreasm flag, otherwise if you work with standard loops (that is without SSE) it will work really slowly. See the Wiki if you need to know how to.