cancel
Showing results for 
Search instead for 
Did you mean: 

Overclock not working with bios 3101?

Terminal_Meltdo
Level 10
I updated the bios Monday due to some issues I was trying to resolve with a TrackIR device -- which didn't solve the problem -- and I just found out I can no longer overclock my system with the settings I used before in 1404. I put it back at x47 like I use to have it, but when I go to put a load on the CPU is stays at 3.3ghz. I must be missing something? Any ideas with the new bios?

Antec 2002 Chassis - AMG 1000 Modified
Asus Rampage IV Extreme (bios 4201)
Intel® Management Engine (firmware 8.1.10.1286)
EVGA GTX 680 - PCI-E @ x16 3.0 (driver 332.21)
Intel 3960x revision C2 @ 4.7ghz daily - rock solid
G.Skill Ripsaw Z - 32 gig @ 2133mhz
Corsair: 2x Force GT, AX1200, H80
Windows 7 64bit
6,745 Views
11 REPLIES 11

Thomas
Level 10
Hi,

BIOS 3101 features an updated iROG firmware which runs after the BIOS is updated, it will automatically reboot the system twice during this process. if this update is interrupted it can cause the issue which you are seeing.

Unfortunately you will need to RMA the board.
Thomas Jenner
Asus UK

Terminal_Meltdo
Level 10
The mere words of RMA about gave me a heart attack... You said something about MEI, but now it's gone. I'm gonna try to re-flash it, and then go back to 1404 where that version has been the best. Is there something wrong if the board can't use the new CAP bios and more importantly, is there something wrong with the USB timing? And, how can I test USB - is there an application to verify it? Though, I think TrackIR and GTX 680 has a compatibility problem.

Antec 2002 Chassis - AMG 1000 Modified
Asus Rampage IV Extreme (bios 4201)
Intel® Management Engine (firmware 8.1.10.1286)
EVGA GTX 680 - PCI-E @ x16 3.0 (driver 332.21)
Intel 3960x revision C2 @ 4.7ghz daily - rock solid
G.Skill Ripsaw Z - 32 gig @ 2133mhz
Corsair: 2x Force GT, AX1200, H80
Windows 7 64bit

Thomas
Level 10
I removed what i said about the MEI because after discussing with my colleague it was found it would not fix the problem which you have.
Thomas Jenner
Asus UK

Terminal_Meltdo
Level 10
There has to be a way for you all to make a patch for this so I don't have to RMA.

Antec 2002 Chassis - AMG 1000 Modified
Asus Rampage IV Extreme (bios 4201)
Intel® Management Engine (firmware 8.1.10.1286)
EVGA GTX 680 - PCI-E @ x16 3.0 (driver 332.21)
Intel 3960x revision C2 @ 4.7ghz daily - rock solid
G.Skill Ripsaw Z - 32 gig @ 2133mhz
Corsair: 2x Force GT, AX1200, H80
Windows 7 64bit

Arne_Saknussemm
Level 40
Hey Terminal meltdown...is that what happened? did the flash get interrupted? Seems a bit harsh RMA! :confused: Can't you just get a couple of BIOS chips instead? way less expensive probably?

Sure it's not something simple like turbo disabled etc.?

HiVizMan
Level 40
Either the flash was interrupted or possibly the BIOS flash was completed in OS.
To help us help you - please provide as much information about your system and the problem as possible.

Terminal_Meltdo
Level 10
I don't think RMA is needed. I've ERALL the bios and I'm back to 1404. Now I think Win7 is just glitched from the fresh install I did on Monday because it worked fine before that. Bios 3101 and 1404 both reports 4700mhz, but Win7 refuses to push the cpu past 3300mhz under load with prime95. I'm also going to cap 3101 again ensuring no interruptions and reinstall Windows.

We shall see how that goes. Talk to you all later...


Thanks and have a happy Thanksgiving.

Antec 2002 Chassis - AMG 1000 Modified
Asus Rampage IV Extreme (bios 4201)
Intel® Management Engine (firmware 8.1.10.1286)
EVGA GTX 680 - PCI-E @ x16 3.0 (driver 332.21)
Intel 3960x revision C2 @ 4.7ghz daily - rock solid
G.Skill Ripsaw Z - 32 gig @ 2133mhz
Corsair: 2x Force GT, AX1200, H80
Windows 7 64bit

Arne_Saknussemm
Level 40
Oh yeah! Happy Thanksgiving to you too!

One thing...that kind of GHz result at that frequency 4.7 can sometimes be due to throttling because the VRM is overheating. Do you have dedicated cooling for the VRM have you ruled this out as a possibility? Just a thought.....

Thomas
Level 10
I have seen this issue before and working with the engineers at HQ the conclusion was that the board needed RMA'ing. I know it is a pain in the backside but I am just trying to save you time.

Also was your CPU overclocked while updating the BIOS? If so that might be the cause, even if you think it was 100% stable. You should always be running stock frequencies before a BIOS update!
Thomas Jenner
Asus UK