MSI H81M-E33, attempt to overclock G3258 (new BIOS but overclock fails completely)
MSI H81M-E33, attempt to overclock G3258 (new BIOS but overclock fails completely)
I've noticed many links but haven't found solid videos of someone successfully overclocking this board. Since version 6.6 or earlier, updates have made it possible to overclock the G3258 on this platform. I've even tried a newer version, probably 6.7. Once I attempt to push speeds beyond 3.2, anything at 3.3 or higher causes the system to load Windows but never displays the overclocking indicators. It then restarts and either shows BIOS or prompts for a repair before returning to normal operation. (It never mentions a failed overclock.) It's frustrating because everyone else seems to manage it well, except me. Also, after saving settings and going straight to BIOS, the current speed is shown, suggesting it does overclock but fails to boot past Windows. Please help if you've encountered this problem and found a solution. Sometimes having a different motherboard with the same issue can be useful if you discovered something. Thanks.
I've noticed many links but haven't found solid overclock videos for this exact board. Since version 6.6 or later there are updates that allow overclocking the G3258 on this board. I even have a newer version, probably 6.7. Once I try to overclock beyond 3.2, anything at 3.3 or higher just loads the Windows screen but doesn't show the cycling balls. It restarts and then displays BIOS or asks to run a repair or start normally. It never mentions a failed overclock. It's frustrating because everyone else seems to do it except me. Also, after saving settings and going straight to BIOS, it shows the current speed but never gets past the Windows loading screen.
Having the same problem again. I just installed these components and assembled my budget gaming PC yesterday. Updated the BIOS to version 6.7, but everything else is fine except it won't even start to O/C 3.3 on Windows. I'm not sure what to do now after spending all day trying to get it running.
Model: MSI H81m-E33
CPU: G3258
Cooler: CM Hyper 212 evo
PS: Corsair cx430M
GPU: Sapphire Radeon R7 260x
RAM: 2x4GB GSKILL Sniper
I'm trying to reach the bottom of this. It would be foolish to drop down to version 6.6, wouldn't it?
DuckDastardly :
Same problem here. I just installed these components and set up my budget gaming PC yesterday. Updated the BIOS to 6.7 and everything else, but I still can't get it to open to 3.3... Windows won't start. I'm not sure what to do now after spending all day trying to get this thing running.
MB: MSI H81m-E33
cpu: G3258
cooler: CM Hyper 212 evo
PS: Corsair cx430M
gpu: Sapphire Radeon R7 260x
ram: 2x4gb GSKILL Sniper
I recently attempted a downgrade to 6.6, but it didn't work. It seems the system remains unresponsive even after overclocking to 3.3.
Damn... anyone have a chance to assist? This feels really unfair...
Go into the BIOS, set everything back to default version 6.7. Navigate to the "OC" section, adjust the "CPU Ratio" to 40 and "CPU Core Voltage" to 1.2. Press X in the top right to save and exit, then it should restart. Woody
Same issue occurred again. I followed exactly what you instructed, are you certain no other adjustments were made in the settings? Please share a photo of your bios if possible. Thank you.
I've noticed many links but no quality videos of someone successfully overclocking this board. Since version 6.6 or later, updates have been released allowing overclocking on the G3258. I even have a newer version, probably 6.7. Once I attempt to overclock beyond 3.2, anything at 3.3 or higher causes Windows to load but never displays the cycling balls. It then restarts and shows BIOS or prompts for a repair before returning to normal. This is frustrating because everyone else seems to manage it without issues. Also, after saving settings and going straight to BIOS, the current speed appears, but it never boots past Windows. Could someone with this problem help? It would be useful if you've found a solution, especially if you have a different motherboard but the same issue. Thanks for your time.