cancel
Showing results for 
Search instead for 
Did you mean: 

Rampage IV Extreme Overclock Failed message on boot with STOCK bios settings

Necrosan
Level 12
And the fun continues with this motherboard, unfortunately. 😕

I am loaded to STOCK bios fail safe defaults (not optimized one) and everything seems to work fine once I get into windows, however, once I shut down occasionally (and this doesn't always happen) the system will fail to boot/POST properly and say "overclock failed. hit f1 to check settings" (something along the lines of that.)

When this happens I also see the CPU itself seems to be clocking itself down to 1.2ghz, (well, the POST screen shows that anyway.)

Hitting F1, exiting the bios and letting it reboot will then allow my system to boot. Keep in mind this doesn't ALWAYS happen. It's very sporadic/random.

I'm assuming this is a BIOS issue or something (and am hoping for that and a quick fix).

My hardware is: Rampage 4 Extreme Mobo (BIOS 0803), Intel 3930k CPU, 16GB Corsair Vengeance DDR3/1600, 120GB OCZ Vertex 3 SSD, 2 * GTX 580 SLI.

Please end my rampage 4 nightmare. 🙂
MB: ASUS Rampage IV Black Edition
CPU: Intel Xeon E5-2697 v2 (Cooled by Corsair H100i w/ Noctua NF-F12 fans)
RAM: 64GB G.SKILL RipjawsZ 1600 (10-10-10-30)
GPU: EVGA GeForce GTX Titan X Hybrid
TV Tuners: 2 * Hauppauge HVR-1800
Case: CoolerMaster Cosmos 2

147 Views
18 REPLIES 18

Spoony
Level 7
i will try it now and let you know if it solves my 3 cards crashing issue or none starting

Shamino
Moderator
Keep us updated on the trial of the bios. If all goes well then we should be updating new ones similarly shortly

Raja
Level 13
You may use the "older" BIOS if you wish, it uses a different microcode that suits some of the "cheaper" memory ICs used by some vendors. Everything else in that BIOS build is the same as the newer build.

Raja@ASUS wrote:
You may use the "older" BIOS if you wish, it uses a different microcode that suits some of the "cheaper" memory ICs used by some vendors. Everything else in that BIOS build is the same as the newer build.


If so I think I'll have no more problem, I used to date the old ram, 1366, because the kits certified quad I arrived this morning.
If the problem occurs even with the new Ram will communicate.
Thank you.

Same thing has been happening to me - stock setup except for an XMP profile on G.Skill memory at 2133 (32GB). This is with 0901 bios version (latest on the web site). PSU is a 1200W Enerimax. SLI EVGA 580s.

kahveen wrote:
Same thing has been happening to me - stock setup except for an XMP profile on G.Skill memory at 2133 (32GB). This is with 0901 bios version (latest on the web site). PSU is a 1200W Enerimax. SLI EVGA 580s.


Set Rampage Tweak to Mode 1
Set Clock Gen Filter to 20U
Set VTT to Auto
Set VCCSA to 1.25v-1.3v

Tried the listed settings - and various other variations on a them ... (for next bios revision - ability to dump out the saved config to USB for attaching, or upload would be great for troubleshooting help ).
I did notice that when the VTT was set to Auto it was coming in under CSA (I had not OCed the CPU). For giggles I OCed the CPU to retain the VTT >= CSA from the comment Raja had on one of his OC postings in the forum. Pretty much everything is at Auto right now with XMP values as the basis. Multiplier to 45. Temperature hits a high of about 65. No pattern to the rebooting either, not time based and not really based on workload. Ran a game (SWTOR) for a few hours without issue. I was working in Chrome browsing facebook a couple hours later when it decided to reboot.
Happened with Rampage Tweak on both 1 and 2 (left it at 2 for now). Ditto with the CPU Clock Filter (left it at 20u). Voltage settings are all on Auto. Current Coverage (in the DIGI+ menu) for the memory is set to 140%.
Should note: I am using all eight banks using G.Skill F3-1700CL9-4GBZH (SPD)

that can happen if vccSA is higher than vcore.
you running speedstep? try to make sure vcore is higher than SA at all times, at least for verification first - example manually setting vccsa to 1.20v and vcore to 1.37v -(with load line at auto it should sag to maybe say 1.33v at loads , still decently above SA)

SA is currently running 1.287 - I would imagine that down rating it falls into that category of "not a good idea" 🙂 I had tried a fixed 1.4/1.3 setup that was generating the same issue earlier ...