GA-P67A-UD4 "The system has experienced boot failures because of overclocking.."

[Oubadah]

I've just put together an i7 2600k based sysem with the GA-P67A-UD4 as motherboard, and I'm having an issue with running my RAM at it's rated speed.

I am NOT overclocking.

The RAM is Corsair Dominator GT CMT4GX3M2A2133C9, rated at 2133MHz/9-10-9-24/1.65v.

When I first ran the system, the RAM had defaulted to 1333MHz/9-9-9-24/1.5v, so I set the above values in the BIOS, and at first my RAM was running fine at 2133MHz.

But then after a few restarts the sytem restarted it'self half way through POST and I got this message:

"The system has experienced boot failures because of overclocking or changes in voltage. Latest settings in BIOS may not coincide with current H/W states"

Nothing is overclocked, I was just trying to run my RAM at it's rated specs, and 2133MHz is within the specs of the UD4 too.

What can I do? I'm running the latest BIOS F7b, and I've also tried older versions...

[Dark Mantis]

Hi and welcome to the Gigabyte Forum.

I am afraid that you are overclocking by trying to run the RAM at it's rated speed. Anything over 1333 is overclocked as far as the JEDEC ratifications goes and although it is common practice it remains overclocking.

You could probably get the memory to run at somewhere near it's rating by setting it all up manually in the BIOS but it won't be happy at that speed on Auto.

[Oubadah]

OK, well I guess technically speaking I'm overclocking then. But the RAM is rated at 2133MHz, and the UD4 is rated at 2133MHz by Gigabyte, so there shouldn't be any problem.

You say it's 'not happy at that speed at auto'. Does that mean I need to configure anything else in the BIOS? (apart from RAM clock, timings and voltage)

I've already tried raising the RAM voltage a little higher, and the QPI voltage.

Also, can someone tell me what the difference is between 'Standard', 'Turbo' and 'Extreme' for Performance Enhance (As found in Advanced Memory Settings). What exactly do they do?

[Oubadah]

This has really tainted my formerly flawless experience with Gigabyte motherboards.

I'm hoping that Gigabyte will be able to fix my issues with BIOS uptates.

Really, the board seems perfectly stable once it has finished booting - I haven't had one single crash or blue screen etc. in Windows or any program, no matter what my RAM settings are. And I've run memtest for 14 hours @ 2133MHz with no error at all. It's just getting past POST that seems to be the problem; frequent error messages, resetting my configurations, reflashing to backup BIOS, mini boot loops etc... It's driving me mad! But once the system has actually booted, no issues...

[Dark Mantis]

Did you download the new version of @BIOS program to run the initial update of your BIOS as the included version doesn't work properly. Once updated the BIOS seems to accept QFlash for subsequent installs of finished updates. It could just be a BIOS update that didn't take properly.

[Oubadah]

Did you download the new version of @BIOS program to run the initial update of your BIOS as the included version doesn't work properly. Once updated the BIOS seems to accept QFlash for subsequent installs of finished updates. It could just be a BIOS update that didn't take properly.

I had to use @BIOS to flash to F7b (QFlash wasn't working after it reset itself to F3). I used @BIOS 2.10. Now I've used QFlash to F7d (latest), but I've noticed no improvement (the moment I set 2133MHz, it rebooted half way through POST and reset to 1333MHz generic settings again).

[Tordon]

I am experiencing exactly the same problem here, can we get some help ? Been trying to fix it for almost a month now.

MOBO: Gigabyte P67A-UD5 with latest BIOS - F6D (F6 is out, havent tested it yet). Flashed with the proper version of @BIOS w/o any problems. Both main bios and back up bios.
CPU: i7 2600K
RAM: G.SKILL Pi Series 2133mhz 7-10-7-27  1.65v
PSU: SilverStone Olympia OP750 - 60A on the 12V line...

I have tested the memory with memtest for about 1 hour and no errors. The system is rock solid once i manage to boot in Windows all day long. But as soon as i shut it down and boot up later on, it gives me the message where the clocks have failed and reverts the memory back to 1333mhz. At this point the bios remembered my settings so all i have to do is hit SAVE and EXIT and than it loads at 2133mz fine. But why is it having a problem when i power down the system and boot up later ? Its extremely annoying. Thera are at least 2 more people from other foprums tha ti know of and who have this problem so it is not an isolated issue. I feel the motherboard "testing" scripts on boot up are extremely sensitive due to the DUAL bios deal. This needs to change, i have been having the mobo for about a month now from BIOS F3 all the way to F6D i still have the problem.

If i leave the memory on AUto - 1333mhz, there is no problem and it boots up fine after i power it down. Even at 4.9 ghz CPU and it is stable. Only when i change the RAM settings it reports the "overclock failed" issues and than i have to go in bios again and SAVE and EXIT. I tried setting the ram to 1866mhz but i still get ths issue. I tried even 1600Mhz, the same issue. I tried QPI/VTT up to 1.2v, no help it still says overclcoks failed after a shut down and boot up later. At the same time, the system is perfectly stable at 2133mhz 7-10-7-27 1.65v 4.9Ghz CPU. Ran Prime 95 for 4 hours to test out the CPU, memtes for 1 hour, Lin X with latest libraries - everything registers stable but it will double boot after i shut down and it will report failed clocks for some reason.

[Dark Mantis]

Hi and welcome to the Gigabyte Forum.

First thing I notice is that you have 1.65v memory. This is more than the 1.5v rating for this motherboard. Are you trying to run it at 1.65v if so that could be a problem. In fact you could possibly burn out your memory controller on the CPU.

You are unlikely to run the memory at the full rated speed unless you are overclocking anyway but you should be able to get 1600+ Mhz out of it and maybe even tighten the timings a touch.

One hour for Memtest86+ is nowhere near enough. If you want to do the test properly follow these instructions.


Memtest86+ V4.20 Beta 13         http://www.memtest.org/

Insert one stick of memory in slot 1 and run Memtest on it for at least 10 loops and if there are no errors then swap it over with the next one and continue untill you have checked all  modules.

If you have any errors the module is faulty.

If you have any faulty modules you will have to return the whole kit as they are matched.

Post back when you have done that with the results.

[Tordon]

There are G.SKILL memories (Ripjaw X) certified for the new P67 and this motherboard specifically ( Gigabyte P67A-UD5) at 1.65v so burning anything at this voltage is some kind of a mistake. I will try this memtest but i seriously doubt that my memories are faulty. I will even tried running them at 1600mhz but the same thing happens. I even tried running them at 1333mhz at 1.5v - the default which the motherboard sets them when it fails and that did not work, stangre totally. So basically anything i set in the BIOS manually, it doesnt want to boot up.

[Dark Mantis]

You didn't mention how much memory you have installed. If you are using all the slots then it will put an extra load on the memory controller which will have to be compensated for.

[Tordon]

Two sticks 2 GB each - 2x2Gb. I am also aware that 4 sticks are not compatible. I also tried different slots, slot 1 and 3, slots 2 and 4, it does the same thing with both pair of slots. Just today another guy in G.SKILL forum reported the same issue with Gigabyte P67A-UD7 - there are 3 of us alone in that thread with exact same problem but with different motherboard. There is also another same thread in G.SKILL forum with that problem also, something is going on.

[Tordon]

Ran that ugly DOS memtest86+ and it did not report any problems at 2133mhz memory 1.66v from bios + 1T for CR. So this leaves the problem with the motherboard i guess since it keeps saying failed colocks upon cold boot only. In my opinion the power distribution of the motherboard is messed up. Asus P67 also had this problem and they have a fix for it. They recommended to enable in their Advanced Power Options boot from PCI-express or somethiong but my Gigabyte board doesnt have it.

[Dark Mantis]

It wouldn't be possible to boot from PCIE unless you had a Revodrive or similar installed anyway.

It can possibly be fixed by a BIOS update.

[Oubadah]

I am also aware that 4 sticks are not compatible.

What do you mean by this?

[stransky]

I've also experienced the exact same error - my build:

i5-2500K
GA-P67A-UD5 running latest F6 BIOS
HD6970
Corsair 750AX
8GB Corsair Vengeance (2x4GB) CL8 rated @ 1600Mhz/8-8-8-24/1.5V - supposedly rated for P67
Crucial C300 128GB
2 x Samsung 1TB HD103SJ

Had only just finished getting everything stable after having the same Windows freeze problems (as many others have posted about both here and on A$U$ forums - resolved by disabling power savings options in BIOS and setting High Performance/no sleep in Win7, HPET to 64 and Suspend type to POS).

I have tried setting XMP in BIOS and also manually setting RAM timings and voltage etc - both result in the same failure - I'm only attempting 1600Mhz - nothing higher than what the memory/board is rated for - although I'm aware that strictly speaking this is an 'overclock'.

I power on from cold, don't even get to POST, board resets, then powers up with the error message "The system has experienced boot failures because of overclocking or changes in voltage. Latest settings in BIOS may not coincide with current H/W states"

However I can run at 1333Mhz and CL9 instead of CL8 with no dramas (so far) - although if I'd wanted that I would have just bought the CL9 kit ;-)

Memtest doesn't show any problems with the modules.

I can also run the XMP settings by updating the BIOS, resetting (i.e. not from cold boot) and powering up (like another user posted).

Likewise, I've also overclocked (hit 4.5Ghz with some very minor tweaks (RAM @ 1333MHz)) with absolutely no dramas.

It's only changing the RAM settings that puts a spanner in the works...