Overclocking into the Haswell

Swizz

Swizz

Swizz

Associate
Joined
5 Jun 2013
Posts
181
Location
Liverpool - UK
Hello all..Bit of an embarrassing topic regarding my first ever OC'ing experience..lets just say it didn't turn out to be expected. It was so bad I couldn't even boot back into Windows. I received my new Haswell chip yesterday and I was raring to go to reach that magic number. I did follow a tutorial video, but still, it didn't go to plan. I was tempted to dabble with EasyTune. But all-in-all I think it's best to stay away from that program from what I have been told. Any additional tips/info would be appreciated to help me OC this processor.


Thanks all.
 
Last edited:
3GB EVGA GTX 780
Intel Core i5 4670K,
256GB Samsung 840 Pro
Gigabyte GA-Z87X-UD4H
G,Skill Ripjaws X 2133MHz 8GB
750W XFX Pro Black Edition
Microsoft Windows 7 Ult
3TB Seagate ST3000DM001 Barracuda 7
Noctua NH-D14 Dual Radiator x6 Heat
Fortress FT02
Arctic Cooling MX-4


I'll have a bash of that and report back. Thanks man.
 
Last edited:
I have to admit it was unnerving the first time around. it took near enough around the three hour mark before I could actually get back into Windows. Fingers crossed everything will breeze smoothly now

EDIT - Reason being, it wouldn't proceed past the Gigabyte splash-screen. It constantly stalled upon that point, till' three hours later, it booted in perfectly
 
Last edited:
Alrighty sorry about the delay I grabbed my laptop..okay I'm in the bios now, I was able to find the CPU Vcore voltage and changed it 1.200v. but I' can't seem to find the CPU Multiplier. I came across the Memory Multiplier, but not the CPU
 
Okay dude, that went great. i'm logged back into Windows now, and I am about to stress it with the use of Prime95 for 20 minutes, will report back once more.

thanks for your time fella
 
Approaching 13 minutes and temps are staying at 50. 53. 49. 51 in RealTemp. Prime was set on blend
 
Alrighty just getting everything up to speed. Upcore Ratio 42. CPU Clock Ratio 43. bluescreening through 1.23v to 1.25 and 1.27v
 
Still bluescreened. I did happen to noticed that both settings in Chipset Core was set to off..it was in red. PCH Core was raised from 1.090 - 1.095. PCH IO 1.50 to 1.530v
 
By clicking On to both, didn't make a difference mate.

At CPU Status now. vCore 1.212v. Should I raise the CPU Vcore a little more?
 
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?
 
Last edited:
OLDPHART said:
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.
Click to expand...

Hey, thanks. That will come in handy :D
 
Well...Just over 5 hours ago I started a Linpack test using OCCT. Straight after that I have been running AIDA64. it seems good so far. We are 45 minutes in :)
 
The Turbo Ratios. 1 to 4..Should I bump those up to 43, the next time I fly into the Bios? At this moment they have remained at "40"
 
You must log in or register to reply here.
Back
Top Bottom