Originally Posted by Defoler;12029926
BSOD from my experince and data I have collected from time to time:
0X00000050 incorrect memory timing
0X00000124 incorrect vtt (too low/high)
0X00000101 not enough vcore
0X0000000Aunstable ram, increase qpi or vcore
0X0000001Enot enough vcore
0X0000003Bnot enough vcore
0X000000D1incorrect vtt (too low/high)
0X0000009Cincorrect vtt (too low/high)
0X00000119incorrect memory volt
Most of the rest are for too low vcore.
In the process of finding your highest clock, I suggest going with as low blk as you can. Keep it around the 140-150 with just upping the multiplier.
This eliminates the issue of too high QPI.
And keep memory and uncore very low at start, to eliminate the vtt volt errors (like the 124).
After that, start increasing the memory and uncore slowly.
Get memory / uncore at x1.5, and increase it up to x2 and increase vtt a bit, than up the memory so it goes back to around the x1.5-1.6, and up the uncore again.
If you like, you can keep uncore down at x1.5-1.6 from memory, but higher uncore = higher performance.
Also, testing, I usualy run 3dmark vantage cpu tests and 3dmark 11 physics test.
That will almost always tell you if your cpu is stable or not (if it stops mid run), and after that you can run linx if you like.
^Do this. Another stress test I found works nicely is folding on your CPU. That will really tell you if your overclock is stable or not.
Originally Posted by brock_samson;12033354
maybe you missed a setting in your CPU config that needs to be disabled? can you post your bio's settings?
and forget what they are called but did you set the two bottom settings on the first page to disabled?
Yes, please give us a BIOS screen shot. I think he's talking about the power saving settings (c1/c2/c3...ect.)
I was unaware brock samson knew how to overclock! I thought he specialized in destroying henchmen and dr. venture handled the overclocking.