"Page Fault in Non-Paged Area" - major Windows update fails

Windows has been thrashing my HDD for a week now bugging me to install the big update. Every month I update my PC with no issues. I finally decided last night to let the big update install. It failed several times at 88% through the normal "windows update" method. I did some research and downloaded Windows10Upgrade9252.exe direct from Microsoft. I ran it with administrator privileges and it started the upgrade. Took almost 2 hours, then said it needed to reboot a few times while it finished applying the updates.

The update seemed to be going well, and rebooted a couple times to continue. Suddenly around 64% it reboots and I get a "Page Fault in Non-Paged Area" BSOD. It reboots, and goes to the motherboard UEFI screen with seemingly no settings applied. I hit the power button, and it reboots and says it will try to recover the update and try again, and then I get another "Page Fault in Non-Paged Area" BSOD. Same thing again with the UEFI screen. After 3 times it says it's undoing changes. 15 minutes later my PC is back the way it was before the update.

I tried reading up on "Page Fault in Non-Paged Area" relating to updates, and saw several mentions of possible hardware memory issues, or pagefile issues. I ran Windows memory diagnostic tool and my memory is fine. I ran sfc/scannow and it's fine. I read a suggestion to try disabling the pagefile, so I disabled it (it was set to system managed). I then tried again tonight, first using the normal method, and then again with Windows10Upgrade9252.exe, and the same exact thing happened tonight. After 2+ hours, I got the same exact BSOD and UEFI screens again. Luckily it undid the changes successfully again.

Meanwhile, every bloody time I turn on my PC now, "Modern Setup Host" thrashes my HDD for 10 minutes, preparing my PC for the update again.

How do I either get this update to go through, or stop "Modern Setup Host" from taking over my PC every time I start my PC. I have tons of software configured exactly how I need it so doing a clean install is not a possibility right now, especially with the holidays upon us. What could be causing this update to fail?

UEFISecureBoot is Enabled.

Please run both V2 and DM and upload results into this thread:
BSOD - Posting Instructions

Update the specs in the "My Computer" section:

System Specs - Fill in at Ten Forums
In the left corner below in your post you find 'My System Specs'.
After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.
System Info - See Your System Specs - Windows 7 Help Forums

Include PSU. cooler, case, peripherals and anything attached to the computer by wired or wireless (mouse, keyboard, headset, printer, xbox, USB wireless network card, etc.)


1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /scanhealth
4) dism /online /cleanup-image /restorehealth
5) sfc /scannow
6) chkdsk /scan
7) wmic recoveros set autoreboot = false
8) wmic recoveros set DebugInfoType = 7
9) bcdedit /enum {badmemory}

10) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

11) Make sure that there is no over clocking while troubleshooting.

12) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings

a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery window into the thread

b) > on the advanced tab under performance > click on settings > on the performance options window > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory window into the thread

13) If the computer has Ccleaner (do not install the software if it is not already installed) > click windows tab or custom clean > scroll down to system and advanced > post an image into the thread

I never get BSOD. It only happened due to me trying the feature update. So this is directly related to the update.

As I already said, I already ran sfc/scannow, chkdsk, and tested my memory, and everything tested fine. I have heard feature updates are particularly problematic which is why I posted it in the general forum, for more exposure, since it's an issue with updating. In here it won't get as much exposure, and I was hoping others who have run into trouble with installing the latest feature update could make any suggestions.

Page fault in non paged area is a BSOD.

The bugcheck is 50.

https://docs.microsoft.com/en-us/win...-nonpaged-area


Please see posting instructions:

BSOD - Posting Instructions

I know it's a BSOD. I said so in my first post. The point is it only happened after the update. It has never happened before. So it's clearly something related to the update in my case. I have never gotten that BSOD before I ran the update the other night. From what I've read, feature updates are problematic and simple things like USB devices plugged in is all it can take to botch the update. It also may be a driver that the update doesn't like. That's what I'm trying to figure out.

Consider a broader approach as updates may or may not correlate with other problems.

For example a normally working computer develops malfunctioning RAM or drive problems around the time an upgrade was performed.

Please see posting instructions.

I mean, it happened both times I tried to take the feature update, at the exact same spot of the update both times, during the reboot phase, right at the same exact percentage. So something at that particular point of the update is causing an issue. Something about this update is clearly not working with my system, and I doubt it's faulty hardware. I also don't think it's drivers, as it's crashing before Windows is even loaded - during the final installation of the updates, between boots.

As you commented it could be or could not be related to other problems.

If you would like to problem solve (rule in / rule out) factors that can be done by viewing logs, and performing steps and or tests.

You might find the following useful to try and explore the logfiles created during a feature upgrade to see if there is anything obvious you can do to fix it.

https://docs.microsoft.com/en-us/win...rade/setupdiag