BSOD upgrading to Win10, error PAGE_FAULT_IN_NONPAGED_AREA

Page 2 of 3 FirstFirst 123 LastLast

  1. Posts : 4,132
    Windows 3.1 to Windows 11
       #11
      My Computer


  2. Posts : 14,901
    Windows 10 Pro
       #12

    I have asked Kyhi about false positives with sfc /scannow in windows 10, because there are false positives in windows 8 and I'm unsure if the same files are false positive in windows 10.

    The link he posted points to a tool he wrote that helps with the sfc and dism commands.
      My Computers


  3. Posts : 48
    Windows 10 Pro 64bit
    Thread Starter
       #13

    I have run the memtest for about 14 hours with the default settings, and there appears to be no errors.

    Attachment 33904

    On the other hand, sfc /scannow still cannot fix all the errors, even though I restarted at least 5 times, and some of them in safe mode too.

    If DISM is meant to be replacing files from a system image, maybe I should just reinstall Win7Pro and then try to upgrade from there?
      My Computer


  4. Posts : 14,901
    Windows 10 Pro
       #14

    DISM is meant to fix problems when sfc can't.
      My Computers


  5. Posts : 48
    Windows 10 Pro 64bit
    Thread Starter
       #15

    DISM in windows 7 can only scanhealth, not restorehealth..

    Attachment 33926

    I had another go at upgrading to Windows 10 from my current system in case something was fixed somewhere, but no.. the same BSOD and error code again....

    Any other ideas?
      My Computer


  6. Posts : 14,901
    Windows 10 Pro
       #16

    Check for any drivers that could cause trouble:



    Diagnostic Test

     DRIVER VERIFIER


    warning   Warning
    Please make a backup of your important files and get your rescue media or create one.
    Please create a restore point.

    Please read and run driver verifier.

    Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

    If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

    Note   Note
    Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.
      My Computers


  7. Posts : 48
    Windows 10 Pro 64bit
    Thread Starter
       #17

    So far, it's ok. How long should I leave it running? Can I shut down my computer later tonight? Or leave it in standby mode?
      My Computer


  8. Posts : 14,901
    Windows 10 Pro
       #18

    You should run driver verifier for max 48 hours at a time, or until you get a bluescreen, which comes first.
    You can leave the pc while driver verifier is running, but do not shut your pc down!
      My Computers


  9. Posts : 48
    Windows 10 Pro 64bit
    Thread Starter
       #19

    It's still ok..

    I've decided to do a clean install, so thanks for your help anyway.
      My Computer


  10. Posts : 14,901
    Windows 10 Pro
       #20

    If driver verifier hasn't crashed then it is most likely a hardware problem with windows 10.
    Before a clean install, would you mind to do a couple of hardware related tests?
      My Computers


 

  Related Discussions
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 20:25.
Find Us




Windows 10 Forums