Q6600 and DS3L overclock keeps giving me Blue Screen

asmolow

Distinguished
Nov 10, 2007
36
0
18,530
I have followed the overclock guide to overclock my Q6600 on my GA-P35-DS3L. I have played with the fsb to overclock from 3.0 -3.4, but no matter what I have it set at, I end up crashing and getting a blue screen after a few hours.


Temps are all well under 71 when running prime95 and I have left the vcore on auto which usually is a value of 1.36. I have tried adjusting a little bit above that manually, but it still crashes.

I have tried running with all power saving options on and off, still crashes.

I am using vista ultimate with 4 gb of ram. I have relaxed my timings at 5 5 5 15 and increased the voltage to 2.1.

Any Ideas?
 

asmolow

Distinguished
Nov 10, 2007
36
0
18,530
I will post the Hex Code when I get home from work. I have not messed with bios revisions yet, but do you think updating it would make a difference?
 

asmolow

Distinguished
Nov 10, 2007
36
0
18,530
Well I got home from work today and my computer didn't crash, but all 4 threads had an error on prime95 after 3 to 4 hours.

I did 9*356, which should be within the limits of my GO Q6600.

Should I try giving the vcore a large bump? It seems like 1.36 should be plenty.
 

asmolow

Distinguished
Nov 10, 2007
36
0
18,530
I just set my vcore to 1.375 in my bios, but both speedfan and cpu-z are saying my vcore is 1.33 while idle. Speedstep and such are off. Whats the deal?

 

cnumartyr

Distinguished
Nov 3, 2007
2,287
0
19,780



That is called vOffset... without going into insane detail it's basically vDrop to make sure you don't ever go over the voltage you set in the BIOS because of full-load to idle conditions.
 

asmolow

Distinguished
Nov 10, 2007
36
0
18,530
Should I do anything to compensate for it or just test for stability at my current setting? The reason I ask is prime95 kept getting errors while I had my voltage set to auto, which was 1.36 according to cpu z. Now that I have it set to 1.375 manually, cpu z is actually giving a lower value than auto which leads me to believe it is even more likely to error.
 

cnumartyr

Distinguished
Nov 3, 2007
2,287
0
19,780



Subtract your CPU-Z from your BIOS setting. Add that to 1.36 and you get what you would need to set in your BIOS to get 1.36. From there find the closest, and increase one notch.
 

asmolow

Distinguished
Nov 10, 2007
36
0
18,530
Out of curiosity, when everyone is referring to vcore while overclocking, are they referencing what they enter in bios, what cpu z says while idle, or their vcore after vdroop?

If I enter a value in the bios greater than the 1.5 limit, but cpu z reports a value less than that cause of voffset. Does that mean I technically have not reached the limit?
 

cnumartyr

Distinguished
Nov 3, 2007
2,287
0
19,780


I reference my loaded vCore.

1.5 is a guideline, but yes... CPU-Z is showing the ACTUAL vCore.
 

cnumartyr

Distinguished
Nov 3, 2007
2,287
0
19,780



The "rule of thumb" is 1.5vCore max in CPU-Z for Air Cooling and 1.6v for Water Cooling.

I think it's all opinions.. I've benched my CPU on air at 3.9 GHz with 1.58vCore... I just leave it at 3.6 and 1.4vCore for 24/7 operation.