New
#1
BSOD on Shutdown - PAGE_FAULT_IN_NONPAGED_AREA
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.