Solved BSOD when gaming/transferring files - Page_Fault_In_NonPaged_Area

[onyxaj]

Still got crashes with the older driver. Went into Device Manager and disabled the Intel HD Graphics. Checked this morning, and the system crashed overnight. What's next? I really don't know what to do, or why I am having this issue.

 

[writhziden]

Can you upload the latest crash reports to analyze? That would be a tremendous help to provide any further troubleshooting steps.

One thing we should do is make sure Windows is running as it should:

• Run http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.

 

[onyxaj]

Scannow found nothing. The system was working fine for a couple days (Haven't tried gaming, but nothing overnight). But the system gave me a new BSOD this morning:
BAD_POOL_CALLER

Now my question is, since I've tested all other hardware, can this be a MOBO issue?

New dump attached.

 

[writhziden]

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\onyxaj\Windows_NT6_BSOD_jcgriff2 (2)\Windows_NT6_BSOD_jcgriff2\032912-16302-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`02e0e000 PsLoadedModuleList = 0xfffff800`03052650
Debug session time: Thu Mar 29 05:11:40.329 2012 (UTC - 6:00)
System Uptime: 1 days 11:57:58.188
Loading Kernel Symbols
...............................................................
................................................................
.............
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C2, {b, fffffa800fb533b0, 1, fffffa800fb53ec0}

Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiDecrementContextReference+a6 )

Followup: MachineOwner
---------

4: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

BAD_POOL_CALLER (c2)
The current thread is making a bad pool request.  Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 000000000000000b, type of pool violation the caller is guilty of.
Arg2: fffffa800fb533b0
Arg3: 0000000000000001
Arg4: fffffa800fb53ec0

Debugging Details:
------------------


FAULTING_IP: 
dxgmms1!VidSchiDecrementContextReference+a6
fffff880`0ffadfb6 ebd3            jmp     dxgmms1!VidSchiDecrementContextReference+0x7b (fffff880`0ffadf8b)

BUGCHECK_STR:  0xc2_b

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002fb7c93 to fffff80002e8ad40

STACK_TEXT:  
fffff880`02dcf918 fffff800`02fb7c93 : 00000000`000000c2 00000000`0000000b fffffa80`0fb533b0 00000000`00000001 : nt!KeBugCheckEx
fffff880`02dcf920 fffff880`0ffadfb6 : 00000000`0fb8ed50 00000000`00000001 fffff880`02dcfbc0 00000000`0fb8ed50 : nt!ExDeferredFreePool+0x12bf
fffff880`02dcf9d0 fffff880`0ffad0d4 : fffffa80`0fb8c720 fffffa80`0f672000 fffffa80`0f672000 fffffa80`0d2e0370 : dxgmms1!VidSchiDecrementContextReference+0xa6
fffff880`02dcfa00 fffff880`0ffacf8c : fffffa80`0fb8c720 fffffa80`0f60b410 fffffa80`0f60b410 00000000`00000001 : dxgmms1!VidSchiSwitchContext+0x84
fffff880`02dcfa50 fffff880`0ffad193 : fffffa80`0f60b410 fffffa80`0fb8c720 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiSwitchContextWithCheck+0x13c
fffff880`02dcfab0 fffff880`0ffd9e7a : 00000000`00000000 fffffa80`0fb8ed50 00000000`00000080 fffffa80`0f60b410 : dxgmms1!VidSchiScheduleCommandToRun+0xa7
fffff880`02dcfbc0 fffff800`03124f7a : 00000000`03830598 fffffa80`0f61f620 fffffa80`0ca6e040 fffffa80`0f61f620 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`02dcfc00 fffff800`02e7b9c6 : fffff800`02fffe80 fffffa80`0f61f620 fffff800`0300dcc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02dcfc40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VidSchiDecrementContextReference+a6
fffff880`0ffadfb6 ebd3            jmp     dxgmms1!VidSchiDecrementContextReference+0x7b (fffff880`0ffadf8b)

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  dxgmms1!VidSchiDecrementContextReference+a6

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1

FAILURE_BUCKET_ID:  X64_0xc2_b_dxgmms1!VidSchiDecrementContextReference+a6

BUCKET_ID:  X64_0xc2_b_dxgmms1!VidSchiDecrementContextReference+a6

Followup: MachineOwner
---------

Ran a Registry Fix - few errors found and fixed

It could be the motherboard. I have a question, though: How often do you run a registry clean on your system?

 

[onyxaj]

I don't run it very often. Usually only when I detect issues with the system. The program I used was Eusing Free Registry Cleaner since I couldn't remember what I use to use. If you have anything else I can try, I'll do so, but if not, I might just have to suck it up and buy a new MOBO. I am soooo tired of not having a usable PC. This was suppose to be my huge gaming upgrade and it's turned into a disaster.

By the way, what did the dump file note was wrong? I have never seen that error before.

 

[writhziden]

The .dmp file pointed to your graphics card again. You could try a clean install and see if it resolves the problem. http://www.sevenforums.com/tutorials/1649-clean-install-windows-7-a.html

Backup any important files first.


Also, did you do all the steps in my previous post (quoted here for convenience with some additions):

• Monitor temperatures during the following tests.
  
  Use the following programs to monitor the temperatures.​
  • Real Temp is a good CPU temperature monitor.
  • Speccy - System Information - Free Download will monitor all hardware temperatures.
  • HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
  • Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Let it run until the GPU temperatures even out or until the GPU temperatures reach a dangerous level (you can find the max temperature for your card on either the nVidia or AMD sites; if you are not sure, ask us). Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
    
    
  • Run http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
    
    
  • Follow the steps for doing a CPU stress test using IntelBurnTest

The new step is added in bold...

 

[onyxaj]

Thats alot of testing to run... and with my limited free time would take forever. The thing is, although the dmp files point to my grpahics card, it make NO sense. Like I've said before, I have used three different graphics cards and got the same BSOD errors. I have reloaded Windows before (When I first installed it, the updates wouldnt install), but I guess I can do it again.

 

[writhziden]

I understand the time constraints. However, since we know it is not the graphics card, those tests may allow us to determine whether it is the motherboard, your processor, or your PSU causing problems.

It could also still be RAM related. How many passes did you let Memtest86+ run for?


In regards to your registry cleaning to try to fix problems:

• Many of us on the forums actually do not recommend automated optimization tools for Windows 7. Windows 7 does a much better job of handling its own optimization than its predecessors did. We especially do not recommend registry cleaning as an "optimization" step because automated registry cleaning causes more harm to the registry than it actually repairs.
  
  In the future, if you need help optimizing Windows 7, please post a thread in Performance & Maintenance - Windows 7 Forums or follow the tutorial enclosed in that forum to http://www.sevenforums.com/tutorial...ws-7-a.html?filter[2]=Performance Maintenance.

 

[onyxaj]

Alright, I'll leave the rigistry alone until otherwise needed then. I just resintalled Windows 7, grabbed all updateds, and installed MSE last night. I THINK I already had a BSOD or two, but it was while I was not at the system, so I will let those be. I'll grab the latest NVidia cards, disble my onboard video, and give the system a run. I'll post back if I get anything. If I can run for two or so days with no errors, I'll mark resolved.

 

[writhziden]

Sounds like good troubleshooting steps.

Also, how many passes did Memtest86+ run when you ran it?

 

[onyxaj]

Blast! It crashed again. I'm not sure of the error, since it did it while I was away from the system. When I got back, the game was closed, and I had the little 'unexpected shutdown' message.

As for the MemTest runs, I don't really remember how many passes, maybe 5 or so?

Anyway, here is the latest BSOD error.

 

[writhziden]

Still blames the graphics card. Since you only ran 5 passes of Memtest86+, I suspect it still may be memory related. The RAM itself may be fine, but you may have too much RAM running at once without the proper settings. We should first make sure the RAM itself is fine. Run with 8 GB at a time and see how the system responds. Then run with the other set of 8 GB and see. Just do your normal routine in Windows with 8 GB each time. If the system works with both sets of 8 GB, it is probably just that adjustments need to be made for the 16 GB, and we can help with that.

Before taking out 8 GB, do the following with all 16 GB installed:

• Download and install CPU-Z and Upload screenshots of the CPU, Mainboard, Memory, and SPD tabs. In the SPD tab, upload an image of each slot.

Many times, the BIOS is configured to handle 4 GB with auto voltage settings. Increasing over 4 GB can sometimes result in crashes (although in my experience, 8 GB usually runs fine and it is at more than 8 that systems have issues). So do the above and post back your CPU-Z screenshots with 16 GB installed. Then test 8 GB at a time and see if maybe there is one bad set or if it is possibly a settings issue.

 

[onyxaj]

Never thought of having too much RAM. Okay, got the tools and captured each tab.

View attachment 205175

 

[writhziden]

Timings all look good. It may be a bad module or voltage adjustments that are needed. We'll have to see how things go when you test two modules at a time.

 

[onyxaj]

I have two in now. Slots 1 and 3. So far, no issues. Gaming was fine with no crashes, and no idle crashes as of yet. I will let it sit overnight and see in the morning. Now, if this is successful, do you want me to try the other two in the same slots, or should we think about tweaking the BIOS and using all four?

 

[writhziden]

Try the other two in the same slots first. We need to be sure both sets are good before doing the BIOS tweaks.

 

[onyxaj]

Okay, I assume the two sticks are working fine since the system would have normally crashed a few times, and I have had nothing. I just put the other two sticks in and will test today. I'll wait until tomorrow morning to verify I don't have any idle crashes overnight. I will post my results sometime tomorrow and we can go from there. Thanks again for all the help. It's been a hell of a ride, but I can see the end now.

 

[writhziden]

Glad to see we are at least on the right track. Let us know what happens with the other set of 8 GB.

 

[onyxaj]

Alright, I think I have at least 1 bad RAM stick. I put the other two in yesterday, and had a crash within ten minutes, then another within the next ten. I ran MemTest with both stick in, but after 12 passes, there will still no errors for some reason. I guess my only option now is to use each stick indiviadually to find which stick is bad. I assume the crashes are quicker now since its hitting the bad section of RAM faster. I have really lost faith in Memtest at this point though. I'll try each stick when I get a chance, chuck the bad one, and try the other three together and see if it works.

 

[writhziden]

Unfortunately, Memtest86+ does not always find problems. Memory can be very finicky, so it is not necessarily a fault of Memtest86+ but of electronics in general. When electronics fail, diagnostic utilities are not always able to catch the failure, especially if it is out of the realm of what they usually test for. That is why it is sometimes necessary to test through doing your normal routine through Windows itself.