BSOD page_fault_in_nonpaged_area Win7 and Win8

Page 2 of 9 FirstFirst 1234 ... LastLast
  1.    #11

    The BSOD can be due to defective hardware, which in turn can be caused by overheating thus damaging the components, and also could please run Driver Verifier (see post #9).
      My Computer


  2. Posts : 45
    Windows 8 Pro x64
    Thread Starter
       #12

    x BlueRobot said:
    Your BSOD is not loading for some reason;

    STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA

    The dump file has loaded now, and having a look at it.

    Code:
    PAGE_FAULT_IN_NONPAGED_AREA (50)
    
    Could not read faulting driver name
    Probably caused by : Npfs.SYS ( Npfs!NpReadDataQueue+1e4 )
    
    Image path: \SystemRoot\System32\Drivers\Npfs.SYS
        Image name: Npfs.SYS
        Timestamp:        Thu Jul 26 03:30:26 2012 (5010ABC2)
    Driver Reference Table - Npfs.sys

    From Call Stack -

    Code:
    Image path: \SystemRoot\system32\drivers\fltmgr.sys
        Image name: fltmgr.sys
        Timestamp:        Thu Jul 26 03:30:09 2012 (5010ABB1)
    Driver Reference Table - fltmgr.sys

    Please run:

    Thanks for this. Will run with Driver Verifier enabled as soon as I get home. The guide says not to target drivers under Microsoft Corporation - but won't both of these be under that Provider?

    Also, what do these drivers do? And how can the timestamp be July when I only re-installed Windows on Saturday (10th Nov)?
      My Computer

  3.    #13

    Yes, don't target the Windows drivers, sometimes BSODs don't always give us the real driver which is causing the problems, and therefore it blames a Windows driver instead; Driver Verifier will help cause another BSOD which should hopefully display a real cause.

    For the driver explanations, fltmgr.sys is related to the file system (see fltmgr.sys also) and Npfs.sys is another Windows driver which I'm not able to find much information about.

    You can read the Stop Code links, as they have a list of usual causes, which you could also try and test.
      My Computer


  4. Posts : 45
    Windows 8 Pro x64
    Thread Starter
       #14

    x BlueRobot said:
    Yes, don't target the Windows drivers, sometimes BSODs don't always give us the real driver which is causing the problems, and therefore it blames a Windows driver instead; Driver Verifier will help cause another BSOD which should hopefully display a real cause.

    For the driver explanations, fltmgr.sys is related to the file system (see fltmgr.sys also) and Npfs.sys is another Windows driver which I'm not able to find much information about.

    You can read the Stop Code links, as they have a list of usual causes, which you could also try and test.
    Thanks for your help. Will enable Driver Verifier this evening and post up any subsequent BSOD's. Hopefully we can get to the bottom of this!
      My Computer

  5.    #15

    Just had a look at your System Information file (.NFO file), and noticed you have Dameon Tools installed, this is known is cause BSODs:

    • Uninstall Dameon Tools Lite

    Driver (Dameon Tools) - dtsoftbus01 13/01/2012 13:45:46
      My Computer


  6. Posts : 45
    Windows 8 Pro x64
    Thread Starter
       #16

    x BlueRobot said:
    Just had a look at your System Information file (.NFO file), and noticed you have Dameon Tools installed, this is known is cause BSODs:

    • Uninstall Dameon Tools Lite

    Driver (Dameon Tools) - dtsoftbus01 13/01/2012 13:45:46
    Hmm so this is a known issue with Daemon Tools? Will uninstall and do the Driver Verifier.

    Are there any suitable replacements for Daemon Tools, that would not cause a BSOD?
      My Computer


  7. Posts : 212
    Windows 8 64-bit (6.2, Build 9200) (9200.win8_rtm.120725-1247)
       #17

    Don't just uninstall it run the sptd uninstaller too. Just download their installer and choose to uninstall it when you run it. it is the sptd.sys driver that is causing the BsoD with a lot of people with Windows 7.

    Here is the link to the installer/uninstaller.
      My Computer


  8. Posts : 45
    Windows 8 Pro x64
    Thread Starter
       #18

    Enabled Driver Verifier, rebooted. Blue Screen on reboot, Blue Screened again on second reboot. Windows 8 Repair came up, had to restore from a previous point. Restored, and rebooted. Now it just takes me to the Win 8 loading screen, the screen goes black and nothing happens.

    Could be graphics card driver? Can't get into windows at all now...great :|
      My Computer


  9. Posts : 45
    Windows 8 Pro x64
    Thread Starter
       #19

    Managed to get in. Removed the graphics card and used on board DVI port. Nvidia drivers are installed, tried reinstalling but it says no device detected.

    The win 8 reinstalled has been rolled back to Saturday. The graphics drivers are installed yet I cannot get a picture through the card. Ay ideas how turning on driver verifier could do this?
      My Computer

  10.    #20

    I wouldn't say that Driver Verifier is the issue, have you now turned off Driver Verifier?

    Have the BSOD dump files been removed due to the restores you had to carry out?
      My Computer


 
Page 2 of 9 FirstFirst 1234 ... LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 06:34.
Find Us