Official Seven Forums Overclock Leader boards [2]

Nice OC NoN, Updated. Yes, I thought you would have known by now, you only need to be stable just long enough to validate lol. I don't think my CPU would have run that speed for 1 second longer not alone attempting to run IBT!

Thanks Paul Updating leaderboard!

Grabbed two places and also YES i'll cheat enough now 'cause IBT up the 4.9GHz might not do it, i can see tears already for a fried mobo/cpu combo!

NoN, it's not cheating here. None of us have ever claimed our highest overclocks to be stable. And, I wouldn't suggest you try IBT at 5.0. I have some pretty good cooling and can do it, but it gets pretty toasty even under water. That chart you showed is recommended vcore for every day overclocks. I can assure you they go much higher than that on 'suicide' runs.

essenbe said:

NoN, it's not cheating here. None of us have ever claimed our highest overclocks to be stable. And, I wouldn't suggest you try IBT at 5.0. I have some pretty good cooling and can do it, but it gets pretty toasty even under water. That chart you showed is recommended vcore for every day overclocks. I can assure you they go much higher than that on 'suicide' runs.

I was looking to highest point being stable with my mobo, i know now.

Of course i understand "we ever ever claimed our highest overclocks to be stable".

I just can see some "suicide runners" around, past the 4.9Ghz going green. I'll join the club soon or later!

Are you guys after some high OC'ing doing some repair start-up or scannow command in case corrupted files happening during the run?

I have noticed that up the 4.7GHz on mine, some apps won't launch properly or takes time to load, therefore i do end processes for them not interfere, just in case. I'm in Raid/Caching setup so i have to temporarily disable it to have the command & OS at boot for winRE.

Sometimes I get the start up repair screen, but I choose start Windows normally and it's fine, I know why I got a BSOD, self inflicted.

I couldn't tell you NoN, my CPU blew up on that last run lol.

But no I never had that before that.

When i was working OC'ing on 4th attempt (4.8Ghz), after validation, when came back to reasonable settings i had to do some repair start-up and a scannow command 'cause multiple BSODs have mess the OS (HID keyboard driver mainly).

This fifth (4.9GHz) gave me Bsod only before the 10 hours running (two first boot, the time to find the right vCore) and one Bsod after returning back to 4.2Ghz but not straight after... Might in case do scannow at boot just to check.

EDIT: Did sfc /scannow at boot and a repair start-up (3 times), no particular errors were found.

Looking good Madcratebuilder