BSOD upgrading to Win10, error PAGE_FAULT_IN_NONPAGED_AREA

krytoned · 23 Aug 2015

I tried to upgrade my laptop to Windows 10 Pro 32bit using the USB installation media (from the media creation tool).

However during the first reboot, I encountered a Windows 10 BSOD with the message:
PAGE_FAULT_IN_NONPAGED_AREA
and was then rolled back to Windows 7 Pro 32bit.

I then get the following error code after I logged back on:
0xC1900101 - 0x20017
The installation failed in the SAFE_OS phase with an error during BOOT operation.

This is the 3rd time I tried to upgrade this laptop, and I got the same BSOD and error code. I have already ran a chkdsk command.

Would appreciate some help on this, thanks!

Attachment 33283 (C:\$Windows.~BT\Sources\Panther)
Attachment 33284 (C:\$Windows.~BT\Sources\Rollback)
Attachment 33285 (C:\$Windows.~BT\Sources\Rollback)

axe0 · 25 Aug 2015

Please upload the zip again, there are no dump files in the uploaded zip file.
Please make sure your pc is configured for small dump files How to configure minidump | Windows 10 tutorial

krytoned · 25 Aug 2015

Followed the instructions to enable small dump files, then ran the windows upgrade again, followed by the same BSOD and error and rollback.

However the dm_log_collector.exe says there's no dump file to save (and checking the directory itself confirms this). Presumably, this is because the BSOD occurs in Windows 10 and not my current rolled back Windows 7.

The error logs look the same though.

I have already ran the memtest86 tool before this, and there were no problems.

axe0 · 25 Aug 2015

Do you have some hardware replaced, or added hardware?
Do you have any peripherals connected while upgrading?

krytoned · 25 Aug 2015

No peripherals connected, and I even detached the removable DVD writer on one of my upgrade tries.
The only thing attached is the USB drive containing the Win10 iso image.

I have not changed or added any hardware. It works well in Vista, and even when I upgraded it to Win7 later on.

axe0 · 25 Aug 2015

How much free space do you have?

krytoned · 25 Aug 2015

I got one disk drive partitioned into this:

Attachment 33770

axe0 · 25 Aug 2015

You ran the memtest, which test did you use, how long and how many passes?
It makes a difference which test you run and unless you do at least 8 complete passes (or until you get an error) it isn't worth doing.

Please run in admin command prompt sfc /scannow. We need to make sure there are no software/driver/hardware corruption or hardware problems.
To open admin command prompt, press windows logo + x, choose command prompt (admin). If you get a message from UAC, allow it.

krytoned · 25 Aug 2015

For memtest, I just ran the default test once, and I think it only took an hour or so. I'm not sure how many passes is that. I only know I quit it when it said there were no errors.
I'll try it again later. Can I leave it unattended overnight? What settings or menus should I select?

The sfc says it found some errors that it can't be fixed. Here's the CBS.log file. Thanks.

axe0 · 25 Aug 2015

Memtest for 8 passes takes several hours, each pass tests another part of the RAM.
It is recommended to run memtest overnight, because of the time it takes.
It is also recommended to abort the test when there is an error, but it doesn't hurt to continue until at least 8 passes have finished.
It is recommended to abort the test when there is an error, because there isn't a reason to continue anymore.
Keep the settings on default for now.

Please reboot your pc and try sfc /scannow again.
Try sfc /scannow, reboot, sfc /scannow a couple of times. When sfc says it can't fix problems then you have to reboot for sfc to try fixing it. It may take a couple of times in order for sfc /scannow to fix the errors.