Overclocking into the Haswell
- Thread starter Swizz
- Start date
Yeah, sounds about right.
Try those chipset voltages, try increasing the CPU ring voltage by 0.08 to 0.1v. If you still can't get into Windows then I'd try the newer BIOS. Make sure you drop everything back to default settings before you flash the BIOS.
Heading to bed soon mate - will check the thread tomorrow to see how you get on. At the very least, you're good to go with the chip at 4.2Ghz. Mine needs a lot more than 1.200v to get 4.2Ghz stable, so it could be worse.
Try those chipset voltages, try increasing the CPU ring voltage by 0.08 to 0.1v. If you still can't get into Windows then I'd try the newer BIOS. Make sure you drop everything back to default settings before you flash the BIOS.
Heading to bed soon mate - will check the thread tomorrow to see how you get on. At the very least, you're good to go with the chip at 4.2Ghz. Mine needs a lot more than 1.200v to get 4.2Ghz stable, so it could be worse.
And yet we step onward lol Okay we're on 4.3Mhz now, stable with OCCT Linpack 70c 71c 69c 66c Maxium according to RealTemp. Volts are also running at 1.260. I did notice in Bios the Volts are lower then what is shown in CPU-Z & CPUID HWMonitor, is that normal? I need your opinion guys. From my results is it worth pushing it to 4.4Mhz?
Cheers.
EDIT - I just noticed that the volts in CPU-Z Are swaying from 1.260 to 1.272v. Again, guys is that normal?
Cheers.
EDIT - I just noticed that the volts in CPU-Z Are swaying from 1.260 to 1.272v. Again, guys is that normal?
Last edited:
Hi, this might help with your overclocking -
Common BSOD Error Codes for Overclocking
0x101 = increase vcore
0x124 = increase/decrease QPI/VTT first, if not increase/decrease vcore...have to test to see which one it is
on i7 45nm, usually means too little VVT/QPI for the speed of Uncore
on i7 32nm SB, usually means too little vCore
0x0A = unstable RAM/IMC, increase QPI first, if that doesn't work increase vcore
0x1A = Memory management error. It usually means a bad stick of Ram. Test with Memtest or whatever you prefer. Try raising your Ram voltage
0x1E = increase vcore
0x3B = increase vcore
0x3D = increase vcore
0xD1 = QPI/VTT, increase/decrease as necessary, can also be unstable Ram, raise Ram voltage
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)
0x7E = Corrupted OS file, possibly from overclocking. Run sfc /scannow and chkdsk /r
BSOD Codes for Sandy Bridge
0x124 = add/remove vcore or QPI/VTT voltage (usually Vcore, once it was QPI/VTT)
0x101 = add more vcore
0x50 = RAM timings/Frequency add DDR3 voltage or add QPI/VTT
0x1E = add more vcore
0x3B = add more vcore
0xD1 = add QPI/VTT voltage
“0x9C = QPI/VTT most likely, but increasing vcore has helped in some instances”
0X109 = add DDR3 voltage
0x0A = add QPI/VTT voltage
For a complete list of BSOD error codes that may or may not be related to overclocking vist this link.
You may also want to give this other article I wrote a read if you are wondering how to disable auto restart after a BSOD.
Common BSOD Error Codes for Overclocking
0x101 = increase vcore
0x124 = increase/decrease QPI/VTT first, if not increase/decrease vcore...have to test to see which one it is
on i7 45nm, usually means too little VVT/QPI for the speed of Uncore
on i7 32nm SB, usually means too little vCore
0x0A = unstable RAM/IMC, increase QPI first, if that doesn't work increase vcore
0x1A = Memory management error. It usually means a bad stick of Ram. Test with Memtest or whatever you prefer. Try raising your Ram voltage
0x1E = increase vcore
0x3B = increase vcore
0x3D = increase vcore
0xD1 = QPI/VTT, increase/decrease as necessary, can also be unstable Ram, raise Ram voltage
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)
0x7E = Corrupted OS file, possibly from overclocking. Run sfc /scannow and chkdsk /r
BSOD Codes for Sandy Bridge
0x124 = add/remove vcore or QPI/VTT voltage (usually Vcore, once it was QPI/VTT)
0x101 = add more vcore
0x50 = RAM timings/Frequency add DDR3 voltage or add QPI/VTT
0x1E = add more vcore
0x3B = add more vcore
0xD1 = add QPI/VTT voltage
“0x9C = QPI/VTT most likely, but increasing vcore has helped in some instances”
0X109 = add DDR3 voltage
0x0A = add QPI/VTT voltage
For a complete list of BSOD error codes that may or may not be related to overclocking vist this link.
You may also want to give this other article I wrote a read if you are wondering how to disable auto restart after a BSOD.
Hi, this might help with your overclocking -
Common BSOD Error Codes for Overclocking
0x101 = increase vcore
0x124 = increase/decrease QPI/VTT first, if not increase/decrease vcore...have to test to see which one it is
on i7 45nm, usually means too little VVT/QPI for the speed of Uncore
on i7 32nm SB, usually means too little vCore
0x0A = unstable RAM/IMC, increase QPI first, if that doesn't work increase vcore
0x1A = Memory management error. It usually means a bad stick of Ram. Test with Memtest or whatever you prefer. Try raising your Ram voltage
0x1E = increase vcore
0x3B = increase vcore
0x3D = increase vcore
0xD1 = QPI/VTT, increase/decrease as necessary, can also be unstable Ram, raise Ram voltage
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)
0x7E = Corrupted OS file, possibly from overclocking. Run sfc /scannow and chkdsk /r
BSOD Codes for Sandy Bridge
0x124 = add/remove vcore or QPI/VTT voltage (usually Vcore, once it was QPI/VTT)
0x101 = add more vcore
0x50 = RAM timings/Frequency add DDR3 voltage or add QPI/VTT
0x1E = add more vcore
0x3B = add more vcore
0xD1 = add QPI/VTT voltage
“0x9C = QPI/VTT most likely, but increasing vcore has helped in some instances”
0X109 = add DDR3 voltage
0x0A = add QPI/VTT voltage
For a complete list of BSOD error codes that may or may not be related to overclocking vist this link.
You may also want to give this other article I wrote a read if you are wondering how to disable auto restart after a BSOD.
Hey, thanks. That will come in handy
Great info there Oldphart - will save for future reference
How did the clocking go, Swizz - did you achieve stability with 4.3Ghz?
edit:
yes - absolutely normal.
How did the clocking go, Swizz - did you achieve stability with 4.3Ghz?
edit:
yes - absolutely normal.
Last edited:
Can do, but from my experience with this board the CPU multiplier overrides the turbo frequencies. As long as you're seeing a true 4.3Ghz (or near enough) in CPU-z while you're stress testing then you know that your CPU is finding the right frequency.
If all is good, then push for 4.4Ghz and beyond - see how far that bitch will go
If you can manage 4.5Ghz at reasonable temps then you probably have an above average clocking chip Can do, but from my experience with this board the CPU multiplier overrides the turbo frequencies. As long as you're seeing a true 4.3Ghz (or near enough) in CPU-z while you're stress testing then you know that your CPU is finding the right frequency.
If all is good, then push for 4.4Ghz and beyond - see how far that bitch will go
Sounds good lol What is the maximum voltage that I should be looking at, would you say?
It depends on your temperatures really... Haswell really ramps up the temps when you push beyond 1.28v (unless you "de-lid" or use extreme cooling). For now I'd keep the Vcore voltage as it is and see how far you can push the frequency. As long as your max temps under full load stay below say 85-90C then you should be safe for day to day operations (full stress testing load won't happen under regular usage).
I'll bet you manage 4.5Ghz - which is a good overclock (much better than my chip will manage).
Screw that - I don't have the patience for 1hr+ runs
Push it further now, see what it can do. Once you get a fail during stress testing either clock down or bump up the volts until your temps get unacceptable
Last edited:
Those readings that OldPhart posted..When'ever it bluescreens I am seeing "0x124" BS = (increase/decrease QPI/VTT first, if not increase/decrease vcore...have to test to see which one it is.) Should I raise the QPI/VTT? If so, where would I find it.
Thanks man.
Thanks man.
Hmm... Tough to say. Play around and see what it gives you. 1.26-1.27v Vcore is already fairly high.
As a baseline, increase QPI/VTT until the bar goes "yellow" in BIOS. That should be a good baseline. You shouldn't need more voltage than that through the chipset for air cooling.