Win 10 G3258 issue, microcode?

People are reporting a one core as a fix, this is not a fix. MY machine is crippled. 

Cause I love running on one core.... Seriously get this one fixed. 

 

Discussion Info


Last updated October 13, 2019 Views 25,163 Applies to:

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

Hello,

Welcome to Microsoft Community. I will certainly help you on the issues that you face with Windows.

 

The issue description seems a bit unclear and I would like to have a better understanding before we start working on it. I would appreciate if you could help me with more information.

Please reply with the detailed description of the issue including the issue, error message or code (if any) and make-model of your computer.

I would also suggest you to refer to the Microsoft Help Article given below.

https://support.microsoft.com/en-us/kb/555375

Please post back with the required information, we'll be glad to assist you.

The issue is that with all builds after 10130 a computer with the G3258 cpu would be stuck in a bootloop unless one core is disabled in the BIOS. As you can imagine, for a dual core CPU to run with one core disabled is a rather large hit to performance. It is most likely a microcode issue, and a quick Google search would be enough to show how prevalent this issue is, since this is a CPU rather popular with budget system builders.

I cannot speak for all users of this CPU, but I first encountered this issue when trying to upgrade from 10130 to 10162. In addition, please stop giving formulaic responses to try 20 different things; this issue is all over the internet.

Here

Here

Here

Here (I did encounter this error before disabling one core, so it is the same issue.)

I could go on and on. I understand this is not a popular OEM cpu, so perhaps it is treated as low priority for the RTM release, but the silence regarding this is deafening. It would be great if a rep from Microsoft can give an update on whether this bug is being worked on, and if there is a timeline as it really is a dealbreaker. Personally I am a developer and we have been running a combination of Windows and Linux machines, but how can I continue to recommend Windows if such low-level issues arise with little response from Microsoft, and has not been fixed even a few days before RTM? With Linux-based systems, it is trivial to simply revert back to old kernels if upgrades fail; if Windows wishes to continue the tradition of the OS build being intricately tied to the kernel builds, perhaps testing needs to be much more thorough.

I have submitted a thread of my own, and I was dealt with the same formulaic response to do a bunch of stuff. I have done everything, nothing worked except disabling one core in the BIOS.

Sahil,

Just google "windows 10 G3258 problem". Google is picking up on this, why isn't Microsoft? Please pay some attention. It's isn't so hard to piece together what's happening

Refering to generic Microsoft articles isn't adressing the real problem. Somehow after build 10130 code was introduced that's seems to effect systems based on an Intel G3258 processor. From the different posts it seems the chipset (H81 or Z97) doesn't really matter. The processor seems key. 

Simply boot any G3258 based system (with all cores enabled) and windows 10 won't boot after build 10130  (10240, 10168 etc). Upgrades from any build (10130 or less) from to 10168/10240 will fail with 0xC1900101 - 0x20017 error

or a boot loop. Any attempt of a clean clean system install and/or boot from 10168/10240 installation media (DVD / USB) will result in a boot loop.  Believe me I've tried everything and so have others with the same results.

The only confirmed "workarround" so far is disabling a processor core in the BIOS. Effectively turning the G3258 into a single core processor. Once you do that all other options suddenly work: upgrade via windows update, upgrade via DVD/USB, clean install from DVD/USB. This workaround will allow you to update windows 10 to build TH1 10240 via any of the usual means. However once you are on 10240 and try to enable all processor cores again you are back at a boot loop. 

Unless Microsoft wakes up and fixes this bug any G3258 system will not be able to upgrade to windows 10 as the majority of system owners won't even begin to grasp howto disable a core in the BIOS (if they even now what a BIOS is)

Apodictus

It seems that the issue occurs for windows 7 and 8 users as well, and all signs seem to point to a Intel microcode update as the reason. The update is KB3064209. Unfortunately it seems as though the microcode update is packaged with later Windows 10 builds and you cannot revert to anything.
There are plenty of posts that describe the issue, below that are referenced. The user base just wants acknowledgement of the issue, acknowledgement is the first step in working on correcting it. This is a pretty popular CPU if not fixed by the 29th....You'll defiantly get some calls on this one.

I have made some progress. I have found that it is possible to boot with both cores, however, the BIOS must be completely reset; it would be unable to boot with any changes to the CPU settings whatsoever. That includes overclocking, but also includes other stuff such as disabling certain lower power states, etc.

It is still frustrating, but at the very least it is much more usable.

I have made some progress. I have found that it is possible to boot with both cores, however, the BIOS must be completely reset; it would be unable to boot with any changes to the CPU settings whatsoever. That includes overclocking, but also includes other stuff such as disabling certain lower power states, etc.

It is still frustrating, but at the very least it is much more usable.

 Tried a BIOS reset anyway and still loops. I am on a B85 chipset, not overclocking or anything still loops.
Didn't work for me either, but I just reset to UEFI defaults. Did you clear CMOS to completely reset?
Yup I had to open up my computer and use the hardware jumper to reset.

Just to be clear here- is that to get BOTH cores working AND overclocking or just BOTH cores working at stock speeds (3.2GHz)?

I can run both cores @ stock speed (3.2GHz) or ONLY 1 OC'ed (4.2GHz)- but not both. That's without clearing/resetting CMOS using jumper. Though I did reload latest BIOS version 2205 as part of process to try to get both cores to work OC'ed, but 2205 was already on before I ran into problems anyway. I doubt reloading 2205 made any difference.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.