Can no longer OC with new MOBO?

PhotoMajor

Junior Member
Apr 20, 2013
4
0
0
Last night I accidentally fried my MSI z68 ed55 mobo by improperly seating RAM.

I picked up a new MOBO this morning, installed everything, but can no longer OC.
Not manually anyway.

My current rig -

MSI z77a g45
8600GT
12GB Corsair Vengeance RAM
Intel QC 2500k w/ Cooler Master Hyper 212 Plus
GS600 PSU

The only way I can OC is via the OC genie.
Initally, with the old MB, I had it @ 4.5ghz. With the OC Genie, it OCs to 4.2ghz.

Here's the weird part. If I go into the OC genie options, and change the multiplier from auto to 42, it still doesn't boot. Even though the settings are identical.

As it stands right now, everything is on auto in the OC Genie option.
So ram is @ 1333 and cpu is at 4.2. I really can't see what I'm missing.

Also, temps across the board are about 32C

Thanks
 

2is

Diamond Member
Apr 8, 2012
4,281
131
106
Well the settings may be identical but the board isn't and there could be small enough variances that make the new one unstable. Particularly if you had tuned your voltages in the previous system to be just barely enough for "stability."

Instead if trying to duplicate the same overclock with the same settings, you should probably just treat this as a new setup and go from there.
 

PhotoMajor

Junior Member
Apr 20, 2013
4
0
0
Well the settings may be identical but the board isn't and there could be small enough variances that make the new one unstable. Particularly if you had tuned your voltages in the previous system to be just barely enough for "stability."

Instead if trying to duplicate the same overclock with the same settings, you should probably just treat this as a new setup and go from there.

You misread my post. The settings are identical within the same board. Only one is set manually, and the other is set via OC Genie.
 

Idontcare

Elite Member
Oct 10, 1999
21,110
64
91
That's weird, and sucks :( I feel bad for you but have nothing to offer beyond my condolences. I hope someone here can help you troubleshoot this problem.