Jump to content

W10 won't boot after changing CPU ratio (G3258)

So i attempted to overclock a g3258 to 3,3 ghz (just to try it out)

 

The problem is that W10 won't boot when i change the CPU ratio from 32 to 33. it will keep on rebooting over and over again. I also changed the Vcore from auto to 1.1

 

My motherboard has an updated BIOS and it's a MSI H81i motherboard.

 

Does someone has a suggestion what my mistake is?

Link to comment
Share on other sites

Link to post
Share on other sites

So i attempted to overclock a g3258 to 3,3 ghz (just to try it out)

 

The problem is that W10 won't boot when i change the CPU ratio from 32 to 33. it will keep on rebooting over and over again. I also changed the Vcore from auto to 1.1

 

My motherboard has an updated BIOS and it's a MSI H81i motherboard.

 

Does someone has a suggestion what my mistake is?

The problem is your H81 motherboard.

You should only overclock on Z boards.

I wonder how it was even possible for you to change the multiplier.

 

 

 

 

Link to comment
Share on other sites

Link to post
Share on other sites

1.1 seems really low to me for vcore.

Try overclocking from within Windows instead of from bios.

When in doubt, re-format.

Link to comment
Share on other sites

Link to post
Share on other sites

The problem is your H81 motherboard.

You should only overclock on Z boards.

I wonder how it was even possible for you to change the multiplier.

You can. Don't post if you're wrong

Link to comment
Share on other sites

Link to post
Share on other sites

Give it littlebit more voltage ?

32 Ratio does boot with 1.1v.. 33 can't be that much more to raise voltage right?

Link to comment
Share on other sites

Link to post
Share on other sites

32 Ratio does boot with 1.1v.. 33 can't be that much more to raise voltage right?

If you havent tried it yet, you might as well. It might be just enough to require that little extra.

When in doubt, re-format.

Link to comment
Share on other sites

Link to post
Share on other sites

You can. Don't post if you're wrong

You know, I kinda have to post wrong stuff to learn new stuff. That's how life works.

You make a statement, people proof you're wrong and you learn.

Only weak people hide and don't say anything.

Oh yeah, and you're not completly right. It depends on your motherboard:

http://forums.anandtech.com/showthread.php?t=2389948

 

 

 

 

Link to comment
Share on other sites

Link to post
Share on other sites

32 Ratio does boot with 1.1v.. 33 can't be that much more to raise voltage right?

Thats not always true. Processors generally hit a point where the next 100mhz takes far more voltage than the previous 100mhz. The silicon lottery will determine this per chip.

Link to comment
Share on other sites

Link to post
Share on other sites

32 Ratio does boot with 1.1v.. 33 can't be that much more to raise voltage right?

idk men when i had my intel i7 4820k on 4.4 ghz 1.2 volt worked fine but 4.5 nope i had to turn it up to 1.35 to work.

Link to comment
Share on other sites

Link to post
Share on other sites

idk men when i had my intel i7 4820k on 4.4 ghz 1.2 volt worked fine but 4.5 nope i had to turn it up to 1.35 to work.

But you didn't have a H81 MoBo lool

Link to comment
Share on other sites

Link to post
Share on other sites

32 Ratio does boot with 1.1v.. 33 can't be that much more to raise voltage right?

 

There's always a wall somewhere. Such behavior is not unheard of, and 1.1 V does sound a tad low, I suppose. Try goosing the vcore up to 1.2-1.25 V or so and see if it will boot.

 

Your BCLK still at 100 MHz, right? Best to leave that alone on a Haswell system.

Link to comment
Share on other sites

Link to post
Share on other sites

there is an issue with windows 10 and the pentium overclocking. google it. 

Link to comment
Share on other sites

Link to post
Share on other sites

there is an issue with windows 10 and the pentium overclocking. google it. 

Oh.. Well i broke my motherboard in the process but thanks for telling me LOL

Link to comment
Share on other sites

Link to post
Share on other sites

didn't it post? i tried yesterday. if the proc is OCed or even XMP settings enabled it would just boot loop.. so i installed Win 10 on base clocks and all that default settings.. after installation  you can delete a file on System32 (i dont know exactly the name) to enable OCing. then it worked for me.. running 4.0GHz on G3258 on a H81 mobo.. :D

Link to comment
Share on other sites

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×