Topic: MSI MEG X399 Creation, Blue Screen during Win10 Install (and a fix!) (Read 8238 times)

codezone · « **on:** 07-October-18, 22:08:57 »

When trying to do a fresh install of the latest Windows 10 build 1809 (10.0.17763.1) (aka Redstone 5, or October 2018 windows update) via USB drive from an image generated by Microsoft's media creation tool, I encountered a blue screen during the installation process. Having network connectivity via the onboard LAN didn't seem to help, the windows installer did not seem to search for a a newer driver on the internet during the install.

The blue screen code was pretty basic and basically just displayed the error BUGCODE_NDIS_DRIVER. I eventually narrowed the problem down to the driver for the onboard wireless adapter. This device also seems to not have a way to be disabled in the BIOS. Since the blue screen occurs during the installation of windows after the USB media has been copied to the hard drive, the installer gets permanently broken and you have to delete the partitions to try again by booting the installation media and starting over from scratch.

The way to fix this issue is to manually load a newer driver for the Intel Wireless-AC 9260 device from a second USB drive. On the screen asking which drive and partition windows should install to, there is also an option to load additional drivers during the install process here, which is what needs to be done here.

Relevent page (might link to newer versions in the future):
https://www.intel.com/content/www/us/en/support/articles/000017246/network-and-i-o/wireless-networking.html

Actual download needed (typically the Win10 64 bit package) (links to the latest as of this post, Intel driver version 20.80.0)
https://downloadcenter.intel.com/download/28147

Unzip to USB drive, find the directory that the 'Load Driver' option scans and shows compatible drivers to install, select it and get on with your life.

The windows installer will display a large number of progress bars when scanning the folder with the drivers and during installation of the driver, but don't panic, it will eventually figure things out and install it so you can get on with the windows installation

jhchris2 · « **Reply #1 on:** 08-October-18, 12:51:09 »

codezone, this is great! Thank you so much! Do you happen to know which driver the Intel 9260 requires? Thanks and enjoy, John.

EDIT: I think it is the five files of the Netwtw08 set. Please let me know if you disagree.

plutomate · « **Reply #2 on:** 09-October-18, 01:29:52 »

RS5 has some major bugs and microsoft has postponed the release time

I'd expect those bugs to be fix along with the official RS5 release (hopefully, lol)

jhchris2 · « **Reply #3 on:** 09-October-18, 11:54:14 »

plutomate, thanks, first I heard. Please post an MS reference for this fiasco. Thanks and enjoy, John.

cybrnook · « **Reply #4 on:** 10-October-18, 09:22:45 »

Quote from: plutomate on 09-October-18, 08:29:52

RS5 has some major bugs and microsoft has postponed the release time

I'd expect those bugs to be fix along with the official RS5 release (hopefully, lol)

Re-Release of the October update is underway, build 17763.17. Though media creation tool site is still providing 17134.1, so not quite there yet. However, since this is a driver issue, and the release is more to fix the deletion of old KFR directories, I think this is still needed.

jhchris2 · « **Reply #5 on:** 10-October-18, 10:56:47 »

Thanks, cybrmook, what the heck are "KFR directories"? I guess I am showing my ignorance. BTW 17134 is 1803 and the Media Creation site is providing 17134.345 - at least yesterday when I updated my LT. Enjoy, John.

EDIT: Please see here. Looks like 17763.55 was released on 9 Oct (KB4464330 ). It is available in Microsoft Update Catalog.

plutomate · « **Reply #6 on:** 11-October-18, 02:00:39 »

https://support.microsoft.com/en-us/help/4464619/windows-10-update-history

there you go

cybrnook · « **Reply #7 on:** 11-October-18, 08:24:48 »

No, what I am talking about is the release of the mediacreationtool for making a new windows install iso or thumb drive. You want to make sure it's the updated version:

And just google KFR, there is a lot of info already on the Oct 2 release of 1809 and it's issues.

"The company determined that the data deletion issue resides with a bug related to the Known Folder Redirection (KFR) feature. If KFR had been previously enabled, intentionally or by mistake/automatically, but the files remained in the old location instead of being moved to the redirected location, they ended up being deleted. That’s because Microsoft attempted to fix a previous KFR issue from the April 2018 upgrade, where KFR would create duplicate but empty Known Folders."

jhchris2 · « **Reply #8 on:** 11-October-18, 08:58:55 »

Thanks, plutomate.
Thanks, cybrnook.
I assume this bug has no effect on new installs, which is what I almost always do.
Enjoy, John.

xxwyx2003 · « **Reply #9 on:** 04-November-18, 23:29:18 »

Thank you so much, I solved the problem by using this method, thanks a lot.

argonagui · « **Reply #10 on:** 03-December-18, 04:22:09 »

Quote from: codezone on 08-October-18, 05:08:57

When trying to do a fresh install of the latest Windows 10 build 1809 (10.0.17763.1) (aka Redstone 5, or October 2018 windows update) via USB drive from an image generated by Microsoft's media creation tool, I encountered a blue screen during the installation process. Having network connectivity via the onboard LAN didn't seem to help, the windows installer did not seem to search for a a newer driver on the internet during the install.

The blue screen code was pretty basic and basically just displayed the error BUGCODE_NDIS_DRIVER. I eventually narrowed the problem down to the driver for the onboard wireless adapter. This device also seems to not have a way to be disabled in the BIOS. Since the blue screen occurs during the installation of windows after the USB media has been copied to the hard drive, the installer gets permanently broken and you have to delete the partitions to try again by booting the installation media and starting over from scratch.

The way to fix this issue is to manually load a newer driver for the Intel Wireless-AC 9260 device from a second USB drive. On the screen asking which drive and partition windows should install to, there is also an option to load additional drivers during the install process here, which is what needs to be done here.

Relevent page (might link to newer versions in the future):
https://www.intel.com/content/www/us/en/support/articles/000017246/network-and-i-o/wireless-networking.html

Actual download needed (typically the Win10 64 bit package) (links to the latest as of this post, Intel driver version 20.80.0)
https://downloadcenter.intel.com/download/28147

Unzip to USB drive, find the directory that the 'Load Driver' option scans and shows compatible drivers to install, select it and get on with your life.

The windows installer will display a large number of progress bars when scanning the folder with the drivers and during installation of the driver, but don't panic, it will eventually figure things out and install it so you can get on with the windows installation

-------------------------------------------------------------------------------------------------------------

Perfect solution

Actulized driver version now Version: 20.90.0 (Latest)

https://downloadcenter.intel.com/downloads/eula/28275/Intel-PROSet-Wireless-Software-and-Drivers-for-IT-Admins?httpDown=https%3A%2F%2Fdownloadmirror.intel.com%2F28275%2Fa08%2FWiFi_20.90.0_Driver32_Win10.zip

Thanks a lot @codezone!!!

indu111 · « **Reply #11 on:** 18-December-18, 14:12:50 »

Quote from: codezone on 08-October-18, 05:08:57

When trying to do a fresh install of the latest Windows 10 build 1809 (10.0.17763.1) (aka Redstone 5, or October 2018 windows update) via USB drive from an image generated by Microsoft's media creation tool, I encountered a blue screen during the installation process. Having network connectivity via the onboard LAN didn't seem to help, the windows installer did not seem to search for a a newer driver on the internet during the install.

The blue screen code was pretty basic and basically just displayed the error BUGCODE_NDIS_DRIVER. I eventually narrowed the problem down to the driver for the onboard wireless adapter. This device also seems to not have a way to be disabled in the BIOS. Since the blue screen occurs during the installation of windows after the USB media has been copied to the hard drive, the installer gets permanently broken and you have to delete the partitions to try again by booting the installation media and starting over from scratch.

The way to fix this issue is to manually load a newer driver for the Intel Wireless-AC 9260 device from a second USB drive. On the screen asking which drive and partition windows should install to, there is also an option to load additional drivers during the install process here, which is what needs to be done here.

Relevent page (might link to newer versions in the future):
https://www.intel.com/content/www/us/en/support/articles/000017246/network-and-i-o/wireless-networking.html

Actual download needed (typically the Win10 64 bit package) (links to the latest as of this post, Intel driver version 20.80.0)
https://downloadcenter.intel.com/download/28147

Unzip to USB drive, find the directory that the 'Load Driver' option scans and shows compatible drivers to install, select it and get on with your life.

The windows installer will display a large number of progress bars when scanning the folder with the drivers and during installation of the driver, but don't panic, it will eventually figure things out and install it so you can get on with the windows installation

THANK YOU SO MUCH! THIS FIXED MY WINDOWS 10 INSTALL!

I was so annoyed that i was running in to this exact same issue. I followed the exact steps and solved it and had a clean fresh install. Thank you again.

janis.robens · « **Reply #12 on:** 21-December-18, 16:50:49 »

Thank you so much man! You're a legend. I just built a new PC from scratch and just couldn't figure out what the problem was for hours. Eventually my girlfriend found you post on here, so thanks again!

One thing I wonder is, if you could also use the drivers supplied on the MSI support page for this board. I think i saw WiFi drivers in the download section.

plutomate · « **Reply #13 on:** 23-December-18, 19:52:04 »

yes it should be working just fine

erpsracing · « **Reply #14 on:** 15-January-19, 22:38:36 »

Big THANK YOU codezone for this info!!!

Catworm · « **Reply #15 on:** 17-January-19, 14:04:34 »

Thank you codezone, I was trying to install windows for 2 days and getting really REALLY sad,

I did this and it worked perfectly.

Thanks again.

keltrik · « **Reply #16 on:** 18-January-19, 10:36:42 »

Ah, also a great way to solve this annoying problem. I have another solution: I was using a bootable USB with Win10 v1607. The MSI board was the first one to refuse booting from that stick which installed dozens of PCs before it without a problem. In a reddit forum someone said that win10 v1709 is the one to go. And that's it indeed: USB boots up like a charm and windows installs without BSOD. After installation just run Windows Update and you get the newest version.
What's kind of strange with that board: the BIOS initialization is REALLY long! Even my outdated laptops (2010!) are way faster! But oh well, that's a different topic.

rbleroy91 · « **Reply #17 on:** 18-January-19, 11:23:19 »

Hello,

Quote

In a reddit forum someone said that win10 v1709 is the one to go. And that's it indeed: USB boots up like a charm and windows installs without BSOD. After installation just run Windows Update and you get the newest version.

Have to install 1709 release of Windows 10 to be able to use 1809!

1809 is really the worst release I have seen! Microsoft is... And, clearly, Intel does not help.

Quote

What's kind of strange with that board: the BIOS initialization is REALLY long! Even my outdated laptops (2010!) are way faster!

At this time, MEG X399 Creation is a recent mobo with only 2 bios releases. Post delay should be improved in the futur.
Have a good day,

hammah · « **Reply #18 on:** 20-January-19, 17:37:25 »

A million thanks! I was putting together a new build this weekend and ran into the BSOD upon windows install. This worked like a charm!

nick.shin · « **Reply #19 on:** 22-January-19, 13:51:55 »

installing 1709 is what worked for me. i've tried many ways to get 1809 to install -- plowed as many drivers to another USB stick to get it going -- but, 1709 finally got going. love the mobo -- installing linux was a breeze. can't wait to see if i can also install OSX on this. (love the boot override option in the BIOS.)

thanks again for the 1709 tip!

matthewphilipdixon · « **Reply #20 on:** 29-January-19, 21:35:16 »

Quote from: codezone on 08-October-18, 05:08:57

OMG thank you so much, just spent 3 hours trying to figure out wth was going on with my new motherboard and your solution worked perfectly!

Monstieur · « **Reply #21 on:** 12-February-19, 18:03:36 »

Disable some CPU cores (or HyperThreading on Intel) during installation so there are <= 10 logical processors. This prevents the BSOD until you update the driver later.

pjcnot-1 · « **Reply #22 on:** 20-February-19, 16:18:47 »

New Creator...had to install an old version of 10 Pro and those drivers listed above, both old or new wouldnt istall. Now with an old windows 10 Pro install, subsequent updates will corrupt things and you get a repair process loop that wont stop. So install with old windows 10 and follow this process to block updates to the Blue Tooth drivers

https://www.howtogeek.com/263851/how-to-prevent-windows-from-automatically-updating-specific-drivers/

and I dont want my workstation to have bluetooth so I also disabled it

Crazy... Im quite capable, how would someone with less patience do this? I guess incapable people arent building AMD boxes from parts :shrug:

pjcnot-1 · « **Reply #23 on:** 20-February-19, 21:32:44 »

OK, nothing is easy.. forget what I said above, I thought it was fixed, I was able to get a windows install, but it was not stable.

So you cant install the drivers that the first poster mentions unless you have an older version of windows 10 pro and during the install as he mentions. but then, even then, if you allow an automatic update to the wifi driver, and above I mistakenly listed the bluetooth driver/system sorry. The link in my post above leads to how to disable a specific driver update. Well now it is stable for hours and reboots and installs of software... miserable.. MSI owes me like 8 hours.

Monstieur · « **Reply #24 on:** 21-February-19, 02:06:01 »

Quote from: pjcnot-1 on 21-February-19, 04:32:44

OK, nothing is easy.. forget what I said above, I thought it was fixed, I was able to get a windows install, but it was not stable.

So you cant install the drivers that the first poster mentions unless you have an older version of windows 10 pro and during the install as he mentions. but then, even then, if you allow an automatic update to the wifi driver, and above I mistakenly listed the bluetooth driver/system sorry. The link in my post above leads to how to disable a specific driver update. Well now it is stable for hours and reboots and installs of software... miserable.. MSI owes me like 8 hours.

The bug is triggered by having more than 10 CPU cores on the outdated driver that ships with Windows. Disabling the additional CPU cores on AMD or switching off HyperThreading on Intel (cuts the logical core count in half so it works for up to 10-core CPUs) is the easiest solution. Once you update the drivers you can re-enable the cores.
Your issue seems to be different. The bug doesn't cause random instability - it results in a BSOD 100% of the time on boot.

pjcnot-1 · « **Reply #25 on:** 21-February-19, 10:21:33 »

OK, I had read your advice above, but couldnt find a place in the Creator Bios to disable cores.. Maybe clarify for others?

gordon.mcnevin · « **Reply #26 on:** 21-February-19, 11:42:27 »

Thanks for the tip of disabling CPU cores to get install to work!

I disabled CPU cores by going into the BIOS settings -> Advanced Mode -> OC Button On Left -> Downcore Control -> FOUR (4 + 0) 8 Cores

Got my install working ;-)

nhan408 · « **Reply #27 on:** 15-April-19, 14:52:10 »

Theres also another way to fix the blue screen issue go bios advance mode >oc>cpu features> disable smt>Iommu>and spread spectrum after disabling try installing window again and it shpuld work fine. Dont forget to enable smt again in the bios later.

francislallen01 · « **Reply #28 on:** 09-May-19, 14:00:11 »

You can follow this link and easily fix your issue. https://errorcodespro.com/fix-driver-irql_not_less_or_equal-error-for-windows-10/

volsfan846 · « **Reply #29 on:** 11-May-19, 14:12:25 »

I had this issue but went into bios and disabled the WiFi adapter and loaded windows. Now I have installed the latest Intel driver in Windows but the system won't boot, it always hangs right before loading Windows. Is there a way to fix this without re-installing Windows? Hate to waste all that time. Wish I had seen this before I found my work around...

Love the motherboard and the Threadripper other than this issue.

rbleroy91 · « **Reply #30 on:** 12-May-19, 02:24:32 »

Hello,
Keep [MAJ]+[F10] when the circle for Windows loading displays.
Hoping it shall help,

MarkusTheArtist · « **Reply #31 on:** 16-May-19, 12:54:52 »

Was up until 5AM trying to get the new build of my X299 Creation system past that first reboot after the install to no avail...codezone you're a freakin LIFESAVER. Gonna try this tonite after work...and hopefully get some sleep after Windows installs...

Yeah right if this works there's no way I'm sleeping tonite with this board going along with an 2080 ti GXT in there!!!

sullycollin · « **Reply #32 on:** 18-May-19, 18:14:56 »

Hi. This may be a noob question, but how do i delete partitions if i can't even get windows to load? I'm first time installing win 10 to my meg creation from a usb stick and i keep getting the blue screen after reboot. I'd like to try this driver trick but i'm not sure how to reinstall when i'm stuck in this boot loop. Thanks in advance...

plutomate · « **Reply #33 on:** 23-May-19, 00:49:29 »

you press F11 during booting to go into usb at startup again (before loading OS) and load driver from there

Register Now!

News:

Author Topic: MSI MEG X399 Creation, Blue Screen during Win10 Install (and a fix!) (Read 8238 times)