BSOD page_fault_in_nonpaged_area Win7 and Win8

[cdog27]

Morning all,

Having issues with a page_fault_in_nonpaged_area BSOD. I was running Win7 Home Premium x64 and this kept happening randomly. I could be watching a YouTube video and browsing a forum and it would BSOD, or just reading e-mails. Didn't seem to happen if I was doing anything taxing.

Yesterday I took advantage of the cheap deal to upgrade to Windows 8 Pro (which I'm loving so far!). And now instead of the old BSOD screen we know and love, I get the new version with the face, but it's the same page_fault_in_nonpaged_area error message.

I've run a few pases of MemTest86+ as I believe this error could be to do with memory; but not errors came up. Attached is a .zip of the SF Diagnostic Tool (did I need to censor any personal info in any of these files??? :shock

Any help would be greatly appreciated!

Thanks,
CDog.

 

[OldMX]

Memtest your ram for some loops

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

 

[cdog27]

Memtest your ram for some loops

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

I have already done this for a number of passes (hours) with no faults.

 

[cdog27]

Any other suggestions? Possibly program related perhaps?

 

[cdog27]

bump

 

[tlarseth]

bump

Bumping only causes people to ignore your problem, if your memory checks out, have you cleaned your system fans and vents lately, and have you used a temp monitoring program like coretemp to see if your system might be overheating?

 

[cdog27]

bump

Bumping only causes people to ignore your problem, if your memory checks out, have you cleaned your system fans and vents lately, and have you used a temp monitoring program like coretemp to see if your system might be overheating?

Apologies for bumping. Will let the thread run its course naturally going forward!

Inside of my case is as clean as a whistle. I use HWMonitor to check temps; everything seems fine, even when gaming CPU temps stay cool (<70C).

A note to add: I've never had this BSOD whilst gaming, it always tends to be whilst I'm doing mundane tasks - listening to music/browsing.

 

[tlarseth]

If you have your files backed up, a clean install might fix this, my laptop used to get that error until I clean installed the OS, and the problem was fixed.

Also, for a desktop, 70 degrees Celcius is kind of hot, my desktop that only has stock fans, only gets to about 45-55 degrees while gaming, including Diablo III.

How long ago has it been since new bonding agent artic silver or the like was applied to your CPU/Heatsink?

 

[x BlueRobot]

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.

[B]PAGE_FAULT_IN_NONPAGED_AREA (50)[/B]

Could not read faulting driver name
Probably caused by : [COLOR="Red"]Npfs.SYS[/COLOR] ( Npfs!NpReadDataQueue+1e4 )

Image path: \SystemRoot\System32\Drivers\Npfs.SYS
    Image name: [COLOR="red"]Npfs.SYS[/COLOR]
    Timestamp:        [COLOR="red"]Thu Jul 26 03:30:26 2012[/COLOR] (5010ABC2)

Driver Reference Table - Npfs.sys

From Call Stack -

Image path: \SystemRoot\system32\drivers\fltmgr.sys
    Image name: [COLOR="red"]fltmgr.sys[/COLOR]
    Timestamp:        [COLOR="red"]Thu Jul 26 03:30:09 2012[/COLOR] (5010ABB1)

Driver Reference Table - fltmgr.sys

Please run:

• http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

 

[cdog27]

If you have your files backed up, a clean install might fix this, my laptop used to get that error until I clean installed the OS, and the problem was fixed.

Also, for a desktop, 70 degrees Celcius is kind of hot, my desktop that only has stock fans, only gets to about 45-55 degrees while gaming, including Diablo III.

How long ago has it been since new bonding agent artic silver or the like was applied to your CPU/Heatsink?

I had Win7 Home Premium x64 on the machine, did a fresh install of this on Saturday, then upgraded to Win 8 Pro. I did the fresh install prior to upgrading in the hope it would solve the problem, and I wouldn't carry it over to Win 8. Unfortunately that was not the case.

70C is the highest I've seen; I just mentioned it to demonstrate the peak temp I've seen (think I was running Prime95 when I saw that). I've had this i3 overclocked to 4GHZ for 2 years now and it's been stable. I haven't refreshed the thermal paste since I built this, a couple years ago.

What makes you think this particular BSOD is attributable to overheating?

 

[x BlueRobot]

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).

 

[cdog27]

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.

[B]PAGE_FAULT_IN_NONPAGED_AREA (50)[/B]

Could not read faulting driver name
Probably caused by : [COLOR="Red"]Npfs.SYS[/COLOR] ( Npfs!NpReadDataQueue+1e4 )

Image path: \SystemRoot\System32\Drivers\Npfs.SYS
    Image name: [COLOR="red"]Npfs.SYS[/COLOR]
    Timestamp:        [COLOR="red"]Thu Jul 26 03:30:26 2012[/COLOR] (5010ABC2)

Driver Reference Table - Npfs.sys

From Call Stack -

Image path: \SystemRoot\system32\drivers\fltmgr.sys
    Image name: [COLOR="red"]fltmgr.sys[/COLOR]
    Timestamp:        [COLOR="red"]Thu Jul 26 03:30:09 2012[/COLOR] (5010ABB1)

Driver Reference Table - fltmgr.sys

Please run:

• http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

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)?

 

[x BlueRobot]

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.

 

[cdog27]

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!

 

[x BlueRobot]

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

 

[cdog27]

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?

 

[tlarseth]

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.

 

[cdog27]

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 :|

 

[cdog27]

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?

 

[x BlueRobot]

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?