• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

GPU2 Error: Folding@home has run into a serious error and will now shut down

LOUISSSSS

Diamond Member
i got this error twice today and it seems to be continuous...

Folding@home has run into a serious error and will now shut down



client info:
GPU2 client
8800gt
177.35 unofficial driver

misc info
Performance very low: locked @ 60 iter/sec or less
 
The only time the GPU2 client has crashed on me was when my display driver stopped responding a couple of times on Vista. It's fine again after a reboot.
 
when I got too aggressive on my oc I started getting screen corruptions. finally I just gave up and rolled it back to stock.
 
my current work unit says:

Name: test protein A
Progress: .0145%
Performance: 60iter/sec
Time Left: 11d:13h: 30s


why am i crunching this stuff? did i do something wrong? cpu is 100% prime and OCCT stable and GPU is not overclocked or overheating (crunching @ 60C)
 
You aren't processing a WU, at the right side of the screen it probably says "core not running".

Look at your log file, post it here.
 
oh, yea. i see that it says Core is Not Running Now. What should i do?

Log File:



--- Opening Log file [June 28 15:43:28]


# Windows Console GPU Edition #################################################
###############################################################################

Folding@Home Client Version 6.12beta6

http://folding.stanford.edu

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

Launch directory: C:\Documents and Settings\Louis\Application Data\Folding@home-gpu


[15:43:28] - Ask before connecting: No
[15:43:28] - User name: Louis_Wong (Team 198)
[15:43:28] - User ID: 7710648D69CC043B
[15:43:28] - Machine ID: 2
[15:43:28]
[15:43:28] Loaded queue successfully.
[15:43:28] Initialization complete
[15:43:28] + Benchmarking ...
[15:43:28]
[15:43:28] + Processing work unit
[15:43:28] Core required: FahCore_11.exe
[15:43:28] Core found.
[15:43:28] Working on Unit 04 [June 28 15:43:28]
[15:43:28] + Working ...
[15:43:28]
[15:43:28] *------------------------------*
[15:43:28] Folding@Home GPU Core - Beta
[15:43:28] Version 1.05 (Thu Jun 12 15:39:34 PDT 2008)
[15:43:28]
[15:43:28] Compiler :
[15:43:28] Build host: amoeba
[15:43:28] Preparing to commence simulation
[15:43:28] - Ensuring status. Please wait.
[15:43:38] - Looking at optimizations...
[15:43:38] - Working with standard loops on this execution.
[15:43:38] - Previous termination of core was improper.
[15:43:38] - Files status OK
[15:43:38] - Expanded 43197 -> 246249 (decompressed 570.0 percent)
[15:43:38] Called DecompressByteArray: compressed_data_size=43197 data_size=246249, decompressed_data_size=246249 diff=0
[15:43:38] - Digital signature verified
[15:43:38]
[15:43:38] Project: 5004 (Run 0, Clone 53, Gen 15)
[15:43:38]
[15:43:38] Entering M.D.
[15:43:44] Working on p5002_supervillin_e1
[15:43:46] CoreStatus = FFFFFFFF (-1)
[15:43:46] Client-core communications error: ERROR 0xffffffff
[15:43:46] This is a sign of more serious problems, shutting down.


--- Opening Log file [June 28 15:44:18]


# Windows Console GPU Edition #################################################
###############################################################################

Folding@Home Client Version 6.12beta6

http://folding.stanford.edu

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

Launch directory: C:\Documents and Settings\Louis\Application Data\Folding@home-gpu


[15:44:18] - Ask before connecting: No
[15:44:18] - User name: Louis_Wong (Team 198)
[15:44:18] - User ID: 7710648D69CC043B
[15:44:18] - Machine ID: 2
[15:44:18]
[15:44:18] Loaded queue successfully.
[15:44:18] Initialization complete
[15:44:18] + Benchmarking ...
[15:44:18]
[15:44:18] + Processing work unit
[15:44:18] Core required: FahCore_11.exe
[15:44:18] Core found.
[15:44:18] Working on Unit 04 [June 28 15:44:18]
[15:44:18] + Working ...
[15:44:18]
[15:44:18] *------------------------------*
[15:44:18] Folding@Home GPU Core - Beta
[15:44:18] Version 1.05 (Thu Jun 12 15:39:34 PDT 2008)
[15:44:18]
[15:44:18] Compiler :
[15:44:18] Build host: amoeba
[15:44:18] Preparing to commence simulation
[15:44:18] - Ensuring status. Please wait.
[15:44:27] - Looking at optimizations...
[15:44:27] - Working with standard loops on this execution.
[15:44:27] - Previous termination of core was improper.
[15:44:27] - Going to use standard loops.
[15:44:27] - Files status OK
[15:44:27] - Expanded 43197 -> 246249 (decompressed 570.0 percent)
[15:44:27] Called DecompressByteArray: compressed_data_size=43197 data_size=246249, decompressed_data_size=246249 diff=0
[15:44:27] - Digital signature verified
[15:44:27]
[15:44:27] Project: 5004 (Run 0, Clone 53, Gen 15)
[15:44:27]
[15:44:27] Entering M.D.
 
I get the same problems. It runs like a champ with no errors for several days and now it has crashed 5 times in the last 24 hours.
 
Originally posted by: LOUISSSSS
[15:44:27] - Working with standard loops on this execution.
[15:44:27] - Previous termination of core was improper.
[15:44:27] - Going to use standard loops.

On the regular client "standard loops" means VERY slow crunching. Would this be part of why LOUISSSSS is crunching slower?

Originally posted by: buddry
I get the same problems. It runs like a champ with no errors for several days and now it has crashed 5 times in the last 24 hours.

Are there new WUs? Maybe they are faulty? Anyone else having problems?
 
Originally posted by: GLeeM
Originally posted by: LOUISSSSS
[15:44:27] - Working with standard loops on this execution.
[15:44:27] - Previous termination of core was improper.
[15:44:27] - Going to use standard loops.

On the regular client "standard loops" means VERY slow crunching. Would this be part of why LOUISSSSS is crunching slower?

Originally posted by: buddry
I get the same problems. It runs like a champ with no errors for several days and now it has crashed 5 times in the last 24 hours.

Are there new WUs? Maybe they are faulty? Anyone else having problems?

where did u get this info on the different types of loops?

anyone else getting these errors? and who is running fine and what "performance: xxx iter/sec" are you getting with an 8800gt + 1 x SMP client?
 
A couple of things.

1. A 8800GT + 1 SMP client should get you ~ 6000+ ppd.
2. Your core is not running, the client is screwed up, if a reboot doesn't fix it you likely need to wipe the directory and reinstall.
3. When you have an EUE the client will use "standard loops", or in other words no SSE optimizations, you can override this by using the -forceasm flag, I don't know if this works with the GPU2 client or not. If you have a number of EUE in a row (can't remember how many, maybe around 5) the client will lock you out for a period of time.
 
From your own log file:
[15:43:46] CoreStatus = FFFFFFFF (-1)
[15:43:46] Client-core communications error: ERROR 0xffffffff

It isn't even starting. Make sure there isn't a crashed copy of FahCore_11 still showing in Task Manager. Make sure you are running the latest drivers, ideally 177.xx. If you haven't rebooted in a while, it's always worth a shot.

You also have an outdated client and core at this point. Uninstall, manually delete FahCore_11.exe from the data directory, and download Beta8 (which will then grab Core 1.06)
 
Also take note: If uninstalling the program, make sure you use the "run" command, type "msconfig" and make sure all Folding programs (if multiple) are checked before you uninstall. After, it will prompt you to reboot and do so. Also make sure all directories are erased. Basically, start from scratch. I have gone through what you are experiencing and this is what I did to make it work. Since then, not a glitch. 🙂
 
Back
Top