Advice for Getting my Q6600 G0 @ 3.6GHz Stable?

[AuDioFreaK39]

I'm having trouble getting my Q6600 G0 stable at 3.6GHz. I have an ASUS P5K Premium motherboard and an Ultra 120-Extreme heatsink with plenty of airflow in the case. I also have Patriot eXtreme Performance DDR2 800 (5-5-5-15) that I would like to keep at a 1:1 ratio. Please let me know what settings I should try changing. Thanks in advance.

http://i57.photobucket.com/alb...ioFreaK39/DSC02110.jpg

http://i57.photobucket.com/alb...ioFreaK39/DSC02109.jpg

http://i57.photobucket.com/alb...ioFreaK39/DSC02111.jpg

http://i57.photobucket.com/alb...ioFreaK39/DSC02112.jpg


Specs:

ASUS P5K Premium (Black Pearl Edition) rev. 2.00
Intel Core 2 Quad Q6600 2.40GHz (G0 Stepping)
Thermalright Ultra 120-Extreme (push-pull configuration with SilenX iXtrema 75CFM)
4GB (2 x 2GB) Patriot eXtreme Performance DDR2 800 (6400)
eVGA GeForce 8800GTX 768MB (625/1007)
PC Power and Cooling Silencer 610W Continuous @ 40C
Samsung HD501LJ 500GB SATAII
NZXT LEXA Blackline

Vista Ultimate x64

 

[GFORCE100]

Originally posted by: AuDioFreaK39
I'm having trouble getting my Q6600 G0 stable at 3.6GHz. I have an ASUS P5K Premium motherboard and an Ultra 120-Extreme heatsink with plenty of airflow in the case. I also have Patriot eXtreme Performance DDR2 800 (5-5-5-15) that I would like to keep at a 1:1 ratio. Please let me know what settings I should try changing. Thanks in advance.

http://i57.photobucket.com/alb...ioFreaK39/DSC02110.jpg

http://i57.photobucket.com/alb...ioFreaK39/DSC02109.jpg

http://i57.photobucket.com/alb...ioFreaK39/DSC02111.jpg

http://i57.photobucket.com/alb...ioFreaK39/DSC02112.jpg


Specs:

ASUS P5K Premium (Black Pearl Edition) rev. 2.00
Intel Core 2 Quad Q6600 2.40GHz (G0 Stepping)
Thermalright Ultra 120-Extreme (push-pull configuration with SilenX iXtrema 75CFM)
4GB (2 x 2GB) Patriot eXtreme Performance DDR2 800 (6400)
eVGA GeForce 8800GTX 768MB (625/1007)
PC Power and Cooling Silencer 610W Continuous @ 40C
Samsung HD501LJ 500GB SATAII
NZXT LEXA Blackline

Vista Ultimate x64

Well turning on the Voltage Damper won't hurt.

It could be dying due to extreme heat? What are you temps according to CoreTemp BETA 95.4?

Try the above for starters.

 

[PlasmaBomb]

The voltage damper should stop the voltage dropping when the CPU is fully loaded which may affect stability.

 

[aigomorla]

you need to raise the FSB termination voltage past auto.

I would put it second to the highest possible, which is around 1.4-1.5

Quadcores communicate to each other though the FSB, so if your voltage is lacking you wont be stable.

Also you need to up your NB voltage as well. I would put it 2 above stock, and raise 1 until its stable.

Lastly, even G0's need at least 1.45Vcore in bios to load up at 3.6ghz. 1.45 in bios usually means around 1.41-1.42 after vdroop. So try to play with your voltages a little. I think thats where your wall is.

 

[AuDioFreaK39]

Originally posted by: aigomorla
you need to raise the FSB termination voltage past auto.

I would put it second to the highest possible, which is around 1.4-1.5

Quadcores communicate to each other though the FSB, so if your voltage is lacking you wont be stable.

Also you need to up your NB voltage as well. I would put it 2 above stock, and raise 1 until its stable.

Lastly, even G0's need at least 1.45Vcore in bios to load up at 3.6ghz. 1.45 in bios usually means around 1.41-1.42 after vdroop. So try to play with your voltages a little. I think thats where your wall is.

Thanks for the advice. I set the Vcore to 1.4875, the NB to 1.50 and the FSB termination a few steps above auto and now it's running stable after 6 hour of Prime95. Did not know that cores communicate to each other through the FSB. Learned something new, thanks.

P.S. I wll try to get to 3.75GHz next week

 

[aigomorla]

Originally posted by: AuDioFreaK39

Originally posted by: aigomorla
you need to raise the FSB termination voltage past auto.

I would put it second to the highest possible, which is around 1.4-1.5

Quadcores communicate to each other though the FSB, so if your voltage is lacking you wont be stable.

Also you need to up your NB voltage as well. I would put it 2 above stock, and raise 1 until its stable.

Lastly, even G0's need at least 1.45Vcore in bios to load up at 3.6ghz. 1.45 in bios usually means around 1.41-1.42 after vdroop. So try to play with your voltages a little. I think thats where your wall is.

Thanks for the advice. I set the Vcore to 1.4875, the NB to 1.50 and the FSB termination a few steps above auto and now it's running stable after 6 hour of Prime95. Did not know that cores communicate to each other through the FSB. Learned something new, thanks.

P.S. I wll try to get to 3.75GHz next week

Glad to see it work. Heh, i own 5 quadcores. 1 ES, 1 G0, 3 B3's So i know how these girls act. :]

Good luck on the higher overclock. Just make sure you watch your temps carefully. Also you may want to put an active fan on your NB now that you added a bit more voltage to it. You'll notice it getting really hot quickly with the added voltage.

 

[GFORCE100]

Originally posted by: AuDioFreaK39

Originally posted by: aigomorla
you need to raise the FSB termination voltage past auto.

I would put it second to the highest possible, which is around 1.4-1.5

Quadcores communicate to each other though the FSB, so if your voltage is lacking you wont be stable.

Also you need to up your NB voltage as well. I would put it 2 above stock, and raise 1 until its stable.

Lastly, even G0's need at least 1.45Vcore in bios to load up at 3.6ghz. 1.45 in bios usually means around 1.41-1.42 after vdroop. So try to play with your voltages a little. I think thats where your wall is.

Thanks for the advice. I set the Vcore to 1.4875, the NB to 1.50 and the FSB termination a few steps above auto and now it's running stable after 6 hour of Prime95. Did not know that cores communicate to each other through the FSB. Learned something new, thanks.

P.S. I wll try to get to 3.75GHz next week

Keep a watch on your temps in CoreTemp. No good going higher if it's already frying and throttling itself to save itself