• Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!

Am I just behind the times?

Overclockers is supported by our readers. When you click a link to make a purchase, we may earn a commission. Learn More.
IMO there's something wrong with this new core. My overclock is no where near max, I can run 850/2125/1000, just don't for stability and heat. My card is at 55C max and has never had a bad unit before this core.
 
I've been checking out the Folding Forum this morning and can't find any info on this new GPU2 core... I would think there would be more reports of problems.

Anyone find any further info?
 
Got another one.

[23:59:57] Run: exception thrown during GuardedRun
[23:59:57] Run: exception thrown in GuardedRun -- Gromacs cannot continue further.
[23:59:57] Going to send back what have done -- stepsTotalG=25000000
[23:59:57] Work fraction=0.2231 steps=25000000.
[00:00:01] Warning: problem accessing logfile work/wudata_07.log: NO problem w/ file (COSM_PASS) -- race condition(?). status=0
[00:00:01] logfile size: 0 info=0 bed=0 hdr=23
[00:00:01] - Writing 642 bytes of core data to disk...
[00:00:01] ... Done.
[00:00:01]
[00:00:01] Folding@home Core Shutdown: EARLY_UNIT_END
[00:00:03] CoreStatus = 72 (114)
[00:00:03] Sending work to server
[00:00:03] Project: 5506 (Run 1, Clone 570, Gen 88)

Using 178.13 Vista driver
 
There were reports of problems before it went public. Reducing shader clocks seems to have brought stability to most of my rigs.
 
There were reports of problems before it went public. Reducing shader clocks seems to have brought stability to most of my rigs.

yup, same here. I reduced shader clock on 3 of mine which were having CoreStatus=66 error (not unstable nor eue), and they all are folding happily now. :)
 
How would you update to the new Core if your using the tray app? Only files associated with the GPU app are [email protected], viewer.exe and licenses.rtf.

Stop your client (Quit), then delete FaHCore_11.exe (search for it) and restart [email protected]. It will download the new client automatically when you restart it. The new client will as well be called FaHCore_11.exe however the log will indicate v1.13 of client instead of v1.09.
 
[00:05:18] Run: exception thrown during GuardedRun
[00:05:18] Run: exception thrown in GuardedRun -- Gromacs cannot continue further.
[00:05:18] Going to send back what have done -- stepsTotalG=25000000
[00:05:18] Work fraction=0.4218 steps=25000000.
[00:05:22] Warning: problem accessing logfile work/wudata_06.log: NO problem w/ file (COSM_PASS) -- race condition(?). status=0
[00:05:22] logfile size: 49644 info=49644 bed=0 hdr=23
[00:05:22] - Writing 50180 bytes of core data to disk...
[00:05:22] ... Done.
[00:05:22]
[00:05:22] Folding@home Core Shutdown: EARLY_UNIT_END
[00:05:25] CoreStatus = 72 (114)
[00:05:25] Sending work to server
[00:05:25] Project: 5506 (Run 3, Clone 58, Gen 111)

and another...so far always 5506

edit:Grrrr

[00:54:28] Run: exception thrown during GuardedRun
[00:54:28] Run: exception thrown in GuardedRun -- Gromacs cannot continue further.
[00:54:28] Going to send back what have done -- stepsTotalG=25000000
[00:54:28] Work fraction=0.3205 steps=25000000.
[00:54:32] Warning: problem accessing logfile work/wudata_07.log: NO problem w/ file (COSM_PASS) -- race condition(?). status=0
[00:54:32] logfile size: 34403 info=34403 bed=0 hdr=23
[00:54:32] - Writing 34939 bytes of core data to disk...
[00:54:32] ... Done.
[00:54:32]
[00:54:32] Folding@home Core Shutdown: UNSTABLE_MACHINE
[00:54:36] CoreStatus = 7A (122)
[00:54:36] Sending work to server
[00:54:36] Project: 5506 (Run 9, Clone 612, Gen 104)

backing Shader down to 1950Mhz :(

edit 2: after dropping the shader and core it immediately errored the next unit :banghead: So now I'm going to try 760/1900/950. If I get one more error then I'm going back to the old core and try like 825/2060/1000.
 
Last edited:
Back