BSOD playing Black Ops (page fault in nonpaged area)

Hello everyone,

I have been experiencing lots of BSODs with the message PAGE_FAULT_IN_NONPAGED_AREA recently when attempting to play Black Ops. It seems to only happen when I am trying to join a server (just when the loading screen is meant to appear). Sometimes it allows me to see the BSOD, other times it just restarts, but it is always happening when I try to join. I have attached my dump files hoping someone can point me in the right direction to fix this :). Thanks in advance!

My system:
Windows 7 Ultimate x64
Hardware is roughly 2 years old
OS age is under 6 months (since last re-install)

victorrodrz said:

Hello everyone,

I have been experiencing lots of BSODs with the message PAGE_FAULT_IN_NONPAGED_AREA recently when attempting to play Black Ops. It seems to only happen when I am trying to join a server (just when the loading screen is meant to appear). Sometimes it allows me to see the BSOD, other times it just restarts, but it is always happening when I try to join. I have attached my dump files hoping someone can point me in the right direction to fix this :). Thanks in advance!

My system:
Windows 7 Ultimate x64
Hardware is roughly 2 years old
OS age is under 6 months (since last re-install)

1-ASACPI.SYS

The pre 2009 version of this driver is a known BSOD cause.

Please visit this link: ASUS teK Computer Inc. -Support- Drivers and Download P7P55D LE
ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE

Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit" (it's about the 12th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.SYS file is date stamped from 2009 or 2010 (NOTbefore).



2-Old drivers needing updating

Code:

wacommousefilter.sys    2/16/2007 1:12:17 PM        fffff880`069e8000    fffff880`069f0000    0x00008000    0x45d5f401                        
ISODrv64.sys    2/10/2009 4:22:18 AM        fffff880`04068000    fffff880`04086000    0x0001e000    0x4991474a                        
yk62x64.sys    2/23/2009 10:02:27 AM        fffff880`05331000    fffff880`05394000    0x00063000    0x49a2ba83

3-Might want to mention your hardware. We need your system specs to know what hardware you have (especially if it is a Mac)

Related to MDFSYSNT.SYS MacDrive Partition Manager from Mediafour Corporation.

Thanks for your help zigzag. I noticed that you advised me to update a driver for P7P55D LE. My current motherboard is a P6X58D-E. Is this going to be a problem? Being a different board. I should also note it does not happen in any other game I play. Also another thing I believe could be the culprit is how many times I have done a system restore due to driver issues with the GPU. Would you recommend a clean reinstall?

Hardware specs:

HIS ATI HD5970 (11.10 Catalyst. 11.11 gives me bad performance in games and also crashes)
ASUS P6X58D-E Motherboard
6GB G.SKILL TRIDENT MEMORY
750W Corsair Power Supply
Intel i7 930 @ 4.0ghz w/ Thermaltake Venomous X CPU cooler
X-Fi Titanium sound card

victorrodrz said:

Thanks for your help zigzag. I noticed that you advised me to update a driver for P7P55D LE. My current motherboard is a P6X58D-E. Is this going to be a problem? Being a different board. I should also note it does not happen in any other game I play. Also another thing I believe could be the culprit is how many times I have done a system restore due to driver issues with the GPU. Would you recommend a clean reinstall?

Hardware specs:

HIS ATI HD5970 (11.10 Catalyst. 11.11 gives me bad performance in games and also crashes)
ASUS P6X58D-E Motherboard
6GB G.SKILL TRIDENT MEMORY
750W Corsair Power Supply
Intel i7 930 @ 4.0ghz w/ Thermaltake Venomous X CPU cooler
X-Fi Titanium sound card

I believe they all use the same update. If it is not for your system it will tell you when you install it.


I ALWAYS RECOMMEND A CLEAN INSTALL AND PRACTICE WHAT i PREACH. Quarterly I re-install from a clean image as I install and un-install a lot.

It wont help a hardware problem but will take of most of the software difficulties.

Hey Zigzag,

I did a clean install of windows and also updated the motherboard driver as you recommended (I think). The problem still persists in the same game (also reinstalled). I have also re seated the memory sticks, no help. I have attached the recent dumps I got. Thank you!

victorrodrz said:

Hey Zigzag,

I did a clean install of windows and also updated the motherboard driver as you recommended (I think). The problem still persists in the same game (also reinstalled). I have also re seated the memory sticks, no help. I have attached the recent dumps I got. Thank you!

Bug check 0x50 usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).
Another common cause is the installation of a faulty system service.
Antivirus software can also trigger this error, as can a corrupted NTFS volume.





These crashes were caused by memory corruption. Please run these two tests to verify your memory and find which driver is causing the problem.


1-Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

RAM - Test with Memtest86+



2-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/Win7 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" (without the quotes) 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