Solved BSOD Page Fault in Nonpaged Area

[supermonkey]

Hi All,

I have today found BSOD Page Fault in Nonpaged Area. Laptop working ok in safe mode with networking.

I've attached the dump file as directed.

When I try perfmon /report it states "an error occured while attempting to generate the report."

Spec: Win 7 Home Premium x64, pre installed on laptop by HP. OS never re-installed. System approx 3 years old.

 

[koolkat77]

Please upload your msinfo32.nfo file. To get this:

• Click on the Start rb:
• Type msinfo32 into the Search programs and files box
• When it opens, go to File, Save
• Save as msinfo32.nfo and save in a place you will remember
• Let it finish the process of gathering and saving the system info
• Right click the .nfo file, click send to compressed (zipped) folder
• Upload the .zip file here.

 

[supermonkey]

Thanks for your help.

Requested file is attached

 

[supermonkey]

Ok, I cleared my Java cache & tried rebooting. Got further than earlier, but then got the BSOD which states something like "your pc has been shut down to prevent further problems"

I've attached an updated dump file

 

[koolkat77]

Thanks.

STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS

[LIST=1]
Start Menu\Programs\Security\Kaspersky Internet Security 2012	Jamie-PC\Jamie:Start Menu\Programs\Security\Kaspersky Internet Security 2012	Jamie-PC\Jamie[/LIST]

Please replace Kaspersky with Microsoft Security Essentials
→ Microsoft Security Essentials - Free Antivirus for Windows
Make a full scan once downloaded, installed and updated
→ Removal tool for Kaspersky Lab products
Kaspersky does cause blue screen crashes on some systems

Run the system file checker and reboot if integrity violations are found:
→ http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Run Disk Check for any errors on your hard disk for file system errors
and bad sectors on it
→ http://www.sevenforums.com/tutorials/433-disk-check.html

Then check for an update on your BIOS version

BIOS Version/Date	Hewlett-Packard F.04, [COLOR="Red"]10/09/2009[/COLOR]

Do these and let us know the results
We'll do more troubleshooting if the problems persist

 

[supermonkey]

Thanks,

Is Kaspersky definitely the cause? Or just a likely cause?

I've ran the state file checker. Not sure what it found though as when I came back to the pc, it was no longer running, but didn't appear to have rebooted as this web page was stil open.

I'm currently running the disk check. It's taking ages only on 21%

 

[supermonkey]

Ok, That's now finished, still got the BSOD.

Here's a new dump

 

[koolkat77]

Did SFC find violations?

Lets enable driver verifier to rule out buggy drivers.

Driver Verifier

I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in verifier and press Enter
- Select Create custom settings (for code developers) and click Next
- Select Select individual settings from a full list and click Next
- Select everything EXCEPT FOR Low Resource Simulation and click Next
- Select Select driver names from a list and click Next
Then select all drivers NOT provided by Microsoft and click Next
- Select Finish on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
Driver Verifier - Enable and Disable

Verifier puts extreme stress on the drivers, bad ones will cause BSOD. If we change all those drivers we hope for no more BSODs, If you get no BSODs, then its not a driver and we look to hardware. With verifier on your computer may be a little laggy, but actually..its just doing its work.

Information
Driver Verifier runs in the background, "testing" drivers for bugs. If it finds one, a Blue Screen of Death (BSOD) will result; the corresponding dump file will hopefully show the faulty driver.

Driver Verifier monitors kernel-mode drivers and graphics drivers to detect illegal function calls or actions that might corrupt the system. It can subject the drivers to a variety of stresses and tests to find improper behavior.

Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.

 

[supermonkey]

I'm not sure on SFC, when I came back to the PC, it was no longer running, but other windows were still open suggesting it had not rebooted. Should I run this again?

I created a Windows Defender offline disc last night & ran it. Did a full scan & it found no infections.

This morning the PC has booted ok. I am currently using it in normal mode. This is odd as it blue screen last night before the Defender scan.

Hopefully it is now ok but I will monitor it today. Would you recommend I still try the Driver verifier? Perhaps overnight?

I am confident the machine is free of malware, but I'm concerned there may still be a problem as I cannot see what we've done to fix it?

 

[koolkat77]

You need to observe for a while.
Did you replace Kaspersky with MSE?

 

[supermonkey]

I removed Kaspersky 2012 & thought I'd give the 2013 version a go.

I feel more re-assured with Kaspersky & like the av/firewall combined in one program.

 

[koolkat77]

Okay

 

[supermonkey]

Is MSE worth trying then?

Still no BSOD.

Any thing else I should do?

 

[koolkat77]

My suggestion to uninstall kaspersky was because it's known to cause blue screens.
(On some systems)

If you recheck my post #5 you can see the usual causes on your bug check which mentions
"antivirus" in the list. If Kaspersky was replaced with MSE (at least to test) we would
be able to find out if that was the reason behind the blue screens. If it wasn't you could
install it back any time you like.

Anyway, for now I'll just say observe your computer for more blue screens.

 

[koolkat77]

If you did not get a BSoD after your last post, you can mark this thread as solved