PSA: Intel Pentium G3258 + Windows 10 = fail for most users. No official Fix yet....

R

Rav3n

Gawd
Joined
Jul 24, 2014
Messages
1,013
Just wanted to save someone else some time if they have a G3258 and are trying to install Windows 10. Upgrade, clean install, upgrade install. All versions of the current retail Windows 10 version, have the offending code installed. This currently applies to all versions of Windows 10. Current as of July 29th...

Some people have reported being able to install W10 if they are not overclocking, and in some cases disable one core of the G3258. My system is completely stock and still will not install.

What happens:
Installing Windows 10 via the update tool from Windows 7 OR 8.1. ALSO OCCURS WITH A CLEAN INSTALL ISO! All CURRENT Retail and upgrade builds contain the code that does NOT allow the installation to work properly. The update runs checks, downloads Windows 10, and restarts. During the restart, the error occurs. There have been more than a few different error codes, but the error I got in particular was listed below.. When the computer restarts, the following error occurs:

Error:
0x1900101-0x20017 The installation failed in SAFE_OS phase with an error during BOOT operation
Click to expand...


Problem:
Intel sent out a microcode update to Microsoft, apparently limiting OC'ing and some "features" on the G3258 specifically. MS integrated this microcode into a MS update, KB3064209. This update happened to both Windows 7, and Windows 8.1, and it also is currently BY DEFAULT installed in the current retail/upgrade build of Windows 10, both 32 bit and 64 bit. If you un install the KB3064209, and try to repeat the Windows 10 install, it still does not work, because the microcode is already injected into the Windows 10 retail version that is current.
Click to expand...


Manufacturer responses:
Initially MS and Intel did NOT answer. This has ben going on since an update last month to Windows 10 when it was not ready for retail. Intel also did not acknowledge the problem at the time. Now today since Win 10 was "officially" released, the internet has been asking for answers from both sides.

(There have been various posts on different forums about official responses from Intel and MS. I have not directly had contact with either, so I decided to remove this part of the OP)
Click to expand...

EXCEPTIONS / Temp Work Around:
Some users have reported disabling one core on MSI boards allow the G3258 to install windows 10. Other users have stated if the brand motherboard supports disabling cores, the installation CAN work. But you essentially end up with a single core processor. And since Win 10 uses a hashtag type hardware signature as a "Key" during the upgrade process, changing to dual core later may nullify the activation. In other words, its a waste of time....
Click to expand...

**Update #2**

THE ONLY MANUFACTURE TO CREATE A WORK AROUND IS ASROCK SO FAR.... SEE THREAD HERE (ASrock website with custom BIOS update work around). ASrock actually has listened to its forum users, and created individual BIOS updates for people so they can install Win 10, and USE both cores of the G3258...



Many people with G3258's will not be installing Win 10. Hopefully this gets fixed ASAP.
 
Last edited:
Jeremy C said:
Well, that's one of my machines that's not getting 10...
Click to expand...

Thats why I made the post... to save people the last 4 hours I have spent updating drivers, and searching for answers.

If it were some obscure processor no one used... I wouldn't be as concerned. This was a HUGE cash cow for Intel. We overclockers rejoiced, the G3258 brought me back to the old days :)
 
SunnyD said:
The only winner here is AsRock. Props.
Click to expand...

Amazing how the immediately responded and made a CUSTOM bios fix never the less, for the community.

REALLY changed my mind on ASrock. Wish I had bought a ASrock board for my G3258.
 
AsRock lives up to its name :D Why would Intel try to block OC? Is the Pentium cannibalizing i3 sales?
 
PliotronX said:
AsRock lives up to its name :D Why would Intel try to block OC? Is the Pentium cannibalizing i3 sales?
Click to expand...

Seems that way. It baffles me that Intel would release a CPU dedicated to overclocking, and then push a microcode update breaking that ability, unless as you put it, the G3258 was eating too much into i3 sales for Intel's liking.

Then again, this is Chipzilla we are talking about. /shrug
 
Makes me feel bad that I broke the cpu socket in my asrock board.

If you can install with a workaround first, maybe you can use one of the activation hacks to get around it?
 
Mr. Bluntman said:
Seems that way. It baffles me that Intel would release a CPU dedicated to overclocking, and then push a microcode update breaking that ability, unless as you put it, the G3258 was eating too much into i3 sales for Intel's liking.

Then again, this is Chipzilla we are talking about. /shrug
Click to expand...


But in my case, I had a completely stock system. And it still blocked install from a G3258.
 
Last edited:
Unstableone said:
Makes me feel bad that I broke the cpu socket in my asrock board.

If you can install with a workaround first, maybe you can use one of the activation hacks to get around it?
Click to expand...

Win 10 uses a new hashtag type activation, that ties your hardware to the Win 7/8 key, creating a win 10 key based on your hardware. It then stores this information on their servers for future activation....

And if you change the CPU back to dual core, it can trigger windows to de activate.

So I am just waiting for a fix....
 
Rav3n said:
Win 10 uses a new hashtag type activation, that ties your hardware to the Win 7/8 key, creating a win 10 key based on your hardware. It then stores this information on their servers for future activation....

And if you change the CPU back to dual core, it can trigger windows to de activate.

So I am just waiting for a fix....
Click to expand...

Autokms was included in some of the pre-final builds I tried, think you had to use it while the activation servers were down.

Not sure if win10 is "smart enough" to be able to tell the difference, but it would be better than being screwed when the timer runs out.
 
@Rav3n: would you have a source link(s) for:

"**update, MS and Intel respond....**
Intel has officially answered, stating they sent the code to MS, who implemented it. Intel says MS is responsible for a fix or work around.

MS has officially FINALLY acknowledged the issue, stating it was Intel who created the issue, so INTEL is responsible for issuing a fix."

Thanks.

FWIW I went to Intel with a post (and ASUS via Tech Support for my H81M-PLUS board) plus added mine to other 'Insider' MS voices to no avail.
 
Rav3n said:
I dont know what the actual microcode did for sure, but it was some how made to limit the OC, or in some cases disable the OC by not allowing BIOS to force the OC at boot.

But in my case, I had a completely stock system. And it still blocked install from a G3258.

It looks from the outside like Intel tried to push this little microcode change... to tune back the G3258.

Just from a glance, and yes, some shady sources for info at this point. But I do know for sure, the installation currently does not work. Even at stock.
Click to expand...

WTF? I suspect there is going to be a LOT of unhappy G3258 owners grabbing their pitchforks. I have stayed away from budget Intel chips since the CuMine Celerons. I was appalled to find out a Celeron 800 performed like a P3 450/500 in most games. I never bought a budget chip since. Either I wait until a previous gen high end part comes down to mid-range prices, or I save and bite the bullet. Hearing about these woes vindicates this decision.

Sorry that this is happening to you guys. It's not right.
 
I have a G3258 with ECS Z87 micro atx that installed and runs 4.4 GHz 2 cores 2 threads on Windows 10 build 10240 from the insider program and still in fast ring, or are we talking release? ECS does have a bios lock though, have to enable a jumper to flash.
 
m_isom said:
I have a G3258 with ECS Z87 micro atx that installed and runs 4.4 GHz 2 cores 2 threads on Windows 10 build 10240 from the insider program and still in fast ring, or are we talking release? ECS does have a bios lock though, have to enable a jumper to flash.
Click to expand...

Release version
 
Asrock H97M Anniversary + G3258 here....

I've been wrestling with this for 4 days now. The 'death loop' coincided with me moving the PC and desk out so I could install a 50" TV on the wall above the desk. When I plugged everything back in I got the death loop. Reboot, 'Windows is launching startup repair...', reboot, rinse and repeat. I tried reinstalling from a newly created Windows 10 RTM USB installer, a DVD, everything... it would just boot loop no matter what. I even went so far as to start checking sticks of DDR3 and other components.... It wasn't until I gave up and started Googling that I discovered the source of the problem.

In the case of the Asrock H97M it doesn't matter if you're overclocking or not. The death loop happens even with completely stock settings. The ONLY workaround is to disable the second core of the G3258 in the BIOS. And that's one shitty workaround because ... ONE FUCKING CORE!

I have a really hard time believing that this was done purposefully by Intel in the microcode update they sent to MS... I'm sure it's some monumental screw up by some engineer at Intel. But my fucking GOD what a screw up! The G3258 is hugely popular and since the microcode update is rolled into the Windows 10 RTM release, they've pretty much made it impossible to install / upgrade any affected system. Even trying to do a clean install from a DVD or USB flash drive affected systems are just going to boot loop.
 
As I am reading, it seems to be related to the non-Z chipset overclocking. Intel had a fit when the lower end boards could overclock I5 and I7, but I thought they relaxed their stance for the Pentium. Why spend $$$ to overclock a $ CPU? If I had not found the Z87 for $30 I would have tried one of these affected boards for the G3258 build.
 
I was able to run Windows 10 preview just fine on the G3258 + MSI MATE. Guess this is just RTM?
 
defaultluser said:
I was able to run Windows 10 preview just fine on the G3258 + MSI MATE. Guess this is just RTM?
Click to expand...

It started in build 10162 and onward, possibly even the previous build although no one but Microsoft knows for sure.
 
defaultluser said:
I was able to run Windows 10 preview just fine on the G3258 + MSI MATE. Guess this is just RTM?
Click to expand...

It only involves the non-Z boards.

I wonder if you guys just changed the microcode to version 19 if that would do the same. I went over the two BIOSes that ASRock posted and the only difference was the microcode update from 09 to 19.
 
Rav3n said:
Amazing how the immediately responded and made a CUSTOM bios fix never the less, for the community.

REALLY changed my mind on ASrock. Wish I had bought a ASrock board for my G3258.
Click to expand...

I was about to say my install works fine u til I saw the asrock post.

I only buy asrock boards now and have for the last couple of years. They have given me amazing customer support and have been quick with fixes and bios updates. I know a lot of people hated on them at first so I'm glad to see them getting some positive feedback here.
 
Made an account to say this:

I talked with Intel support and he gave me something at least:

Adolfo: Ok this is what I can do I can create a Service Ticket number and notify the engineering department to see if they can do something about it. But it will take some time to get an answer from them.
Click to expand...

He also said he will email me when they let him know anything.
 
Intel intentionally gimping a released product already in the hands of consumers, to push consumers to buy a more expensive product, would be a pretty big fucking anti-trust violation, not to mention a very stupid and obvious one, so I like to hope this was not their goal and this was instead just some coding screw up. An unintentional mistake is of course still a fairly significant problem, but at least it's not a seriously illegal one.
 
From what I understand this is in Microsoft's hands as far as a fix goes, reason being it's a soft-microcode update. It's loaded in the OS at boot and replaces or overrides the microcode that's on the CPU and motherboard BIOS. I could be totally wrong on that though.....

But M$ is pointing the finger at Intel for providing them with the offending microcode update in the first place.
 
If anyone still has a copy of the H97M Pro4 BIOS posted on the ASRock forums, I'd really appreciate if you could send it my way. The link on the forums is no longer available, and I'd love to be able to install Windows 10 on my H97M Pro4/G3258 build.
 
Got another update from Intel:

I wanted to let you know what our engineering department will try to replicate the issue, but we will need to find a processor with the exact same model of the one that you have, so we will required about one week to have an answer from them
Click to expand...
 
defaultluser said:
I was able to run Windows 10 preview just fine on the G3258 + MSI MATE. Guess this is just RTM?
Click to expand...

Just so I'm clear before I try and upgrade myself, you've got the G3258 with a MSI PCMate z97 board correct? That's my exact setup so I just want to be sure I'll still have overclocking abilities on both cores with this board. TIA
 
derek533 said:
Just so I'm clear before I try and upgrade myself, you've got the G3258 with a MSI PCMate z97 board correct? That's my exact setup so I just want to be sure I'll still have overclocking abilities on both cores with this board. TIA
Click to expand...

I have not overclocked. I've been holding-off on that fun until I have a free weekend.
 
ASRock have updated almost all of their affected boards with new BIOS revisions that make them function again with Windows 10 (and previous versions of Windows with the aforementioned microcode update hotfix). However overclocking is effectively disabled....

As much as I found it hard to believe earlier it really does look like Intel sent out this microcode update to purposefully disable overclocking these processors on anything but Z chipsets. That's a low life, shitty, dirty thing to do. Hell, a lot of these H61M boards were sold in combos with the G3258 with overclocking hyped as a feature... and we're not just talking Asrock board here either.
 
Doesn't work on my z87 Classified unless I disable 1 core. It will just restart loop when it tries to load windows from the HDD. I had to disable the core as well to upgrade. Running stock setting with it.
 
I just ran into this today while performing a clean install of win 10 (not an upgrade).

G3258 on an Asus H87i-plus motherboard. Would not load the setup from dvd or usb drive. I installed windows 8.1 and then tried an install from windows explorer. Win10 setup returned a SAFE_OS error.

G3258 was overclocked. I set it back to stock speed and windows 10 installed perfect.
 
Got a computer that's also effected by this, ASUS H81M-D PLUS + G3258. It's on Win7 right now, and I was trying to upgrade to 10, so far nothing has worked and it was never overclocked. I may try the 1-core trick, but I feel a bit wary about modifying windows files and have it break stuff on next update. Waiting it out for now, but this is a massive load of crap from intel on this, none too pleased with them right now.
 
I don't own a G3258 personally, but this is some bullshit.

Sorry all you guys are having such a hard time etc.
 
You must log in or register to reply here.
Back
Top