• Home
  • Forums
  • Register
  • Featured
  • Reviews
  • Guides
  • Contact

3 Step Overclocking Guide – Bloomfield and Gulftown


Posted by miahallen on 07 Sep 2010 / 106 Comments
Tweet



Important Voltages when Overclocking

There a few important voltages which you will need to manipulate while overclocking, below are the main ones.  Not every motherboard BIOS is identical, but all enthusiast level motherboards should provide control of the voltages as shown below.

CPU Vcore – Directly related to the CPU frequency. As you increase the CPU frequency you would need incrementally increase the v-core as well.  Bloomfield has proven to be extremely durable and I ran a number of Bloomfield CPU’s through the gauntlet and back with very high vcore.  Everyone continues to ask what is “safe”, and I’ll continue my previous suggestion that a safe voltage for you system should be determined by your LOADED CPU core temperatures.  So, while you are stress testing, monitor your CPU core temperatures with Real Temp and if the temperature is under control, you can SAFELY increase the voltage.  So, the next logical question is what is a safe temperature, and Intel says 100C, and that’s what I go by.

Nothing I’ve ever used my computer for come close to generating heat like IntelBurnTest configured to use all threads.  Because it generates so much heat, it has become my favorite stress testing application.  As long as I can keep my CPU cores below 100C while running IntelBurnTest, then for me that’s safe.  If you are more conservative/cautious than me that’s perfectly OK.  IntelBurnTest at default will only spawn one thread for each physical core, so if you have HyperThreading support enabled on your CPU, please manuall select the number of threads in the drop-down box corrosponding to your CPUs thread count.  From this point forward I will use the terminology IntelBurnTest (maximum) to remind you to manually configure the thread count if your CPU has HyperThreading enabled.

QPI/VTT voltage – This is the uncore voltage.  Remember that the primary uncore devices are the L3 cache and the memory controller.  This is also the primary adjustment required to increase bclock frequency.  Again, for Bloomfield I personally wouldn’t hesitate to run mine up to about 1.45V on air 24/7.  For Gulftown I don’t like to go over 1.4V for daily use.

DRAM voltage – This is directly related to your RAM modules and increases will allow increase in MEM speeds.  There has been a lot of debate as to the limitation 1.65V limitation Intel has published.  For quite a while users have been running much higher DRAM voltage without ill effect.  The justification has always been that the default VTT is 1.15V and the DRAM voltage has to stay within 0.5V of the VTT.  I have always played by that rule, although many power users have questioned whether it’s needed or not.  Doesn’t really matter to me, because I usually run VTT at 1.3V minimum which would allow me to run DRAM voltage up to 1.8V without breaking the rule, and 1.8V is plenty for most memory on the market these days.

Whether or not it’s necessary I’m not going to debate here, but it’s an easy rule to follow, and it’s stood the test of time that you can safely run your DRAM voltage up to VTT +0.5V

Sample overclocking goals to use as a reference

I keep going back and forth with this guide trying to make it easy to read for everyone, and yet still relevant to anyone’s personal goal.  Sometimes as I’m typing away, I feel like I’m over explaining things over and over and that it’ll cause more confusion than clarity.  So, for clarity, as you read the guide, I’ll be referring to the following thee sample goals and hopefully that’ll allow my explanations to be a little more concise.

  1. 1. Sample #1 – Easy/budget OC – Intel Core i7 920, DDR3-1333 CAS7
    1. Bclock freq goal = 180MHz
    2. CPU freq goal = 3.6GHz
    3. Memory speed goal = DDR3-1440 (uncore @ 2880MHz)

***This OC should be possible with the stock Intel cooler and minimal voltage increases***

  1. 2. Sample #2 – Moderate/midrange OC – Intel Core i7 930, DDR3-2000 CAS9
    1. Bclock freq goal = 200MHz
    2. CPU freq goal = 4.2GHz
    3. Memory speed goal = DDR3-2000 (uncore @ 4000MHz)

***This OC will require high end air cooling at a minimum and moderate voltage increases***

  1. 3. Sample #3 – Hardcore/high end OC – Intel Core i7 970, DDR3-2400 CAS9
    1. Bclock freq goal = 200MHz
    2. CPU freq goal = 4.6GHz
    3. Memory speed goal = DDR3-2400 (uncore @ 3600MHz)

***This OC may require water cooling or better and moderate to high voltage increases***

Step 1)  Maximize Bclock & uncore Frequency

I would start by entering the BIOS and select “load optimized defaults”, then save and exit.  After the reboot, go back into the BIOS and turn off the start-up slash screen, so that you can view your system’s post behavior.  Also, feel free to disable any “integrated peripherals” that will not be used (i.e. NICs, extra PATA/SATA controllers, legacy devices, etc).  All other overclocking settings you can leave on auto for now.

If you are looking for your maximum overclock, and you’re not concerned with power consumption, disable all power saving features.  These include, but are not limited to; EIST, C1E, and all other C-states.

Isolate the bclock from the CPU

First you need to isolate the bclock, because all other major devices derive their frequencies from the bclock, it’s the logical starting point.  In order to isolate the bclock from the other components, the first thing you need to do is manually force a low multiplier for the CPU.

  • Sample #1, #2, and #3 – set the CPU clock ratio to x15

Isolate the bclock from the memory

Just like the CPU, the memory receives its clock from the bclock via a multiplier, in this case the default is 8 (133×8 = DDR3-1066).  This is expressed in the BIOS as “8″.  For now, we want to drop that down a bit.

  • Sample #1, #2, and #3 – set the memory to 6

In all sample system, the IMC is the limiting factor, and we don’t want to push it up yet, that is the reason for all three to be set at 6 for this step, don’t worry it won’t be there for long.

Lock in your desired uncore clock ratio

As previously mentioned, the uncore clock ratio must be set to double the System Memory Multiplier (SPD) with Bloomfield and 1.5 times the memory multiplier with Gulftown.  In this step, set the uncore clock ratio based on your desired System Memory Multiplier (SPD) (not the temporary memory multiplier we’re using right now).

  • Sample #1 – set the uncore clock ratio to x16
  • Sample #2 – set the uncore clock ratio to x20
  • Sample #3 – set the uncore clock ratio to x18

bclock voltages

For this step, there are only two voltages you should play with; VTT, and IOH Core.  IOH Core voltage is easy, if you are running a single PCIe card (graphics card), give the IOH Core 1.1V, two graphics cards 1.15V, three graphics cards 1.2V, or four graphics cards 1.25V.  If you plan to run bclock frequencies far beyond 200MHz, sometimes it may help for the IOH core to be even higher.

As mentioned above, QPI/VTT is the crucial voltage adjustment for achieving high bclock stability.  Default QPI/VTT is 1.15V and to reach 200MHz bclock you’ll likely need to increase this to at least 1.2V, many CPUs will require 1.3V or more.  The only way to know is to follow the instructions here and find out.

For all three sample systems, start by setting the QPI/VTT voltage to 1.2V.

First overclock!

Go into the BIOS and set the CPU Clock Ratio, the Uncore Clock Ratio, and the System Memory Multiplier (SPD) to the setting we just decided on in the previous sections.  Then go to the voltages section and adjust your IOH Core and your QPI/VTT voltages.  Then restart your machine and go back into the BIOS, if your system fails to post, start a new thread in the forums and ask for some specific help.  Please be sure to include as many details as possible when posting in the forums, and post a picture of the specific problem if possible.

After you’ve restarted your system with your manually configured voltages and returned to the BIOS, adjust the bclock speed from 133MHz to 150MHz.  Then save and exit and allow the system to reboot.  This time, allow the system to boot fully into the operating system.

Testing for highest stable bclock frequency

Once the operating system has fully loaded, start up RealTemp.  RealTemp should always be running while checking for stability of an overclocked system to ensure you do not overheat your CPU.  RealTemp shows your CPU’s core temperatures real-time.  Now start up CPU-Z, this utility will allow you to ensure that your overclocked settings have been properly applied, and that you are running at your desired speed.  Check both the CPU tab for the expected CPU frequency, and check the memory tab to ensure your memory and uncore are both running at the appropriate speed.  At this point the sample systems should each show up in CPU-Z with the following speeds.

  • Sample #1 – CPU = 2250MHz, uncore = 2400MHz, memory = 450MHz
  • Sample #2 – CPU = 2250MHz, uncore = 3000MHz, memory = 450MHz
  • Sample #3 – CPU = 2250MHz, uncore = 2700MHz, memory = 450MHz

***Note***, if you have SpeedStep (“EIST”) enabled, the CPU speed will fluctuate in CPU-Z when the load changes, please verify values given above WHILE RUNNING YOUR STRESS TEST.

Now start up your selected test program, for example OCCT (mix) or IntelBurnTest (maximum).  Run the test for just a short amount of time, I usually try to run 3 loops with IntelBurnTest (maximum).  Then reboot the system and return to the BIOS.

  1. If the test ran without error, raise the bclock by 10MHz, reboot into your OS and run the test again.
  2. If the test failed, raise the QPI/VTT voltage by 0.025V, reboot into your OS and run the test again.

Continue to repeat this testing following the two procedures above, until you meet one of the following three criteria:

  • You reach the same bclock speed you identified in step one and successfully pass your stability test.
  • You reach your maximum safe QPI/VTT voltage (as identified above)
  • Raising the QPI/VTT voltage is ineffective in stabilizing the system.

* Note – there is a phenomena known as “bclock holes” that may create confusion and frustration during this process.  But if you appear to have found your limit at a much lower speed than anticipated, please consider trying a step or two higher before continuing on.  A bclock hole cause’s system instability within particular bclock ranges, and going past them may allow you to regain stability.

Fine tuning

After you have met one of the criteria above, you should have a rough idea of your bclock limit, now it’s time to get a little more fine tuned.  So, revert back to the highest speed THAT PASSED the stress test.  Then continue the same procedure as before, but instead of 10MHz bclock changes, shift to 2MHz changes until you meet one of the three criteria again.  Also, ensure you check my note about “bclock holes” above, the same concept can be applied to this fine tuning step as well.

After you have found your highest stable speed to within 2MHz accuracy, lower the bclock by 2MHz and run your test again.  This time let the test run for a full hour.  If it passes the test  - Congratulations! – you have found your highest reasonably stable bclock frequency.  If it does not pass, drop the bclock 2MHz and attempt the full hour long test again, continue to lower the bclock in 2MHz increments until the one hour test will pass.

For the purpose of this guide, I’m going to assume you met the goal as provided in one of the 3 sample systems listed above.


Pages: 1 2 3 4

Written by miahallen

Well, I was playing with computers ever since my Dad got a Commodore 64 when I was 6 years old (1986), when I was 10 (1990) he bought a custom build 486DX33, and I was in love. Mostly back then I was just a kid playing games, but my fascination with computers had a start. Because I had no money of my own, I was stuck playing with my Dad's computers, and really couldn't "play" too much. So in 1998, the year I graduated, I spent some of my college savings to by a "computer for school", haha. It had two Voodoo2 12MB 3D accelerators in it, so you can imagine how much school work was done on it ;-) It had an AMD K6-233 that I had a really mild OC on, but my custom computer builder friend Aaron had done all the work. So I can't really take the credit there. My fascination with graphics just kept growing and growing over the years, and I was constantly in a struggle to keep my games looking as sharp and smooth as possible. OCing played a big role. My whole world was rocked in 2004 when I was deployed to Iraq as a US Army soldier. The whole year I was there I had a cheap IBM Thinkpad R40 with a 2GHz Celeron, 1GB DDR-333 RAM, a 60GB 4200RPM HDD, and ATI Radeon Mobility graphics (same technology as a 7000 series with only 16MB of memory). It started out rough as I was really into Command and Conquer Generals at the time, and the machine would only play the C&C slide show LOL. So, I downloaded PowerStrip, and OC'ed the GPU by 40%...amazingly, the game was playable! Things changed dramatically in 2007 when I met a guy named Matt while I was stationed in Japan. He introduced me to www.ocforums.com, and the "Benchmarking Team" there. I had not had much interest in benchmarking previously, I always though of myself as more practical. But, I thought I'd play along and I joined the team. My first introduction to an actual competition was was is "The Raptor Pit", "Forum Warz 2008" in the spring of 2008. I was running a Q6600 and an 8800GTX. With air cooling I was able to bench my Q6600 at over 4GHz, and tore up the competition in my class. Overall OCF won the Forum War in 2007, Winter and Summer of 2008, and 2009...that means five in a row. I was not part of the first one in 2007, but the four since then, I have participated in. After winning the 2008 Winter and Summer Warz, Tom's Hardware Guide announced they were looking for nominations for individuals to compete in their first ever international overclocking competition, called "Overdrive". I was nominated, and chosen to compete in the North American semi-finals in Los Angeles in November 2008. I was placed on "Team IRONMODS" as they only had two guys, yet three man teams were allowed. We won the semi-finals in LA, and our prize was a trip to Paris the following month, to compete with the best in the world. The following month, Ton, Jake, and myself flew to Paris as "Team USA" to face off against the best from Taiwan, France, Germany, and Italy. It was a very intense competition, but after two heated days of battle (16 hours of benching), we emerged the victors. Amidst our celebration, Ton and Jake officially invited me to join "Team IRONMODS" on a permanent basis, and I graciously accepted. Ton, aka "TiTON", is a world renown case moder, and is also very well known for some of the AMD overclocking he has done. Jake, aka "CPT.Planet", is a genius overclocker, and a really fun guy. The team has a great synergy when working together, we really have complementary styles. After winning the world championship in December 2008 things were a bit quite for a couple months, then in the spring of 2009 I received an invitation to the 2nd annual Gigabyte Open Overclocking Championship "GOOC". I would compete in the North American semi-final in LA, where the winner would win a ticket to the world championship in Taipei Taiwan during CES in June 2009. The competition was tough with 14 of the best from North America gathering for a 1 on 1 competition of OCing. But once again, I completed the competition well, and rose above the others. I won 1st place and the trip to the world finals in Taipei. My luck ran dry in Taipei where I started off with a bad motherboard, and went through 5 more during the course of the competition due to various reasons. Despite the poor finish in Taipei, I have high hopes to redeem myself next year.

Related Posts


[Review] Zalman CNPS8000A – A Simple Top-Down Cooler
January 14, 2011
3 Step Overclocking Guide – Sandy Bridge
January 4, 2011
3 Step Overclocking Guide – Lynnfield
September 7, 2010

106 Comments


Jesse
2 months ago



I didn’t realize how old these comments were, but in case anybody is perusing in the future as I am, I will say I have it under control now. I ended up fiddling with some settings, particularly lowering to be exactly double of my current spd rather than double what spd will be, reason being is my spd was going to stay at 6x rather than increase to 8x like sample #1 suggested. This caused bios to fail to post and repeatedly reboot so I CMOS jumped it.

After reconfiguring again & triple checking, as well as setting qpi ratio to x36 (I forgot that it was recommended earlier in the guide introduction before the actual guide begins), and besides that the only thing I did was turn some other voltages off auto and set them to what would be recommended later on in the guide… For example setting vcore to it’s starting recommendation, as well as dram voltage to 1.5 (stock).

Idk how but last night I was at 60-65 at 190 bclk as opposed to 85-90 as before when I got that high. I figure some of those voltages being on auto was making them messy. I suppose this means I should suggest those standard/base recommended settings described later in the guide should be mentioned in the beginning, at least as a troubleshooting suggestion. Naturally I left everything that isn’t touched in the guide on auto as recommended. I only changed what would eventually be changed off auto and on to its starting point setting.

Now when I get home I’m gonna run memtest after tightening memory timings (I don’t believe I have to go through the 150-190 bclk testing again because I’m not actually raising the spd past 6, since I’m going for 190×21 = 3990 on 1333mhz ram, which would put it at 1540 at x8 and even if I could stabilize it I don’t see a point (first time oc so I’m happy enough as it is).

I think I’ll go through the 150-190 bclk again in case tightening timings requires stability testing as well, even though they’re being set to manufacturer ratings. I assume this is the correct and safe thing to do? (Test anyway even when underclocking).

Anyway enough rambling. I highly doubt any of this monologue was necessary but maybe it’ll help a future browser. If anyone does happen to see this page, has this guide become slightly outdated at all? I know that it is still very useful and will get me where I want to be, but I’ve also read about 20x multipliers being less stable than 19 or 21, which this guide doesn’t mention at all. Are there other tidbits that have been discovered or fine tuned since? Either way I can see this is still a fantastic all in one go to guide especially for a first time oc’er. Incredibly easy to understand and I am very happy I am finally able to do this with my adequate cooling. Thanks goes to the author for his help, which if I am any proof will guide people for years to come – as long as bloomfields are still in use, at the very least.

Jesse
2 months ago



How hot should you be after only the first bclk increases and stress tests? Like literally setting the qpi/vtt, low spd, and low multiplier in those first steps. With my new phanteks cooler (the big one) my temps before changing anything were good, high 30s idle 55 load. After resetting to optimized defaults & beginning this guide, the first test at 15x150bclk I was 70 load. Now 80-83 at 180 bclk.

Nowhere I can find anybody complaining about increased temps from simply raising bclk, especially by utilizing this guide’s method of lowering the multiplier to isolate first. Running i7 930 on x58a-ud3r following sample 1 roughly.

Mind you I’ve yet to blue screen but consider a failure in prime 95 a failure. I’ve upped qpi/vtt by 0.020 once, to 1.220. I’m worried what I’ll see when I get deeper into this guide… Why would my temps go so crazy?

Dickle
9 months ago



@ miahallen, Cool Story Bro.

Long shot computer problem
10 months ago



[...] so has reverted to defaults only problem the defaults never worked properly. i overclocked it using this guide as a basis system specs PSU Antec cp 850 CPU / Processor i7 950 CPU CoolerProlimaTech Super Mega [...]

Looking for great RAM OC'ing advice/tips/articles
10 months ago



[...] the RAM overclocking from the CPU overclock, this article explains that concept. http://www.techreaction.net/2010/09/…-and-gulftown/ And for RAM overclocking, per se, http://www.hardwaresecrets.com/article/152 There aren't any [...]

New to Overclocking. i7 950 Trying to join the 4.0 GHz Club.
12 months ago



[...] you if you fill in your system specs (Settings/Edit Profile I think…) As well as the guide here: 3 Step Overclocking Guide – Bloomfield and Gulftown | TechREACTION Guide to Overclocking the Core I7 920 or 930 to [...]


« Older Comments




Leave a Reply

  Cancel Reply


subscribers

0

followers

Visit the TechReaction.net Forums
  • Sponsor


  • Find us on Facebook

  • Sponsors

  • Popular Categories

    Adapters AMD Apple ATI Audio Cases Cloud Computing Contests Cooling Displays DVD Events Extreme Featured Gaming Guides HTPC Hyper-v Intel Interviews Memory & Storage Microsoft Mobile Modding Motherboards & Chipsets Networking Nvidia Overclocking Peripherals Portable Devices Power Supplies Previews Processors PS3 PSP Reviews Site News Software Storage Uncategorized Video Video Cards Web XBOX 360
  • Categories

    • AMD (120)
    • Apple (9)
    • ATI (43)
    • Audio (40)
    • Cases (128)
    • Cloud Computing (3)
    • Contests (2)
    • Cooling (124)
    • Displays (2)
    • Events (23)
    • Extreme (54)
    • Featured (130)
    • Gaming (51)
      • PS3 (3)
      • PSP (3)
    • Guides (31)
    • HTPC (15)
    • Hyper-v (1)
    • Intel (103)
    • Interviews (1)
    • Memory & Storage (109)
    • Microsoft (14)
    • Mobile (5)
    • Modding (32)
    • Motherboards & Chipsets (82)
    • Networking (6)
    • Nvidia (42)
    • Overclocking (159)
    • Peripherals (104)
    • Portable Devices (36)
    • Power Supplies (14)
    • Previews (23)
    • Processors (64)
    • Reviews (365)
    • Site News (40)
    • Software (19)
    • Storage (5)
      • Adapters (3)
    • Uncategorized (58)
      • DVD (2)
    • Video (5)
    • Video Cards (51)
    • Web (2)
    • XBOX 360 (3)



Copyright © 2012 TechReaction.net - PC Hardware Reviews, Guides, How-To's and News.