Hello everyone. I just built a new computer and am having problems trying to overclock my q6600. I have done a lot of research and it seems that most people can at least get close to 3.0ghz with an aftermarket cooler of some kind. For some reason, I have not been able to overclock my cpu at all. My cpu also seems to be idling at an elevated temperature (around 45-50) for having a cooler installed.
I have a feeling that my cpu is bottlenecking my performance in demanding games such as Crysis (where my performance has been HORRIBLE). I would think that with my setup, I should easily be able to get at least 3.0ghz out of my cpu. Anytime that I change anything in the bios and/or with asus's program in windows, it will never post on the restart. I am getting quite frustrated and would appreciate any advice you guys could give.
I am not anywhere near being called an expert when it comes to things like this, as this is the first time attempting to overclock a computer of mine.
Here's my setup.
q6600 at 2.4ghz with Thermaltake CL-P0114 120mm cooler Asus p5n32-e sli 680i mobo 2x BGF 8800gt superoverclocked 512 MB in SLI 4gb Patriot DDR2 800mhz 4-4-4-12 extreme performance ram Soundblaster x-fi extremegamer Windows Vista Home Premium 32 bit Cooler Master Real Power Pro 1000w psu Cooler Master Cosmos 1000 case
Here's some pics of my info from cpu-z and coretemp 0.95.3 while sitting at idle.
Here's the pics of my 3dMark06 score with...
1280 x 1024 settings.
1920 x 1200 settings
Message edited by sancho on 01-01-2008 at 08:49:43 PM
I recently purchased the same motherboard and cpu and was met with the same problems as you when I tried going past 2.9ghz. By flashing the bios to the 1103 version I was able to surpass 3.0 without any problems. Been running Prime95 for a few hours now, so I am comfortable in saying that this should solve your problem.
Firstly - With that CPU cooler, there is something wrong if your temps are that high. Pull it, thoroughly clean off the CPU/cooler base with isopropyl alcohol, re-apply a *small* amount of thermal grease, and re-install the CPU cooler.
Then:
(1) Reset your BIOS to standard/auto
(2) Update the Bios as mp30 indicates to do
(3) FSB and RAM on most Intal chipsets are linked. So DOWN-clock your RAM before playing with the Front Side Bus/CPU speeds. (i.e. set your 800 stuff to run at 667 before raising FSB) Because when you raise the front side to clock your proc, it's going to take the RAM along for the ride.
Message edited by Scotteq on 01-02-2008 at 02:24:52 PM
------------------------------Which Chip? Well, it depends on which set of thieving b@stardz you choose to support: The ones who use insider trading to enrich themselves while running their company into the ground, or the ones who illegally pay vendors to not support the first group.
Reply to Scotteq
Thanks for the help so far guys. I reset my heatsink using a much smaller amount of AS5 (exactly how much was shown on the directions on their website), and now my idle temps are running right about at 40...so that is a little improvement. Is that still too high, or is that about normal?
I just got done trying to OC this cpu once again. I upped my FSB from 1066 to 1333 (while down-clocking my ram to 677 as you suggested) and windows would not even load. I left all of my voltages on "auto" rather than trying to find a value that will work...do you think this is the reason that I could not get windows to load?
I will try updating the bios as you have suggested and hope that improves things. If this does not work, do you have any more suggestions?
I was getting so frustrated trying to find settings that would work at 1333. It's not that I was displeased with 2.9ghz and just leaving it there, but listening to person after person attest to 3.2+ made me curious. A little investigation into the motherboard revealed a lot of people having the same problem as you and I had and are having.
I didn't try the newest bios version, I rolled back to the older 1103 version that kept on popping up as a solution and it worked perfectly. I can't say that the newest versions won't work as I didn't try them. But, I know that one will.
I used the flash utility in the bios itself, not the version that operates in Windows. Download the bios version, put it on a flash key, and go into the flash utility, it's very simple. There are complete instructions for doing this in your motherboard's manual also.
Sound good, thanks again for you help...I'll give this a try soon. By the way, would you share the settings that you are currently using to overclock your cpu with me? What are your voltages, fsb, etc...?
Off the top of my head: The fsb is at 1333 for 3.0ghz, I pushed the vcore up to 1.35 just to be safe, but I'm not so sure it's necessary and I haven't spent the time to find the lowest voltage that works yet.
No ram divisor, I have the ram and fsb unlinked. I have some sli certified Corsair ram, but the only thing I did was enable the epp settings, which only changes the timings and the voltage and not the speed in my case, but I didn't do any ram overclocking myself.
Those idle temps are fine. I'm running a Q6600 in a micro ATX with admittedly mediocre circulation, and the stock heatsink (with arctic silver 5), and I'm getting around 50*C idle, 71*C full load Prime 95. 2.7ghz OC. Just keep your hottest core under 75*C and you'll be fine. Most people are running this CPU in uber-ventilated towers, and thus conclude anything over 35*C idle unacceptable.
Your problem has got to be your BIOS settings. Have you checked out the Quad OC guide? Have you read your motherboard instruction manual? Temps are the least of your concerns at this point.
Message edited by JJBlanche on 01-05-2008 at 04:52:09 AM
------------------------------"Contrariwise," continued Tweedledee, "if it was so, it might be; and if it were so, it would be; but as it isn't, it ain't. That's logic."
Reply to JJBlanche
You are about to answer a thread that has been inactive for more than 6 months. If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.