• 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.

Long tpf after reboot

K

Kardonxt

2[H]4U
2FA
Joined
Apr 13, 2009
Messages
3,723
I'm having a weird issue after accidentally kicking my machine and causing it to reboot.

My tpf jumped from 39min to 1 hour. Now I just got a message saying "NOTE: Turning on dynamic load balancing" Any idea what happened or how to fix it? The work unit is at 81% so I would hate to scrap it.
 
yeah - check your clock speeds. I was getting longer tpfs one time after a reboot and discovered that all my settings had gone back to default,

(oops just saw your no overclock clarification)
 
? Kicking ?

Don't worry about dynamic load balancing as it is a good thing. Your tpf will go down, so don't scrap the WU.

If you are running Ubuntu on the KGPE-D16 2P system, make sure you did the basic installation and installed the Kraken per musky's guide.
 
Last edited:
lol ya it sits at my feet under my desk. I accidentally kicked it when I was spinning around to get something.

I finished another frame and still an hour QQ. I rebooted just in case it loaded some fail safe mode after an improper shutdown. Will let you guys know if things go back to normal.
 
TPF went back to normal after a proper reboot. All i can think of is it must have been some sort of fail safe settings.

Still a bit confused but I guess it working is all that matters.
 
Kardonxt said:
TPF went back to normal after a proper reboot. All i can think of is it must have been some sort of fail safe settings.

Still a bit confused but I guess it working is all that matters.
Click to expand...

more then likely was the case. probably booted the system at bare minimum settings as a safety measure in case it crashed due to a hardware fault or in this case because of your clumsy feet ;)
 
It happened to me once too -- seems to have been client/core quirk.
I merely restarted the client and TPF went back to "normal" (did _not_
touch the machine).

Are you using Kraken w/your system?
 
Ya I'm running ubuntu with kraken per musky's guide.

Now that tpf is back to normal I'm not too worried about it but just out of curiosity would like to know wtf happened lol.
 
You must log in or register to reply here.
Back
Top