Windows 10: How I fixed my 1803 Upgrade Blue Screen failure Solved

  1.    1 Week Ago #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:

    Click image for larger version. 

Name:	1.jpg 
Views:	2 
Size:	490.0 KB 
ID:	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.
      My ComputerSystem Spec


  2. Posts : 257
    Microsoft Windows 10 Home x64
       1 Week Ago #2

    Hello BBinnard

    I'm glad you eventually resolved your issue and thank you for taking the time to share your situation with other members.

    As you are probably aware, there are some very useful tutorials with regard to BSOD's compiled and produced by Shawn @Brink.

    Windows 10 Tutorials

    Kind Regards

    Neil
      My ComputerSystem Spec


  3. Posts : 12,431
    Windows 10 (Pro and Insider Pro)
       1 Week Ago #3

    nice of you to share you experience with us bbinard.

    The file that caused that mess is part of Driver Talent Pro (formely called Drive The Life). Won't comment of usability of such programs, just to add some info for any readers that comes to this thread for further help

    Worth uninstalling this utility, instead of manually stopping services and deleting files.

    Btw, this utility caused BSODs at Windows updates before ...
      My ComputerSystem Spec


  4. Posts : 17,735
    windows 10 professional version 1607 build 14393.969 64 bit
       1 Week Ago #4

    Hi bbinnard,

    That was nice work.
    You were very resourceful.
    The dump file that you analyzed is one of the Panther logs that is troubleshooted for failed upgrades:

    C:\Windows\Panther
    setuperr.log
    setupact.log
    Setupmem.dmp
    setupapi.dev.log
    BlueBox.log
    Event logs (*.evtx)
    C:\$Windows.~BT\Sources\Rollback
    $Windows.~bt\Sources\Rollback\setupmem.dmp
    $Windows.~bt\Sources\Rollback\setupapi\setupapi.dev.log
    $Windows.~bt\Sources\Rollback*.evtx
    $Windows.~BT\Sources\Panther\UnattendGC
    miglog.xml
    Windows\Logs\Mosetup
    Setupapi.offline.log

    Code:
    *************************************************************************Unable to load image LDrvPro64.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for LDrvPro64.sys
    *** ERROR: Module load completed but symbols could not be loaded for LDrvPro64.sys
    *************************************************************************
    If you need any help troubleshooting the logs for any other problems you can run the BETA log collector and post a zip into the thread:
    /attachment...-v2-beta10.zip
    (extract > open)
    Use the information in this link in case there are any problems running the beta log collector: (post #5)
    DM Log tool problem Solved - Windows 10 Forums
    Last edited by zbook; 1 Week Ago at 15:23.
      My ComputerSystem Spec

  5.    4 Days Ago #5

    Actually I think I was more analytical than resourceful. After many attempts to fix my problem I realized that all the "fixes" I was trying were simply stabs in the dark. That's when I recalled a lesson I had learned a long time ago: the only way to fix a problem is to first know what the problem is.

    I didn't know what it was, and neither did anyone else who was suggesting fixes.

    I knew about all the logs & traces Windows creates, and it only seemed logical that at least one of them should have info that identifies what the actual cause of the update failure was. Luckily 2 people on the Microsoft Windows Support forum knew which log file it was. When I learned that one piece of info I knew I was on the road to recovery. After recreating the failure it took me only about 30 minutes (well, maybe 45) to identify and remove the problematic driver file.

    So in the future I'll remember to identify and address the cause of a problem rather than deal with the results of one.
      My ComputerSystem Spec


 

Related Threads
The laptop supposedly completely upgraded to Wind ows 10, but after it's put on now the blue screen shows up with four options to choose from which are the continue, device, troubleshoot or turn PC off ones. Certainly, at least some of you must be...
Hello there! I upgraded from a fairly old install of Windows 7 (Installed 8/2011) to Windows 10 on 7/21, and have had a series of intermittent blue screens and have been spending the last week or so trying to self-diagnose and see if I could come up...
Hi guys, I know there's many threads on this subject but none seem to answer it for me. System: i7 950 X58A-UD3R Rev 2.0 16gb Ram GTX760. Pretty sure it's a Samsung 250gb SSD. So I upgraded W7 to W10 via iso. Install made it all the way.
I started the upgrade on my Dell Laptop using an ISO from Windows 7 Pro 64-bit. It seemed to start OK, the big clock display got to 6% so I walked away. I returned to find a blank screen with a working mouse cursor. Pressing Ctrl+Alt+Del brings up...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 22:52.
Find Us