cancel
Showing results for 
Search instead for 
Did you mean: 

Overclock BEFORE or AFTER OS installation

EvylCyn
Level 8
Should an overclock be done:

1) BEFORE

2) AFTER

the OS installation? And why?
Case: Cooler Master Storm Trooper
Mobo: Crosshair V Formula-Z
CPU: AMD FX-8350 Lot# 1252PGT
RAM: G.Skill Ares 1866 16Gb (2x8)
HSF: Noctua NH-D14
PSU: KingWin LZP-1000
Optical: LG WH14NS40
1,698 Views
10 REPLIES 10

Arne_Saknussemm
Level 40
Actually EvylCyn I'm not quite sure what you are asking here (but that's probably me not you...happens to me a lot;)). OC testing is, at least for me, not just about running prime overnight. I also like to test an OC using my OS for browsing the web, gaming, watching movies etc. So, I start from the perspective that I am going to test my OS running at my OC and if I get various BSODs and instability I reckon on re-installing my OS. So there will always be a final re-install of the OS when I have found an OS stable OC.

However if you are referring to the actual install of the OS on disc I generally do that at stock settings when I know what my stable OC is...

Hope that answer makes some sense :confused::)

EDIT...oops forgot to vote....so I guess I'll say before...in a roundabout after sort of way.

Arne Saknussemm wrote:
However if you are referring to the actual install of the OS on disc I generally do that at stock settings when I know what my stable OC is...

Hope that answer makes some sense :confused:

So you find your stable OC, return to stock settings, then install OS, then use the OC profile of your stable OC.
If that is correct you find your OC before.
Thanks
Case: Cooler Master Storm Trooper
Mobo: Crosshair V Formula-Z
CPU: AMD FX-8350 Lot# 1252PGT
RAM: G.Skill Ares 1866 16Gb (2x8)
HSF: Noctua NH-D14
PSU: KingWin LZP-1000
Optical: LG WH14NS40

EvylCyn wrote:
So you find your stable OC, return to stock settings, then install OS, then use the OC profile of your stable OC.
If that is correct you find your OC before.
Thanks


You don't even start OC'ing before you install the OS... - what would be the point of it?! People usually OC to get some performance increase, but without OS how can you measure the performance increase?

EvylCyn wrote:
So you find your stable OC, return to stock settings, then install OS, then use the OC profile of your stable OC.
If that is correct you find your OC before.
Thanks


Yes exactly....I figure why chance it. If my stable OC is stable because it will fail once in five years I figure stock will fail once in 10 (numbers just for example) so the best odds for the OS install will be at stock. (though I must admit I have done OS installs OCd...just forgot)

Zka17
Level 16
EvylCyn wrote:
Should an overclock be done:

1) BEFORE

2) AFTER

the OS installation? And why?


Definitely OC AFTER you installed the OS! The reason is that your system is the most stable at stock settings... - and one more thing: use memtest86+ before you would start installing the OS... it will/may save you a lot of headaches...

chrsplmr
Level 18
I'm on the shelf below the bottom shelf of the OC Gurus here .. but how, where would you even attempt this without an OS ?? Technically I guess you can go into bios without and set things to OC'ness .. but ???

"HIVIZ ???? help !!! ???" .c.

chrsplmr wrote:
I'm on the shelf below the bottom shelf of the OC Gurus here .. but how, where would you even attempt this without an OS ?? Technically I guess you can go into bios without and set things to OC'ness .. but ???

"HIVIZ ???? help !!! ???" .c.


I was thinking about using a laptop and ROG Connect...
I have another post with that question...
http://rog.asus.com/forum/showthread.php?32714-Can-Should-I-OC-with-ROG-Connect
Case: Cooler Master Storm Trooper
Mobo: Crosshair V Formula-Z
CPU: AMD FX-8350 Lot# 1252PGT
RAM: G.Skill Ares 1866 16Gb (2x8)
HSF: Noctua NH-D14
PSU: KingWin LZP-1000
Optical: LG WH14NS40

HiVizMan
Level 40
You always want to OC with a dirty OS or an OS that you are not going to keep. The reason why is simple. When your OS has its first BSOD it is more likely to have BSOD in the future.

So OC before you do your 24/7 OS install.
To help us help you - please provide as much information about your system and the problem as possible.

HiVizMan wrote:
You always want to OC with a dirty OS or an OS that you are not going to keep. The reason why is simple. When your OS has its first BSOD it is more likely to have BSOD in the future.

So OC before you do your 24/7 OS install.


This! I voted "before" but I mean exactly this. While finding stability for your overclocking it is quite possible that you'll end up with a corrupted OS installation. Specifically if you're trying to push RAM too much. Of course once you get the hang of how your hardware behaves, you're much safer while tweaking in your "24/7" installation than before but if you're just starting out and want to push things, it's better to do just that. Install OS, find your limits/stability then reinstall:)
RAMPAGE Windows 8/7 UEFI Installation Guide - Patched OROM for TRIM in RAID - Patched UEFI GOP Updater Tool - ASUS OEM License Restorer
There are 10 types of people in the world. Those who understand binary and those who don't!

RealBench Developer.