Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Need help OC my SB 2600K

Featured Replies

Gentlemen, My new SB system is complete and ready to be OC. Please help me with a step by step guide or process. I don't want to fry my 2600K. Here's what I have: Asus P8Z68-V ProI7 2600K8 gig of OZ cas 7 memory (These are my old ones) 7 7 7 24 cas 7. Even though I've asked Dario, Stephen, and Alain to chime in, I welcome all ideas. I want this to benefit everyone. Thanks a million.Jose

MSFS

That was fast Jose :) A basic guide to overclock Sandy Bridge (copy-pasted from the PMDG forums):You'll need:A "K" version Sandy Bridge CPU coupled with a P67 or Z68 board (preferrably with full VRM support) and a proper aftermarket heat sink fan or WC loop to cool your CPU downDo not:Overclock using any auto-tune option in your motherboardOverclock using any kind of windows based tool.Always set everything manually in BIOS and double check your inputs are correct / within specs in windows---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------1.- Test the system at stock settings for a reasonable period of time (at least one week). Download all the necessary tools:- CPU-Z 1.57 to monitor Vcore, CPU and memory speed and timings- Speedfan 4.44 and/or HWMonitor to contrast with CPU-Z and make sure you have correct readings- CoreTemp to monitor temperatures (and RealTemp)- Prime95, Lynx, OCCT to stress test- Memtest (latest version, compatible with SB)Stress test on stock settings and make sure your max temps are fine (50 - 60ºC or so, depends on your cooler and ambient temps)Run a couple of runs of Memtest to ensure your RAM is fine2.- Keep your memory at default speed and timings and start with manual Vcore and LLC at High, Ultra High or Extreme to limit or cancel Vdroop. Disable EIST and C1E (so you can see your actual cloks and Vcore even when idle)Try a moderate OC first. Something like 1.3V and 4.3 - 4.4GHz. If you want to go for a higher OC straight away, don't exceed 1.37 - 1.38VBoot into windows and open CPU-Z and CoreTemp. Make sure your CPU clock is where you set it to, temps are in check and Vcore is ok too (max 1.37 - 1.38V, but with LLC on and C1E disabled it should be pretty close to what you set in BIOS)If CPU frequency, temps and Vcore are fine, stress test with Prime95 or OCCT for half an hour more or less.Keep a close look at your core temps and CPU-Z for Vcore: that's the Vcore that matters, the one you get at full load. If it's significantly lower than your idle Vcore, raise your LLCIf it passes the test, you can try lowering your Vcore or raising your clocks. Repeat until you get your desired clocks or maximum safe full load Vcore.Once you are done, fine tune your overclock stress testing for 8+ hours. If it fails raise your Vcore one notch, of course without exceeding 1.37 - 1.38V at full load, and repeat until you pass at least 8+hours. Monitor temps and VcoreYou know now what Vcore you need for your OC.3.- Obtaining the offset value to get the Vcore at which your OC was stable in the previous step (in manual mode)this are the approximate values for each LLC level. I believe this table was made at 4.6GHz. Not sure thoughoffsetm.pngSo for example, if you want 1.35V and your LLC is set to Ultra High, set your offset to -0.010.Boot into windows and open CPU-Z. Stress test for a minute to see what full load Vcore you have and see if your Vcore is where you want it to. Lower? raise it in BIOS and try again. Higher? lower it in BIOS.Once you have your offset, you can enable C1E and EIST. Check if it throttles down to 1.6GHz and 0.9 - 1V while idle, and stress test again for 8+hours. Monitor temps and Vcore while you do4.- You have (hopefully) a rock solid CPU overclock now, time to focus on memory speed.Set your RAM speed, timings and voltage at what your sticks are rated and stress test for 8+hours. Monitor temps and Vcore while you doIf you want to overclock your memory, do so, and stress test for 8+hours. Monitor temps and Vcore while you doSB is not so picky with memory as previous generations were, so you could try setting your RAM at it's rated speed, timing and voltage from the beginning and skip this step, but I still prefer the old school wayNOTE: maximum core temp, 80ºC under full load. Maximum Vcore 1.375V at full load

I don't quite understand the thread. You are old overclocker, do read these forums too, saw the SB overclocking tutorials, possibly went over many threads about overclocking, what's stopping you from starting to overclock it? Can't do much burning on the CPU if you don't overdo it... And, noone is going to save you from the possibility of the CPU-burning... it's always a risk. And it could burn at 4.0 already if you are unlucky. Though higly unlikely. Here is my favorite though:http://www.overclock.net/intel-general/910467-ultimate-sandy-bridge-oc-guide-p67a.htmlIt explains well what is what.

  • Author

Impressive performance even at stock speeds. Still learning the BIOS. I can't seem to raise the multiplier above 35. Maybe I miss something.

MSFS

Impressive performance even at stock speeds. Still learning the BIOS. I can't seem to raise the multiplier above 35. Maybe I miss something.
Why can't you raise it? You should be able to boot into windows just by changing the multi to 40. Without any Vcore change too.

You'll need to set "AI Overclock Tuner" to Manual before you can raise the multiplier index.php?app=core&module=attach&section=attach&attach_rel_module=post&attach_id=28833

  • Author

As I said, I'm still learning the new BIOS. Just to test I ran it at auto and now I understand why the performance is so good. It does it all for you: 896Test_CPUZ.jpg I'm still going to try to manually OC to 4.5 +. For now, I'll test without manual OC. I am having some minor stutters in the FTX world, but I think it's probably a BP issue. I think?

MSFS

I would disable Hyperthreading. If you need it for something else, save two profiles in BIOS with and w/o HT

  • Author

I certain will. Thanks.

MSFS

  • Author

I just want to say that this is the best money I have ever spent on an upgrade. I wish I would have done this sooner. High 20s and 30s everywhere and smooth simulation, without the need to OC manually.

MSFS

A suggestion: I discovered something lately. I had my FPS limited always in FSX, around 30. While it mostly gave nice performance, it has always been stuttering a bit. Try setting 60, which will in most cases give you 60fps while flying, will drop to 20-30 in the airports, but I get less stuttering than when limited on 30. Good to know you are satisfied with performance! It's not that hard to OC a 2600K. And yes, disable HT for FSX. You are rarely going to need it.Be careful with Auto Voltages, especially Vcore, if going north of what you have now, Vcore might tend to jump up quite a lot. Just go with manual Vcore (preferably offset), all depending what LLC you are commanding. I prefer LLC off, inspite all the "very high" suggestions. My machine is more stable with LLC at off.

  • Author

Word Not Allowed, Thanks for your input. I use the external limiter set to 30 and it works great. It's only in the forest ares of FTX that I experience some micro stutters, but I found a way to rectify that in the past with a different BP setting. So far so good. I'm ready to test manually. I saw the post to Ryan. I will try using those simple steps.

MSFS

  • Author

So far I'm stable at 4.5 with 1.35 volts. I might try to go higher. Probably not necessary.

MSFS

So far I'm stable at 4.5 with 1.35 volts. I might try to go higher. Probably not necessary.
There is some push from 4.5 to 5.0, but probably not worth for most of people... not really worth going 4.8 to 5.0, I'm doing it for the numbers :D
I just want to say that this is the best money I have ever spent on an upgrade. I wish I would have done this sooner. High 20s and 30s everywhere and smooth simulation, without the need to OC manually.
I told ya! tongue.png

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.