Win 10/g3258/h81 microcode issue = no boot/install

[lyssword]

Just starting this thread to keep track of g3258/h81 issue, apparently intel has put out some kind of microcode to disable OC'ing on h81. Issue can only be fixed by disabling 1 core, which really cripples the performance. I'm sticking with 8.1 till this is fixed either via MS/Intel or h81 manufacturers. http://answers.microsoft.com/en-us/...eathloop/c4319829-6200-40aa-95f7-040fbc7f3f55

 

[zShowtimez]

Good heads up.... Looks like the HTPC is sticking to Win7.. =/

 

[ShintaiDK]

Windows 10 is really just a public beta still. So dont put too much into it yet.

My PC at default couldnt find the network. Because the Intel 217-V driver that Microsoft added to RTM is broken.

Also if you disable a NIC, you cant reenable it because Explorer crashes due to the latest Windows 10 security patch.

 

[SunnyD]

According to this AsRock thread, it's not the H81 chipset but rather the G3258 CPU and a specific Microsoft update (KB3064209) that got pushed across all OS's, Win7 and Win8 aas well that had the issue. It just so happens that Win10 users had no choice but to have the update forced upon them, so they're experiencing the issue immediately.

Source: http://forum.asrock.com/forum_posts.asp?TID=441&PN=1&title=kb3064209-breaks-the-g3258

 

[richierich1212]

Wow, really Intel? Lame.

 

[hornirl]

According to this AsRock thread, it's not the H81 chipset but rather the G3258 CPU and a specific Microsoft update (KB3064209) that got pushed across all OS's, Win7 and Win8 aas well that had the issue.

Most posts- including this one (see post # 3 here for more links)- suggest it's builds after 10130 for Windows 10. That's my experience too going from 8.1 to 10 where everything worked fine (G3258 OC'ed to 4.2GHz both cores) in 8.1 with all updates applied.

 

[ShintaiDK]

Seems its a bug:
http://hardforum.com/showthread.php?p=1041761574#post1041761574

Power saving features is also semi broken in Windows 10 it seems:
http://www.pcworld.com/article/2952...ng-to-squash-windows-10-battery-life-bug.html

Really beta

I got a handful of bugs already in my Windows 10 install.

People also report keys/activations not working.

 

[SunnyD]

Most posts- including this one (see post # 3 here for more links)- suggest it's builds after 10130 for Windows 10. That's my experience too going from 8.1 to 10 where everything worked fine (G3258 OC'ed to 4.2GHz both cores) in 8.1 with all updates applied.

Do you have KB3064209 installed?

 

[R0H1T]

Seems its a bug:
http://hardforum.com/showthread.php?p=1041761574#post1041761574

Power saving features is also semi broken in Windows 10 it seems:
http://www.pcworld.com/article/2952...ng-to-squash-windows-10-battery-life-bug.html

Really beta

I got a handful of bugs already in my Windows 10 install.

People also report keys/activations not working.

You mean an Intel only bug? It's also not just limited to win10, the problem's a lot older than you think!

https://social.technet.microsoft.co...tel-g3258-processor?forum=WinPreview2014Setup
https://communities.intel.com/thread/77391
http://answers.microsoft.com/en-us/...e/2b8ba9bd-24e4-4b4a-8d39-abc738a3dec5?auth=1
www.sevenforums.com/windows-updates...date-kb3064209-causes-windows-7-not-boot.html

 

[cytg111]

yea, gonna give this a few months to settle before even thinking about upgrading..

 

[hornirl]

Do you have KB3064209 installed?

I believe I did (I took all 8.1 MS updates neat). But impossible to say now for sure as I did a clean install of 10 from an ISO to try to fix the problem.

 

[escrow4]

Windows 10 is really just a public beta still. So dont put too much into it yet.

My PC at default couldnt find the network. Because the Intel 217-V driver that Microsoft added to RTM is broken.

Also if you disable a NIC, you cant reenable it because Explorer crashes due to the latest Windows 10 security patch.

Zero issues on this i3 4170/H81 box. Clean install after upgrade with automatic updates. Then again my boxes are always lean minimal installs. I don't junk them up.

 

[lyssword]

Zero issues on this i3 4170/H81 box. Clean install after upgrade with automatic updates. Then again my boxes are always lean minimal installs. I don't junk them up.

I don't doubt it, it's a very specific issue. It is literally impossible to install w10 as I described it, fresh on empty disk or otherwise, it just keeps rebooting forever unless you disable 1 core.

 

[waltchan]

G3258 wasn't designed to overclock with H81 chipset in the first place, and it's totally motherboard dependent. A recommended requirement of Z87 or Z97 allows full overclock potential.

 

[JoeRambo]

My PC at default couldnt find the network. Because the Intel 217-V driver that Microsoft added to RTM is broken.

Also if you disable a NIC, you cant reenable it because Explorer crashes due to the latest Windows 10 security patch.

It's even more interesting for me. I upgraded from Win7 x64 and Intel 217-V was broken with all symptoms You describe ( got away from it using Sammy S4 as usb tether and downloading latest driver from ASUS). Couldn't get it to activate.

Then I did install Win 8.1 and upgraded from there, Ethernet worked perfectly at start and Windows activated just fine. Then I did clean install of win10 and now it wont activate despite being on same hw and ms account as before. MS can really eat some things not in forum CoC, seriously this is beta even after all previews... Combined with .NET 4.6 SNAFU, it is business as usual for MS in 2015?

 

[lyssword]

G3258 wasn't designed to overclock with H81 chipset in the first place, and it's totally motherboard dependent. A recommended requirement of Z87 or Z97 allows full overclock potential.

K. Meanwhile, I've been enjoying a very stable 4.6 OC for the last 2 years.

 

[MiddleOfTheRoad]

Windows 10 is really just a public beta still. So dont put too much into it yet.

My PC at default couldnt find the network. Because the Intel 217-V driver that Microsoft added to RTM is broken.

Also if you disable a NIC, you cant reenable it because Explorer crashes due to the latest Windows 10 security patch.

Sounds like crappy Intel drivers to me. (seriously, it's sarcasm.... I'm not serious)

Windows 10 did work perfectly on my AMD A8 laptop out of the box.

 

[Dufus]

You could take ownership of Mcupdate_genuineintel.dll in the windows/system32 directory and rename it *.dl_ or whatever to prevent Windows updating the microcode.

 

[JM Popaleetus]

K. Meanwhile, I've been enjoying a very stable 4.6 OC for the last 2 years.

That's interesting, considering the G3258 had only been out for about a year.

 

[lyssword]

That's interesting, considering the G3258 had only been out for about a year.

Actually yeah, I've only used the g3258 for a year. But I guess I'm fond of my h81 mobo because I also used g3220 for 9 months before g3258 (which I donated to my brother).
ALSO from the looks of it, z97 users also have same issue with g3258

 

[sm625]

Wait, if you can update the microcode on the fly like that, then shouldnt it also be possible to perhaps unlock HT on a G3258?

 

[lyssword]

Pretty sure HT is a physical thing on the processor, not software

 

[ShintaiDK]

HT is there on the die. So its just disabled, just like with i5 desktops.

However its very unlikely its microcode controller, but rather fused.

 

[ShintaiDK]

I recommend people to do clean installs. Because while the clean install got issues of its own. Upgrade seems to be a complete mess on what works and what doesnt in the OS afterwards. And I am not talking about 3rd party apps.

But MS is having huge issues with the keys. So while you may get unactivated upgrades. Its pretty much close to impossible to do an activated clean install currently.

Even better if you can wait a month.

 

[Sabrewings]

I got a handful of bugs already in my Windows 10 install.

I only managed to get it to install on one of three machines yesterday. :thumbsdown: