Originally Posted by HaMMeR=GoM= View Post
I was wondering why my Gigaflops were a little on the low side and now I know why. Everyone needs to read this:
It also helps both Linx and IBT to update the Linpack libraries manually to the latest version.
When running Linx or IBT the GigaFlops have to be close to the rating for your particular chip. If it isn't then, you're not stressing the Overclock correctly.
After I loosely followed this guide my GigaFlops increased dramatically and my core temps rocketed by 5Â°C Luckily, I had previously increased my vcore and my qpi voltage due to Prime 95 Bsod after 8hrs. I now feel that if Linx is run properly, it will tell you if you're overclock is stable within 99%, I would guess
I found these here on OCN and I feel that the above and these should be added to the guide.
BSOD codes for overclocking
0x101 = increase vcore
0x124 = increase/decrease vcore or QPI/VTT...have to test to see which one it is
0x0A = unstable RAM/IMC, increase QPI first, if that doesn't work increase vcore
0x1E = increase vcore
0x3B = increase vcore
0x3D = increase vcore
0xD1 = QPI/VTT, increase/decrease as necessary
0x9C = QPI/VTT most likely, but increasing vcore has helped in some instances
0x50 = RAM timings/Frequency or uncore multi unstable, increase RAM voltage or adjust QPI/VTT, or lower uncore if you're higher than 2x
0x109 = Not enough or too Much memory voltage
0x116 = Low IOH (NB) voltage, GPU issue (most common when running multi-GPU/overclocking GPU)