Newb @ OCing Q6600

S

Silvers24

Gawd
Joined
Oct 11, 2007
Messages
514
Just got my PC up and running, with a Q6600 *My guess G0 version, idk for sure though, on the CPu it said SLACR)
Also got a GIGABYTE GA-P35-DS3L LGA 775 & a Tuniq Tower 120.
With 4 GB of Gskill ram.
So what do I need to do?
Would like to at least hit close to 3.6
 
Read this helpful thread first, it's sticked for a reason ;)

After getting through with it, come back and ask questions that seemed confusing. It also helps that you understand what our tips are by reading the guide first
 
I looked it over many times, tried the OC twice, and it failed.
I still dunno wtf I am doing.

Could someone make it a tad bit easier for me? Like maybe I could mirror someone who has the same mobo/CPU & has it OC'd? At least so I know WHAT TO mess with?
 
Silvers24 said:
I looked it over many times, tried the OC twice, and it failed.
I still dunno wtf I am doing.

Could someone make it a tad bit easier for me? Like maybe I could mirror someone who has the same mobo/CPU & has it OC'd? At least so I know WHAT TO mess with?
Click to expand...

Sounds like you're an ultra noob at OCing. Sit back. Watch, listen, read for a while. Over clocking isn't rocket science, but before you corrupt your drives by doing an unstable over clock, do some reading and make sure you get your methods and procedures right before you start. Write out your plan if that helps you get started. If you read around here or on XS forums, you'll find a good deal of information for over clocking on the core 2 architecture.

Don't count on getting the same OC as someone else. You don't know what the average person has done to volt-mod their gear in order to get the clocks they get. Overclocking is easy. Just don't slack off on learning the details through reading and thoughtful experimentation to get a feel for what works. At the very base of overclocking, you need to first learn about the relationship between clocks and voltage. Remember, there are many components in your system with different clocks and different voltages. So make sure you know which one you're adjusting first.
 
I am, however I was able to OC a AMD CPU before, but I took a wild guess at what to set and it worked. (939 socket one, single core I belive)
And so figured it would of been easy to OC a Q6600 lol
 
Silvers24 said:
I am, however I was able to OC a AMD CPU before, but I took a wild guess at what to set and it worked. (939 socket one, single core I belive)
And so figured it would of been easy to OC a Q6600 lol
Click to expand...

do some research using google and browse the forums. There are tons of threads and "how-to"s on overclocking, especially the Q6600 ;)
 
I just don't get it, I have edited pretty much what I know I can edit, when it POSTS I can get it to show 3.0 GHZ or 3.10 (If I set it to 333, or 345) but when it does a Memory Check it shows my memory higher then 800mhz and reboots & resets my OC settings back to stock.

What am I doing wrong? :(
I've tried editing my ram so it shows 800mhz b4 it even posts & it still reboots & resets it. :-\
 
Silvers24 said:
I am, however I was able to OC a AMD CPU before, but I took a wild guess at what to set and it worked. (939 socket one, single core I belive)
And so figured it would of been easy to OC a Q6600 lol
Click to expand...

Good god man. I do not mean to offend...but that strategy is depressingly ignorant to a subject that is not hard or time consuming to learn. I would hate not knowing how to do it right, and not understanding what I'm doing.
 
Silvers24 said:
I just don't get it, I have edited pretty much what I know I can edit, when it POSTS I can get it to show 3.0 GHZ or 3.10 (If I set it to 333, or 345) but when it does a Memory Check it shows my memory higher then 800mhz and reboots & resets my OC settings back to stock.

What am I doing wrong? :(
I've tried editing my ram so it shows 800mhz b4 it even posts & it still reboots & resets it. :-\
Click to expand...

>_<
I've tried getting the 1:1 ratio and such, and still reboots a second time and clears my OC settings.
I've tried adjusting the vcore aswell, and still the same ol crap.
Weird thing is, when I OC it it boots just fine, I get the OK BEEP then after it posts the memory it reboots again & clears my OC settings.

Bad mobo?
 
Try posting a picture of your CMOS settings.
Are you sure you setting the System memory muliplier to TWO and then saving?
 
Don't think I have, i'll try that, also, I have 4x 1GB of G-Skill 800 mhz ram.
With the timings of 5-5-5-12 (I belive)
 
set fsb to 400
set mem ratio to to 1:1

increase northbridge voltage 1 "notch"

increase vcore voltage 3 "notches"

done
 
mxpxrulzz said:
set fsb to 400
set mem ratio to to 1:1

increase northbridge voltage 1 "notch"

increase vcore voltage 3 "notches"

done
Click to expand...

Thanks
However don't work for me.
I give up, this is bullshit.
Does it without fail.
Save to CMOS, it reboots with the new settings, during POST right after the memory is checked, reboots again & clears the OC.
 
Take out all but one stick of memory. Then start with everything set to "auto" and a 9x multiplier on the CPU.

Should be 266 FSB. Memory timings auto, voltage auto, etc. Get it running that way first.


Then, give us some more information, like what speed is your memory?
 
rainman said:
Take out all but one stick of memory. Then start with everything set to "auto" and a 9x multiplier on the CPU.

Should be 266 FSB. Memory timings auto, voltage auto, etc. Get it running that way first.


Then, give us some more information, like what speed is your memory?
Click to expand...

http://www.newegg.com/Product/Product.asp?Item=N82E16820231136

Brand G.SKILL
Model F2-6400CL5Q-4GBNQ
Type 240-Pin DDR2 SDRAM
Tech Spec
Capacity 4GB(4 x 1GB)
Speed DDR2 800 (PC2 6400)
Cas Latency 5
Timing 5-5-5-15
Voltage 1.8V - 2.0V
Heat Spreader Yes
 
Does it overclock at all? By that I mean does it reboot if you make any changes at all to the BIOS settings, or have you just been jumping to a high FSB and wondering why it doesn't work? Try changing the FSB by just a tiny amount, like from 266 to 270, and see if it boots up that way. That doesn't tell you much, but any little bit helps. Also, you might want to provide some more information on what you've tried - what voltages, what FSB speeds, memory setting, etc. That combo should overclock with relative ease, so maybe you're just missing something simple.
 
Forceman said:
Does it overclock at all? By that I mean does it reboot if you make any changes at all to the BIOS settings, or have you just been jumping to a high FSB and wondering why it doesn't work? Try changing the FSB by just a tiny amount, like from 266 to 270, and see if it boots up that way. That doesn't tell you much, but any little bit helps. Also, you might want to provide some more information on what you've tried - what voltages, what FSB speeds, memory setting, etc. That combo should overclock with relative ease, so maybe you're just missing something simple.
Click to expand...

To Leftside: BIOS was the first thing I thought of, didnt help, but they are updated.

Yes it does OC, it boots well, but as I said more then once, during the POST screen after it shows my memory total, it then reboots on it's own, and resets my OC back to stock/default.
(Make it more clearer, never makes it to windows)

K, i'll try to change it just a tiny amount.
The first time I tried OC'ing, I fucked up (before I made this thread) by setting the FSB to 100 (didn't know stock FSB was 266) and got some heavy errors, luckily it resetted back to normal and everything was ok, however I can't OC to 333 or anything. And now I don't even know if I could have had I not made that sort of mistake.
Don't suppose that could be why I am not able to OC is it? For setting it so low in the first place? >_<
 
Silvers24 said:
Yes it does OC, it boots well, but as I said more then once, during the POST screen after it shows my memory total, it then reboots on it's own, and resets my OC back to stock/default.
(Make it more clearer, never makes it to windows)
Click to expand...

Getting through the memory POST test doesn't really qualify as booting well. If you change the FSB even a tiny bit, does it then do this reboot thing? Or is it only when you get aggressive and try for something like 333 does it do the rebooting thing? At stock settings, does it boot into windows without problems? I'm assuming that at stock settings you are able to get to Windows and run programs and such, or has it never booted correctly?

Setting it wrong initially should have no bearing on it now, unless you somehow also set the DRAM or NB voltages really low and never set them back.
 
What's your power supply?

I got to 3.0 ( 9 * 334) Easy.

I'm just curious, because my last computer had a gigabyte board and a crappy PSU. It wouldn't overclock even 200 Mhz without going bonkers.
 
On my board there's an option that let's me choose what kind of ram I have DDR800, 1066, 1600, 1800 etc. If I touch that setting with my overclock, I can't post the system. I leave it to auto and manage the ram FSB and timings myself. Most "auto" settings are fine, the only ones you should concern yourself with a CPU voltage, CPU voltage dampener (if exist prevents vdroop), DDR base timings the famed x-x-x-x on the box, DDR voltage, FSB(front side bus (the key to overclocking), PCIe speed (lock to or choose 100 or risk damaging video card and PCI slots), and multiplier.

Try a 8x400 for a clean 3.2 which uses your ram at it's rated speed. Most G0 steppings can do 3.2@ stock voltage, but if it's not posting for grins try 1.35 (the box voltage of a CPU). I've found by default, my board uses looser timings than advertised by my ram, in my experience I've found many boards that go more conservative if left to SPD. Also for the DDR voltage, set it to the max of the range on the box, some say 1.8-2.0V so choose 2.0V.
 
Forceman said:
Getting through the memory POST test doesn't really qualify as booting well. If you change the FSB even a tiny bit, does it then do this reboot thing? Or is it only when you get aggressive and try for something like 333 does it do the rebooting thing? At stock settings, does it boot into windows without problems? I'm assuming that at stock settings you are able to get to Windows and run programs and such, or has it never booted correctly?

Setting it wrong initially should have no bearing on it now, unless you somehow also set the DRAM or NB voltages really low and never set them back.
Click to expand...
I have not tested it with a small increase, but I will when I get home.
Stock is the ONLY setting where I get into windows A-OK (btw I dual boot, Windows XP and Home Prem, Vista, can get into both OS's just fine), no problems, I been posting from the same PC I have been trying to OC (minus this post, being done by my mom's laptop)
There is nothing 100% wrong, but it is weird.
To the other one, I am using a FSP Group 700 Watt PSU, brand new, and I am sure this is more then powerful for the build of my PC.

When I set it wrong the first time, I did not mess with anything else, and everything else went back to stock anyway. It's just odd as hell as to why I can not OC it, but it works just fine at stock.
 
Does that gigabyte board have the control f1 button to give more options? If it does maybe you can give it the mem multipler of 2.5 and bump the fsb up to 333. Thats what i did with the g33 chipset gigabyte and my e6400. mem would run at 833 and cpu from 2.13 to 2.66
 
luke51087 said:
Does that gigabyte board have the control f1 button to give more options? If it does maybe you can give it the mem multipler of 2.5 and bump the fsb up to 333. Thats what i did with the g33 chipset gigabyte and my e6400. mem would run at 833 and cpu from 2.13 to 2.66
Click to expand...

I belive my board has this option, but I have not tried this yet.
 
I've got a Gigabyte P35 based motherboard (though not the DS3) in my server machine - I haven't tried overclocking it yet, but later on I will try and see if I see anything funny in the BIOS.
 
Just tried it in small incriments, and alas, the same shit.
270, 280 etc. Everything else on auto.
 
Grabbed this from a different forum. Same motherboard, different processor. Try out these specs and see if you can get past post.

"This is what I'm using for my brother's PC. He has an E6600 with a x9 multi. I didnt push it to the limits by any means, but it should help you get started:

The OCing features are in MB Intelligent Tweaker(M.I.T.) option.


CPU Host Clock Control - enable
CPU Host Frequency (Mhz) - set to 380
PCI Express Frequency (Mhz) - Set to 100 (this is the deafult for the video card)
System Memory Multiplier (SPD) - change the multi until it says 800 (what ram is rated to)

Then move down to System Voltage Control:
DDR2 OverVoltage Control - +0.2v (this is if your ram is rated for 2.0v, the default for the board is 1.8v)
FSB OverVoltage Control - +0.2v (you might not need to increase this, but at 400 FSB, it will ensure stability)
(G)MCH OverVoltage Control - +0.2 (you might not need to increase this, but at 400 FSB, it will ensure stability)
CPU Voltage Control - 1.35v (if it is stable, try lowering it until it becomes unstable, then bring it back up 2 notches.

Good Luck

Oh yeah, if you hit the [Ctrl + F1], you can change the memory timings to match the manufacturer's specs if not already set."
 
Silvers24 said:
Just tried it in small incriments, and alas, the same shit.
270, 280 etc. Everything else on auto.
Click to expand...

If you are having the same problems with even a small overclock like 270, there is definitely something set wrong in your BIOS.
 
I agree, until you get cozy with your bios options, expect hard times.
 
lowdy15 said:
Grabbed this from a different forum. Same motherboard, different processor. Try out these specs and see if you can get past post.

"This is what I'm using for my brother's PC. He has an E6600 with a x9 multi. I didnt push it to the limits by any means, but it should help you get started:

The OCing features are in MB Intelligent Tweaker(M.I.T.) option.


CPU Host Clock Control - enable
CPU Host Frequency (Mhz) - set to 380
PCI Express Frequency (Mhz) - Set to 100 (this is the deafult for the video card)
System Memory Multiplier (SPD) - change the multi until it says 800 (what ram is rated to)

Then move down to System Voltage Control:
DDR2 OverVoltage Control - +0.2v (this is if your ram is rated for 2.0v, the default for the board is 1.8v)
FSB OverVoltage Control - +0.2v (you might not need to increase this, but at 400 FSB, it will ensure stability)
(G)MCH OverVoltage Control - +0.2 (you might not need to increase this, but at 400 FSB, it will ensure stability)
CPU Voltage Control - 1.35v (if it is stable, try lowering it until it becomes unstable, then bring it back up 2 notches.

Good Luck

Oh yeah, if you hit the [Ctrl + F1], you can change the memory timings to match the manufacturer's specs if not already set."
Click to expand...
Aight, i'll try this & see what happens.
Thanks :)
 
Well. I know when I have been beaten.

I give the hell up.

Same ol shit, even with me using those to a T, tried adjusting the Vcore too.
No luck.
 
How about you start posting things like:

1) What settings you tried
2) How many sticks of RAM you're using (you should just be trying 1 or 2 right now)
3) What else is installed (i.e. sound card, etc ... nothing else should be in but CPU, RAM, HD, GFX)
4) What BIOS revision

Etc.


Or, use memory that has been tested for compatability with the motherboard: http://www.gigabyte-usa.com/FileList/MemorySupport/motherboard_memory_ga-p35-ds3l_2.0.pdf


Or, just stop trolling. And before you say I'm full of bullshit, I just had an issue with my GA-X38T-DQ6 that would not boot with both memory sticks installed after flashing the BIOS...but booted fine with one. Once I got the settings for the memory set right, I could boot with both sticks in.

It is simply something fundamental you're doing wrong.
 
rainman said:
How about you start posting things like:

1) What settings you tried
2) How many sticks of RAM you're using (you should just be trying 1 or 2 right now)
3) What else is installed (i.e. sound card, etc ... nothing else should be in but CPU, RAM, HD, GFX)
4) What BIOS revision

Etc.
Click to expand...
#1: A ton, mainly with the FSB.
270, 275, 300, 333, 340, 370, 375, 400.
Everything else auto. Not much to say in this part.
Other then what users have suggested (In order to find these out, just read the posts...)
#2: Been answered. However have not tried it with 1 or 2 sticks.
#3: PCI Wireless card, GFX card.
#4: New ones, AWARD BIOS rev 6.

Or, use memory that has been tested for compatability with the motherboard: http://www.gigabyte-usa.com/FileList/MemorySupport/motherboard_memory_ga-p35-ds3l_2.0.pdf
Click to expand...
Already bought my memory, so guess I am sol for compatibility.


Or, just stop trolling.
Click to expand...
http://en.wikipedia.org/wiki/Internet_troll
prove I am trolling.

And before you say I'm full of bullshit, I just had an issue with my GA-X38T-DQ6 that would not boot with both memory sticks installed after flashing the BIOS...but booted fine with one. Once I got the settings for the memory set right, I could boot with both sticks in.

It is simply something fundamental you're doing wrong.
Click to expand...
I wassen't going to say you are.
It might be, but already 2 pages in, and I am sure people are already tired of this thread.
I will probably return to this one day. but atm, 2.4 for now is good enough. All options have failed me so far.
 
Getting a Q6600 to 3.0GHz shouldn't require much of anything other than setting the FSB to 333.

Set the FSB to 333, set v.core to 1.27, set everything else auto.

I like to try unsynch/unlink ram first. If that works, then try link/synch.

Leave ram timings and memory volts to auto/manufacturer specs.

If it's stable, then you can lower the v.core until it's unstable, then kick it up a notch to stable again.

My v.core
3GHz - 1.25v
3.2GHz - 1.26
3.4GHz - 1.35
3.6GHz - 1.49v
 
Again, grabbed this from another thread. Let's hope this works?

"I posted this 10 or 12 pages back, but it probably got lost in the mix by now. That happens when these threads get this long and I noticed this issue is still happening to others again. Anyways, I was having the same problem. I'd OC. I test with Orthos, OCCT or Prime95 all night long and pass just fine. Then I'd power the system up the very next day and everything would go back to default again, every single time. It was driving me crazy. I did some Googling and found out that this was happening to others as well. The fix was a setting in the BIOS. Under the "Halt On" section, set it to "NO Errors". This completely fixed my problem and it has never done it since. It's been almost a month now and it's still working just fine. From what I was reading is that the system sees that the CPU is not running at the correct/specified speed and it's thinks that that is an error, so it stops the booting process and resets everything. I don't know if it will work for all of you, but it worked for me.

Also, my board was shipped with the F3 BIOS. I flashed to the F6 version and the problem still persisted until I changed that one setting, so I'm going to assume that it's not a BIOS version problem for any of you."
 
lowdy15 said:
Again, grabbed this from another thread. Let's hope this works?

"I posted this 10 or 12 pages back, but it probably got lost in the mix by now. That happens when these threads get this long and I noticed this issue is still happening to others again. Anyways, I was having the same problem. I'd OC. I test with Orthos, OCCT or Prime95 all night long and pass just fine. Then I'd power the system up the very next day and everything would go back to default again, every single time. It was driving me crazy. I did some Googling and found out that this was happening to others as well. The fix was a setting in the BIOS. Under the "Halt On" section, set it to "NO Errors". This completely fixed my problem and it has never done it since. It's been almost a month now and it's still working just fine. From what I was reading is that the system sees that the CPU is not running at the correct/specified speed and it's thinks that that is an error, so it stops the booting process and resets everything. I don't know if it will work for all of you, but it worked for me.

Also, my board was shipped with the F3 BIOS. I flashed to the F6 version and the problem still persisted until I changed that one setting, so I'm going to assume that it's not a BIOS version problem for any of you."
Click to expand...

haha, you know, that might be it, I do have this option. Time to go check see.
 
lets hope thats it. BTW, ill be getting this same MB tomorrow. You got me scared haha!
 
lowdy15 said:
lets hope thats it. BTW, ill be getting this same MB tomorrow. You got me scared haha!
Click to expand...

haha, weird though, had kickass reviews. >_<
Tried it, all failed. Same thing.
Don't pass go. :(
Tried it with memory @ 1:1 ratio, and @ 800mhz
Using FSB 333
 
You must log in or register to reply here.
Back
Top