Overclocking my Q6600 soon


Recommended Posts

Just thought I would post to get some ideas of what this can do, it is the G0 stepping, and I run water cooling.

Now, here is the cool part, I also have an Antec 900 case (very bada-- case IMO), my Q6600 idle temps are 25C. How is that for an idle temp on a quad? Good? Bad? Before you respond, take into account that the computer room it is sitting in has an ambient temp of around 27C, so basically my water cooling is keeping my stock Q6600 below ambient room temps. The highest I have seen it (havnt gone 100% load for hours, but have played games for hours) is 31C.

That being said, what would you guys estimate an achievable overclock is just based on the temps I am getting fully stock in a fairly high ambient room temp?

The ram I am getting here soon is DDR2 1000, I plan on probably setting it to 800 so it has more overhead for the overclock, good or bad idea?

Another question I have is what is a good voltage for a high O/C on a Q6600?

Last, the setting that underclocks your processor when its got a low load on it, is it ok to keep that on when O/Cing or should that be disabled, and what exactly would it be called in the BIOS?

Just trying to get all the info together in one spot before I get started.

EDIT: Ok, I went ahead and threw a small overclock on it, from 2.4 up to 3Ghz (25% O/C) and turned the voltage to 1.35, ran prime95 (the multi-core version) for ~10 minutes (under max heat mode), came back and it was sitting at a nice 33C, room temperature is at ~26.6C (80 F). I feel confident I will be able to hit a pretty decent overclock with it. Yes I know a 10 min test isnt much, but I figure in all practical usage, 10 minutes of 100% cpu usage on all 4 cores isnt pretty practical when the main usage of the computer is gaming.

EDIT2: As reference, my old case (crappy 4 year old cooler master) ran an AMD 4200+ X2 at 40C+ idle (around 50C load), with the same water cooling, and the same block (different mounting on it). Goes to show you what a case with good ventilation can do, even when you have water cooling.

Edited by mwpeck
Link to comment
https://www.neowin.net/forum/topic/663690-overclocking-my-q6600-soon/
Share on other sites

Okay, there are a few things I'd like to point out in the your second paragraph, don't take them too personally. First off, even though no one should care about idle temperatures, people do for some reason. Why shouldn't you care? Well, unless your chip doesn't play nice with subzero temperatures (it's happened before on XS), then the lowest temperature the chip is going to reach is not important. It is the highest temperature that defines when the chip will throttle itself and then when it will shut down. Since you couldn't have a cold bug issue, we can go ahead and not care about your idle temperatures.

Next, the nature of the digital thermal sensors used by these new chips from Intel translates to them not being very accurate in load temperatures, but even more so with idle temperatures. The temperatures you're looking at are most likely found using this formula: Tjunction Max - Delta to Tjunction Max (read from the on die registers) = Temperature. Tjunction max is individually calibrated per chip at the factory *and* we don't have numbers released for 65nm chips, unlike the 45nm chips. The register reads the delta from tjunction max as an offset of zero, with the 45nm chips it "bottoms out" at 20?C under Tjunction max, some people have done testing (here) so we know tj max is still pretty far away from your 25?C.

Next, there is NO WAY for your chip to run under ambient temperatures unless you have a chiller. If you didn't have a chiller, then that requires evaporative cooling methods with a coolant with a wet bulb point much lower than the ambient temperature. Water's dew point is relatively close to ambient temperatures, so it does not possess that property. Then we consider thermodynamics concepts and we'll realize that your loop cannot be cooled to sub ambient temperature. The transfer of heat from the water to the air is done via the fans and the radiator, however it is the temperature of the air in the end that is one of the determinants in the delta between water entering the radiator and the water leaving as it is the medium that is carrying away the heat. If your water was running cooler than your ambient temperature, it will absorb heat from the environment until the two reach an equilibrium point. It's like your prcocessor running cooler than the temperature of your water, it's possible..but it won't stay like that for long. I'm not sure if your entire second paragraph was some attempt of showing off or not, but either way it doesn't really add much to your thread. Idle temperatures are useless and it's unlikely that you're running cooler than ambient.

Next up, to actually answer your question. No on can tell you what you can overclock, every system is different, each chip has minor defects as do northbridge chipsets, RAM chips, the motherboards themselves, your power regulators, etc etc. So, you're going to have to try it yourself. With that said, you should be able to pull of 3.6 GHz with your water (no idea what board you have..if it's an Nvidia based board then probably not).

500?9 would be quite a feat, 400?9 is pretty good for most Q6600's, however you've already got the RAM so there's nothing you can do about it now. DDR2-1000 won't hurt, that's for sure.

A good voltage? Again goes back to each system being different, you'll have to do it yourself. The voltage ceiling for the 65nm chips seems to be around 1.6v though, you'll want to take this reading at idle via CPU-Z or something. Why idle? Same concept as temperatures, it's the highest value and also most likely the only value that will affect longevity.

You'll want to disable Speedstep and C1E until you've found a stable point. It's just one more factor to remove from the equation as the feature drops the vcore, in addition to the multiplier, which could lead to instability.

I've noticed most of these threads end up with "just try it".

Thanks for the reply, I wasnt trying to show off, I just found it interesting in how cool it was running. For reference, the individual cores are running between 28-35C when its idle (at 25C). I guess what I need to ask is how is 33?C for 10 minutes of full load in a 27?C room?

I understand theres always differences in hardware, no two setups no matter how similar are guarenteed to get the same overclock, what I was wondering is how much overclock room does that leave having a load temp not a whole lot higher than ambient temp?

33?C leaves you plenty of room from a temperature standpoint, just wanted to point out that it's not possible to run sub ambient so your temperature reading is probably inaccurate.

Anyway, I guess the short answer to your question is.....temperature is not a factor in your overclock right now.

edit: Oh yeah, just curious but what are you running in your loop?

Would it just be an inaccurate sensor or the program? I sort of doubt the program (everest) is wrong because it shows the same temps for each individual core as core temp does. Under load the hottest individual core is around 45?C, the coolest can be down around 35?C.

And to answer your first paragraph again, don't look at absolute temperatures. Look at the term coined as "delta to Tjunction max" which is directly from the on die registers.

And to further elaborate, Core 2 Duo chips (Conroe and onward) use what is called "tjunction maximum" to determine absolute temperatures.

The formula is roughly as follows:

Tjunction Max (a number, which Intel has not released for 65nm chips, but for 45nm dual core chips it is 100C) - Delta to Tjunction max (and from this point onward will be called delta) = CPU Temperature

Now what is the problem with this formula, and why should you be looking at the "delta" and not the "CPU temperature" ?

Well to make an extremely long story short, since the "delta" is the only actual number that the CPU is providing you with, it is in fact the "most" accurate value that is provided to the CPU owner. In order to calculate absolute temperature (CPU temperature; refer to formula above) one must know the Tjunction maximum (which should be provided from Intel, and at this point is not available for 65nm chips).

Now what is this "delta" and "tjunction max" anyway, and why is it important?

Tjunction maximum is the temperature at which the CPU sends out the "PROCHOT#" signal and tells the CPU fans to go to 100% in an attempt to cool your CPU. Now what is important to understand is that, this tjunction maximum is not available for 65nm CPU users (and this will be the third time that I state this fact). So this translates to the following, since we don't know the Tjunction maximum, we will be forced to look at the "delta" which is the distance (in degrees C) TO the tjunction maximum. And IN THEORY, one should be be able to run a CPU at 1C (delta to tjunction max, or distance from tjunction max) 24 hours a day 7 days a week 365 days a year, for 3 years; and if your CPU fails (assuming you have not overclocked) Intel will give you a new chip (this analogy was taken from a user at HardForums.com)

Now with that in mind, remember that the Tjunction max is the temperature at which PROCHOT# signal is sent, and does NOT meant that your CPU will spontaneously combust at that temperature, any further from the Tjunction max, and your CPU will shutdown to save itself.

And also remember, that the only relatively accurate value that the CPU provides to the user, is the delta to tjunction max. The actual value of Tjunction maximum for each individual chip is (at this point in time) unknown.

So to make an extremely long story short in a small equation:

A (Tjunction max) - B (Delta or distance FROM Tjunction max) = C (CPU Temperature; The absolute temperature)

Now, if the CPU is providing us with B. And Intel has provided the very rough number of 100C (for 45nm C2D chips).

Then that must mean that if A = 100, and B = Let's say 55 in this situation.

Then that must mean that A - B = C which means 100 - 55 = 45.

BUT, here is the catch! For each individual processor, the "A" is different (maybe one or two degrees, maybe by one hundredth of a degree; we will never know).

So if A is unknown, and B is known, and in order to find C we need to know A. Then really, all we know is that as long as "B" remains ~10-20C, then my CPU will not reach the point at which PROCHOT# signal is sent. :)

It's like using the Pythagorean theorem or Sine , Cosine and Tangent to find angles and lengths of a side in a right triangle. You don't want to use calculated values to find other values. You want to use the numbers that are given to you, and that you know for sure 100% are correct. And in this case, you don't want to use A to find C, because we are not sure of what A is in the first place, so just make sure B never gets lower than 10C and you will be fine. ;)

Edited by shift.

Thanks for the replies, I was at first going to stick it on 3Ghz and just let it go at that, but my average FPS in CS:S's benchmark (I know not the best thing to use) went up about 20FPS just by going from 2.4Ghz to 3Ghz.

That being said I think I will likely do what I have done on all my AMD chips (this is my first intel chip :D), and thats, overclock till it doesnt post (or becomes unstable) then back it off until its stable. That seems to be the general answer and is likely the best way to go about overclocking, push it till it errors, then lower it until its nice and smooth.

Would it just be an inaccurate sensor or the program? I sort of doubt the program (everest) is wrong because it shows the same temps for each individual core as core temp does. Under load the hottest individual core is around 45?C, the coolest can be down around 35?C.

Okay now this is kind of confusing. What is this 25?C reading from? Your cores sound about right as they're all above ambient, is the 25?C the Tcase or something?

and lol I shift, I read that exact same thread with the analo:p. :p

Also, mwpeck check out this database, it's the one i've found with the most entries:

http://www.hardforum.com/showthread.php?t=1138241

It's too bad XS doesn't have something similar, but they do have this. You'll just have to work harder for your information.

http://www.xtremesystems.org/forums/showth...highlight=q6600

I'm not exactly sure what the 25?C is reading from, its just labeled(in everest) as "CPU", the 25?C doesnt show up in Core Temp, but core temp just shows the internal core temps. I have a feeling the 25?C is the temp if you were to touch the outside casing of the processor(probably the Tcase).

Like I said, with the same cooler on my 4200, the "CPU" reading was never lower than 40?C.

Ok, it ran overnight and stayed at the same ?C to Tjunction max, I overclocked to 3.6ghz and I after re-adjusting the voltages, I get a hard lock after about a minute of stress testing. Hard locks are something I havnt seen in my previous overclocks, what from overclocking can cause a hard lock? I figured maybe it cannot handle that high FSB (bought this as a budget board way back in the workstation I put it in), but I want to check to be sure.

Sorry for the double post (cant edit my last one), got it to 3.4Ghz stable, I'm pretty happy with that as its still 400Mhz above the previously highest processor I had (when I had my FX, it ran at 3Ghz), and its quad to boot. That being said if anyone knows what would have caused the hard locks at higher speeds, let me know, I dont plan on pushing it higher unless I can find for certain whats causing the locks. Core temps at this O/C vary from 38?C to 46?C, rather low IMO, but then again I am running water cooling.

Well, like I said, if anyone has any thoughts on the hard locks, let me know, otherwise I'm happy sitting at 3.4Ghz.......I have a feeling the hard locks are from the MOBO FSB, its an nVidia 650i chipset which has a rated max FSB of 1333 Mhz, I'm running it stable at 1512 Mhz.

Ok, FSB of 1600 (or 400, w/e number you wanna go by) didnt freeze with a multiplier of 8x, but it did fail a prime95 test after about 8 minutes, FSB of 1556 (or 389) seemed to not freeze and it lasted at least 10 minutes (when I stopped it) in prime95.

Would that mean my CPU's limit is somewhere between 3.4 and 3.5 Ghz (runs fine on 9x at 3.4 ghz but not at 3.5 ghz), or is there another setting or something I could change that would fix it (like possibly raising the voltage a little more)?

EDIT: Just tried 3.5 with a higher voltage and it froze after about 11 minutes of prime95, hard lock, forced to reboot it. Think somewhere between 3.4 and 3.5 is just the limit for my proc? Either way, I'm happy with what I was able to get.

Edited by mwpeck
I'm the kind of person who likes overclocking, but doesnt like spending hours getting the settings tweaked just right, think I'll just stick with my 3.4 and be done with it, decent enough O/C for me.

3.4 isn't bad for a q6600. There's not much to be gained going to 3.6. Tweak your RAM timings and tRD as much as you can.

You can also try Set Affinity for a slight performance boost. It can assign single-threaded programs to core 3 & 4 so that they don't utilize the first two cores which most Windows software uses. This way you can get use out of all four cores. Assign all the stuff that runs in the background like AVs, firewalls, hardware utilities to cores 3 & 4. You could also limit programs to a core(s) so that they can't lock up your PC because of 100% CPU usage.

http://www.geocities.com/edgemeal_software...inity/index.htm

3.4 isn't bad for a q6600. There's not much to be gained going to 3.6. Tweak your RAM timings and tRD as much as you can.

You can also try Set Affinity for a slight performance boost. It can assign single-threaded programs to core 3 & 4 so that they don't utilize the first two cores which most Windows software uses. This way you can get use out of all four cores. Assign all the stuff that runs in the background like AVs, firewalls, hardware utilities to cores 3 & 4. You could also limit programs to a core(s) so that they can't lock up your PC because of 100% CPU usage.

http://www.geocities.com/edgemeal_software...inity/index.htm

I'll think about setting the affinity, as for my ram, it was running at (auto detected) 5-5-5-18, it was rated at 4-4-4-15, so I tuned them down to their rated speeds (lower timings) and its running fine.

Quick question about Affinities.......if I set a program (lets say my internet browser) to Affinity 4, if I reboot (or just close and reopen it) will it default to Affinity 4?

stumbled across this thread after inheriting a pc. looks like a stock cooler, no name that sticks out. overall I am getting idle temps in the 50's and under some load I am in the 60's and games I can see 70 and what looks to be 75 max. Is this too hot? (I am new to overclocking) also please keep in mind I am running a 280 gtx as well.

Edited by MiPeNiS
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Flameshot 14.0 Final by Razvan Serea Flameshot is a free and open-source, cross-platform tool to take screenshots with many built-in features to save you time. Using Flameshot is as simple as launching, dragging the selection box to cover the area you want to capture, making annotations as needed in on-screen and saving the shot to your computer, all with a very simple and straightforward interface. Flameshot allows users to simply upload their screenshots directly to the cloud in order to easily share it with others. You can upload your image directly to Imgur with a single click and share the URL with others. In-app screenshot editing - You can choose to add an arrow mark, highlight text, blur a section (blur or pixelate an area), add a text, draw something, add a rectangular/circular shaped border, add an incrementing counter number, and add a solid color box with Flameshot's built-in editing tools. Command-line interface (CLI) - Flameshot has several commands you can use in the terminal without launching the GUI via a command line interface. The command line interface lets you script Flameshot and use it as the subject of key binds. Flameshot 14.0 release notes: This release brings major improvements to multi-monitor support, fractional scaling support, new capture workflows, and a long list of bug fixes across all platforms. Changelog: New Multi-Monitor Capture Workflow New monitor selection screen before capture for better multi-monitor and mixed-scaling support. Option to auto-capture the monitor under the cursor (X11 & Windows). Tray menu can directly select a monitor. Linux Improvements XDG Desktop Portal is now the primary screenshot method. Added legacy X11 fallback option for minimal window managers. New D-Bus capture API for scripting and automation. Windows Enhancements Global screenshot hotkeys now supported (not limited to Print Screen). New portable mode stores settings next to the executable. Clipboard now always uses PNG format for better compatibility. CLI & Platform Updates Redesigned flameshot screen command with per-monitor capture support. Added native Nix Flake support. More compact launcher UI and improved update notifications. Major Fixes Multiple Wayland stability fixes, including KDE Plasma crash fixes. Clipboard compatibility improvements for GNOME, Wayland, X11, Windows, and macOS. Fixed D-Bus hangs, capture crashes, and HiDPI region issues. Other Changes Dropped Ubuntu 20.04 (Focal) support. Updated translations and build infrastructure. Intel macOS builds are no longer provided. [full release notes] Download: Flameshot 14.0 | 18.1 MB (Open Source) Download: Flameshot Portable | 53.0 MB Links: Flameshot Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Helium Browser 0.13.4.1 by Razvan Serea Helium is a private, fast, and honest Chromium-based web browser — built for people, with love. It offers the best privacy by default, unbiased ad-blocking, and a clean experience free from bloat and noise. Proudly based on Ungoogled-Chromium, Helium removes Google’s clutter while keeping a fast, efficient development pipeline. With thoughtful touches like native !bangs and split view, Helium is a people-first, fully open-source browser that puts control back in your hands. Privacy, security, and control come first. Ads, trackers, and third-party cookies are blocked automatically, HTTPS is enforced everywhere, and all Chromium extensions work seamlessly — while Google can’t track your activity. Helium’s 13,000+ offline-ready !bangs let you jump straight to sites or AI tools like ChatGPT instantly. Open-source, people-first, and unbiased, Helium delivers a browsing experience that’s fast, secure, and free from noise, ads, and compromises. Helium Browser key features: Performance Fast, efficient, and lightweight — built on Chromium’s optimized engine. Energy-saving and consistent — stays fast over time without slowing down. No bloat — stripped of unnecessary components for maximum speed. Minimalist interface — compact, clean, and distraction-free. Customizable toolbar — hide elements you don’t need. Smooth and stable — no flicker, lag, or animation glitches. Comfort-focused experience — intuitive and unobtrusive. Privacy & Security Best privacy by default — blocks ads, trackers, phishing, and third-party cookies. Unbiased ad-blocking — powered by community filters and uBlock Origin. No telemetry or analytics — zero background web requests on first launch. Strict HTTPS enforcement — warns for insecure sites. Passkeys supported — modern authentication made simple. No built-in password manager or cloud sync — your data stays yours. Extension Compatibility Full Chromium extension support — including MV2 extensions. Anonymized Chrome Web Store requests — Google can’t track extension installs. Extended MV2 support — maintained for as long as possible. Smart Features Native !bangs — browse faster using 13,000+ offline-ready shortcuts. AI integration — use !chatgpt and others directly from the address bar. Offline functionality — bangs work without an Internet connection. Philosophy People-first design — open source, transparent, and community-driven. No ads, no noise, no bias — privacy and honesty over profit. Helium Browser 0.13.4.1 changelog: 0a4f1149 revision: bump to 4 (#1969) 4848de1f helium/core: enable the chromium screenshot feature (#1968) e0dec3f5 onboarding: integrate strings to i18n system (#1948) 417fa5bc i18n: fix newline parsing for onboarding 7a339b39 i18n: add foraged translations for onboarding 4f090cff i18n/generate: add handling for onboarding strings bfe48d58 i18n_apply: manually override parent grd logic for onboarding strings ab214e3c onboarding: bump in deps, wire up grdp afa6a059 helium/core: disable pdf infobar feature (#1965) eba585e7 helium/ui/vertical: fix new tab button alignment and icon size (#1964) 6ecfc9e0 helium/ui/tabs: fix horizontal tab hover background color (#1963) 3db87dc0 helium/ui/tabs: fix new tab button hover/press colors (#1962) 6bbdcc3e helium/ui: improve tab group UI in all layouts (#1961) 53deb314 helium/ui/tabs: enable tab group hover cards e93aece7 helium/ui/vertical: fix tab group appearance, prevent line overlap 629f5495 helium/ui/tabs: restore solid group header colors, enable new colors 961c962e helium/ui/tabs: move horiz tab group underline to bottom, make it thick c96deab6 merge: update to chromium 149.0.7827.155 (#1959) 36db56b4 i18n: update source.gen.json 5ce006ae patches: refresh for chromium 149.0.7827.155 b4c1ea62 merge: update ungoogled-chromium to 149.0.7827.155 4e5e8671 Update to Chromium 149.0.7827.155 08a3e7da helium/ui/layout: disable mute on collapsed vertical tabs (#1778) a0a5bbaf helium/core: simplify context menu and prevent huge widths (#1951) c4732aac devutils/i18n: add forage command (#1944) 11d16986 devutils/i18n: add an option to translate using local CLI tools (#1942) d820c3a2 i18n/prompt: tighten translation rules to prevent common errors (#1940) cf827007 Update to Chromium 149.0.7827.114 6e3d5164 Update to Chromium 149.0.7827.102 Download: Helium 64-bit | Portable 64-bit |~100.0 MB (Open Source) Download: Helium ARM64 | Portable ARM64 Links: Helium Home Page | macOS | Linux | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
    • One Month Later
      eurospharma62 earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      579
    2. 2
      +Edouard
      183
    3. 3
      PsYcHoKiLLa
      75
    4. 4
      Michael Scrip
      74
    5. 5
      neufuse
      64
  • Tell a friend

    Love Neowin? Tell a friend!