BIOS won't overclock my CPU but Easytune 6 will???

[AndroidVageta]

I don't know if my problem is a unusual case or not but I'll do my best to explain.

Using a Gigabyte EP45-UD3R, Intel E5200, and OCZ 2x2gb DDR2-800 and when I try to overclock in the BIOS I can't seem to get anywhere with it. Anything like 10mhz above stock just plain WILL NOT BOOT. AT ALL. No matter what the voltages (believe me, I've pushed them, so I know under voltage isn't the problem) or the multiplier/FSB /mem timings I can't seem to overclock at all.

However, when I use the Easytune 6 software, its able to push my CPU to 3.16ghz with a 1400fsb!!! RAM at 350mhz!!! I can't even break 205mhz with the BIOS without it refusing to boot. Even if I use the settings that the Easytune software originally made in the BIOS and UNDERCLOCK the FSB (just for testing reasons, I should be able to underclock from the 350mhz with no issues, right?) the system won't boot. If I go back to the settings that Easytune made in the BIOS the system won't boot...so I can't even adjust the BIOS BACK to what Easytune was able to do stable!

And believe me, the Easytune 6 adjustments are stable. Nothing can make my system crash with the software overclock.

I'm like wtf on this one. It makes no sense, Ive always heard to not use software to overclock but it seems as though that is my only option.

If anyone has suggestions please help me...I've got a nice heatsink and a awesome case with good cooling so heat isn't an issue. So I know my CPU can easily do 4ghz without heat issues...this is just confusing the hell out of me.

Anyone else experience the same problems? I mean, before Easytune 6 I thought my CPU might be fucked, but if the Easytune can overclock then that just proves that my CPU and the rest of my hard ware is in perfect working order right?

 

[VirtualLarry]

Do you have "Performance Enhance:" at "Standard" or "Turbo"? Turn it down to standard.

 

[AndroidVageta]

It's on standard.

 

[Tweakin]

Disable everything from auto, use standard and disable all the memory enhancements and set them to the correct values.

Now go up and disable your cpu multiplyer and manually enter the value you want. It seems that eveytime you make an adjustment with memory or video set to auto, the cpu defaults back to 333fsb.

 

[JonW]

******Motherboard Intelligent Tweaker (M.I.T.)******

Robust Graphics Booster.........................[ Auto ]
CPU Clock Ratio.................................[ 10 ]
Fine CPU Clock Ratio............................[ + 0.0 ]
CPU Frequency 3.33GHz............................[ 333Mhz x 10 ]

******Clock Chip Control******

CPU Host Clock Control..........................[ Enabled ]
CPU Host Frequency (Mhz)........................[ 333 ]
PCI Express Frequency (Mhz).....................[ 100 ]
C.I.A 2 [Disabled]

******Advanced Clock Control******

CPU Clock Drive.................................[ 800mv ]
PCI Express Clock Drive.........................[ 900mv ]
CPU Clock Skew..................................[ 0ps ]
MCH Clock Skew..................................[ 0ps ]

******DRAM Performance Control******

Performance Enhance.............................[ Standard ]
(G) MCH Frequency Latch.........................[ 333 ]
System Memory Multipler.........................[ 2.40B ] "You can try 2.00B, this set your ram fsb in 1:1 ratio"
Memory Frequency 1066............................[ 400 ]
DRAM Timing Selectable..........................[ Manual ]

CAS Latency Time................................[ 5 ]
tRCD............................................[ 5 ]
tRP.............................................[ 5 ]
tRAS............................................[ 15 ]

******Advanced Timing Control******

tRRD[4]............................................[ Auto ]
tWTR[4]............................................[ Auto ]
tWR[8].............................................[ Auto ]
tRFC[68]............................................[ 55 ]
tRTP[4]............................................[ Auto ]
Command Rate (cmd)[0]..............................[ Auto ]

******Channel A Timing Settings******

Static tRead Value [ 11 ] ...............[ 8 ]
tRD Phase0 Adjustment [ 0 ] ................[ Auto ]
tRD Phase1 Adjustment [ 0 ] ................[ Auto ]
tRD Phase2 Adjustment [ 0 ] ................[ Auto ]
tRD Phase3 Adjustment [ 0 ] ................[ Auto ]

tRD 2rd (Differnt Rank) [ 6 ] ................[ Auto ]
tWR 2wr (Differnt Rank) [ 6 ] ................[ Auto ]
tWR 2rd (Differnt Rank) [ 5 ] ................[ Auto ]
tRD 2wr (Same/Difft Rank) [ 8 ] ................[ Auto ]

Dimm 1 Clock Skew Control.......................[ Auto ]
Dimm 2 Clock Skew Control.......................[ Auto ]
DDR Write Training..............................[ Auto ]

******Channel A Driving Settings******

Drive Strength Profile..........................[ Auto ]
Data Driving Pull Up Level......................[ Auto ]
cmd Driving Pull Up Level.......................[ Auto ]
ctrl Driving Pull Up Level......................[ Auto ]
clk Driving Pull Up Level.......................[ Auto ]

Data Driving Pull Down Level....................[ Auto ]
cmd Driving Pull Down Level.....................[ Auto ]
ctrl Driving Pull Down Level....................[ Auto ]
clk Driving Pull Down Level.....................[ Auto ]

******Channel B Timing Settings******

Static tRead Value [ 11 ] ...............[ 8 ]
tRD Phase0 Adjustment [ 0 ] ................[ Auto ]
tRD Phase1 Adjustment [ 0 ] ................[ Auto ]
tRD Phase2 Adjustment [ 0 ] ................[ Auto ]
tRD Phase3 Adjustment [ 0 ] ................[ Auto ]

tRD 2rd (Differnt Rank) [ 6 ] ................[ Auto ]
tWR 2wr (Differnt Rank) [ 6 ] ................[ Auto ]
tWR 2rd (Differnt Rank) [ 5 ] ................[ Auto ]
tRD 2wr (Same/Difft Rank) [ 8 ] ................[ Auto ]

Dimm 1 Clock Skew Control.......................[ Auto ]
Dimm 2 Clock Skew Control.......................[ Auto ]
DDR Write Training..............................[ Auto ]

******Channel B Driving Settings******

Drive Strength Profile..........................[ Auto ]
Data Driving Pull Up Level......................[ Auto ]
cmd Driving Pull Up Level.......................[ Auto ]
ctrl Driving Pull Up Level......................[ Auto ]
clk Driving Pull Up Level.......................[ Auto ]

Data Driving Pull Down Level....................[ Auto ]
cmd Driving Pull Down Level.....................[ Auto ]
ctrl Driving Pull Down Level....................[ Auto ]
clk Driving Pull Down Level.....................[ Auto ]

******Motherboard Voltage Control******

Load-Line Calibration...........................[ Disabled ]
CPU Vcore [ 1.25 ]...................[ 1.3500 ] (Lower when stable, Add when unstable)
CPU Termination [ 1.20 ]...................[ 1.20 ] (Bump this until P95 instant errors disappear, Both CPU/MCH reference scale with this voltage)
CPU PLL [ 1.50 ]...................[ 1.50 ]
CPU Reference [ 0.760 ]...................[ 0.80 ] (67*vtt) "Don't touch this setting once it is set"

MCH Core [ 1.100 ]...................[ 1.28v ] (Lower when stable, Add when it doesn't boot (tripple boot and oc fail message appear) )
MCH Reference [ 0.760 ]...................[ 0.76 ] (63*vtt) "Don't touch this setting once it is set"
MCH/DRAM Refernce [ 0.900 ]...................[ Auto ]
ICH I/O [ 1.500 ]...................[ 1.500 ]
ICH Core [ 1.100 ]...................[ 1.100 ]

DRAM Voltage [ 1.800 ]...................[ 1.9000v-2.000v ]
DRAM Termination [ 0.900 ]...................[ Auto ]
Channel A Ref [ 0.900 ]...................[ Auto ]
Channel B Ref [ 0.900 ]...................[ Auto ]

******Advanced BIOS Features******

Limit CPUID Max to 3............................[ Disabled ]
No-Execute memory Protect.......................[ Disabled ]
CPU Enhance Halt (CIE)..........................[ Disabled ]
C2/C2E State Support............................[ Disabled ]
C4/C4E State Support............................[ Disabled ]
CPU Thermal Monitor.............................[ Disabled ]
CPU EIST Function...............................[ Disabled ]
Virtualization Technology.......................[ Disabled ]

Goodluck,

 

[AndroidVageta]

Nope, those settings are a no go...I just do not understand this, could it be a defective motherboard?

 

[Idontcare]

Originally posted by: AndroidVageta
Nope, those settings are a no go...I just do not understand this, could it be a defective motherboard?

I've seen cases in the past with gigabyte boards specifically where the BIOS loses its sanity for some reason but all it takes to recover the sanity is for the operator to

1. (1) turn off your PSU with the power switch on your PSU
   (2) press the power-on button on your computer case just once, this discharges capacitors
   (3) physically remove the power plug from the PSU
   (4) set the clear CMOS jumper to the clear CMOS position
   (5) leave the rig sit for >60s in this situation
   (6) set the CMOS jumper to the operating CMOS position (no longer clearing the CMOS)
   (7) plug in PSU power cable
   (8) switch on PSU power switch
   (9) boot computer
   (10) enter BIOS, select BIOS option for "load default BIOS parameters" or wording to that effect
   (11) reboot system
   (12) enter BIOS and set up options to stock settings you need to get into your OS
   (13) reboot system
   (14) once booted into OS, initiate a full shutdown from the OS (not a reboot, actual shutdown)...the gigabyte bios takes user-initiated shutdowns as indication that the existing BIOS parameters are "good" and not causing failures, reboots (even user initiated) confuse the BIOS into thinking the existing BIOS parameters are "bad OC parameters" and it will eventually default the BIOS parameters to a fixes set, causing you to need to repeat this list again
   (15) cold boot your system, enter BIOS and setup options as you like, once you are in the OS again initiate shutdown (not reboot) so BIOS knows these new parameters are "good"

 

[JonW]

AV, try flashing to a new bios then follow Idontcare procedure on clearing cmos etc...make sure C.I.A.2 is disabled.

 

[AndroidVageta]

OK this is really starting to irritate me to the EXTREME.

I did what Idontcare said and its still all the same sad story...

Again, BIOS settings WILL NOT alter...I've used BIOS 5,6, and beta 7 to no good end.

Easytune can overclock using the 3 default choices (2.7ghz - 1200mhz, 2.97ghz - 1320, and 3.15ghz - 1400) however even if I try manually overclocking through Easytune system won't boot. Even if I overclock below 2.7ghz through the software it won't boot...all I can use are the 3 default settings the Easytune provides with stable results (and the only results that will work).

So, I know it can't be a bad motherboard if the system (through Easytune) can achieve a stable overclock...right? If so then what in the flying shit fuck is causing this???

Should I just return my RAM, motherboard, and CPU and just start over? Is that really what I'm going to have to do...I'm out of ideas here and it sounds like all of you are getting there too.

 

[AndroidVageta]

NOW WERE GETTING SOMEWHERE!!!

After flashing back to the original BIOS that came with the motherboard (F5) and then going into the BIOS and changing NOTHING MORE THAN the FSB (to 300mhz - 1200mhz - 3.75ghz) and voltages (1.45v CPU, 1.3v NB, 2.1v RAM) the system has booted completely stable.

What could cause this? Is it all the other lil stuff that I turned off i.e - CIE, EIST, etc.?

This is really weird I gotta say...

 

[AndroidVageta]

Scratch that...able to do 3.75ghz unstable (boot to Windows, won't do a single pass in Crysis...BSOD) but won't clock to ANYTHING other than 3.75ghz or 2.5ghz (stock)...won't even boot to 2.6ghz...shit, won't even boot to 2.4ghz...the process of going insane is initializing...

 

[Idontcare]

You very well could have a "bad board" in that it doesn't overclock as expected. Probably can't RMA for that reason alone though, if it functions at stock then that is all it was guaranteed to do.

 

[AndroidVageta]

I can fry it...a little metal scraped here and there :-D

---

I hope you are joking. If not, the next time you post to advocate fraud on our forums, we can do the same to your posting privileges, and it wouldn't even require scraping any metal.

Harvey
Senior AnandTech Moderator

 

[Gillbot]

Originally posted by: AndroidVageta
I can fry it...a little metal scraped here and there :-D

Nothing like trying to rip off a company by forcing an RMA for a completely functional piece of equipment by sabotage. Man up and buy another board.

 

[Idontcare]

Originally posted by: AndroidVageta
Scratch that...able to do 3.75ghz unstable (boot to Windows, won't do a single pass in Crysis...BSOD) but won't clock to ANYTHING other than 3.75ghz or 2.5ghz (stock)...won't even boot to 2.6ghz...shit, won't even boot to 2.4ghz...the process of going insane is initializing...

If you don't mind humoring me for one more test, put it at stock and run prime95 small FFT while taking note of your Vdroop with CPU-z.

I had a gigabyte board (DS3L) blow a vrm on me (did not realize it at the time) but the way I knew something was amiss was that I couldn't overclock worth crap because my Vdroop was something ridiculous like 0.25V or thereabouts.

It would run stable but only because there was so much engineering margin in my Q6600 that it could run stable at stock while being 0.2V+ undervolted at load.

 

[AndroidVageta]

Well, Prime95 will run...but I opted to try IntelBurnTest which from what I've read is more stressful and just better overall than Prime95...and when I start BurnTest it instantly tells me that the test failed and that "it is undeniable to conclude that you RAM and/or CPU is unstable"

This is running off of fail-safe BIOS settings with nothing changed (floppy drive disabled).

Also, Idontcare (don't let his name deceive you) tried your settings in you PM and as expected, completely failure.

Whether true or not, I've concluded that my board must be bad...even if it runs stock settings stable (not so sure, some games still randomly crash) Ill just call newegg and get a replacement. It's not that odd to think its broken either, when I first bought it, like the very first day I built it, I could overclock to any setting and it would boot, then it stopped being able to abruptly and thats when all the settings would cause unstable booting.

However, is it purely a motherboard problem or could the CPU be bad? I'm pretty sure after hours of Memtest that the RAM is in fact good and cannot be part of the problem.

 

[AndroidVageta]

After some searching I found that I had to use the "half-memory" option in IntelBurnTest...something about the 32-bit OS limitation...anyways, at stock the CPU passed 20 passes on the test...temps up to 48C. Only thing this tells me is that at stock the CPU is stable...but I do not want stock...so that really means nothing to me.

I'm just going to assume that its the motherboard...I mean, the CPU is fine (according to multiple stress tests at stock speeds), RAM was tested for hours as working correctly, video card is brand new and has passed all benchmarks and games I've thrown at it, power supply is more than adequate for my uses, hard drives are completely functional (1tb and 1.5tb), sound card works correctly as does my PCI wifi card.

CPU heatsink is installed correctly and heats rather well (never went above 47C), so I know heat isn't the issue...I mean, after a couple of weeks of stress testing the LOGICAL conclusion is that its the motherboard...like Idontcare said, just cause it can run at stock doesn't mean a thing, I bought this motherboard purely because of its overclocking capabilities, and so far its just about failed all tests.

Only thing I can't seem to get over is the stable Easytune 6 overclock...which was used and tested at 3.17ghz (highest default setting) and it's passed 20mins of the IntelBurnTest at 53C WITH NO ERRORS.

A result like this makes me second guess the motherboard being bad...I just don't know.

 

[Idontcare]

I continue to agree with you that it sounds like something is fubar with your mobo.

Any chance you looked at the Vcore with cpuz while running that InteBurnTest? I'm just curious (really curious) how big your Vdroop is.

Remember Vdroop = Vidle - Vload, while running cpuz in windows...for this purposes, you need to turn off (disable) C1E and EIST in the BIOS so that Vidle in windows is for the same GHz and Vcc that Vload will be driven with as well.

http://www.anandtech.com/cpuch...howdoc.aspx?i=3184&p=5

An excessive Vdroop (0.2V+) could explain the crappy OC issues with the board, as well as go some distance in supporting your possible requesting of an RMA for warranty from gigabyte.

 

[AndroidVageta]

OK...after disabling C1E and EIST and keeping the 3.17ghz overclock here are my results:

All readings via CPU-Z load test by IntelBurnTest

Idle core voltage: 1.376v

100% Load core voltage - 1.360 - 1.344

Under LOAD CPU-Z keeps switching back and forth between 1.360v and 1.344v.

Comparing 1.376V to 1.344v thats a .032v drop!

Are these dramatic changes? Can I finally say its the motherboard???

 

[AndroidVageta]

Went ahead and did the test at stock too...

Idle - 1.184v

LOAD - 1.168v

vdroop = .016 ... cause for alarm or RMA?

 

[Idontcare]

Originally posted by: AndroidVageta
OK...after disabling C1E and EIST and keeping the 3.17ghz overclock here are my results:

All readings via CPU-Z load test by IntelBurnTest

Idle core voltage: 1.376v

100% Load core voltage - 1.360 - 1.344

Under LOAD CPU-Z keeps switching back and forth between 1.360v and 1.344v.

Comparing 1.376V to 1.344v thats a .032v drop!

Are these dramatic changes? Can I finally say its the motherboard???

Those aren't dramatic changes, your Vdroop is pretty good. 0.05V Vdroop is normal.

0.10 and higher Vdroop is suspicious. My Vdroop was 0.2V (not 0.02) and I was still able to run prime95 stable at stock, just couldn't overclock and be stable.

Still seems like your mobo is the culprit, but not because of Vdroop issues.

 

[AndroidVageta]

I can't help but too agree. In either case, I issued an RMA from Newegg and returning the motherboard for replacement...not a big deal, its at no cost to me...just 4-5 days waiting.

In either case...once I get my new motherboard, what would be your recommended settings, Idontcare, to overclock to 4ghz? That really is my magic number...I just want an 8ghz CPU LOL...10ghz would be better ;-)

I'll be sure to follow up on this thread and let you know how it went. Thanks for all your help!

 

[aigomorla]

its called startup voltage requirement, and also the fact that windows load will require a stable OC.

You havent told us anything that shows your stable in windows with EZ tune, just the only fact you dont blue screen.

Well if it makes you feel any better, on asus turboz i can ram as high as 4.6ghz, but the moment i load, i blue screen.

Originally posted by: AndroidVageta
Well, Prime95 will run...but I opted to try IntelBurnTest which from what I've read is more stressful and just better overall than Prime95...and when I start BurnTest it instantly tells me that the test failed and that "it is undeniable to conclude that you RAM and/or CPU is unstable"

^ see im correct.

 

[AndroidVageta]

No, IntelBurnTest said errors when testing full RAM (turns out its a OS limitation)...if I chose half RAM it ran without a hitch at the highest EasyTune setting (3.17ghz)...so yes, the EasyTune software overclock was stable, completely stable...I never had an issue with it...IN EITHER CASE, I just sent the motherboard back to Newegg for a new replacement...I'll get it in a few days, and if the motherboard isn't the issue we will soon find out.

 

[aigomorla]

Originally posted by: AndroidVageta
No, IntelBurnTest said errors when testing full RAM (turns out its a OS limitation)...if I chose half RAM it ran without a hitch at the highest EasyTune setting (3.17ghz)...so yes, the EasyTune software overclock was stable, completely stable...I never had an issue with it...IN EITHER CASE, I just sent the motherboard back to Newegg for a new replacement...I'll get it in a few days, and if the motherboard isn't the issue we will soon find out.

id say flash your bios and retry.