Constant BSOD from 3d gaming, ntoskrnl+7cc40

Possible out of date drivers:

Code:

iirsp	fffff880`01558000	fffff880`01569000	Tue Dec 13 14:47:54 2005 (439f418a)	00019fb9		iirsp.sys
nfrd960	fffff880`016cf000	fffff880`016df000	Tue Jun 06 15:11:48 2006 (4485ef94)	0000ffcb		nfrd960.sys
adpu320	fffff880`01200000	fffff880`0122f000	Tue Feb 27 17:04:15 2007 (45e4c6ff)	0003588d		adpu320.sys
adpahci	fffff880`01397000	fffff880`013ed000	Tue May 01 11:30:09 2007 (46377921)	00058e0f		adpahci.sys
arc	fffff880`0149d000	fffff880`014b6000	Thu May 24 15:27:55 2007 (4656035b)	00017fb4		arc.sys
SiSRaid2	fffff880`019dd000	fffff880`019eb000	Wed Sep 24 12:28:20 2008 (48da86c4)	00011d5d		SiSRaid2.sys
sisraid4	fffff880`01800000	fffff880`01818000	Wed Oct 01 15:56:04 2008 (48e3f1f4)	0001ec6b		sisraid4.sys
adp94xx	fffff880`0131c000	fffff880`01397000	Fri Dec 05 16:54:42 2008 (4939bf42)	0007c740		adp94xx.sys
lsi_fc	fffff880`01569000	fffff880`01588000	Tue Dec 09 15:46:09 2008 (493ef531)	0001dc09		lsi_fc.sys
arcsas	fffff880`014b6000	fffff880`014d1000	Wed Jan 14 12:27:37 2009 (496e3ca9)	0001f176		arcsas.sys
ql2300	fffff880`01839000	fffff880`019dd000	Thu Jan 22 16:05:06 2009 (4978fba2)	0017acdb		ql2300.sys
vsmraid	fffff880`01769000	fffff880`01793000	Fri Jan 30 18:18:57 2009 (4983a701)	00028def		vsmraid.sys
elxstor	fffff880`014d1000	fffff880`01558000	Tue Feb 03 15:52:11 2009 (4988ca9b)	0008214f		elxstor.sys
stexstor	fffff880`01818000	fffff880`01822000	Tue Feb 17 16:03:36 2009 (499b4248)	0000b026		stexstor.sys
hamachi	fffff880`047f5000	fffff880`04800000	Thu Feb 19 03:36:41 2009 (499d3639)	0000a5d7		hamachi.sys
amdsbs	fffff880`0144b000	fffff880`01492000	Fri Mar 20 12:36:03 2009 (49c3e213)	0003938a		amdsbs.sys
lsi_scsi	fffff880`0159b000	fffff880`015ba000	Thu Apr 16 16:13:50 2009 (49e7ad9e)	0002a7b5		lsi_scsi.sys
HpqKbFiltr	fffff880`04a7f000	fffff880`04a8b000	Wed Apr 29 07:48:30 2009 (49f85aae)	00006ec8		HpqKbFiltr.sys
AtiPcie	fffff880`02050000	fffff880`02058000	Tue May 05 09:00:22 2009 (4a005486)	000134c7		AtiPcie.sys
Apfiltr	fffff880`04400000	fffff880`0443f000	Tue May 12 03:38:59 2009 (4a0943b3)	0003ca71		Apfiltr.sys
GEARAspiWDM	fffff880`04a46000	fffff880`04a53000	Mon May 18 06:17:04 2009 (4a1151c0)	000159b4		GEARAspiWDM.sys
lsi_sas	fffff880`01033000	fffff880`01050000	Mon May 18 18:20:23 2009 (4a11fb47)	000230a6		lsi_sas.sys
lsi_sas2	fffff880`01588000	fffff880`0159b000	Mon May 18 18:31:48 2009 (4a11fdf4)	0002002e		lsi_sas2.sys
megasas	fffff880`015ba000	fffff880`015c6000	Mon May 18 19:09:46 2009 (4a1206da)	000169a1		megasas.sys
ql40xx	fffff880`0170a000	fffff880`01769000	Mon May 18 19:18:11 2009 (4a1208d3)	00029201		ql40xx.sys
MegaSR	fffff880`0162b000	fffff880`016cf000	Mon May 18 19:25:54 2009 (4a120aa2)	00052e51		MegaSR.sys
Rt64win7	fffff880`04a0d000	fffff880`04a46000	Fri May 22 08:52:30 2009 (4a16bc2e)	00041606		Rt64win7.sys
enecir	fffff880`045d9000	fffff880`045f6000	Sun Jun 28 20:17:30 2009 (4a48243a)	00019675		enecir.sys

iirsp.sys
nfrd960.sys
adpu320.sys
adpahci.sys
arc.sys
SiSRaid2.sys
sisraid4.sys
adp94xx.sys
lsi_fc.sys
arcsas.sys
ql2300.sys
vsmraid.sys
elxstor.sys
stexstor.sys
hamachi.sys
amdsbs.sys
lsi_scsi.sys
HpqKbFiltr.sys
AtiPcie.sys
Apfiltr.sys
GEARAspiWDM.sys
lsi_sas.sys
lsi_sas2.sys
megasas.sys
ql40xx.sys
MegaSR.sys
Rt64win7.sys
enecir.sys

Code:

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


Loading Dump File [D:\Kingston\BSODDmpFiles\Vimicry\Windows7_Vista_jcgriff2\030712-31340-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03257000 PsLoadedModuleList = 0xfffff800`0349c670
Debug session time: Wed Mar  7 01:13:47.905 2012 (UTC - 7:00)
System Uptime: 0 days 1:45:26.590
Loading Kernel Symbols
...............................................................
................................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {1, 2, 8, 1}

Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000001, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: 0000000000000001, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003506100
 0000000000000001 

CURRENT_IRQL:  2

FAULTING_IP: 
+3332333431616164
00000000`00000001 ??              ???

PROCESS_NAME:  javaw.exe

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

TRAP_FRAME:  fffff880087497e0 -- (.trap 0xfffff880087497e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000007ffffeca000 rbx=0000000000000000 rcx=00000000c0000102
rdx=00000000000007ff rsi=0000000000000000 rdi=0000000000000000
rip=0000000000000001 rsp=fffff88008749970 rbp=fffff880058bcc01
 r8=fffffa800653f0e8  r9=0000000000000000 r10=fffffffffffffffe
r11=00000000002f5b00 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
00000000`00000001 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800032d31e9 to fffff800032d3c40

FAILED_INSTRUCTION_ADDRESS: 
+3332333431616164
00000000`00000001 ??              ???

STACK_TEXT:  
fffff880`08749698 fffff800`032d31e9 : 00000000`0000000a 00000000`00000001 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
fffff880`087496a0 fffff800`032d1e60 : fffff880`00000001 fffff880`0539f704 fffff880`087499c0 fffff800`03449e80 : nt!KiBugCheckDispatch+0x69
fffff880`087497e0 00000000`00000001 : fffff880`00000001 00000000`00000000 00000000`00000000 fffffa80`056059b0 : nt!KiPageFault+0x260
fffff880`08749970 fffff880`00000001 : 00000000`00000000 00000000`00000000 fffffa80`056059b0 fffff880`08749a20 : 0x1
fffff880`08749978 00000000`00000000 : 00000000`00000000 fffffa80`056059b0 fffff880`08749a20 fffff880`044ed400 : 0xfffff880`00000001


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiPageFault+260
fffff800`032d1e60 440f20c0        mov     rax,cr8

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiPageFault+260

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_nt!KiPageFault+260

BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_nt!KiPageFault+260

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

Loading Dump File [D:\Kingston\BSODDmpFiles\Vimicry\Windows7_Vista_jcgriff2\030612-21028-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0301e000 PsLoadedModuleList = 0xfffff800`03263670
Debug session time: Tue Mar  6 14:40:10.385 2012 (UTC - 7:00)
System Uptime: 0 days 12:51:51.071
Loading Kernel Symbols
...............................................................
................................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
...................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffffffffffffff8, 2, 0, fffff800030a6b2c}

Probably caused by : ntkrnlmp.exe ( nt!KiInsertTimerTable+1cc )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffffffffffffff8, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800030a6b2c, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032cd100
 fffffffffffffff8 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiInsertTimerTable+1cc
fffff800`030a6b2c 4c3b78f8        cmp     r15,qword ptr [rax-8]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  LolClient.exe

TRAP_FRAME:  fffff88007cd7890 -- (.trap 0xfffff88007cd7890)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa8004b01080
rdx=fffffa8003cd65f0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800030a6b2c rsp=fffff88007cd7a20 rbp=fffffa8006613890
 r8=ffffffffffffffff  r9=000000000000003f r10=fffff80003210e80
r11=fffff80003210e00 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!KiInsertTimerTable+0x1cc:
fffff800`030a6b2c 4c3b78f8        cmp     r15,qword ptr [rax-8] ds:ffffffff`fffffff8=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000309a1e9 to fffff8000309ac40

STACK_TEXT:  
fffff880`07cd7748 fffff800`0309a1e9 : 00000000`0000000a ffffffff`fffffff8 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`07cd7750 fffff800`03098e60 : 00000000`00000000 fffff800`0309d8a4 00000000`00000000 fffffa80`04be23a0 : nt!KiBugCheckDispatch+0x69
fffff880`07cd7890 fffff800`030a6b2c : 00000000`00000000 00000000`00000002 fffffa80`04a15720 fffff800`030a0fda : nt!KiPageFault+0x260
fffff880`07cd7a20 fffff800`030a0092 : fffffa80`04be22e0 fffffa80`04be22e0 00000000`00000000 fffffa80`00000000 : nt!KiInsertTimerTable+0x1cc
fffff880`07cd7a80 fffff800`030a274f : 00000000`00000170 fffff800`030a0b6c 00000000`0000003f 00000000`03a5fd20 : nt!KiCommitThreadWait+0x332
fffff880`07cd7b10 fffff800`0339144e : 00000000`02afd000 fffff880`00000006 00000000`00000001 fffff800`03385000 : nt!KeWaitForSingleObject+0x19f
fffff880`07cd7bb0 fffff800`03099ed3 : fffffa80`04be22e0 00000000`00000170 fffff880`07cd7bf8 fffffa80`03981c80 : nt!NtWaitForSingleObject+0xde
fffff880`07cd7c20 00000000`756c2e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`03a5ecb8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x756c2e09


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiInsertTimerTable+1cc
fffff800`030a6b2c 4c3b78f8        cmp     r15,qword ptr [rax-8]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KiInsertTimerTable+1cc

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0xA_nt!KiInsertTimerTable+1cc

BUCKET_ID:  X64_0xA_nt!KiInsertTimerTable+1cc

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

Loading Dump File [D:\Kingston\BSODDmpFiles\Vimicry\Windows7_Vista_jcgriff2\030412-23852-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e4a000 PsLoadedModuleList = 0xfffff800`0308f670
Debug session time: Sun Mar  4 23:02:20.297 2012 (UTC - 7:00)
System Uptime: 0 days 2:04:45.983
Loading Kernel Symbols
...............................................................
................................................................
................................................................
............
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff87f93544ab5, 1, fffff80002eee6c0, 5}


Could not read faulting driver name
Probably caused by : memory_corruption

Followup: memory_corruption
---------

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

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


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030f9100
 fffff87f93544ab5 

FAULTING_IP: 
nt!MiIssueHardFault+27c
fffff800`02eee6c0 088d55204d8b    or      byte ptr [rbp-74B2DFABh],cl

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x50

PROCESS_NAME:  hl2.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88008072860 -- (.trap 0xfffff88008072860)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000103 rbx=0000000000000000 rcx=f88001a5c16b0000
rdx=fffffa8004cf6a71 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002eee6c0 rsp=fffff880080729f0 rbp=fffff88008072a60
 r8=fffffa8004cf6a70  r9=fffff88008072a78 r10=fffffa800340ce00
r11=fffff880080728d0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!MiIssueHardFault+0x27c:
fffff800`02eee6c0 088d55204d8b    or      byte ptr [rbp-74B2DFABh],cl ss:fffff87f`93544ab5=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e713bf to fffff80002ec6c40

STACK_TEXT:  
fffff880`080726f8 fffff800`02e713bf : 00000000`00000050 fffff87f`93544ab5 00000000`00000001 fffff880`08072860 : nt!KeBugCheckEx
fffff880`08072700 fffff800`02ec4d6e : 00000000`00000001 fffff87f`93544ab5 fffffa80`055fae00 fffffa80`05da21c0 : nt! ?? ::FNODOBFM::`string'+0x44791
fffff880`08072860 fffff800`02eee6c0 : 00000000`00000001 00000000`00000001 fffffa80`05da2170 fffffa80`05da2170 : nt!KiPageFault+0x16e
fffff880`080729f0 fffff800`02ed502a : 00000000`00000000 00000000`00000000 ffffffff`ffffffff fffffa80`00000000 : nt!MiIssueHardFault+0x27c
fffff880`08072ac0 fffff800`02ec4d6e : 00000000`00000008 00000000`6af3428a fffffa80`052ace01 00000000`13b5d878 : nt!MmAccessFault+0x146a
fffff880`08072c20 00000000`6af3428a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`203dfee0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x6af3428a


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff80002eee6c0 - nt!MiIssueHardFault+27c
	[ 48:08 ]
1 error : !nt (fffff80002eee6c0)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  ONE_BIT

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

Followup: memory_corruption
---------

Loading Dump File [D:\Kingston\BSODDmpFiles\Vimicry\Windows7_Vista_jcgriff2\030412-24008-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e5a000 PsLoadedModuleList = 0xfffff800`0309f670
Debug session time: Sun Mar  4 20:17:32.381 2012 (UTC - 7:00)
System Uptime: 0 days 0:11:39.067
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Probably caused by : amdppm.sys ( amdppm!C1Halt+2 )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+3332333431616164
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR:  0x1E_0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

EXCEPTION_RECORD:  fffff80000b9ca28 -- (.exr 0xfffff80000b9ca28)
ExceptionAddress: fffff80002e414f0 (hal!HalpKInterruptHeap+0x00000000000004f0)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000001
   Parameter[1]: 0000000000000048
Attempt to write to address 0000000000000048

TRAP_FRAME:  fffff80000b9cad0 -- (.trap 0xfffff80000b9cad0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000001b59b rbx=0000000000000000 rcx=fffffa8004c888b0
rdx=fffffa8004c917e8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002e414f0 rsp=fffff80000b9cc68 rbp=0000000000000000
 r8=0000000000000000  r9=000000003f31219a r10=0000000000019897
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di pl zr na po nc
hal!HalpKInterruptHeap+0x4f0:
fffff800`02e414f0 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ece5fe to fffff80002ed6c10

STACK_TEXT:  
fffff800`00b9bb08 fffff800`02ece5fe : fffffa80`03938801 00000000`00000002 fffff800`00b9c280 fffff800`02f02830 : nt!KeBugCheck
fffff800`00b9bb10 fffff800`02f024fd : fffff800`030e0488 fffff800`0301ec8c fffff800`02e5a000 fffff800`00b9ca28 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`00b9bb40 fffff800`02f012d5 : fffff800`030210fc fffff800`00b9bbb8 fffff800`00b9ca28 fffff800`02e5a000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`00b9bb70 fffff800`02f12361 : fffff800`00b9ca28 fffff800`00b9c280 fffff800`00000000 00000000`00000001 : nt!RtlDispatchException+0x415
fffff800`00b9c250 fffff800`02ed62c2 : fffff800`00b9ca28 00000000`00000000 fffff800`00b9cad0 fffff800`0304ce80 : nt!KiDispatchException+0x135
fffff800`00b9c8f0 fffff800`02ed4e3a : 00000000`00000001 00000000`00000048 fffff800`02e41400 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff800`00b9cad0 fffff800`02e414f0 : fffff880`044d17f2 00000000`00000010 00000000`00000246 fffff800`00b9cc98 : nt!KiPageFault+0x23a
fffff800`00b9cc68 fffff880`044d17f2 : 00000000`00000010 00000000`00000246 fffff800`00b9cc98 00000000`00000018 : hal!HalpKInterruptHeap+0x4f0
fffff800`00b9cc70 00000000`00000010 : 00000000`00000246 fffff800`00b9cc98 00000000`00000018 fffffa80`035f0b20 : amdppm!C1Halt+0x2
fffff800`00b9cc78 00000000`00000246 : fffff800`00b9cc98 00000000`00000018 fffffa80`035f0b20 fffff800`02ee04a9 : 0x10
fffff800`00b9cc80 fffff800`00b9cc98 : 00000000`00000018 fffffa80`035f0b20 fffff800`02ee04a9 00000000`00223022 : 0x246
fffff800`00b9cc88 00000000`00000018 : fffffa80`035f0b20 fffff800`02ee04a9 00000000`00223022 fffffa80`04c92738 : 0xfffff800`00b9cc98
fffff800`00b9cc90 fffffa80`035f0b20 : fffff800`02ee04a9 00000000`00223022 fffffa80`04c92738 fffff800`0305acc0 : 0x18
fffff800`00b9cc98 fffff800`02ee04a9 : 00000000`00223022 fffffa80`04c92738 fffff800`0305acc0 00000000`00000001 : 0xfffffa80`035f0b20
fffff800`00b9cca0 fffff800`02ece97c : fffff800`0304ce80 fffff800`00000000 00000000`00000000 fffff880`05009588 : nt!PoIdle+0x52a
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x6c


STACK_COMMAND:  kb

FOLLOWUP_IP: 
amdppm!C1Halt+2
fffff880`044d17f2 c3              ret

SYMBOL_STACK_INDEX:  8

SYMBOL_NAME:  amdppm!C1Halt+2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: amdppm

IMAGE_NAME:  amdppm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc0fd

FAILURE_BUCKET_ID:  X64_0x1E_0_amdppm!C1Halt+2

BUCKET_ID:  X64_0x1E_0_amdppm!C1Halt+2

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

1. Possible cause is Drivers...
2. Possible causes are Memory problems... Corrupted hard disk file system... Corrupted System Files... BIOS... Lack of Windows updates... Antivirus Software... Backup... Hardware...
3. Possible causes are Memory problems... Graphics card memory problems... BIOS... Corrupted hard disk file system... Corrupted System Files... Missing Windows Updates... Drivers...
4. Possible causes are Memory problems... Viruses... Corrupted hard disk file system... Corrupted System Files... Lack of Windows updates... Drivers...
   Thanks to JMH for helping with my understanding of this crash.

Thanks to Dave76 for help understanding possible causes.



We will start with the common problems first (see bold possible causes). Do the following steps and test by doing your normal routine after each step to see if stability increases (the memory tests you can run concurrently as they will not increase stability unless you are forced to move modules around). Post back your results after each step, and if you get a blue screen crash, upload the files again and await further instructions after we are able to analyze the crash.

If you can do your normal routine for a few weeks without a crash, and your crashes are usually more frequent than that, then the problem is likely solved.

• If you are overclocking any hardware, please stop.
  
  
• Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log
  
  
• Use HD Diagnostic to determine your hard disk manufacturer and run the diagnostics provided by that manufacturer. You can find the diagnostic links within that guide, as well. If you have a Samsung drive, use Seagate SeaTools to test the drive with both the short and long tests.
  
  
• 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. 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 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.
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
  If you swap any memory components, follow these steps for ESD safety:
  
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
  
  Once these steps have been followed, it is safe to remove and replace components within your computer.

Thanks for replying!
So far, I've decided I wanted to start clean, I reformatted my computer to factory settings. The BSOD was fine for 3 days until the BSOD's came back again. I have ran the disk check with no errors. Also did the HD Diagnostic but nothing seemed to change. I also did the Video Memory Stress Test with no problems after 7 passes. Finally, after doing the hardware stress test, I received a BSOD. It was only 2-3 minutes in, the temperature of my CPU gradually rose and I crashed at 92 degrees celsius.

other notes: I installed the latest video drivers but nothing else.
The Furmark test didn't launch, so that hasn't been done yet.
I have yet to do the memtest86+.

Lastly, here are my dmp files as requested.
HOPE THIS WILL END WELL. :)

Are you using

Code:

tuneuputilitiesapp64.exe	c:\program files (x86)\tuneup utilities 2012\tuneuputilitiesapp64.exe	2628	8	200	1380	3/14/2012 8:51 PM	12.0.3010.5	1.29 MB (1,352,512 bytes)	2/9/2012 5:13 AM
tuneuputilitiesservice64.exe	c:\program files (x86)\tuneup utilities 2012\tuneuputilitiesservice64.exe	2100	8	200	1380	3/14/2012 8:51 PM	12.0.3010.5	2.04 MB (2,143,552 bytes)	2/9/2012 5:13 AM

to "tune up" Windows 7?


Antivirus software? Recommend either

http://windows.microsoft.com/en-US/w...ity-essentials

or the

Good and Free system security combination.

Run a full scan once the security software is installed and updated.


Possible out of date drivers

Code:

iirsp	fffff880`01581000	fffff880`01592000	Tue Dec 13 14:47:54 2005 (439f418a)	00019fb9		iirsp.sys
nfrd960	fffff880`014a4000	fffff880`014b4000	Tue Jun 06 15:11:48 2006 (4485ef94)	0000ffcb		nfrd960.sys
adpu320	fffff880`013ac000	fffff880`013db000	Tue Feb 27 17:04:15 2007 (45e4c6ff)	0003588d		adpu320.sys
adpahci	fffff880`01356000	fffff880`013ac000	Tue May 01 11:30:09 2007 (46377921)	00058e0f		adpahci.sys
arc	fffff880`0101d000	fffff880`01036000	Thu May 24 15:27:55 2007 (4656035b)	00017fb4		arc.sys
SiSRaid2	fffff880`018a5000	fffff880`018b3000	Wed Sep 24 12:28:20 2008 (48da86c4)	00011d5d		SiSRaid2.sys
sisraid4	fffff880`018b3000	fffff880`018cb000	Wed Oct 01 15:56:04 2008 (48e3f1f4)	0001ec6b		sisraid4.sys
adp94xx	fffff880`012db000	fffff880`01356000	Fri Dec 05 16:54:42 2008 (4939bf42)	0007c740		adp94xx.sys
lsi_fc	fffff880`01592000	fffff880`015b1000	Tue Dec 09 15:46:09 2008 (493ef531)	0001dc09		lsi_fc.sys
arcsas	fffff880`00c40000	fffff880`00c5b000	Wed Jan 14 12:27:37 2009 (496e3ca9)	0001f176		arcsas.sys
ql2300	fffff880`01641000	fffff880`017e5000	Thu Jan 22 16:05:06 2009 (4978fba2)	0017acdb		ql2300.sys
vsmraid	fffff880`018d5000	fffff880`018ff000	Fri Jan 30 18:18:57 2009 (4983a701)	00028def		vsmraid.sys
elxstor	fffff880`014fa000	fffff880`01581000	Tue Feb 03 15:52:11 2009 (4988ca9b)	0008214f		elxstor.sys
stexstor	fffff880`018cb000	fffff880`018d5000	Tue Feb 17 16:03:36 2009 (499b4248)	0000b026		stexstor.sys
hamachi	fffff880`0493e000	fffff880`04949000	Thu Feb 19 03:36:41 2009 (499d3639)	0000a5d7		hamachi.sys
amdsbs	fffff880`01200000	fffff880`01247000	Fri Mar 20 12:36:03 2009 (49c3e213)	0003938a		amdsbs.sys
usbfilter	fffff880`04451000	fffff880`0445d000	Fri Apr 03 05:39:51 2009 (49d5f587)	000128e6		usbfilter.sys
lsi_scsi	fffff880`015c4000	fffff880`015e3000	Thu Apr 16 16:13:50 2009 (49e7ad9e)	0002a7b5		lsi_scsi.sys
HpqKbFiltr	fffff880`0446e000	fffff880`0447a000	Wed Apr 29 07:48:30 2009 (49f85aae)	00006ec8		HpqKbFiltr.sys
AtiPcie	fffff880`01c50000	fffff880`01c58000	Tue May 05 09:00:22 2009 (4a005486)	000134c7		AtiPcie.sys
Apfiltr	fffff880`04274000	fffff880`042b3000	Tue May 12 03:38:59 2009 (4a0943b3)	0003ca71		Apfiltr.sys
HpSAMD	fffff880`012c4000	fffff880`012db000	Mon May 18 17:43:49 2009 (4a11f2b5)	0001819b		HpSAMD.sys
lsi_sas	fffff880`01000000	fffff880`0101d000	Mon May 18 18:20:23 2009 (4a11fb47)	000230a6		lsi_sas.sys
lsi_sas2	fffff880`015b1000	fffff880`015c4000	Mon May 18 18:31:48 2009 (4a11fdf4)	0002002e		lsi_sas2.sys
megasas	fffff880`015e3000	fffff880`015ef000	Mon May 18 19:09:46 2009 (4a1206da)	000169a1		megasas.sys
ql40xx	fffff880`01846000	fffff880`018a5000	Mon May 18 19:18:11 2009 (4a1208d3)	00029201		ql40xx.sys
MegaSR	fffff880`01400000	fffff880`014a4000	Mon May 18 19:25:54 2009 (4a120aa2)	00052e51		MegaSR.sys
enecir	fffff880`043da000	fffff880`043f7000	Wed May 20 00:08:57 2009 (4a139e79)	000212b0		enecir.sys
Rt64win7	fffff880`0440d000	fffff880`04446000	Fri May 22 08:52:30 2009 (4a16bc2e)	00041606		Rt64win7.sys

Code:

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


Loading Dump File [D:\Kingston\BSODDmpFiles\Vimicry\Windows_NT6_BSOD_jcgriff2\031412-37752-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 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16917.amd64fre.win7_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`02c50000 PsLoadedModuleList = 0xfffff800`02e8ce70
Debug session time: Wed Mar 14 21:48:26.108 2012 (UTC - 6:00)
System Uptime: 0 days 0:09:01.183
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.........
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000096, fffff80002cc66f3, fffff8800647e648, fffff8800647deb0}

Unable to load image \SystemRoot\system32\DRIVERS\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
Probably caused by : atikmdag.sys ( atikmdag+6146a )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000096, The exception code that was not handled
Arg2: fffff80002cc66f3, The address that the exception occurred at
Arg3: fffff8800647e648, Exception Record Address
Arg4: fffff8800647deb0, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000096 - {EXCEPTION}  Privileged instruction.

FAULTING_IP: 
nt!SwapContext_PatchXSave+70
fffff800`02cc66f3 0f00d1          lldt    cx

EXCEPTION_RECORD:  fffff8800647e648 -- (.exr 0xfffff8800647e648)
ExceptionAddress: fffff80002cc66f3 (nt!SwapContext_PatchXSave+0x0000000000000070)
   ExceptionCode: c0000096
  ExceptionFlags: 00000000
NumberParameters: 0

CONTEXT:  fffff8800647deb0 -- (.cxr 0xfffff8800647deb0)
rax=0000000000000001 rbx=fffff880009e8180 rcx=0000000000000070
rdx=0000000000000000 rsi=fffffa8005246b60 rdi=fffffa80038adb60
rip=fffff80002cc66f3 rsp=fffff8800647e880 rbp=fffff88009d1cdb0
 r8=0000000000000000  r9=0000000000000001 r10=fffff80002c50000
r11=0000000000000000 r12=0000000000041eb0 r13=0000000000066979
r14=fffffa80033f7700 r15=000000000000013c
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
nt!SwapContext_PatchXSave+0x70:
fffff800`02cc66f3 0f00d1          lldt    cx
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

CURRENT_IRQL:  2

ERROR_CODE: (NTSTATUS) 0xc0000096 - {EXCEPTION}  Privileged instruction.

BUGCHECK_STR:  0x7E

DEFAULT_BUCKET_ID:  STATUS_PRIVILEGED_INSTRUCTION

LAST_CONTROL_TRANSFER:  from fffff80002cc635a to fffff80002cc66f3

STACK_TEXT:  
fffff880`0647e880 fffff800`02cc635a : 00000000`00000000 ffffffff`fffffffd fffff880`009e8180 fffff800`02cc6722 : nt!SwapContext_PatchXSave+0x70
fffff880`0647e8c0 fffff800`02cc75c2 : fffffa80`05246b60 fffffa80`05246b60 fffffa80`0549a000 fffff880`00000001 : nt!KiSwapContext+0x7a
fffff880`0647ea00 fffff800`02cc9a8f : 00000000`00000005 fffff880`05126c84 fffffa80`00000083 00000001`3d98818f : nt!KiCommitThreadWait+0x1d2
fffff880`0647ea90 fffff880`0508a46a : fffffa80`0549ab00 00000000`00000000 fffffa80`0549a000 fffff880`0512c200 : nt!KeWaitForSingleObject+0x19f
fffff880`0647eb30 fffffa80`0549ab00 : 00000000`00000000 fffffa80`0549a000 fffff880`0512c200 fffff880`009e8180 : atikmdag+0x6146a
fffff880`0647eb38 00000000`00000000 : fffffa80`0549a000 fffff880`0512c200 fffff880`009e8180 00000000`00000200 : 0xfffffa80`0549ab00


FOLLOWUP_IP: 
atikmdag+6146a
fffff880`0508a46a ??              ???

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  atikmdag+6146a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME:  atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4f3b1dc8

STACK_COMMAND:  .cxr 0xfffff8800647deb0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_atikmdag+6146a

BUCKET_ID:  X64_0x7E_atikmdag+6146a

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

Loading Dump File [D:\Kingston\BSODDmpFiles\Vimicry\Windows_NT6_BSOD_jcgriff2\031412-14554-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 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16917.amd64fre.win7_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`02c1e000 PsLoadedModuleList = 0xfffff800`02e5ae70
Debug session time: Wed Mar 14 18:30:08.894 2012 (UTC - 6:00)
System Uptime: 0 days 3:02:09.032
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck FE, {8, 6, 6, fffffa8004cce000}

Unable to load image \SystemRoot\system32\DRIVERS\usbfilter.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for usbfilter.sys
*** ERROR: Module load completed but symbols could not be loaded for usbfilter.sys
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: usbport!_DEVICE_EXTENSION                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: usbhub!_DEVICE_EXTENSION_HUB                  ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: usbhub!_DEVICE_EXTENSION_HUB                  ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: usbhub!_DEVICE_EXTENSION_HUB                  ***
***                                                                   ***
*************************************************************************
Probably caused by : usbfilter.sys ( usbfilter+3c22 )

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

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

BUGCODE_USB_DRIVER (fe)
USB Driver bugcheck, first parameter is USB bugcheck code.
Arguments:
Arg1: 0000000000000008, USBBUGCODE_RESERVED_USBHUB
Arg2: 0000000000000006, USBHUB_TRAP_FATAL_TIMEOUT
Arg3: 0000000000000006, TimeoutCode: Timeout_PCE_Disable_Action - PortData->PortChangeListDone - Timeout trying to set Disable bit
Arg4: fffffa8004cce000, TimeoutContext - PortData

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

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: usbport!_DEVICE_EXTENSION                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: usbhub!_DEVICE_EXTENSION_HUB                  ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: usbhub!_DEVICE_EXTENSION_HUB                  ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: usbhub!_DEVICE_EXTENSION_HUB                  ***
***                                                                   ***
*************************************************************************

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xFE

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff880051427fa to fffff80002c8e540

STACK_TEXT:  
fffff880`08ec7718 fffff880`051427fa : 00000000`000000fe 00000000`00000008 00000000`00000006 00000000`00000006 : nt!KeBugCheckEx
fffff880`08ec7720 fffff880`0514d5bd : fffffa80`04cce000 fffffa80`04cce1d8 fffffa80`04cce000 fffffa80`0485d050 : usbhub!UsbhWaitEventWithTimeoutEx+0x3aa
fffff880`08ec77d0 fffff880`0514cbd8 : 00000000`00000000 fffffa80`50447100 fffffa80`04cce000 00000000`00080000 : usbhub!Usbh_PCE_Disable_Action+0x4f1
fffff880`08ec7830 fffff880`05151f7c : fffffa80`0485d050 00000000`00000001 00000000`00000001 fffffa80`0485d708 : usbhub!UsbhDispatch_PortChangeQueueEventEx+0x110
fffff880`08ec7870 fffff880`0514a744 : fffffa80`0485d050 fffffa80`04cce000 fffffa80`04cce000 00000000`00000000 : usbhub!UsbhPCE_Disable+0xb4
fffff880`08ec78c0 fffff880`05149a3c : 00000000`00000007 00000000`00000003 fffffa80`0485d050 fffffa80`0485d708 : usbhub!UsbhBusPause_Action+0x184
fffff880`08ec7910 fffff880`05149eb6 : fffffa80`0485d1a0 00000000`00000007 fffffa80`0485d050 00000000`00000000 : usbhub!Usbh_BS_BusRun+0x94
fffff880`08ec7950 fffff880`0514a92b : 00000000`00000003 fffffa80`0485d708 fffffa80`0485d050 00000000`00000000 : usbhub!UsbhDispatch_BusEvent+0x20e
fffff880`08ec79a0 fffff880`0515f362 : fffffa80`03de69e8 fffffa80`0520bec0 fffffa80`0520bec0 fffffa80`03de69e8 : usbhub!UsbhSyncBusPause+0x4f
fffff880`08ec79e0 fffff880`0515da92 : fffffa80`0485d050 fffffa80`0485d708 fffffa80`0485d708 00000000`00000004 : usbhub!UsbhFdoSetPowerDx_Action+0x9a
fffff880`08ec7a40 fffff880`0515c70b : fffffa80`03de69e8 fffffa80`0485d1a0 fffffa80`0485d050 fffffa80`03de67b0 : usbhub!UsbhFdoDevicePowerState+0x206
fffff880`08ec7a90 fffff880`0515b9c7 : fffffa80`03de67b0 00000000`00000000 fffffa80`0485d050 fffff800`02d90832 : usbhub!UsbhFdoPower_SetPower+0x93
fffff880`08ec7ad0 fffff880`05142fdf : fffffa80`03de67b0 fffffa80`04517040 fffffa80`0465ee20 fffff880`00dc2f3a : usbhub!UsbhFdoPower+0xaf
fffff880`08ec7b10 fffff800`02d908f2 : fffffa80`03de67b0 00000000`00000000 fffffa80`04517040 fffffa80`03de67b0 : usbhub!UsbhGenDispatch+0x7f
fffff880`08ec7b40 fffff880`04ccac22 : fffffa80`04517040 fffff880`04cc85cb fffffa80`03de67b0 fffff800`02d72e03 : nt!IopPoHandleIrp+0x32
fffff880`08ec7b70 fffffa80`04517040 : fffff880`04cc85cb fffffa80`03de67b0 fffff800`02d72e03 fffffa80`04517190 : usbfilter+0x3c22
fffff880`08ec7b78 fffff880`04cc85cb : fffffa80`03de67b0 fffff800`02d72e03 fffffa80`04517190 fffffa80`03de69e8 : 0xfffffa80`04517040
fffff880`08ec7b80 fffffa80`03de67b0 : fffff800`02d72e03 fffffa80`04517190 fffffa80`03de69e8 fffffa80`04517190 : usbfilter+0x15cb
fffff880`08ec7b88 fffff800`02d72e03 : fffffa80`04517190 fffffa80`03de69e8 fffffa80`04517190 00000000`00000000 : 0xfffffa80`03de67b0
fffff880`08ec7b90 fffff800`02d7387e : fffffa80`04517190 fffffa80`03de69e8 fffff880`00000000 fffffa80`05b34560 : nt!PopDiagTraceDeviceAcquireIrp+0xf3
fffff880`08ec7c60 fffff800`02da92c5 : fffffa80`04517040 fffffa80`03de67b0 00000000`00000001 fffffa80`03de6858 : nt!PoDeviceAcquireIrp+0x3e
fffff880`08ec7c90 fffff800`02f2d726 : ffffffff`fa0a1f00 fffffa80`0562ab60 00000000`00000080 00000000`00000000 : nt!PopIrpWorker+0x3c5
fffff880`08ec7d40 fffff800`02c6cac6 : fffff800`02e07e80 fffffa80`0562ab60 fffffa80`06502b60 00000000`00000246 : nt!PspSystemThreadStartup+0x5a
fffff880`08ec7d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
usbfilter+3c22
fffff880`04ccac22 ??              ???

SYMBOL_STACK_INDEX:  f

SYMBOL_NAME:  usbfilter+3c22

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: usbfilter

IMAGE_NAME:  usbfilter.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  49d5f587

FAILURE_BUCKET_ID:  X64_0xFE_usbfilter+3c22

BUCKET_ID:  X64_0xFE_usbfilter+3c22

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

Loading Dump File [D:\Kingston\BSODDmpFiles\Vimicry\Windows_NT6_BSOD_jcgriff2\031412-17035-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 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`02c0a000 PsLoadedModuleList = 0xfffff800`02e47e70
Debug session time: Wed Mar 14 01:16:45.014 2012 (UTC - 6:00)
System Uptime: 0 days 2:54:19.089
Loading Kernel Symbols
...............................................................
................................................................
................................................................
....
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff96000123f63, fffff880075e60d0, 0}

Probably caused by : win32k.sys ( win32k!TimersProc+73 )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff96000123f63, Address of the instruction which caused the bugcheck
Arg3: fffff880075e60d0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
win32k!TimersProc+73
fffff960`00123f63 8b5348          mov     edx,dword ptr [rbx+48h]

CONTEXT:  fffff880075e60d0 -- (.cxr 0xfffff880075e60d0)
rax=0000000009bc00cd rbx=0000000000001808 rcx=0000000009bc00dd
rdx=0000000000000000 rsi=0000000000000080 rdi=0000000000001820
rip=fffff96000123f63 rsp=fffff880075e6aa0 rbp=0000000000000010
 r8=fffffa800501b5a8  r9=0000000000000000 r10=fffffffffffffffd
r11=00000000002f6b00 r12=0000000000000000 r13=fffff960003442c0
r14=0000000000000002 r15=0000000000000000
iopl=0         nv up ei pl nz na po cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010207
win32k!TimersProc+0x73:
fffff960`00123f63 8b5348          mov     edx,dword ptr [rbx+48h] ds:002b:00000000`00001850=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff96000124a64 to fffff96000123f63

STACK_TEXT:  
fffff880`075e6aa0 fffff960`00124a64 : 00000000`00000000 fffff960`00344a90 00000000`00000004 00000000`00000001 : win32k!TimersProc+0x73
fffff880`075e6af0 fffff960`000b502c : fffffa80`0000003b 00000000`0000000f fffff880`00000001 ffffffff`80000100 : win32k!RawInputThread+0x9b4
fffff880`075e6bc0 fffff960`0013539a : fffffa80`00000002 fffff880`075d2f40 00000000`00000020 00000000`00000000 : win32k!xxxCreateSystemThreads+0x58
fffff880`075e6bf0 fffff800`02c79813 : fffffa80`05089060 00000000`00000004 000007ff`fffd3000 00000000`00000000 : win32k!NtUserCallNoParam+0x36
fffff880`075e6c20 000007fe`fd693d5a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`013bfad8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fd693d5a


FOLLOWUP_IP: 
win32k!TimersProc+73
fffff960`00123f63 8b5348          mov     edx,dword ptr [rbx+48h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  win32k!TimersProc+73

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4f10fe35

STACK_COMMAND:  .cxr 0xfffff880075e60d0 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_win32k!TimersProc+73

BUCKET_ID:  X64_0x3B_win32k!TimersProc+73

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

Loading Dump File [D:\Kingston\BSODDmpFiles\Vimicry\Windows_NT6_BSOD_jcgriff2\031312-22120-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 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`02c1c000 PsLoadedModuleList = 0xfffff800`02e59e70
Debug session time: Tue Mar 13 14:02:31.212 2012 (UTC - 6:00)
System Uptime: 0 days 9:02:04.835
Loading Kernel Symbols
...............................................................
................................................................
................................................................
....
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {0, 2, 1, fffff80000b96080}

Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff80000b96080, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ec40e0
 0000000000000000 

CURRENT_IRQL:  2

FAULTING_IP: 
+3332333431616164
fffff800`00b96080 0000            add     byte ptr [rax],al

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff80000b9cbb0 -- (.trap 0xfffff80000b9cbb0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000001
rdx=0000000000187000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80000b96080 rsp=fffff80000b9cd40 rbp=fffff80000b9cd40
 r8=fffffa80033dc918  r9=0000000000000000 r10=fffffffffffffffe
r11=fffffa800562b168 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
fffff800`00b96080 0000            add     byte ptr [rax],al ds:1881:00000000`00000000=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c8bb29 to fffff80002c8c5c0

STACK_TEXT:  
fffff800`00b9ca68 fffff800`02c8bb29 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff800`00b9ca70 fffff800`02c8a7a0 : 00000000`00000000 fffff800`02e06e80 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`00b9cbb0 fffff800`00b96080 : fffffa80`033dc890 00000000`00000000 00000000`00000000 fffffa80`03ef96e0 : nt!KiPageFault+0x260
fffff800`00b9cd40 fffffa80`033dc890 : 00000000`00000000 00000000`00000000 fffffa80`03ef96e0 fffff800`02e14c40 : 0xfffff800`00b96080
fffff800`00b9cd48 00000000`00000000 : 00000000`00000000 fffffa80`03ef96e0 fffff800`02e14c40 00000000`00000001 : 0xfffffa80`033dc890


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiPageFault+260
fffff800`02c8a7a0 440f20c0        mov     rax,cr8

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiPageFault+260

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aa44

FAILURE_BUCKET_ID:  X64_0xD1_nt!KiPageFault+260

BUCKET_ID:  X64_0xD1_nt!KiPageFault+260

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

1. Caused by your graphics card/graphics card driver(s).
2. Caused by a USB device or the ports themselves.
3. Possible causes are Memory problems... Corrupted hard disk file system... Corrupted System Files... Graphics Driver... Drivers...
4. Possible cause is Drivers...

Thanks to Dave76 for help understanding possible causes.


If you are using Tune Up Utilities to "tune up" Windows 7... 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 Optimize Windows 7.

I would recommend reformatting your computer, clean installing Windows 7, and not using Tune Up Utilities. If you used it prior to the blue screen crashes, this may well be why your computer was running fine for a few days. If you used it after the blue screen crashes started, continue with the next step.


We should try to determine if one of your out of date drivers is conflicting with Windows.

• 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 and in step 3, only select Standard settings. Do not select the other two settings in the red boxes.
  
  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.
  The idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.

Thanks for the fast reply. I've gotten rid of tuneup utilities and installed Microsoft Security Essentials. I've crashed 2 times so far doing the same thing that normally makes me crash. Oddly enough, at times, I don't crash for a 2-3 hours straight. I'll post more when I can.

Security Software

Code:

msmpeng.exe	c:\program files\microsoft security client\antimalware\msmpeng.exe	876	8	200	1380	3/17/2012 4:49 PM	3.0.8402.0	12.48 KB (12,784 bytes)	4/27/2011 5:21 PM
nissrv.exe	c:\program files\microsoft security client\antimalware\nissrv.exe	2788	8	200	1380	3/17/2012 4:49 PM	3.0.8402.0	281.52 KB (288,272 bytes)	4/27/2011 5:21 PM
msseces.exe	c:\program files\microsoft security client\msseces.exe	2712	8	200	1380	3/17/2012 4:49 PM	2.1.1116.0	1.37 MB (1,436,736 bytes)	6/15/2011 2:35 PM

What were the results of your security scan?

Code:

Loading Dump File [D:\Kingston\BSODDmpFiles\Vimicry\Windows_NT6_BSOD_jcgriff2\031612-22448-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 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16917.amd64fre.win7_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`02c5a000 PsLoadedModuleList = 0xfffff800`02e96e70
Debug session time: Sat Mar 17 00:44:59.673 2012 (UTC - 6:00)
System Uptime: 0 days 0:02:53.811
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...........
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck FC, {fffff80002fc095e, a240000002fc0121, fffff880029a5a60, 2}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+41f07 )

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

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

ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc)
An attempt was made to execute non-executable memory.  The guilty driver
is on the stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff80002fc095e, Virtual address for the attempted execute.
Arg2: a240000002fc0121, PTE contents.
Arg3: fffff880029a5a60, (reserved)
Arg4: 0000000000000002, (reserved)

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0xFC

PROCESS_NAME:  LoLLauncher.ex

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880029a5a60 -- (.trap 0xfffff880029a5a60)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002fc095e rsp=fffff880029a5bf0 rbp=fffff880029a5ca0
 r8=fffffa80042e50e8  r9=0000000000000000 r10=fffffffffffffffd
r11=fffffa80053b38f0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
nt!NtDelayExecution+0x59:
fffff800`02fc095e 4883c428        add     rsp,28h
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002d4a1df to fffff80002cca540

STACK_TEXT:  
fffff880`029a58f8 fffff800`02d4a1df : 00000000`000000fc fffff800`02fc095e a2400000`02fc0121 fffff880`029a5a60 : nt!KeBugCheckEx
fffff880`029a5900 fffff800`02cc862e : 00000000`00000008 fffffa80`06351910 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x41f07
fffff880`029a5a60 fffff800`02fc095e : fffffa80`06351910 00000000`7ef83000 00000000`0d19f100 00000000`00000085 : nt!KiPageFault+0x16e
fffff880`029a5bf0 fffff800`02cc9793 : 00000000`746c26f0 fffff880`029a5ca0 ffffffff`ffffd8f0 00000000`7ef83000 : nt!NtDelayExecution+0x59
fffff880`029a5c20 00000000`74a12dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0d19f0f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74a12dd9


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+41f07
fffff800`02d4a1df cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+41f07

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4ec7a284

FAILURE_BUCKET_ID:  X64_0xFC_VRF_nt!_??_::FNODOBFM::_string_+41f07

BUCKET_ID:  X64_0xFC_VRF_nt!_??_::FNODOBFM::_string_+41f07

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

Loading Dump File [D:\Kingston\BSODDmpFiles\Vimicry\Windows_NT6_BSOD_jcgriff2\031612-24304-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 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16917.amd64fre.win7_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`02c1c000 PsLoadedModuleList = 0xfffff800`02e58e70
Debug session time: Sat Mar 17 00:41:22.692 2012 (UTC - 6:00)
System Uptime: 0 days 1:38:05.830
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..........
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {411, fffff6fc500579e0, 9840000075226882, fffff6fc500579a1}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+5fe1 )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000000411, The subtype of the bugcheck.
Arg2: fffff6fc500579e0
Arg3: 9840000075226882
Arg4: fffff6fc500579a1

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


BUGCHECK_STR:  0x1a_411

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  League of Lege

CURRENT_IRQL:  2

TRAP_FRAME:  fffff8800a43c950 -- (.trap 0xfffff8800a43c950)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000624 rbx=0000000000000000 rcx=0000000000000624
rdx=0000000000100000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002f7c510 rsp=fffff8800a43cae0 rbp=fffff8800a43cc00
 r8=0000000000000000  r9=0000000000000001 r10=fffff80002f82970
r11=fffff8800a43cc18 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!ObReferenceObjectByHandleWithTag+0xb0:
fffff800`02f7c510 8b465c          mov     eax,dword ptr [rsi+5Ch] ds:00000000`0000005c=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c5369e to fffff80002c8c540

STACK_TEXT:  
fffff880`0a43c5f8 fffff800`02c5369e : 00000000`0000001a 00000000`00000411 fffff6fc`500579e0 98400000`75226882 : nt!KeBugCheckEx
fffff880`0a43c600 fffff800`02cbe07d : fffff8a0`0af3cfec fffff6fc`500579e0 0000007f`fffffff8 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x5fe1
fffff880`0a43c650 fffff800`02ca8976 : 00000000`00000000 fffff800`02ee3642 00000000`00000000 fffff800`02e17b40 : nt!MiResolveTransitionFault+0x38d
fffff880`0a43c6e0 fffff800`02ca6941 : fffff880`00961000 0000007f`fffffff8 fffff880`0a43c980 fffff800`02ca8976 : nt!MiDispatchFault+0x946
fffff880`0a43c7f0 fffff800`02c8a62e : 00000000`00000000 fffff880`0a43cc38 00000000`00000000 fffff8a0`021a58b0 : nt!MmAccessFault+0x8f1
fffff880`0a43c950 fffff800`02f7c510 : fffff800`02f7c460 00000000`00000018 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`0a43cae0 fffff800`02f829d9 : 00000000`738d2400 00000000`00100000 00000000`00000000 fffff880`0a43cc01 : nt!ObReferenceObjectByHandleWithTag+0xb0
fffff880`0a43cbb0 fffff800`02c8b793 : fffffa80`044638f0 00000000`00000624 fffff880`0a43cbf8 00000000`00000000 : nt!NtWaitForSingleObject+0x69
fffff880`0a43cc20 00000000`738d2dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0008ebf8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x738d2dd9


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+5fe1
fffff800`02c5369e cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+5fe1

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4ec7a284

FAILURE_BUCKET_ID:  X64_0x1a_411_VRF_nt!_??_::FNODOBFM::_string_+5fe1

BUCKET_ID:  X64_0x1a_411_VRF_nt!_??_::FNODOBFM::_string_+5fe1

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

1. Verifier enabled crash. Possible causes are Memory problems... Drivers...
2. Verifier enabled crash. Possible causes are Memory problems... Drivers...

The above point to a hardware related crash: specifically memory modules not working properly. They do not show a driver causing the crash with Verifier enabled, so this typically means hardware or system problems.

Questions:

• Did you at any time use tune-up utilities in the past to clean the registry?
  
  
• What were your results of sfc /scannow?

Hardware checks:

• If you are overclocking any hardware, please stop.
  
  
• Disable Verifier: Start Menu -> All Programs -> Accessories -> Right click Command Prompt -> Run as administrator ->
  verifier /reset
  -> restart your computer
• 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. 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 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.
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
  If you swap any memory components, follow these steps for ESD safety:
  
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
  
  Once these steps have been followed, it is safe to remove and replace components within your computer.

Responding to your questions, I never used Tune-up utilities to clean up my registry in the past, only after the reformat from the reccomendation of my friend, the results of sfc /scannow showed up with no errors.
So far, I have done the memtest86+ for 8 hours, receiving 5 passes and no errors. (can't do it for long periods of time, busy.) I will report more after I'm done the other series of tests.

Recently did the Furmark test (burn-in test), I crashed without a blue screen, my computer shutdown and restarted. I crashed at around 210 frames. Should I continue the test again?

Were you monitoring the temperatures during Furmark? It sounds like something overheated...

Check the temps using Hardware Monitor or another similar monitoring program