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

Overclocking problem..

devarinti

Weaksauce
Joined
Feb 15, 2009
Messages
74
I just tried overclocking my Desktop PC which is running a E8400 Wolfdale Intel 3.0 Ghz processor on a Gigabyte EP43 motherboard. I intended to get the processor all the way up to 3.8 but I started off with the first test at 3.2 and I encountered a problem.

I basically followed the following hardforum thread:

http://www.hardforum.com/showthread.php?t=1169366

I had set the clock ratio at 9x which was max and the frequency at 356 mhz.

The problem that I encountered was that as soon as I restarted after setting to 3.20 ghz was that the whole thing started making a lound whine noise. So I just let it start up anyway but it just goes to the loading user applications screen and then pretty much just freezes at that screen. I then set back all the clocks to defaults and everything to default and tried starting it up but this time there was no whine noise yet the computer would still just freeze up at the loading your personal settings screen. I tried resetting via taking out the battery on the motherboard and putting it back in and same problem persists.

Any help would be appreciated greatly. I just need it to run properly on normal settings at the least forget overclocking.

Thanks guys
 
Interesting. Sounds as if something died.

The key would be the whining noise and the fact it locks up there every time
How high a frequency was it? Perhaps a component of the PWM on the motherboard was already on the brink and it took a final hit with that small overclock.

Take a close look at the motherboard, see if there's anything noticeably damaged. Look for busted capacitors, small areas of scorched pcd/components, etc.
 
Interesting. Sounds as if something died.

The key would be the whining noise and the fact it locks up there every time
How high a frequency was it? Perhaps a component of the PWM on the motherboard was already on the brink and it took a final hit with that small overclock.

Take a close look at the motherboard, see if there's anything noticeably damaged. Look for busted capacitors, small areas of scorched pcd/components, etc.

Well I don't notice any scorched areas from my naked eye at least. Tell me if i'm wrong but I'd think the motherboard wouldn't beep and start up all the way to that screen if there was something really damaged. Also, pressed ctrl + alt + del when it came up to the screen with a background and no icons and no taskbar and the task manager came up. After about 15 mins the comp started to normalcy with icons and a taskbar. I just did a system restore but that didn't do much of anything besides the same. As for the frequency of the noise I'd say its just an annoying coil noise. Its kind of high pitched somewhat. Hard to describe. Any other suggestions??
 
Hmm, odd. In this particular circumstance, I'd pop open BIOS, make sure all the CPU info looks correct, then run a memtest before it gets into Windows. If both look good, once in windows, I'd perform a SFC scan. Load up the run box from the start menu and type in sfc /scannow. This will make sure no windows files got corrupted from the last overclock.
 
Hmm, odd. In this particular circumstance, I'd pop open BIOS, make sure all the CPU info looks correct, then run a memtest before it gets into Windows. If both look good, once in windows, I'd perform a SFC scan. Load up the run box from the start menu and type in sfc /scannow. This will make sure no windows files got corrupted from the last overclock.

Well I never actually got around to doing that whole SFC scan thing but I just ended up giving up on it as nothing I tried worked and reinstalled windows and set everything back in bios to defaults. That actually ended up working fine. I just can't figure out why it did that in the first place and if I can overclock again without going through the same problem..
 
Back
Top