Windows 10: BSOD with Win 10 upgrade 1903 and possible issues with Netr28ux.sys

Back in June 2016 I sought help from this site for a similar problem. I have seen issues with release 1607, 1803 now 1903
I followed all the steps published on the Microsoft websites … ran the MS update troubleshooter, replacing SSU, deleting Anti-Virus, have sought to fix file corruption, and attempted an in-place upgrade using the Windows 10 Media creation tool.


At the "blue screen" prior to recovery, the error PAGEFAULT IN A NONPAGED AREA, error code 0x80240031 with the file NETR28UX.SYS being highlighted as the culprit. I estimate that this was some 95 to 99% through the upgrade.


Again in the past I sought help from the Microsoft Answer Techs and allowed them to remotely log in and check the PC, delete anti-virus etc, download the Media Tool with no success. I've repeated this process multiple times myself and with the assistance of different agents.


SOLUTION

Cutting a long and very painful story short … My solution - turn off wireless and connect with a 30 yard cable to the LAN. Success - I have upgraded to version 1903 ! No BSOD. Windows works perfectly.


PROBLEM

Shutdown the PC and re-boot with wireless connected and no LAN cable. The result is the BSOD and the good ol PAGE FAULT error. Switch back to LAN and it runs perfectly again. Can you hear me screaming ?


I have tried USB wireless devices from several manufacturers … nothing worked.


I’m not sure I can see a way forward. I can’t leave a cable running through the house with young children back and forth.

Is there any bright spark out there who can provide me a workable solution ?


The system is an i7 processor, 16GB RAM and plenty of Disk space


John

:)

 

Local profile issue after upgrading to 1903

Hi roblinb

Not listed in the Known.

Known issues for Windows 10 May 2019 Update version 1903


As far as Wifi any chance it is Qualcom inside USB adapter, if Qualcom then yes known issue.


I might create another user (Local) and when if try again see if this issue occurs on both users.

Would also suggest you run the first 5 steps in this tutorial to see if you have any corruption with current build.

Use DISM to Repair Windows 10 Image


Ken

 

Win 10 1809 to 1903 Failure And Odd Issue Found

No listing under MSConfig Boot tab / not sure what to do

Similar there.
You are missing an EFI partition too. Here's mine (1903) - note the 99Mb EFI partition:



- noting the Recovery partition is NTFS - not sure where the idea in that thread about FAT32 comes from.

Here are all the partitions - Disk Management omits the 16Mb one:




In the thread I quoted- not the most straightforward- it seems one basic step taken was to
a. Image 'C: '
b. Clean install Windows
c. Replace the new Windows partition by restoring it from the image created
d. (Note when rebooting, this may sort itself out via automated repair, or need Startup repair to be run)

If you search for
msconfig boot empty
or
msconfig boot empty "Windows 10"
you will find numerous references which may help.

 

Can't upgrade from Win 8 to Win 10

Jessen P -- Thanks for responding. I looked at the link you provided, but it just provides a small list of error codes and possible causes for the error. Didn't see any steps to take to resolve the issue. And none of the listed error codes are the
same as the one I got 0x80070006-0x90016 when I tried to upgrade to win 10.