it's late at night and I'm home after a long day at work OC'ing my i5 3570k.
I find the lowest stable vcore for 4.4ghz (1.248) on manual.
Next I'm gonna find an offset and call it good. So at 4.4ghz I put vcore on auto thinking "it'll be stupid high as usual (when I punch in 4.2ghz auto vcore puts it at 1.32v) but I need to know where it lands first so I can enter a value in the offset field"
but holy shit, when I booted up my cpu fan was going full blast and I opened up cpuz and had a heart attack, my vcore was hitting 1.52v. I held down my front panel start button to do an emergency shutdown. Then I attempted to boot it back up but then it said it wasn't detecting my keyboard. So I shut the whole thign down again and unplugged my computer and opened my case up and jumpered the cmos. all while my heart is pounding. Got my bios back to default. my pc booted into bios and into windows and started up valley heaven benchmark and let it run for a bit and everything looked stable.
So am I alright? did I get away with it?
I find the lowest stable vcore for 4.4ghz (1.248) on manual.
Next I'm gonna find an offset and call it good. So at 4.4ghz I put vcore on auto thinking "it'll be stupid high as usual (when I punch in 4.2ghz auto vcore puts it at 1.32v) but I need to know where it lands first so I can enter a value in the offset field"
but holy shit, when I booted up my cpu fan was going full blast and I opened up cpuz and had a heart attack, my vcore was hitting 1.52v. I held down my front panel start button to do an emergency shutdown. Then I attempted to boot it back up but then it said it wasn't detecting my keyboard. So I shut the whole thign down again and unplugged my computer and opened my case up and jumpered the cmos. all while my heart is pounding. Got my bios back to default. my pc booted into bios and into windows and started up valley heaven benchmark and let it run for a bit and everything looked stable.
So am I alright? did I get away with it?
Facebook
Twitter
Instagram