• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Odd...5pts from 6 WUs?

Check the stability of your box...you've most likely got the work units ending early, check the log for something like EARLY_UNIT_END...then use programs like Prime95 and MemTest86 to get your box stable (adjust voltages as necessary/drop your overclock, etc.)...then start folding again.
 
Maniacmous said:
Check the stability of your box...you've most likely got the work units ending early, check the log for something like EARLY_UNIT_END...then use programs like Prime95 and MemTest86 to get your box stable (adjust voltages as necessary/drop your overclock, etc.)...then start folding again.
Yeah, I found the culprit - not quite sure what caused it exactly, but one of my boxes just went psycho. It's now folding without problems...just odd that it would have so many Early Unit Ends (Unfortunately, it's not overclocked, and the temperature is fine, so I'm not sure what the problem is).

 
Check your memory with Memtest. You might have a bad stick of ram. Running Memtest for half a day is better then having your computer fold for a day plus and corrupt the work unit, and lose all that time. As always, fold on - after you figure out what's causing the issue. :)

-MN Scout
 
I recently had a similar situation with only 1 of 2 threads going bad on a stock-clocked P4... I basically deleted everything of the bad thread (including registry key) and re-installed , now all works well again.. never touched the bios or memory... what client were you using when it went bad ? (standard 5.02 or beta5.04 ?)

 
RPhArrow said:
I recently had a similar situation with only 1 of 2 threads going bad on a stock-clocked P4... I basically deleted everything of the bad thread (including registry key) and re-installed , now all works well again.. never touched the bios or memory... what client were you using when it went bad ? (standard 5.02 or beta5.04 ?)

Standard - Core 78 was running.

I was having some power supply issues after moving the board into a new case and finally hooked it up to an external supply until I can get to Fry's to get another one. Not quite sure what was up, but I think the supply was underpowered and while parts of the computer would power up, not everything was, so maybe that caused some errors (i had no video to see what was happening), but everything seems fine now (running MemTest to be sure).

 
blakex said:
Standard - Core 78 was running.

I was having some power supply issues after moving the board into a new case and finally hooked it up to an external supply until I can get to Fry's to get another one. Not quite sure what was up, but I think the supply was underpowered and while parts of the computer would power up, not everything was, so maybe that caused some errors (i had no video to see what was happening), but everything seems fine now (running MemTest to be sure).


It’s not a bad idea to go through and delete all the cores once and a while as sometimes they seem to become corrupt, no clue why. Once you delete the core it will automatically download a new one and things will become stable again.

Just a thought


 
BillR said:
It’s not a bad idea to go through and delete all the cores once and a while as sometimes they seem to become corrupt, no clue why. Once you delete the core it will automatically download a new one and things will become stable again.

Just a thought
Yeah, I might do that. Everything is running fine now - still not sure what was up. I let MemTest run for a while and it covered 1500% of the memory...no errors.

So, just seems to have been a random occurrence due to a bad power supply.

 
Back
Top