Help OC 6700K

[smokefest]

Hi guys,

I tho I had a stable 6700k @ 4.5 ghz 1.3 vcore 1.1 VCCSIO and 1.125 VCCIO Agent (maybe not the exact terms but u know..)
With the CPU cache min and max set to 43

 

I have good temp, I ran AIDA 64 for 20 min, all good,
Ran cinebench all good, played BF1 all good,

But I still get some blu screen in win10 after a while that my PC is open, even if on idle..

Any idea ?

Any other program I shud use to test stability ?

 

thx for the help guys

[xephoneration]

prime 95 27.9v that will tell you if your OC is really stable or not. and you dont have to run it all day or night either. just watch it really. 

[Litargirio]

3 minutes ago, smokefest said:

Any other program I shud use to test stability ?

...doesn't the fact that the PC bluescreened already demonstrate that it's unstable? 

 

Try 1.35 volts to see if it keeps bluescreening (since the bluescreen could be caused by somehting else entirely). If it stops, lower to 1.31 and test from there.

[Litargirio]

1 minute ago, xephoneration said:

prime 95 27.9v that will tell you if your OC is really stable or not. and you dont have to run it all day or night either. just watch it really. 

Prime95 is dangerous. It can damage the CPU.

[xephoneration]

9 minutes ago, Litargirio said:

Prime95 is dangerous. It can damage the CPU.

no... not that version, more recent version can and will....  also overclockers.net suggest to run prime95 27.9v for a stablility test since it will let you know whether or not your oc works. 

 

 

EDIT: also to add if you do have a skylake cpu (this is for everyone how has one) do follow that guide it is very comprehensive and does provide very thorough information about OCing a skylake cpu

[jools]

disable throttling-some times pc,s work fine with overclock and load  but don't handel idle very well

[smokefest]

31 minutes ago, Litargirio said:

...doesn't the fact that the PC bluescreened already demonstrate that it's unstable? 

 

Try 1.35 volts to see if it keeps bluescreening (since the bluescreen could be caused by somehting else entirely). If it stops, lower to 1.31 and test from there.

Yeah sounds right i'll do that i guess