***G3258 Owners*** - Windows 10 will not install/boot when overclocked

[Pill Monster]

Are you sure this isn't on purpose to stop G3258 overclocking?

Yes, Microsoft logic....Let's celebrate 20 years of Pentium by releasing a highly overclockable chip and then basically nerf it. Nice one.

Of course, because overclocking is dangerous and to blame for several issues with Intel CPU's that could computer crashes or functions incorrectly.

About this update
This update fixes several issues with Intel CPUs that could cause computer crashes or functions incorrectly. Also, this update improves the reliability of computers that uses certain Intel CPUs .

Microsoft are just looking out for your best interests, like they always do

 

[xorbe]

Yes, Microsoft logic....Let's celebrate 20 years of Pentium by releasing a highly overclockable chip and then basically nerf it. Nice one.

No, Intel. MS has no ability to create CPU microcode.

 

[...PACMAN...]

No, Intel. MS has no ability to create CPU microcode.

yes oops

 

[plonk420]

mine won't even install at stock clocks (10160, 10240, and whatever the official MS tool downloads). 10130 works nearly perfectly fine.

 

[theonedub]

Any news or update on a fix for this?

 

[OneMoar]

Any news or update on a fix for this?

its a microcode issue so one of two fixes are possible (from what I can tell it Only effects H87, H81, Q87, Q85, B85,H97)
1. microsoft issues a patch to work around the problem(which means lnstall media would need to be re-packaged with the fix) not likely because its the board vendors fault and Not Intels.
2. board vendors need to issue a update

the issue occurs on all boards -except Z87/Z97
its likely a a issue with board vendors using H@X0R'd bios's to get around the overclocking lockout on non Z boards

 

[Nordic]

Having issues myself. Updating my bios to the latest, which has microcode revisions. Will post if I have better luck afterwords.

 

[fat_slug]

Possible fix: delete mcupdate_GenuineIntel.dll in C:\Windows\System32

Supposedly this will prevent Windows 10 from borking the CPU with the new microcode.

 

[xorbe]

Possible fix: delete mcupdate_GenuineIntel.dll in C:\Windows\System32

Supposedly this will prevent Windows 10 from borking the CPU with the new microcode.

Pro-tip, rename if daring, no need to delete ...

 

[theonedub]

Looks like some MB manufacturers are releasing new BIOS updates (Asrock in particular is already rolling a couple out and more in the coming days). I'll just sit tight for the BIOS update for my Asrock board before upgrading my G3258 machine.

 

[R0H1T]

its a microcode issue so one of two fixes are possible (from what I can tell it Only effects H87, H81, Q87, Q85, B85,H97)
1. microsoft issues a patch to work around the problem(which means lnstall media would need to be re-packaged with the fix) not likely because its the board vendors fault and Not Intels.
2. board vendors need to issue a update

the issue occurs on all boards -except Z87/Z97
its likely a a issue with board vendors using H@X0R'd bios's to get around the overclocking lockout on non Z boards

Probably, have one H97m pro4 myself, now Asrock removed OC support completely with the latest V2.0 BIOS

No, Intel allowed it, though tacitly, for well over a year now (google H97 overclock) & seems they're the ones pushing for it to be blocked (yet) again! This reminds me not to trust that company ever again & this will be my last Intel build ever

To make matters worse, I updated to RTM & then after a few (optional?) updates I'm back to boot loop with no way to recover the installation. System restore or even reset/refresh doesn't work either since the system won't boot from any media having win10

 

[BiggusDoggus]

Just to confirm here - the Windows 10 upgrade isn't working even if the G3258 is at stock speeds. Yes, it appears that if one core is disabled it will work, but again only if even that one core is not overclocked. And who the hell wants that!?

There's 4 days of my life trying to get the upgrade to work I'm never getting back.

 

[Nordic]

Having issues myself. Updating my bios to the latest, which has microcode revisions. Will post if I have better luck afterwords.

No luck.

Possible fix: delete mcupdate_GenuineIntel.dll in C:\Windows\System32

Supposedly this will prevent Windows 10 from borking the CPU with the new microcode.

Will try this. I know it goes against proper troubleshooting, but I am going to disable one core while I do this. I just want windows 10 installed. I can fix it later. It takes almost 24 hours to get windows 10 to upgrade on this pc, while it took 3 hours on my slower laptop.

edit: This worked. I deleted that file and ran with one core while installing. After install I tried running it with both cores installed, and it failed to boot. I eagerly await a bios that will allow me to enable both cores. For now I am happy that I have the install out of the way. The computer is not being used much right now, so a single core is not a concern.

 

[ismaxGG]

No luck.

Will try this. I know it goes against proper troubleshooting, but I am going to disable one core while I do this. I just want windows 10 installed. I can fix it later. It takes almost 24 hours to get windows 10 to upgrade on this pc, while it took 3 hours on my slower laptop.

edit: This worked. I deleted that file and ran with one core while installing. After install I tried running it with both cores installed, and it failed to boot. I eagerly await a bios that will allow me to enable both cores. For now I am happy that I have the install out of the way. The computer is not being used much right now, so a single core is not a concern.

It has served you, How I can resolve this problemmm??????? Please, answer me as soon as possible!!!!!

 

[OneMoar]

It has served you, How I can resolve this problemmm??????? Please, answer me as soon as possible!!!!!

you can't your motherboard vendor must release a updated bios

 

[theonedub]

So the updated BIOS from AsRock allows Win10 to be installed, but disables the ability for the non-Z motherboards to overclock the CPU (known as the NonZ OC Function on their boards). I wouldn't exactly call that a fix.

The entire situation makes little sense to me. For Intel to be disabling the ability for non-Z MBs to overclock after being aware of it AND allowing it for such a long period of time would be an incredibly odd and poor decision. I don't want to touch these new BIOSes until Intel makes some sort of statement or correction so I don't have to deal with a possible BIOS downgrade, etc.

 

[OneMoar]

intel didn't allow anything the board vendors pretty much said fuck it and did it anyway...
and now intel put a stop to it
pretty simple is you ask me
sure its a dickmove but thems the brakes

 

[Nordic]

It has served you, How I can resolve this problemmm??????? Please, answer me as soon as possible!!!!!

If you read my post you would of saw what I did to get windows 10 to install. You would also see that I can only use 1 core because of it.

you can't your motherboard vendor must release a updated bios

I mentioned earlier I was updating my bios, but I found out that the bios were from May 2015. They do not have the necessary microcode revisions yet still I was able to install windows 10.

 

[hatchet5891]

I have an ASRock H97M Anniversary motherboard and updated to the latest bios and was able to finally upgrade to windows 10 with a G3258. I think motherboard makers are going to fix this microcode issue before Intel or Microsoft so I would watch for new bios updates. I know ASRock's update came out a few days after Windows 10 release. I didn't have to do any silly single core things or anything either, but the microcode issue should have been fixed before Windows 10 launch in my opinion.

 

[theonedub]

The Asrock BIOS updates disable overlooking though, which is a shame. Still hoping for a compromise between MB manufacturers and Intel.

 

[hatchet5891]

The Asrock BIOS updates disable overlooking though, which is a shame. Still hoping for a compromise between MB manufacturers and Intel.

That is a shame. I don't over clock so luckily it doesn't matter to me. Hopefully somebody officially fixes it for the people who like to OC. Lucky you brought that up.

 

[Solaris17]

But those boards aren't meant for overclocking? I mean it totally sucks for those affected but in reality these platforms never were supposed to support overclocking so manufacturers giving you the ability to begin with only instilled the false belife that it was supposed to be there. IMO

 

[theonedub]

It was just a little underhanded to not address the issue directly and instead have people find out when trying to update Windows. It's not as if Intel was unaware that manufacturers were offering boards with these features.

 

[Solaris17]

It was just a little underhanded to not address the issue directly and instead have people find out when trying to update Windows. It's not as if Intel was unaware that manufacturers were offering boards with these features.

meh devils advocate in a way i guess you could say they solved the problem? What is more interesting to me is how they are doing it? Im curious as to why modifying or deleting the authentic intel dll allows the use of the chip overclocked on some systems. but only in single core mode? That doesnt make much sense. I can only imagine its a break in the chain if you will. There has to be more too it. They have to be pulling motherboard information and making the distinction. If thats the case all taking the dll out of the equation does is confuse the OS as to what intel CPU is used on the mobo. The actual problem isnt fixed. That also probably explains why only one core works since it cant use the advanced sync or call functions to the CPU itself. meaning that HT encryption entire cores etc are probably unavailable. though im sure WMI pulls the information fine.

 

[archie]

I just finished upgrading to W10 on an overclocked g3258. Went fine in one pass without messing with the BIOS. I suppose the fact that I have a z97 mobo helped.

My understanding in that this processor was explicitly designed to be overclockable with the z97 chipset and no other. Mobo manufacturers didn't agree and released tweaked bios'es to unlock the pentium on other chipsets. Maybe Intel decided to get back at them by releasing this stupid microcode for Windows and ... put their foot in their mouth. As a result, any G3258, OC'ed or not would have issues with Windows, unless the chipset was Z97 or the mc-update DLL file was removed. Both Intel and Microsoft are to blame for this. Harshly I reckon.

Before upgrading (which required a registry edit in W8.1 for completion), I renamed the microcode DLL file in ../system32, just in case. I was ready for the next boot to fail and have to tweak the BIOS until I could rename again in W10. Did not happen : the update took about 30 minutes clocked at 4.3.

One could feel some anger towards those geeks working for giant corporations/administrations, crossing the line farther every day. First time I felt really angry about this was 10 years ago about the Sony rootkit. It's getting worse every year and this is a nice illustration of how there doesn't seem to be a way back. Just like I have been boycotting Sony for 10 years, I might consider going AMD, until another competitor finally emerges (like it will aver happen...).

I bought this nice (and expensive) z97 mobo with the idea of purchasing the most expensive broadwell processor later on the road and be OK for a few nice years. Not sure I'll go along with my plan after all.

Angry