BSOD When Gaming BCCode 50 PAGE_FAULT_IN_NONPAGED_AREA

Nick05 · 27 Jan 2012

Hi All....

My first post here and unfortunately its BSOD help im after....

Hers some info from BlueScreenView...

012712-27612-01.dmp 27/01/2012 17:33:23 PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffff8a0`1084792c 00000000`00000001 fffff880`07647e47 00000000`00000000 crashdmp.sys crashdmp.sys+37ad550 x64 ntoskrnl.exe+7cc40 C:\Windows\Minidump\012712-27612-01.dmp 8 15 7601 288,365

system spec. Windows 7 Forums - View Profile: Nick05

I hope ive provided all the correct info, pls forgive me if i have not.

I look forward to your response.

Nick.

writhziden · 28 Jan 2012

Code:


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


Loading Dump File [K:\BSODDmpFiles\Nick05\BSOD\Windows_NT6_BSOD_jcgriff2\012712-27612-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*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.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e1b000 PsLoadedModuleList = 0xfffff800`03060670
Debug session time: Fri Jan 27 10:31:31.481 2012 (GMT-7)
System Uptime: 0 days 0:20:27.370
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff8a01084792c, 1, fffff88007647e47, 0}

Unable to load image atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys

Could not read faulting driver name
Probably caused by : atikmdag.sys ( atikmdag+3b3e47 )

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

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

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: fffff8a01084792c, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff88007647e47, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000000, (reserved)

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


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030ca100
 fffff8a01084792c 

FAULTING_IP: 
atikmdag+3b3e47
fffff880`07647e47 87422c          xchg    eax,dword ptr [rdx+2Ch]

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  TESV.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800ec4f550 -- (.trap 0xfffff8800ec4f550)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=fffff8a010810278
rdx=fffff8a010847900 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88007647e47 rsp=fffff8800ec4f6e0 rbp=fffff8a010810128
 r8=0000000000000003  r9=fffff80002e1b000 r10=fffff8000300f420
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
atikmdag+0x3b3e47:
fffff880`07647e47 87422c          xchg    eax,dword ptr [rdx+2Ch] ds:f350:fffff8a0`1084792c=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e439fc to fffff80002e97c40

STACK_TEXT:  
fffff880`0ec4f3e8 fffff800`02e439fc : 00000000`00000050 fffff8a0`1084792c 00000000`00000001 fffff880`0ec4f550 : nt!KeBugCheckEx
fffff880`0ec4f3f0 fffff800`02e95d6e : 00000000`00000001 fffff8a0`1084792c fffffa80`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4611f
fffff880`0ec4f550 fffff880`07647e47 : fffff8a0`10810168 ffffffff`af969b98 fffff8a0`10810158 00000001`06140000 : nt!KiPageFault+0x16e
fffff880`0ec4f6e0 fffff8a0`10810168 : ffffffff`af969b98 fffff8a0`10810158 00000001`06140000 fffff880`6d4d6901 : atikmdag+0x3b3e47
fffff880`0ec4f6e8 ffffffff`af969b98 : fffff8a0`10810158 00000001`06140000 fffff880`6d4d6901 00000000`00000000 : 0xfffff8a0`10810168
fffff880`0ec4f6f0 fffff8a0`10810158 : 00000001`06140000 fffff880`6d4d6901 00000000`00000000 fffff8a0`1080a600 : 0xffffffff`af969b98
fffff880`0ec4f6f8 00000001`06140000 : fffff880`6d4d6901 00000000`00000000 fffff8a0`1080a600 fffff880`07d56a00 : 0xfffff8a0`10810158
fffff880`0ec4f700 fffff880`6d4d6901 : 00000000`00000000 fffff8a0`1080a600 fffff880`07d56a00 ffffffff`af969b98 : 0x1`06140000
fffff880`0ec4f708 00000000`00000000 : fffff8a0`1080a600 fffff880`07d56a00 ffffffff`af969b98 00000000`00000000 : 0xfffff880`6d4d6901


STACK_COMMAND:  kb

FOLLOWUP_IP: 
atikmdag+3b3e47
fffff880`07647e47 87422c          xchg    eax,dword ptr [rdx+2Ch]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  atikmdag+3b3e47

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME:  atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4edd8367

FAILURE_BUCKET_ID:  X64_0x50_atikmdag+3b3e47

BUCKET_ID:  X64_0x50_atikmdag+3b3e47

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

Loading Dump File [K:\BSODDmpFiles\Nick05\BSOD\Windows_NT6_BSOD_jcgriff2\012512-27877-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*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.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e06000 PsLoadedModuleList = 0xfffff800`0304b670
Debug session time: Wed Jan 25 13:34:31.697 2012 (GMT-7)
System Uptime: 0 days 1:40:00.571
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa80072484e0, fffff88006c5d8f0, 0, 2}

*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+78f0 )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa80072484e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88006c5d8f0, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000002, Optional internal context dependent data.

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


FAULTING_IP: 
atikmpag+78f0
fffff880`06c5d8f0 4883ec28        sub     rsp,28h

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`029ef9c8 fffff880`06d08000 : 00000000`00000116 fffffa80`072484e0 fffff880`06c5d8f0 00000000`00000000 : nt!KeBugCheckEx
fffff880`029ef9d0 fffff880`06d07d0a : fffff880`06c5d8f0 fffffa80`072484e0 fffffa80`071a0ab0 fffffa80`0745a410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`029efa10 fffff880`07d35f07 : fffffa80`072484e0 00000000`00000000 fffffa80`071a0ab0 fffffa80`0745a410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`029efa40 fffff880`07d5fb75 : 00000000`ffffffff 00000000`0005ddb7 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`029efb20 fffff880`07d5e2bb : 00000000`00000102 00000000`0000000a 00000000`0005ddb7 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`029efb50 fffff880`07d312c6 : ffffffff`ff676980 fffffa80`0745a410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`029efbf0 fffff880`07d5de7a : 00000000`00000000 fffffa80`06042950 00000000`00000080 fffffa80`0745a410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`029efd00 fffff800`0311dfee : 00000000`fffffc32 fffffa80`071a9b60 fffffa80`054fc040 fffffa80`071a9b60 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`029efd40 fffff800`02e745e6 : fffff880`009e9180 fffffa80`071a9b60 fffff880`009f40c0 fffff880`01249384 : nt!PspSystemThreadStartup+0x5a
fffff880`029efd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+78f0
fffff880`06c5d8f0 4883ec28        sub     rsp,28h

SYMBOL_NAME:  atikmpag+78f0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4f026739

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

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

Most likely due to a graphics card driver being corrupt. Could also be the card itself overheating, having dust buildup, not being seated correctly, or outright failing. Other possible causes are Memory problems... Graphics card memory problems... CMOS... Corrupted hard disk system files... Corrupted System Files... Missing Windows Updates... Drivers...
Your video card did not respond to the system's instructions in a timely manner.

Thanks to Dave76 for help understanding possible causes.

Start with the following steps to diagnose the graphics card. After each step, post back before proceeding to the following step.

If you are overclocking anything, please stop.
Re-install/install your latest display card drivers. Even if they are the latest, they may have been corrupted, so re-install if they are the latest.
1. Download the latest drivers for your display card(s)
2. Click Start Menu
3. Right Click My Computer/Computer
4. Click Manage
5. Click Device Manager from the list on the left
6. Expand Display adapters
7. Do the following for each adapter (in case you have multiple display cards)
  - Right click the adapter
  - Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
  - Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
8. Restart your computer after uninstalling drivers for all display cards
9. Install the latest driver for the display cards once Windows starts
Alternatively:
1. Login as an adminstrative user
2. Download the latest drivers for your display card(s)
3. Click Start Menu
4. Click Control Panel
5. Click Hardware and Sound
6. Click Device Manager (the last link under Devices and Printers)
7. Expand Display adapters
8. Do the following for each adapter (in case you have multiple display cards)
  - Right click the adapter
  - Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
  - Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
9. Restart your computer after uninstalling drivers for all display cards
10. Install the latest driver for the display cards once Windows starts
Closely follow the first three posts of STOP 0x116: VIDEO_TDR_ERROR troubleshooting and proceed through each step. Let us know if you need further help.
Run Hardware - Stress Test With Prime95 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.
Please remove Daemon Tools, as it uses a driver called dtsoftbus01.sys that is known to cause BSODs.

I prefer TotalMounter as my CD/DVD virtualization software as it allows me to burn images to a virtual CD/DVD if I just want an ISO file instead of a disc, and it is free.

Many use MagicISO - Convert BIN to ISO, Create, Edit, Burn, Extract ISO file, ISO/BIN converter/extractor/editor as well, which is also free.
An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:

a. Backup your system and user files
b. Create a system restore point
c. If you do not have a Windows 7 DVD, Create a system repair disc
d. Run Driver Verifier

If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using System Restore OPTION TWO.

Thanks to zigzag3143 for contributing to the Verifier steps.
If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.

Nick05 · 28 Jan 2012

Hi writhziden, Thank you for your response...

I did have my system o/c'ed but did reset all back to auto and still got the BSOD, I also removed one of my graphics cards and it stopped so i swapped the other card back in on its own thinking it may be faulty but all the time it was running on its own it was fine, I only seem to get these when running crossfire, I have consistently monitored my GPU temps and they never overheat, my case has ample cooling and is regularly cleaned with compressed air....

I was running ATI 12.1a preview drivers and removed those thinking it could be the beta's and swapped for the newly released 12.1 WHQL. but still got the BSOD, it is very strange as i have had no problems today at all so far today...

I am about to run Furmark so i will report back soon.

Nick.

writhziden · 28 Jan 2012

So if you run both cards, you get crashes, but either one by itself works fine? Do they both work individually in each slot, or have you tested both slots yet? Could be a bad slot, or there could be a problem with them working together in which case you should contact the manufacturer of the card and of your motherboard to determine troubleshooting steps for the dual card setup.

Nick05 · 28 Jan 2012

Ran Furmark for 20 mins and all was fine, temps never went over 90deg.C.....

I only tested the 2 cards singularly in one slot, i will test both cards individually in slot 2 and post back any results, thanks for help so far....

Speak soon...

Nick.

Nick05 · 28 Jan 2012

OK the last 45 mins have been very eventful indeed....

I ran the driver verifier as instructed and rebooted, it booted into a BSOD stating "IRQL NOT LESS OR EQUAL" so rebooted again and got x3 black screens although i could still see and move my mouse cursor, re3booted again and the system hung at the "starting windows" screen......

I then unplugged my G27 racing wheel, my ext HDD and also x2 of my 3 screens in thinking that maybe one of those could be the cause and rebooted into startup repair and let it run which finished unable to repair the system....
Upon the next reboot i got another BSOD this time stating "the io manager has detected a violation by a driver that is being verified....HIDCLASS.SYS the system is now stuck in a circle, it boots to windows and then BSOD's everytime with the above statement, I am now on the wife's laptop.......

Nick.

Nick05 · 28 Jan 2012

was in a bit of a blind panick and completely forgot about rolling back to restore point

Nick05 · 28 Jan 2012

more mini dumps.....

writhziden · 28 Jan 2012

So you were able to restore back to a restore point?

HIDCLASS.SYS is typically blamed if you have an external device plugged in (mouse, keyboard, gaming controllers, some hard drives, etc). It can also be caused by Bluetooth devices internal to the computer.

writhziden · 28 Jan 2012

Code:


Loading Dump File [E:\BSODDmpFiles\Nick05\Windows_NT6_BSOD_jcgriff2\012812-21387-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\Users\Mike\Documents*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.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e18000 PsLoadedModuleList = 0xfffff800`0305d670
Debug session time: Sat Jan 28 11:20:34.126 2012 (GMT-7)
System Uptime: 0 days 0:00:59.030
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C9, {23b, fffff88006747710, fffff9800c220dc0, 0}

Probably caused by : HIDCLASS.SYS ( HIDCLASS!HidpMajorHandler+0 )

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

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

DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 000000000000023b, The caller has changed the status field of an IRP it does not understand.
Arg2: fffff88006747710, The address in the driver's code where the error was detected.
Arg3: fffff9800c220dc0, IRP address.
Arg4: 0000000000000000

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


BUGCHECK_STR:  0xc9_23b

DRIVER_VERIFIER_IO_VIOLATION_TYPE:  23b

FAULTING_IP: 
HIDCLASS!HidpMajorHandler+0
fffff880`06747710 48895c2410      mov     qword ptr [rsp+10h],rbx

FOLLOWUP_IP: 
HIDCLASS!HidpMajorHandler+0
fffff880`06747710 48895c2410      mov     qword ptr [rsp+10h],rbx

IRP_ADDRESS:  fffff9800c220dc0

DEVICE_OBJECT: fffffa80090d3310

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

LOCK_ADDRESS:  fffff80003093b80 -- (!locks fffff80003093b80)

Resource @ nt!PiEngineLock (0xfffff80003093b80)    Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE: 
	Lock address  : 0xfffff80003093b80
	Thread Count  : 0
	Thread address: 0x0000000000000000
	Thread wait   : 0x0

LAST_CONTROL_TRANSFER:  from fffff8000331e3dc to fffff80002e94c40

STACK_TEXT:  
fffff880`033850e8 fffff800`0331e3dc : 00000000`000000c9 00000000`0000023b fffff880`06747710 fffff980`0c220dc0 : nt!KeBugCheckEx
fffff880`033850f0 fffff800`0332847a : fffff800`0331c9f0 fffff880`06747710 fffff980`0c220dc0 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`03385130 fffff800`03329483 : 00000000`0000023b 00000000`c0000010 fffff980`0c220dc0 00000000`ffffffff : nt!ViErrorFinishReport+0xda
fffff880`03385180 fffff800`03329b42 : fffff980`0c220f20 fffff880`06747710 00000000`00000000 00000000`00000000 : nt!VfErrorReport1+0x63
fffff880`03385220 fffff800`0331e071 : fffffa80`07b481c8 00000000`00000001 00000000`00000000 fffff980`0c220f20 : nt!ViGenericVerifyIrpStackUpward+0x62
fffff880`03385250 fffff800`0332ab2d : fffffa80`08dfb010 fffffa80`07b48010 fffff980`0c220dc0 fffff980`0c220dc0 : nt!VfMajorVerifyIrpStackUpward+0x91
fffff880`03385290 fffff800`0333c50d : fffff980`0c220f20 fffff880`03385480 00000000`c0000010 fffff980`0c220f20 : nt!IovpCompleteRequest2+0xad
fffff880`03385300 fffff800`02e98021 : fffff980`0c220f23 00000000`00000000 00000000`000000ff fffff800`0331feea : nt!IovpLocalCompletionRoutine+0x9d
fffff880`03385360 fffff800`0333419f : fffff980`0c220dc0 fffff880`06751400 fffffa80`090d3400 00000000`00000000 : nt!IopfCompleteRequest+0x341
fffff880`03385450 fffff800`02e7a876 : fffff880`00000013 fffff880`03385578 fffff980`0c220f20 fffffa80`090d3460 : nt!IovCompleteRequest+0x19f
fffff880`03385520 fffff880`06747a0f : 00000000`00000000 fffffa80`090d3460 00000000`00000001 00000000`00000017 : nt!IopInvalidDeviceRequest+0x16
fffff880`03385550 fffff880`067477fb : 00000000`00000000 fffffa80`090d3460 fffff980`0c220dc0 fffff880`03385600 : HIDCLASS!HidpIrpMajorDefault+0x8b
fffff880`03385590 fffff800`0333ac16 : fffff980`00000002 fffff980`0c220dc0 00000000`00000002 fffff800`0333637e : HIDCLASS!HidpMajorHandler+0xeb
fffff880`03385600 fffff800`03339c42 : fffff980`0c220f68 00000000`00000002 fffffa80`090d4190 fffffa80`08f39e70 : nt!IovCallDriver+0x566
fffff880`03385660 fffff800`0333ac16 : fffff980`0c220dc0 00000000`00000002 fffffa80`090d4040 00000000`00000000 : nt!ViFilterDispatchGeneric+0x62
fffff880`03385690 fffff800`03339d58 : fffff980`0c220dc0 fffffa80`090d4040 00000000`00000000 fffffa80`090df180 : nt!IovCallDriver+0x566
fffff880`033856f0 fffff800`03339e42 : fffffa80`090deae0 fffffa80`055b96b0 fffffa80`090deae0 00000000`00000017 : nt!VfIrpSendSynchronousIrp+0xe8
fffff880`03385760 fffff800`03326faf : fffffa80`08ef7d90 00000000`000007ff fffff800`02fce5b8 fffff800`0322a899 : nt!VfWmiTestStartedPdoStack+0x72
fffff880`03385800 fffff800`02f419d2 : fffffa80`08ef7d90 00000000`00000000 00000000`00000000 00000000`00000000 : nt!VfMajorTestStartedPdoStack+0x5f
fffff880`03385830 fffff800`0327ee5c : fffffa80`08ef7d90 fffffa80`055b96b0 00000000`00000001 00000000`00000000 : nt!PpvUtilTestStartedPdoStack+0x12
fffff880`03385860 fffff800`03280a54 : fffffa80`08ef7d90 fffffa80`08ef7d90 fffffa80`055b96b0 00000000`00000001 : nt!PipProcessStartPhase3+0x55c
fffff880`03385950 fffff800`03281018 : fffff800`03091500 00000000`00000000 00000000`00000010 fffff800`03280f80 : nt!PipProcessDevNodeTree+0x264
fffff880`03385bc0 fffff800`02f918e7 : 00000001`00000003 00000000`00000000 00000000`00000001 00000000`00000000 : nt!PiProcessReenumeration+0x98
fffff880`03385c10 fffff800`02e9f001 : fffff800`02f915c0 fffff800`03035201 fffffa80`05546000 23402340`b964b964 : nt!PnpDeviceActionWorker+0x327
fffff880`03385cb0 fffff800`0312ffee : 295e295e`655a655a fffffa80`05546040 00000000`00000080 fffffa80`05518990 : nt!ExpWorkerThread+0x111
fffff880`03385d40 fffff800`02e865e6 : fffff880`0316a180 fffffa80`05546040 fffff880`031750c0 15121512`2bdb2bdb : nt!PspSystemThreadStartup+0x5a
fffff880`03385d80 00000000`00000000 : fffff880`03386000 fffff880`03380000 fffff880`03384cd0 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

SYMBOL_NAME:  HIDCLASS!HidpMajorHandler+0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: HIDCLASS

IMAGE_NAME:  HIDCLASS.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7a665

FAILURE_BUCKET_ID:  X64_0xc9_23b_HIDCLASS!HidpMajorHandler+0

BUCKET_ID:  X64_0xc9_23b_HIDCLASS!HidpMajorHandler+0

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

Loading Dump File [E:\BSODDmpFiles\Nick05\Windows_NT6_BSOD_jcgriff2\012712-28438-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\Users\Mike\Documents*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.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e09000 PsLoadedModuleList = 0xfffff800`0304e670
Debug session time: Fri Jan 27 15:26:42.255 2012 (GMT-7)
System Uptime: 0 days 4:53:32.270
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9C, {0, fffff88002f6cc70, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt!KxMcheckAbort+6c )

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

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

MACHINE_CHECK_EXCEPTION (9c)
A fatal Machine Check Exception has occurred.
KeBugCheckEx parameters;
    x86 Processors
        If the processor has ONLY MCE feature available (For example Intel
        Pentium), the parameters are:
        1 - Low  32 bits of P5_MC_TYPE MSR
        2 - Address of MCA_EXCEPTION structure
        3 - High 32 bits of P5_MC_ADDR MSR
        4 - Low  32 bits of P5_MC_ADDR MSR
        If the processor also has MCA feature available (For example Intel
        Pentium Pro), the parameters are:
        1 - Bank number
        2 - Address of MCA_EXCEPTION structure
        3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
        4 - Low  32 bits of MCi_STATUS MSR for the MCA bank that had the error
    IA64 Processors
        1 - Bugcheck Type
            1 - MCA_ASSERT
            2 - MCA_GET_STATEINFO
                SAL returned an error for SAL_GET_STATEINFO while processing MCA.
            3 - MCA_CLEAR_STATEINFO
                SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA.
            4 - MCA_FATAL
                FW reported a fatal MCA.
            5 - MCA_NONFATAL
                SAL reported a recoverable MCA and we don't support currently
                support recovery or SAL generated an MCA and then couldn't
                produce an error record.
            0xB - INIT_ASSERT
            0xC - INIT_GET_STATEINFO
                  SAL returned an error for SAL_GET_STATEINFO while processing INIT event.
            0xD - INIT_CLEAR_STATEINFO
                  SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event.
            0xE - INIT_FATAL
                  Not used.
        2 - Address of log
        3 - Size of log
        4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO
    AMD64 Processors
        1 - Bank number
        2 - Address of MCA_EXCEPTION structure
        3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
        4 - Low  32 bits of MCi_STATUS MSR for the MCA bank that had the error
Arguments:
Arg1: 0000000000000000
Arg2: fffff88002f6cc70
Arg3: 0000000000000000
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x9C_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  f

LAST_CONTROL_TRANSFER:  from fffff80003404818 to fffff80002e85c40

STACK_TEXT:  
fffff880`02f6cc38 fffff800`03404818 : 00000000`0000009c 00000000`00000000 fffff880`02f6cc70 00000000`00000000 : nt!KeBugCheckEx
fffff880`02f6cc40 fffff800`03403f57 : 00000000`00000008 00000000`00000000 00000000`00000008 00000000`00000000 : hal!HalpMcaReportError+0x164
fffff880`02f6cd90 fffff800`033f7e88 : 00000000`00000000 fffff880`02f64180 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x9f
fffff880`02f6cdc0 fffff800`02e8452c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`02f6cdf0 fffff800`02e84393 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`02f6cf30 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KxMcheckAbort+6c
fffff800`02e8452c 488d8c2400010000 lea     rcx,[rsp+100h]

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nt!KxMcheckAbort+6c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0x9C_GenuineIntel_nt!KxMcheckAbort+6c

BUCKET_ID:  X64_0x9C_GenuineIntel_nt!KxMcheckAbort+6c

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

HIDCLASS.SYS was caught misbehaving by the IO manager.
Similar to STOP0x124, a hardware error.

I would like to keep these in mind, but first narrow down the graphics card issue. We do not want to try to do too many steps at once and rock the boat.