- Joined
- Jan 11, 2012
- Location
- North Carolina
I've gotten my first Intel build going within the past few days and I didn't even bother putting the wimpy little stock cooler on it, I went straight for my Hyper 212 which didn't have any other use at the moment anyway.
So since I've never overclocked Intel before I am stuck in my ways worrying about the temps as I did with my FX. At stock this little chip was running as hot at idle as my FX ran at load and when I put the Haswell under load I was stuck worrying about temps going over 55C.
So after getting over my PBOD (post-bulldozer-overcloking-disorder) I worked my way up to 4.2GHz, which seems to be a real sweet spot. It doesn't take but a small bump in voltage to 1.06v and slightly higher temps, it's lightning fast, the loading screens in Skyrim off of my SSD just look like you blink and it makes me question why I ever liked AMD in the first place.
So anyway, I kept pushing. It took me a while to get it stable at 4.3 because my little voltage bumps were no longer doing it. Finally got stable at 1.155V and max temps around 75C.
But I still wasn't happy and after drinking a few while I let prime95 run at 4.3GHz I decided to go for 4.4 and unwitttingly probably took a few years off of my CPU's life when I did.
So I try 4.4GHz @ 1.16V and 1.165V and it BSODs after a few minutes in prime95 both times. I am feeling pretty good by now and restart the comp, go into BIOS, find Vcore, and what I was thinking was "1.175V", but what my hands decided to type without express permission from my brain was "1.75" and I save and exit.
Windows boots up, I open up prime95 and start stressing the CPU, open up CPU-Z and check on the volts (1.752? Yeah that's close enough to what I typed in, all is good! ) and finally I open up HWmonitor to take a look at temps. I scroll down and see 100C maximum on all cores and I glance back over at the CPU-Z voltage again and finally realise my mistake after prime95 has been running for a minute or two at this point, so I shut it down as fast as I can and correct my mistake in BIOS, set it to 1.175V like I meant to and now it seems mostly stable at 4.4GHz with only one issue; Worker #3 hasn't stopped but it is stuck on the third 1024K test while the rest of the cores have completed a few dozen more tests.
I backed everything back down to stock to make sure I hadn't burnt out a core and it runs as good as the rest, but that's not saying I didn't do some kind of damage to the chip. Anyway, I think I'll go back up to 4.2GHz and leave it alone for a while until I get my nerves up to the task again. You can bet I'm going to be double-checking my voltages every time before I save and exit from now on.
So since I've never overclocked Intel before I am stuck in my ways worrying about the temps as I did with my FX. At stock this little chip was running as hot at idle as my FX ran at load and when I put the Haswell under load I was stuck worrying about temps going over 55C.
So after getting over my PBOD (post-bulldozer-overcloking-disorder) I worked my way up to 4.2GHz, which seems to be a real sweet spot. It doesn't take but a small bump in voltage to 1.06v and slightly higher temps, it's lightning fast, the loading screens in Skyrim off of my SSD just look like you blink and it makes me question why I ever liked AMD in the first place.
So anyway, I kept pushing. It took me a while to get it stable at 4.3 because my little voltage bumps were no longer doing it. Finally got stable at 1.155V and max temps around 75C.
But I still wasn't happy and after drinking a few while I let prime95 run at 4.3GHz I decided to go for 4.4 and unwitttingly probably took a few years off of my CPU's life when I did.
So I try 4.4GHz @ 1.16V and 1.165V and it BSODs after a few minutes in prime95 both times. I am feeling pretty good by now and restart the comp, go into BIOS, find Vcore, and what I was thinking was "1.175V", but what my hands decided to type without express permission from my brain was "1.75" and I save and exit.
Windows boots up, I open up prime95 and start stressing the CPU, open up CPU-Z and check on the volts (1.752? Yeah that's close enough to what I typed in, all is good! ) and finally I open up HWmonitor to take a look at temps. I scroll down and see 100C maximum on all cores and I glance back over at the CPU-Z voltage again and finally realise my mistake after prime95 has been running for a minute or two at this point, so I shut it down as fast as I can and correct my mistake in BIOS, set it to 1.175V like I meant to and now it seems mostly stable at 4.4GHz with only one issue; Worker #3 hasn't stopped but it is stuck on the third 1024K test while the rest of the cores have completed a few dozen more tests.
I backed everything back down to stock to make sure I hadn't burnt out a core and it runs as good as the rest, but that's not saying I didn't do some kind of damage to the chip. Anyway, I think I'll go back up to 4.2GHz and leave it alone for a while until I get my nerves up to the task again. You can bet I'm going to be double-checking my voltages every time before I save and exit from now on.
Last edited: