"Paged Fault in Nonpaged area" after Windows Update

Anonymous

So this all started yesterday morning. I went to Windows Update and it started to update and before I could see what happend my PC hard crashed with a "Paged fault in a non paged area" and then the PC would not start up again.

Initially I thought it had to do with an upgrade I did to Samsung Magician, So I went into safe mode and uninstalled that, and then no luck on the reboot. Do note it started up fine in safe mode and ran fine there.

Then I went into recovery and removed the most recent updated. Again no luck. Same BSOD.

I then started thinking I had a disk error so ran chkdsk, but that came back with no errors. Tried to restart with no luck

I then ran sfc /scannow and it found a couple fixes and added them, but again when I tried to restart it bsod'd with the same error.

I then rolled back to my prior restore point from a week ago but the exact same error.

I then ran a memory check with memtest86 and got no errors. Same error on reboot.

I then ran Prime95 and ran several CPU tests for several hours and had no errors. Rebooted again and the same error.

I've been thinking about getting a new SSD for a bit, so I went out and picked one up and started a new install after backing things up in safe mode.

I then put in the new drive and started the install. I did the install from a fresh set of data off a USB thumb drive. Things start off fine but as soon as I get around the point where I enter my Microsoft account info it crashes. Sometimes before I get it entered, sometimes shortly after, but it always crashes.

At this stage I tried uninstalling several things. Unplugged most everything except a monitor. Did not start taking out graphics card or sound card yet. But nothing helped. Did several installs here.

Next I decided to do an offline install and unhooked my network cable and did another Windows install fully offline. It ran to completion with no errors. I did several reboots and it worked just fine. I then connected my Microsoft account and went into windows update and started it and it crashed within 30 seconds and is BSODing again.

I'm at a complete loss here. The machine is a bit older. But still runs very quickly for what I need. Really not sure what to do next but it really feels like something being updated in Window's Updated is causing it to fail.

Any help would be greatly appreciated.

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

46 answers

Anonymous

2020-10-30T20:18:58+00:00

One other thing I just noticed is that the media creation tool is no longer 2020, it is 20h2, even though the microsoft page still says it is 2020.

Is there a way to get the older version?
Was this answer helpful?

0 comments No comments
Anonymous

2020-10-31T00:37:49+00:00

That's the latest version.

You can use the alternate download site from MS TechBench here: https://tb.rg-adguard.net/public.php

Burn to DVD using WIndows Image Burner or create bootable flash using one of the options here: https://www.tenforums.com/tutorials/2376-create...
Was this answer helpful?

0 comments No comments
Anonymous

2020-10-31T16:57:03+00:00

So had some more time this morning so put in an old SDD and tried again from the older install. Used this iso

Then created the usb drive and installed.

It behaved similarly at first. I did get a blue screen while it was installing the device drivers in the background, but it then restarted and recovered completely on it's own and installed completely.

I believe this initial version of 2004 was from May. So at this stage all seems to be fine. There was an issue, but it recovered without me having to do anything and all seems to be working correctly.

I then went in and disabled feature updates in the registry.

Then I went in and ran Windows Update and let it run. They all ran what appeared to be fine until I restarted. I then received the same bsod again. It automatically restarted several times and then tried to recover on its own, then it rolled back this update.

It is back up now and seems to be running fine again on the old ssd.

So again it really seems like there is a major bug with 20H2 and the October update. Likely related to Windows Updates. It just no longer seems capable of recovering itself like older versions.

Still not heard from BioStar, but this even though there is likely a driver issue with Biostar, there is clearly a huge bug with Windows right now.

Both the Update does not work on older installs and the new windows media install does not work.
Was this answer helpful?

0 comments No comments
Anonymous

2020-11-17T20:33:54+00:00

To put a bookend on this. I was finally able to get some traction with BioStar support after starting to harras them on social media.

Initially, they were able to identify the hardware that was having the issues. It was the:

Intel(R) Management Engine Interface

It was simply showing up in the device manager as a generic:

PCI Simple Communication Controller

Initially, they had me disable that device in the device manager. That allowed me to install Windows and leave Windows Update running. Still is a huge bug with Windows that this was the Only way to get the updates to not install.

Then they found the problem and released a new Bios for the motherboard which allowed the Intel driver to be installed normally again after enabling that device again.

Again, no idea if the underlying Windows 20H2 install bugs are fixed, but hopefully this helps someone if they run into anything similar with the****BIOSTAR Group Hi-Fi Z97WE (SOCKET 0) board
Was this answer helpful?

0 comments No comments
Greg Carmack 24,780 Reputation points Volunteer Moderator

2020-11-18T06:46:05+00:00

Greg-

Thanks for reporting back to help others.
Was this answer helpful?

0 comments No comments