New
#1
PFN_LIST_CORRUPT BSoD at third boot during Windows 10 upgrade to 1909
Hello,
I am finally ending here after having spent quite a lot of time stripping down software, drivers, and possible causes of my issue.
I have a Windows 10 Pro 1809 rig that needs an upgrade to 1909. It has successfully upgraded from previous Windows 10 versions in the past through Windows Update, without issue. This had upgraded from Windows 7 successfully.
However this time, the following occurs :
Upgrade process via WU, Upgrade Assistant, or via USB image (offline upgrade) goes OK until the SECOND_BOOT phase, after the Windows setup has detected the hardware and installed its drivers again, which is visible through the screen resolution that becomes sharp and neat during this process.
During Offline upgrade attempt using USB, I got this error code :
0xC1900101 - 0x40017
SECOND_BOOT phase, with an error during BOOT operation
Basically, after the second boot, shortly after the Windows logo shows up, a PFN_LIST_CORRUPT blue screen shows up.
Windows reboots, tries something to repair, but same BSoD after repair attempt.
So Windows rolls back everything back to 1809, and I'm stuck there.
This occuring at the boot time of a Windows 10 barely at the end of an upgrade process, and the system rollbacking each time, I have not found a MEMORY.DMP file to help me.
What I did already to narrow down possible causes :
- Uninstall crap
- Uninstall BitDefender, only leaving Windows Defender
- Removed optional Windows features
- Forced-disable Hyper-V including in bcdedit
- Unplugged non-necessary peripherals aside ETH, Keyboard, mouse and Screen
- Used DriverStoreExplorer to remove old and useless drivers from DriverStore
- Ensures the remaining drivers aren't abysmally old
- Ran DISM /RestoreHealth numerous times (no issues)
- Ran Memory Check (no issues as well)
- Disabled useless features in BIOS including VT-D, PCI and non-urgent controller stuff
Yet, still get this PFN_LIST_CORRUPT thing, and hardly a clue.
Windows is extremely stable, and errors are rare, if they ever happen.
Thus, I am here, and attach logs and what I could get.
This hard drive has a dual-boot setup with a Linux next to the Windows, meaning I could access the Windows partition easily, before some of the reboots if necessary (which may be an idea).
Yet I am questioning if Grub2 being on the MBR could be the cause, but I doubt it.
I thank you in advance for your help.