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

3 Step Overclocking Guide – Bloomfield and Gulftown


Posted by miahallen on 07 Sep 2010 / 106 Comments
Tweet



Step 2) Optimize Memory Frequency & Uncore

System Memory Multiplier (SPD)

The next step is to find the limit of your memory.  In order to do this, we need to prepare you to meet your memory overclocking goal.  Start off this step be entering the BIOS and setting the bclock frequency back to 150MHz.  Because we have already been through the range of bclocks from 150MHz to 200MHz (or whatever YOU reached), we already know that the bclock and uncore will be stable with these settings.  So that effectively allows you to go back through the same range again, changing only the variable of memory, so that you’ll KNOW that that any instability is memory related.

To do that you need to change your System Memory Multiplier (SPD) to a ratio that will allow you to push the blcock back up to your goal, whichout exceeding the memory’s rated speed.  Also, manually configure the memory timings according to the manufacturer’s specifications.  There will probably be many sub-timings in your BIOS that you could change, but only change the timings specified by the manufacturer, the others leave on auto.

Lets look at the sample systems for an example, for those systems you would configure the System Memory Multiplier (SPD) as follows.

  • Sample #1 – set the System Memory Multiplier (SPD) to 8
  • Sample #2 – set the System Memory Multiplier (SPD) to 10
  • Sample #3 – set the System Memory Multiplier (SPD) to 12

For the sample system #1, the goal is 180MHz bclock, the multiplier is 8, and the memory is rated at DDR3-1333.  If we were successful in reaching the 180MHz bclock goal, the memory would be at 180×8 = DDR3-1440.  This is about an 8% OC and within the 10% I recommend limiting yourself to for this step.

For the sample system #2, the goal is 200MHz bclock, the multiplier is 10, and the memory is rated at DDR3-2000.  If we were successful in reaching the 200MHz bclock goal, the memory would be at 200×10 = DDR3-2000.  This is the memory’s rated speed and within the 10% I recommend limiting yourself to for this step.

For the sample system #3, the goal is 200MHz bclock, the multiplier is 12, and the memory is rated at DDR3-2400.  If we were successful in reaching the 200MHz bclock goal, the memory would be at 200×12 = DDR3-2400.  This is the memory’s rated speed and within the 10% I recommend limiting yourself to for this step.

In the same way, set your multiplier according to your goal, so as to prevent more than a 10% overclock on your memory.  As a generalization, memory rated at lower speeds typically has more overclocking potential than higher rated memory.  My suggestion for now is to focus on getting the IMC overclocked to the memory’s rated speed (cause remember, the IMC is only rated to run at DDR3-1066).

Instead of overclocking memory, I place a higher value on tightening up timings.  Take sample #2 from above, it has DDR3-2000 CAS9 memory.  You’ll get better day-to-day performance out of that memory by tightening the timings down to CAS8 level, as opposed to overclocking the speed to DDR3-2100…..not only that, but tightening the timings is almost always easier than increasing the speed.  Again, I’m not going to get into detail here because tangible differences on a daily system will not exist.

DRAM voltages

There are two voltages we need to focus on in this section, the QPI/VTT voltage you’ve already become familiar with, and the DRAM voltage itself.  QPI/VTT is already high enough to support your bclock and uncore goals, but as we push up the speed of the IMC (which is also part of the uncore), the QPI/VTT voltage may need a bit more.  This is especially true if you are running with all 6 memory slots populated, or if you’re using newer 4GB DIMMs, these configurations can put a lot of added stress on the IMC and require extra QPI/VTT voltage to retain stability.  For all three sample systems, set the DRAM voltage manually to 1.65V (or 1.66V if 1.65V is not possible).

Testing for highest stable memory frequency

Now start up your selected test program, for example OCCT (RAM) 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.0125V, 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.

Just as you did in step one, if needed you can follow the same procedure for fine tuning here.

After you have reached your desired goal, be sure to test the overclock with another one hour pass of your selected stability test to ensure the entire uncore is happy with the current configuration.  However, I would add one additional stability test at this point, memtest86+.  IntelBurnTest and OCCT (RAM) are both very good at identifying IMC and memory error, but neither are as strenuous testing the DRAM modules as memtest.  It’s a good way to verify that the memory modules are not defective, and will operate without error.  Run at least one pass, or for 1 hour, whichever is greater.

Congratulations! - You now have a relatively stable bclock frequency and memory frequency.

Step 3)  Stabilize CPU Frequency

Almost there

The last step in this guide is often the first step for users who run into problems and then troubleshoot for days afterward.  Leaving it to the last step makes the task much simpler.  You now have the following settings locked in; QPI/VTT voltage, IOH Core voltage, memory voltage, QPI clock ratio, memory ratio, and memory timings.  That means when we are looking for our highest CPU frequency, there are only two variables we need to play with: bclock and CPU voltage.

Please start by entering the BIOS and adjust the bclock back down to 150MHz, then adjust the CPU clock ratio as follows.

  • Sample #1 – set the CPU clock ratio to x20
  • Sample #2 – set the CPU clock ratio to x21
  • Sample #3 – set the CPU clock ratio to x23

Load-line calibration (“LLC”)

This actually goes by a few different names, but they are all meant as a means to reduce or prevent v-droop.  It does typically ease the overclocking process at the cost of violating Intel’s design specs.  However, overclocking in its essence violates Intel’s design specs, so you’re not breaking any new ground with this feature.  I highly recommend enabling this feature.  High end Gigabyte motherboards have two settings, select “Level 2”.  For more insight on the theory of LLC, refer to this excellent explanation at anandtech.com.  There was also some real world testing recently; feel free to check out Bobnova’s LLC investigation here.

CPU Vcore

That brings us to the first thing that most users want to play with after powering up their new system for the first time: CPU voltage, aka “Vcore”.  As you can see, this is actually one of the last things you should be changing.  I would recommend starting at a nice and easy 1.2V.  Surprisingly enough, many users are able to achieve very good overclocks with this modest amount of CPU voltage.  I would be surprised if sample #1 needed any more than that, sample #2 probably need a bit more, and sample #3 will probably need quite a bit more.

If you are overclocking with power saving features enabled, Gigabyte motherboards will allow you to set the CPU voltage via “Dynamic Vcore” which improves overclocking capabilities while using your power saving features….to unlock this feature; first you have to set the standard Vcore setting to “normal”.  Then set the “Dynamic Vcore” setting to +0.05 and increase as directed below.

Testing for your highest stable CPU frequency

Once the operating system has fully loaded, start up RealTemp.  Now start up CPU-Z and verify that your overclocked settings have been properly applied, and that you are running at your desired CPU, bclock, and memory frequencies.  Each of the sample systems should look like this.

  • Sample #1 – CPU = 3000MHz, uncore = 2400MHz, memory = 600MHz
  • Sample #2 – CPU = 3150MHz, uncore = 3000MHz, memory = 750MHz
  • Sample #3 – CPU = 3450MHz, uncore = 2700MHz, memory = 900MHz

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

Now start up your selected test program, for example OCCT (CPU) 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 CPU Vcore 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 Vcore (as identified above), or maximum safe temperature.
  • Raising the Vcore is ineffective in stabilizing the system.

Just as you did in step one, if needed you can follow the same procedure for fine tuning here.

Is it stable?

So, once you find your highest CPU frequency by meeting one of the criteria above, and run OCCT (mix) or IntelBurnTest (maximum) for one hour minimum.  I’d like to refer to all this testing as “reasonably stability”.  In my experience, the true test of stability is the regular daily operation of your system, doing what you intended it to do.

The reason we use testing programs like OCCT or IntelBurnTest is to simulate a worst case scenario.  I have never seen any real world application come close to generating the heat that IntelBurnTest (maximum) generates.  But there are a few that can come close to OCCT, like folding or crunching for distributed computing projects, encoding high definition videos, or very heavy multitasking.  But even though OCCT or IntelBurnTest (maximum) stress tests tend to generate more heat, they do not always find 100% of instabilities. In my opinion, the ultimate test is to use the system!

Final Words

Well, that about wraps it up.  Believe me, there is so much more to overclocking.  There are SO MANY settings you can continue to fiddle with, you may have a million questions at this point about all of the settings in the BIOS that we never touched.  They’re valid questions, but not meant for this guide.  My goal was for this guide to get you 95% of the way in 5% off the time.  Hopefully you’re there!  The other settings in your BIOS will be needed to get you to 100%….but if I included those things in this guide, it would be 3 times as long, and much more complicated.

Please feel free to comment, and post any questions in the Intel section of the techreation forums.  The community is the best resource to continue pushing your system beyond this guide.  Post a new thread with a very detailed description of which part of the guide you are having problems with, how far your progressed through the steps, and screenshots to help us understand the problem your encountering if necessary.  We will do our best to help you out with any problems you may encounter!

Thanks to Brolloks, noxqzs, Zithras, and many others for their help with this guide.

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
3 weeks 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
3 weeks 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
8 months ago



@ miahallen, Cool Story Bro.

Long shot computer problem
9 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
9 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.
11 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

  • Twitter

    • NEW! 4 Useful Apps to Rescue You from Sticky Situations: Ever experienced a situation that went south so quick... http://t.co/oqZzBNWbIB
    • AMD’s next-gen APUs to boost performance with unified memory http://t.co/b6oWutJoFJ
    • LadySwoop PMS http://t.co/XlE6Ej5sl9
    • NEW! alienvibes W601 2.2 Speakers: Today we got on our review table the alienvibes W601 2.2 channel speaker sy... http://t.co/Ke1BuzliMV
    • I created group Eastern North Carolins Business n' Industry on Linkedin.: http://t.co/3jTTofpmyo
  • 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.