BSOD on Shutdown - PAGE_FAULT_IN_NONPAGED_AREA

np726 · 10 Aug 2012

First and foremost, I've posted to this forum before with what I think is the same issue. However, it's been two months since I had the issue, and the person that was helping me seems to no longer have an account here. Because of this, I started a new thread, as I have gone about my own troubleshooting differently (and more completely this time). I hope that isn't an issue, and my apologies to the moderators if it is...

I'm experiencing BSODs when I attempt to shut down or restart Windows. It doesn't happen every time though, usually after the machine has been on for more than 24 hours or so. I've run the SF Diagnostic Tool, and the results are attached.

It has just started becoming an issue again in the last week - 8/2, twice on 8/7, and again today (8/10).

Here's what I've tried so far:

I let MemTest86+ run overnight, for a total of 7 passes. No memory errors were found.
Hard drives have all been tested with WD Data Lifeguard Diagnostic tool, and all tests pass.
Ran driver verifier per the instructions found here. I ran videos, opened up various programs (Word, iTunes, Photoshop) and left them running. Also started up Steam and played a few different games (CounterStrike Source, DIRT 3, Bioshock II). I ran with verifier for about 90 minutes, and was unable to generate a BSOD. When I shut down after that, did not get a BSOD.
I've had a "phantom" audio driver which reports "This device cannot start (code 10)". I've posted to the audio section of this forum on the issue, which can be found here. I've disabled this device in Windows Device Manager.

I'm not overclocking my machine, nor have made any modifications to any hardware. My system specs are in my profile.

Any help on solving this issue would be greatly appreciated!

[EDIT]Last night, my Logitech G-110 keyboard became unresponsive while playing DIRT 3. It later became unresponsive while trying to boot into the BIOS too. I swapped the USB port it was plugged into, and still had the issue. My Razer Nostromo was functioning during both of these times, however, leading me to believe that the keyboard itself is faulty. I have removed the keyboard and replaced it with a standard Microsoft USB keyboard. I know that I'm posting a ton of different information here, but I just want to be sure to include everything I can that might help in finding a solution.

FredeGail · 10 Aug 2012

Hello and thank you for coming back.

BSOD Analyse

Problem Devices

Code:

Microsoft PS/2 Mouse    ACPI\PNP0F03\4&FA2F13B&0    This device is not present, is not working properly, or does not have all its drivers installed.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Standard PS/2 Keyboard    ACPI\PNP0303\4&FA2F13B&0    This device is not present, is not working properly, or does not have all its drivers installed.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
High Definition Audio Device    HDAUDIO\FUNC_01&VEN_8086&DEV_2806&SUBSYS_80860101&REV_1000\4&36B8CB0&0&0301    This device is disabled.

You were aware of the last one though. The first one is your mouse, and the second one is your keyboard by the looks of it. I'd suggest you to get the drivers for those, by that you filtered the device problems.

Code:

IMAGE_NAME:  dxgkrnl.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799fa
FAILURE_BUCKET_ID:  X64_0x50_dxgkrnl!DXGADAPTER::ReleaseReference+16
BUCKET_ID:  X64_0x50_dxgkrnl!DXGADAPTER::ReleaseReference+16
Followup: MachineOwner
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
IMAGE_NAME:  dxgkrnl.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799fa
FAILURE_BUCKET_ID:  X64_0x50_dxgkrnl!DXGADAPTER::ReleaseReference+16
BUCKET_ID:  X64_0x50_dxgkrnl!DXGADAPTER::ReleaseReference+16
Followup: MachineOwner

Do you happen to get crashes when you're playing games? The directX files were blamed in some of your dumps. This can indicate a bad video driver, or bad Windows files (also directX files).
To be on the safe side, I'd suggest you to run 3 things.

Fresh up the DirectX files
Reinstall your Graphics Driver within a clean install. By that you're making sure that there's no leftover files.
1. i) Make your way to ATI Drivers - Downloads and download the latest driver for your card, save it to your desktop for instance ii) Uninstall the Graphic driver you currently have and all its extensions (do not reboot yet) iii) Download Driver Sweeper iv) Get to safe mode (without network) and search for Driver Sweeper in your v) Select all the ATI components and analyse them vi) Clean them, head into Windows without internet and install the driver you've downloaded previously.
SFC /scannow - We usually ask people to do this command to check if Windows is corrupted. It's the most common used one to check if the Windows files are corrupted. If it'll find errors, it'll restore them.

Tip

If you're having a custom customization layer on your Aero, it's likely to get restored to default.

Press Start | search 'cmd' | Right-click it
| open as Admin | type SFC /SCANNOW

SFC /SCANNOW Command - System File Checker

Best Regards,
Frederik.

np726 · 10 Aug 2012

Alright, I don't use PS/2 mouse or keyboard on this machine... not even sure I own one lol. Tried to update the drivers, both came back saying that they were already up to date. I uninstalled them, and they do not show back up when I rescan for new h/w.

FredeGail said:

Do you happen to get crashes when you're playing games?

I got a BSOD once while playing DIRT 3 (See dump file for 7/20/12).

I updated DirectX using the link provided.
Uninstalled all of the ATI components (When I went to restart after uninstalling ATI, got another BSOD. I've attached the dump file).
Swept the drivers, and installed a fresh copy per your instructions.

Ran sfc /scannow, no integrity violations were found.

I'm going to run as normal tonight and through tomorrow (play games, etc). Will test shutdown then and post back with an update.

FredeGail · 11 Aug 2012

Ah, of course! It's because you have a gaming mice installed. It'll make the PS/2 drivers showing as Problem Devices. In these cases, they can be ignored.

Glad you were able to update those drivers.

Code:

1: kd> k
Child-SP          RetAddr           Call Site
fffff880`09cf52a8 fffff800`02e3ff0f nt!KeBugCheckEx
fffff880`09cf52b0 fffff800`02e972ee nt! ?? ::FNODOBFM::`string'+0x43d51
fffff880`09cf5410 fffff880`0750e756 nt!KiPageFault+0x16e
fffff880`09cf55a0 fffff880`075366fc dxgkrnl!DXGADAPTER::ReleaseReference+0x16
fffff880`09cf55d0 fffff880`0757a0ea dxgkrnl!DXGADAPTER::DestroyHandle+0xac
fffff880`09cf5600 fffff880`075797e0 dxgkrnl!DXGPROCESS::Destroy+0x35a
fffff880`09cf56b0 fffff960`001667a4 dxgkrnl!DxgkProcessCallout+0x268
fffff880`09cf5740 fffff960`00165ea3 win32k!GdiProcessCallout+0x244
fffff880`09cf57c0 fffff800`0316a641 win32k!W32pProcessCallout+0x6b
fffff880`09cf57f0 fffff800`0314dbdd nt!PspExitThread+0x4d1
fffff880`09cf58f0 fffff800`02e8bcda nt!PsExitSpecialApc+0x1d
fffff880`09cf5920 fffff800`02e8c020 nt!KiDeliverApc+0x2ca
fffff880`09cf59a0 fffff800`02e984f7 nt!KiInitiateUserApc+0x70
fffff880`09cf5ae0 00000000`77962c1a nt!KiSystemServiceExit+0x9c
00000000`0323f4b8 00000000`00000000 0x77962c1a

DirectX is blamed in the stack itself. I would recommend you to look at the memory.

Looking at your bugcheck it's likely that a memory corruption event was triggered. Though a driver could be causing the memory to be borked, but we're usually suggesting a memory test before moving forward. Do a scan with Memtest86+. Memtest is a scanner that'll check your sticks for errors.

Warning

Note that the below instructions may break your WARRANTY rules. If you're unsure check manuals, separated warranty papers, stickers on computer for secure permission.

To ensure that we'll know if it's the slots on the motherboard that's broken, or the sticks itself - we have a little procedure we'll recommend. Remove 1 stick, scan the other with Memtest in the current slot. After 7 passes, move the stick to another slot and scan, and so on and so forth until you've scanned all the sticks, and all the slots, one by one.

Memtest86+ - Advanced Memory Diagnostic Tool

Code:

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffa8c07385feb, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff800030b2e85, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000005, (reserved)

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

Best Regards,
Frederik.

np726 · 11 Aug 2012

I ran MemTest86+ a couple of days ago and let it run for 7 passes. The scan came up clean.

np726 · 11 Aug 2012

Let the system run for about 24 hours. Only had minimal usage, played music and checked email, and that's about it. Went for a restart and got another BSOD. Dump file attached.

FredeGail · 12 Aug 2012

Alright then, let's go for Driver Verifier, to stress test your 3rd party ones.

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff 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) - and create a System Repair Disc (Win7) if you don't have a full installation DVD.
You can do this by going to Start...All Programs...Maintenance...Create a System Repair Disc (don't forget to test the disc to make sure it works).

For Vista, you can download the repair discs from different websites. If unable to locate them, shoot me a PM and I'll point you to them.
For Win8, BSOD's are different - and we'll have to adjust how we do this with them.

Also, to ensure that you can recover, here's another couple of additional steps:
- Get to the Safe Mode menu (rapidly tap F8 just before the Windows splash screen comes up). Scroll down to and select "Disable automatic restart on System Failure"
- Get the RED information from this picture (in particular we will need the name of the file that the error occurred in):
Picture of a BSOD

Then, here's the procedure to run Driver Verifier:
- 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 "IRP Logging", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next" ("Special Pool" may be able to be used depending on amount of RAM and errors being seen. In situations with small amounts of RAM, DO NOT select it),
- 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).

Reboot into Windows (after the crash) and locate the memory dump file. If present, turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page. Then, zip up the memory dump file(s) and upload them with your next post. If no dump files were generated, post back for further suggestions.

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.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Code:

Delete these registry keys to stop Driver Verifier from loading (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

Best Regards,
Frederik.

np726 · 13 Aug 2012

I ran verifier for roughly 36hrs. It never crashed. I stressed the hell out of it, played games, streamed movies, etc. It didn't crash. When I went to restart it a few minutes ago, it got to the point where it usually gives me the BSOD ("Waiting for applications to close" screen), but instead just froze. No dump file was generated...

When I pushed the power button, the system cut power immediately. (As opposed to how it usually takes a few seconds for Windows to get the shutdown signal.) Not sure if that really means anything.

Prior to running verifier, I got curious and found a graphics card memory testing program called VMT. Made a boot and tested the graphics memory... 37 passes... clean...

FredeGail · 14 Aug 2012

A little strange. What's your temperatures overall?

Best Regards,
Frederik.

np726 · 14 Aug 2012

My cores idle around 40C, and the GPU idles at exactly 50C. GPU temp is according to GPU Meter using PC Monitor. It doesn't show a PCB temp because of software/hardware compatibility.