Sign in with
Sign up | Sign in
Your question
Solved

"Overclocking failed" error, what's causing this?

Tags:
  • Homebuilt
  • Overclocking
  • Computer
  • Systems
  • Product
Last response: in Systems
Share
August 12, 2011 6:49:15 PM

So I just built my first computer two days ago and it seems to be running fine for the most part. However, sometimes when I start it up (and only after it's been a while since turning the computer on) the fans, LEDs. etc come on for a few seconds and then the computer shuts off, only to restart itself and occasionally display the message "Overclocking failed". I go into BIOS and launch into windows normally.

I know this is a problem but after doing some reading this error message doesn't seem to point to any specific problem so I figured I'd make my own thread and ask. I have done no overclocking to my knowledge but I'd expect either a problem with memory timings/frequency or a CPU voltage problem, but I have no idea.

I appreciate any help on the matter. Motherboard is an ASUS P8P67 Deluxe, Core-i5 2500k CPU, 8GB Corsair vengeance memory http://www.newegg.com/Product/Product.aspx?Item=N82E168... (I bought a triple channel kit stupidly, running two modules of the 3), and an EVGA GTX 570.

In BIOS current CPU voltage is 1.192V, DRAM voltage is 1.490V (Both set to Auto). "Target DRAM speed" is 1333MHz and Memory freqeuncy is set to auto. Is this a problem considering my RAM is DDR3 1600?

More about : overclocking failed error causing

a b K Overclocking
August 12, 2011 9:18:48 PM

im not 100% sure but i had the same problem with an asus motherboard and a phenomII x6 cpu it used to happen if i switched between ubuntu and windows 7 on start up i reset all bios to default and it has not giving me any trouble since
m
0
l

Best solution

a b B Homebuilt system
August 13, 2011 12:32:48 AM

Aside: I'd use the extra 4GB to go the 12GB rather than let 4GB sit in a drawer. (I wouldn't buy 4GB to go from 8 to 12, but you have the memory and have the slot...). The hardware slows by about 1.5% on an i7-920 for a mix of workloads when you fall out of triple channel mode. It could be worse for i5-2500 to fall out of dual channel mode, but I doubt it. There's a ton of cache on the chip and the memory controller is integrated and the memory speed is higher than that used by the i7-920 memory controller so if anything the penalty should be less. Windows software may gain more than the 1.5% lost by taking fewer page faults, caching more data, etc., but the real value you may see is much shorter application loads times. Windows will use that extra memory to pre-load the applications you typically run.

ref: http://www.tomshardware.com/reviews/Intel-Core-i7-Nehal...

On your actual problem, there were like 800K hits in google. It seems like this is ASUS's generic boot failed message. Some people reported success with 'reset to defaults' and 'save' in the bios, others reported results when they flashed the bios even to the same level they already had. Others said nothing helped.

There was one common thread about running the asus overclocking program. If you are running that, then make sure it's not doing anything unexpected. Some people also reported they had success by moving from 'auto' to setting a specific voltage value even one that was not higher than spec. good luck.

edit: missed this the first time I read your post <<"Target DRAM speed" is 1333MHz and Memory freqeuncy is set to auto. Is this a problem considering my RAM is DDR3 1600? >> I don't' know, but it sure seems like it could be a problem. Maybe play with the memory frequency setting so that it is not auto and is what you want ? Also, while I am editing, I had an SSD that was slow to init. It was never found until i had the bios do extended memory testing. This gave the ssd enough time to finish it's init. What a kludge. If the reset to defaults, flash and forced memory frequency don't make the error go away, then try having the bios do diagnostics on startup. If the problem goes away then suspect one of your components, remove then one by one until you find the one causing the problem.

Share
August 13, 2011 3:55:18 PM

I think the problem is solved. When I booted up just now I didn't get any error and the computer didn't cut out. I think it was the memory frequency, I just had to set it to 1600. Thanks for the help!
m
0
l
August 13, 2011 3:55:33 PM

Best answer selected by ender330.
m
0
l
!