New
#1
How I fixed my 1803 Upgrade Blue Screen failure
After many failed attempts to complete the 1803 upgrade and many posts on this website about my problem and suggested fixes (none of which worked) I finally found out what the problem was and how to fix it. I am now running on 1803 and have just completed a Macrium backup of my updated system. I'll describe what my proiblem was, how I learned how to fix it, and how I actually made the fix.
The Problem
When I tried doing the 1803 upgrade it would fail during the second boot phase with the error "Page fault in non-paged area." I got lots of advice and suggestions from numerous people here about how to fix this, or what to do to eliminate the problem. None of them worked, and I really did try everything under the sun.
Moreover, I did extensive Google searches on "Page fault in non-paged area"; none of the results worked either. I was about to totally give up when I decided to post a message on the Microsoft Answers forum site. This is the link to that posting; it is long and involved, but it tells the whole story: https://answers.microsoft.com/en-us/...2-6384ae6496e0
Identifying the problem
I always felt there must be some log file somewhere that told what caused the failure. I know how to look at normal log files, and I found ones from the failed install in the leftover ~Windows directory. But those files gave no useful information. Fortunately 2 of the responses I got from the Microsoft forum said the only useful log file is named setupmem.dmp located in either the C:\$WINDOWS.~BT\Sources\Rollback directory or the C:\Windows\Panther\NewOs\Rollback directory.
So after I recreated the failure again I looked there and found the log file. That's the good news. The bad news is the file is not human readable, and requires a program to read and interpret it. So I Googled "read windows dmp" and found this program: whocrashed. What this program does is read the dmp file, analyze it, and tell you in plain English what caused the Blue Screen failure. Here is the link to download it: http://www.resplendence.com/downloads
Here is a screenshot of how whocrashed looks:
Attachment 188659
What you do is click the Analyze button and wait for the results. But doing this did nothing. Sso after some searching I discovered that whocrashed expects to find the dmp file in the C:Windows or C:\Windows\Minidump directories. But the dmp file I wanted to analyze was in the C:\$WINDOWS.~BT\Sources\Rollback directory, so whocrashed could not find it. To fix this I simply copied the file into C:\Windows\Minidump.
This time clicking the Analyze button produced a nice report that told me the failure was caused by a device driver named ldrvpro64.sys. So I figured all I had to do was stop this from being loaded at boot time, and I would be good to go.
Fixing the problem
It turns out fixing the problem was not easy. What I ended up doing was booting into Safe Mode and deleting the driver file from there. That was the only way to get rid of it; none of these methods worked: unchecking the Autoruns entry that loaded the driver; deleting the registry entry that identifies the driver, renaming the location of the file in the registry, deleting the file in Explorer, renaming the file in Explorer.
Explorer simply did not show the file as existing at all. Regedit let me delete/rename/change the entry defining it, but whatever I did was undone when I rebooted, and the driver kept coming back. The only way I could stop it was to boot Safe Mode and delete the file from there.
Completing the 1803 Upgrade
After rebooting back to normal (1709) I verified the the driver file was really gone and I ran the 18703 upgrade the way normal people do. When it got past 52% in the second boot phase I knew I was going to succeed, because this is where it always had stopped before. The whole install process ran A-OK, and the final reboot into 1803 was a joy to behold.
I should add that my system is somewhat complex: dual monitors driven by an nVidia graphics card, SSD boot drive, 2 HDD data drives and another SSD for temp files, downloads, etc., BluRay optical drive, multi-function card reader, Logitech keyboard with its own driver file, and a Kensington trackball mouse with its own driver. I changed none of this when I ran the 1803 update and none of it caused any problems.
I hope this post will help other people solve vexing Blue Screen problems. The process really is not that difficult, and is sure beats doing a clean install.
Quote
