Constant BSOD's - ntoskrnl.exe+705c0 - IRQL_NOT_LESS_OR_EQUAL

Mconi3 · 26 Dec 2011

Hi, i keep getting bsod's randomly when i boot up. sometimes they're instant and sometimes they're unexpected during running programs ect. most of my errors come back as IRQL_NOT_LESS_OR_EQUAL but i have had: KMODE_EXCEPTION_NOT_HANDLED & PAGE_FAULT_IN_NONPAGED_AREA. help would be much apperciated.

Pc Specs:
- AMD FX-6100 3.3GHz
- 8GB RAM
- Asus M5a99x Mobo

all new, around a week or two old.

OS:
Windows 7 Home Premium 64bit.

ive included crash dump files but not a 'PERFMON HTML file' :S (could understand how to do it)

writhziden · 26 Dec 2011

I notice you have Norton Internet Security installed on your computer. For testing purposes, remove it with the Norton Removal Tool and install Microsoft Security Essentials. Run MSE with Windows firewall.

Code:


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


Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Mconi3\Windows_NT6_BSOD_jcgriff2\122411-19281-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02816000 PsLoadedModuleList = 0xfffff800`02a53e50
Debug session time: Sat Dec 24 12:24:29.110 2011 (UTC - 7:00)
System Uptime: 0 days 0:10:20.915
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff7ffec8a2117, 0, fffff800028a2115, 2}


Could not read faulting driver name
Probably caused by : hardware ( nt! ?? ::FNODOBFM::`string'+40f90 )

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

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

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002abe0e0
 fffff7ffec8a2117 

FAULTING_IP: 
nt!MmAccessFault+535
fffff800`028a2115 8425fcffffe9    test    byte ptr [fffff7ff`ec8a2117],ah

MM_INTERNAL_CODE:  2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88002b626a0 -- (.trap 0xfffff88002b626a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8006bd5000 rbx=0000000000000000 rcx=00000000000000ff
rdx=00000000000000c0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800028a2115 rsp=fffff88002b62830 rbp=fffff88002b62880
 r8=000000000000000c  r9=fffff6800002fe00 r10=0000000000000000
r11=fffff88002b62a80 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di pl nz ac po nc
nt!MmAccessFault+0x535:
fffff800`028a2115 8425fcffffe9    test    byte ptr [fffff7ff`ec8a2117],ah ds:0fe0:fffff7ff`ec8a2117=??
Resetting default scope

MISALIGNED_IP: 
nt!MmAccessFault+535
fffff800`028a2115 8425fcffffe9    test    byte ptr [fffff7ff`ec8a2117],ah

LAST_CONTROL_TRANSFER:  from fffff80002905bc2 to fffff80002887f00

STACK_TEXT:  
fffff880`02b62538 fffff800`02905bc2 : 00000000`00000050 fffff7ff`ec8a2117 00000000`00000000 fffff880`02b626a0 : nt!KeBugCheckEx
fffff880`02b62540 fffff800`02885fee : 00000000`00000000 00000000`00000002 00000000`00000000 fffff8a0`083962e2 : nt! ?? ::FNODOBFM::`string'+0x40f90
fffff880`02b626a0 fffff800`028a2115 : fffff880`02b62848 00000000`00000000 fffffa80`04517040 fffff800`028ad52e : nt!KiPageFault+0x16e
fffff880`02b62830 fffff680`0002fe00 : 00000000`00000000 00000000`00000000 fffff880`02b62a80 fffffa80`06eebb30 : nt!MmAccessFault+0x535
fffff880`02b62990 00000000`00000000 : 00000000`00000000 fffff880`02b62a80 fffffa80`06eebb30 00000000`00000000 : 0xfffff680`0002fe00


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+40f90
fffff800`02905bc2 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+40f90

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED

BUCKET_ID:  X64_IP_MISALIGNED

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

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Mconi3\Windows_NT6_BSOD_jcgriff2\122411-31995-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a03000 PsLoadedModuleList = 0xfffff800`02c40e50
Debug session time: Sat Dec 24 14:02:07.185 2011 (UTC - 7:00)
System Uptime: 0 days 0:44:16.260
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, 1f8001000000, 8, 1f8001000000}

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

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

1: 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: ffffffffc0000005, The exception code that was not handled
Arg2: 00001f8001000000, The address that the exception occurred at
Arg3: 0000000000000008, Parameter 0 of the exception
Arg4: 00001f8001000000, Parameter 1 of the exception

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


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

FAULTING_IP: 
+6365306261633737
00001f80`01000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000008

EXCEPTION_PARAMETER2:  00001f8001000000

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cab0e0
 00001f8001000000 

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

BUGCHECK_STR:  0x1E_c0000005

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  WinSAT.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88009a5fbf0 -- (.trap 0xfffff88009a5fbf0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff88009a5ff80
rdx=0000077ff65a0080 rsi=0000000000000000 rdi=0000000000000000
rip=00001f8001000000 rsp=fffff88009a5fd80 rbp=fffff88009a5fdd0
 r8=0000000000000001  r9=0000000000000000 r10=fffff88009a60030
r11=fffff88009a5ff80 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di ng nz na pe nc
00001f80`01000000 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ab4a17 to fffff80002a74f00

STACK_TEXT:  
fffff880`09a5f368 fffff800`02ab4a17 : 00000000`0000001e ffffffff`c0000005 00001f80`01000000 00000000`00000008 : nt!KeBugCheckEx
fffff880`09a5f370 fffff800`02a74542 : fffff880`09a5fb48 0000077f`f65a0080 fffff880`09a5fbf0 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x460da
fffff880`09a5fa10 fffff800`02a730ba : 00000000`00000008 0000077f`f65a0080 ffffffff`ffffff00 fffff6fc`500ca728 : nt!KiExceptionDispatch+0xc2
fffff880`09a5fbf0 00001f80`01000000 : fffff880`09a5ff80 fffff880`09a5ff80 0000077f`f65a0080 00000000`00000001 : nt!KiPageFault+0x23a
fffff880`09a5fd80 fffff880`09a5ff80 : fffff880`09a5ff80 0000077f`f65a0080 00000000`00000001 00000000`00000000 : 0x1f80`01000000
fffff880`09a5fd88 fffff880`09a5ff80 : 0000077f`f65a0080 00000000`00000001 00000000`00000000 fffff880`09a60030 : 0xfffff880`09a5ff80
fffff880`09a5fd90 0000077f`f65a0080 : 00000000`00000001 00000000`00000000 fffff880`09a60030 fffff880`09a5ff80 : 0xfffff880`09a5ff80
fffff880`09a5fd98 00000000`00000001 : 00000000`00000000 fffff880`09a60030 fffff880`09a5ff80 00000000`00000000 : 0x77f`f65a0080
fffff880`09a5fda0 00000000`00000000 : fffff880`09a60030 fffff880`09a5ff80 00000000`00000000 00000000`00000000 : 0x1


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+460da
fffff800`02ab4a17 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+460da

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!_??_::FNODOBFM::_string_+460da

BUCKET_ID:  X64_0x1E_c0000005_nt!_??_::FNODOBFM::_string_+460da

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

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Mconi3\Windows_NT6_BSOD_jcgriff2\122411-28735-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`02c13000 PsLoadedModuleList = 0xfffff800`02e50e70
Debug session time: Sat Dec 24 14:28:42.605 2011 (UTC - 7:00)
System Uptime: 0 days 0:05:35.680
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {12, 2, 1, fffff80002c8f7b9}

Probably caused by : ntkrnlmp.exe ( nt!KeGetCurrentProcessorNumberEx+19 )

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

1: 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: 0000000000000012, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff80002c8f7b9, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ebb0e0
 0000000000000012 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KeGetCurrentProcessorNumberEx+19
fffff800`02c8f7b9 668911          mov     word ptr [rcx],dx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  mscorsvw.exe

TRAP_FRAME:  fffff8800b4ee590 -- (.trap 0xfffff8800b4ee590)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff880009e9180 rbx=0000000000000000 rcx=0000000000000012
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002c8f7b9 rsp=fffff8800b4ee728 rbp=0000000000000002
 r8=000000000000001e  r9=000000000000001e r10=fffff80002c13000
r11=fffff8800b4ee878 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di pl nz na po nc
nt!KeGetCurrentProcessorNumberEx+0x19:
fffff800`02c8f7b9 668911          mov     word ptr [rcx],dx ds:c060:00000000`00000012=????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c82b29 to fffff80002c835c0

STACK_TEXT:  
fffff880`0b4ee448 fffff800`02c82b29 : 00000000`0000000a 00000000`00000012 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0b4ee450 fffff800`02c817a0 : fffffa80`079ab000 fffff880`03164102 fffff880`00000003 fffffa80`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`0b4ee590 fffff800`02c8f7b9 : fffff800`031f6b7f 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
fffff880`0b4ee728 fffff800`031f6b7f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeGetCurrentProcessorNumberEx+0x19
fffff880`0b4ee730 fffff800`02c8807d : fffff880`03164180 fffffa80`07a09060 00000000`00000000 00000000`00000000 : hal!HalSendSoftwareInterrupt+0x48
fffff880`0b4ee760 fffff800`02c8bfb4 : 00000000`00000000 fffffa80`07a09060 fffffa80`06e7db60 fffffa80`07a09000 : nt!KiDeferredReadyThread+0x2fd
fffff880`0b4ee7e0 fffff800`02c3f5a4 : fffff880`009e9180 fffffa80`07a09060 00000144`296882ec 00000000`00000001 : nt!KiQueueReadyThread+0x134
fffff880`0b4ee810 fffff800`02c39d22 : 00000000`00000000 fffff880`03288180 fffff880`009e9180 00000000`00000001 : nt!KeSetSystemGroupAffinityThread+0x178
fffff880`0b4ee880 fffff800`02c88754 : 00000000`00000000 fffff8a0`0ca06290 fffffa80`06cf4570 fffff8a0`000003cd : nt!KeFlushQueuedDpcs+0x196
fffff880`0b4ee930 fffff800`02f96394 : fffff8a0`0ca06290 00000000`00000000 fffffa80`07a09060 00000000`00000000 : nt!ObfDereferenceObject+0xd4
fffff880`0b4ee990 fffff800`02f3de64 : 00000000`000000d8 fffff8a0`0ca06290 fffff8a0`0e2ac360 00000000`000000d8 : nt!ObpCloseHandleTableEntry+0xc4
fffff880`0b4eea20 fffff800`02f3dde4 : 00000000`00000004 00000000`00000000 fffffa80`07978060 fffff800`02f264c1 : nt!ObpCloseHandleProcedure+0x30
fffff880`0b4eea60 fffff800`02f3cc2e : fffff8a0`0e445001 00000000`00000001 fffffa80`07978060 fffffa80`07978060 : nt!ExSweepHandleTable+0x74
fffff880`0b4eeaa0 fffff800`02f659d4 : fffff8a0`0e445060 00000000`00000000 00000000`00000000 00000000`fffdb000 : nt!ObKillProcess+0x62
fffff880`0b4eeae0 fffff800`02f3d35b : 00000000`00000000 00000000`00000001 00000000`fffdb000 00000000`00000000 : nt!PspExitThread+0x878
fffff880`0b4eeba0 fffff800`02c82813 : fffffa80`07978060 00000000`00000000 00000000`fffdb001 fffffa80`07a09060 : nt!NtTerminateProcess+0x25b
fffff880`0b4eec20 00000000`77b8f97a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`001edef8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77b8f97a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KeGetCurrentProcessorNumberEx+19
fffff800`02c8f7b9 668911          mov     word ptr [rcx],dx

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KeGetCurrentProcessorNumberEx+19

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aa44

FAILURE_BUCKET_ID:  X64_0xA_nt!KeGetCurrentProcessorNumberEx+19

BUCKET_ID:  X64_0xA_nt!KeGetCurrentProcessorNumberEx+19

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

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Mconi3\Windows_NT6_BSOD_jcgriff2\122611-43508-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`02c01000 PsLoadedModuleList = 0xfffff800`02e3ee70
Debug session time: Mon Dec 26 11:29:22.887 2011 (UTC - 7:00)
System Uptime: 0 days 0:35:13.323
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffff8800a86fb30, e, 1, fffff80002c7fa53}

Probably caused by : ntkrnlmp.exe ( nt!KiIpiProcessRequests+c3 )

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

1: 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: fffff8800a86fb30, memory referenced
Arg2: 000000000000000e, IRQL
Arg3: 0000000000000001, 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: fffff80002c7fa53, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ea90e0
 fffff8800a86fb30 

CURRENT_IRQL:  e

FAULTING_IP: 
nt!KiIpiProcessRequests+c3
fffff800`02c7fa53 f0838500210000ff lock add dword ptr [rbp+2100h],0FFFFFFFFh

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  TrustedInstall

TRAP_FRAME:  fffff8800a86d820 -- (.trap 0xfffff8800a86d820)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000069634d43 rbx=0000000000000000 rcx=ffffffffff3b2968
rdx=fffff8800a86db70 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002c7fa53 rsp=fffff8800a86d9b0 rbp=fffff8800a86da30
 r8=fffffa8007b4caa0  r9=0000000000000000 r10=fffff880009edf00
r11=00000000041fe148 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di pl nz na pe nc
nt!KiIpiProcessRequests+0xc3:
fffff800`02c7fa53 f0838500210000ff lock add dword ptr [rbp+2100h],0FFFFFFFFh ss:fffff880`0a86fb30=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c70b29 to fffff80002c715c0

STACK_TEXT:  
fffff880`0a86d6d8 fffff800`02c70b29 : 00000000`0000000a fffff880`0a86fb30 00000000`0000000e 00000000`00000001 : nt!KeBugCheckEx
fffff880`0a86d6e0 fffff800`02c6f7a0 : 00000000`00000020 f88009c2`03380105 fffff8a0`0ee8626c fffff800`02f522f0 : nt!KiBugCheckDispatch+0x69
fffff880`0a86d820 fffff800`02c7fa53 : fffff8a0`0ee8626c 00000000`00000000 fffff8a0`21d4d820 00000000`00000000 : nt!KiPageFault+0x260
fffff880`0a86d9b0 00000000`000000c0 : fffff8a0`1615b850 00000000`00000000 fffff8a0`0afffd80 00000000`00000000 : nt!KiIpiProcessRequests+0xc3
fffff880`0a86da90 fffff8a0`1615b850 : 00000000`00000000 fffff8a0`0afffd80 00000000`00000000 fffffa80`07d563a0 : 0xc0
fffff880`0a86da98 00000000`00000000 : fffff8a0`0afffd80 00000000`00000000 fffffa80`07d563a0 fffff8a0`1615b7c0 : 0xfffff8a0`1615b850


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiIpiProcessRequests+c3
fffff800`02c7fa53 f0838500210000ff lock add dword ptr [rbp+2100h],0FFFFFFFFh

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KiIpiProcessRequests+c3

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aa44

FAILURE_BUCKET_ID:  X64_0xA_nt!KiIpiProcessRequests+c3

BUCKET_ID:  X64_0xA_nt!KiIpiProcessRequests+c3

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

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Mconi3\Windows_NT6_BSOD_jcgriff2\122611-32713-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`02c4c000 PsLoadedModuleList = 0xfffff800`02e89e70
Debug session time: Mon Dec 26 11:43:47.839 2011 (UTC - 7:00)
System Uptime: 0 days 0:13:00.915
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 : hardware ( nt!KiKernelCalloutExceptionHandler+e )

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

1: 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: 
+6365306261633737
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:  ccsvchst.exe

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff88003122cc8 -- (.exr 0xfffff88003122cc8)
ExceptionAddress: fffff80002cc79d5 (nt!KiRetireDpcList+0x00000000000000f5)
   ExceptionCode: c000001d (Illegal instruction)
  ExceptionFlags: 00000000
NumberParameters: 0

TRAP_FRAME:  fffff88003122d70 -- (.trap 0xfffff88003122d70)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8800186cc50 rbx=0000000000000000 rcx=fffff880009eb300
rdx=fffffa80097e5660 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002cc79d5 rsp=fffff88003122f00 rbp=fffffa80097e5380
 r8=0000000000000000  r9=0000000000000000 r10=fffffa8009bd05f0
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di ng nz na pe nc
nt!KiRetireDpcList+0xf5:
fffff800`02cc79d5 82              ???
Resetting default scope

MISALIGNED_IP: 
nt!KiRetireDpcList+f5
fffff800`02cc79d5 82              ???

LAST_CONTROL_TRANSFER:  from fffff80002cb42ee to fffff80002cbc590

STACK_TEXT:  
fffff880`03121db8 fffff800`02cb42ee : fffffa80`097e8bb0 00000000`00000000 fffff880`03122530 fffff800`02ce9524 : nt!KeBugCheck
fffff880`03121dc0 fffff800`02ce22dd : fffff800`02ecab7c fffff800`02e04e68 fffff800`02c4c000 fffff880`03122cc8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`03121df0 fffff800`02ce9950 : fffff800`02e0ba38 fffff880`03121e68 fffff880`03122cc8 fffff800`02c4c000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`03121e20 fffff800`02cf68cf : fffff880`03122cc8 fffff880`03122530 fffff880`00000000 fffff880`009e9180 : nt!RtlDispatchException+0x410
fffff880`03122500 fffff800`02cbbc02 : fffff880`03122cc8 fffff880`009e9180 fffff880`03122d70 fffffa80`097e5658 : nt!KiDispatchException+0x16f
fffff880`03122b90 fffff800`02cb9d5f : fffff880`03122d70 00000000`00000002 fffff880`009e9100 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`03122d70 fffff800`02cc79d5 : fffffa80`097e5658 fffff800`00000000 00000000`00000000 fffff880`009e9180 : nt!KiInvalidOpcodeFault+0x11f
fffff880`03122f00 fffff800`02cc2705 : 00000000`00000000 fffffa80`0a40db60 00000000`00000000 fffff880`0186cc50 : nt!KiRetireDpcList+0xf5
fffff880`03122fb0 fffff800`02cc251c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KyRetireDpcList+0x5
fffff880`065e1530 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiKernelCalloutExceptionHandler+e
fffff800`02cb42ee 90              nop

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KiKernelCalloutExceptionHandler+e

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED

BUCKET_ID:  X64_IP_MISALIGNED

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

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Mconi3\Windows_NT6_BSOD_jcgriff2\122611-26426-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`02c67000 PsLoadedModuleList = 0xfffff800`02ea4e70
Debug session time: Mon Dec 26 15:16:23.470 2011 (UTC - 7:00)
System Uptime: 0 days 0:39:06.922
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {2710, d, 1, fffff80002ce4479}

Probably caused by : hardware ( nt!KiPageFault+260 )

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

1: 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: 0000000000002710, memory referenced
Arg2: 000000000000000d, IRQL
Arg3: 0000000000000001, 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: fffff80002ce4479, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f0f0e0
 0000000000002710 

CURRENT_IRQL:  d

FAULTING_IP: 
nt!KeUpdateRunTime+99
fffff800`02ce4479 2100            and     dword ptr [rax],eax

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  WinSAT.exe

TRAP_FRAME:  fffff8800bbb69d0 -- (.trap 0xfffff8800bbb69d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000002710 rbx=0000000000000000 rcx=fffff880009e9180
rdx=0000000000002710 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ce4479 rsp=fffff8800bbb6b60 rbp=0000000000000001
 r8=0000000000000001  r9=0000000000000000 r10=fffffa800d54fb60
r11=0000000046980636 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!KeUpdateRunTime+0x99:
fffff800`02ce4479 2100            and     dword ptr [rax],eax ds:6b18:00000000`00002710=????????
Resetting default scope

MISALIGNED_IP: 
nt!KeUpdateRunTime+99
fffff800`02ce4479 2100            and     dword ptr [rax],eax

LAST_CONTROL_TRANSFER:  from fffff80002cd6b29 to fffff80002cd75c0

STACK_TEXT:  
fffff880`0bbb6888 fffff800`02cd6b29 : 00000000`0000000a 00000000`00002710 00000000`0000000d 00000000`00000001 : nt!KeBugCheckEx
fffff880`0bbb6890 fffff800`02cd57a0 : 00000000`00000005 fffff880`009e9180 00000000`00000000 ffffffff`ffffffff : nt!KiBugCheckDispatch+0x69
fffff880`0bbb69d0 fffff800`02ce4479 : fffff700`01080000 fffff6fb`40000970 fffff680`0012eeb0 fffffa80`0000b1d8 : nt!KiPageFault+0x260
fffff880`0bbb6b60 fffffa80`065c8bc0 : fffffa80`0d54fb60 00000000`25dd1000 00000000`00004008 00000000`00000005 : nt!KeUpdateRunTime+0x99
fffff880`0bbb6b90 fffffa80`0d54fb60 : 00000000`25dd1000 00000000`00004008 00000000`00000005 00000000`00000002 : 0xfffffa80`065c8bc0
fffff880`0bbb6b98 00000000`25dd1000 : 00000000`00004008 00000000`00000005 00000000`00000002 00000000`003e77a4 : 0xfffffa80`0d54fb60
fffff880`0bbb6ba0 00000000`00004008 : 00000000`00000005 00000000`00000002 00000000`003e77a4 000007fe`fc650000 : 0x25dd1000
fffff880`0bbb6ba8 00000000`00000005 : 00000000`00000002 00000000`003e77a4 000007fe`fc650000 fffff880`0bbb6c20 : 0x4008
fffff880`0bbb6bb0 00000000`00000002 : 00000000`003e77a4 000007fe`fc650000 fffff880`0bbb6c20 00000000`00024baa : 0x5
fffff880`0bbb6bb8 00000000`003e77a4 : 000007fe`fc650000 fffff880`0bbb6c20 00000000`00024baa 00000000`00000000 : 0x2
fffff880`0bbb6bc0 000007fe`fc650000 : fffff880`0bbb6c20 00000000`00024baa 00000000`00000000 fffff880`009e9180 : 0x3e77a4
fffff880`0bbb6bc8 fffff880`0bbb6c20 : 00000000`00024baa 00000000`00000000 fffff880`009e9180 fffff800`02ce4498 : 0x7fe`fc650000
fffff880`0bbb6bd0 00000000`00024baa : 00000000`00000000 fffff880`009e9180 fffff800`02ce4498 00000000`00000000 : 0xfffff880`0bbb6c20
fffff880`0bbb6bd8 00000000`00000000 : fffff880`009e9180 fffff800`02ce4498 00000000`00000000 00000000`00000000 : 0x24baa


STACK_COMMAND:  kb

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

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiPageFault+260

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED

BUCKET_ID:  X64_IP_MISALIGNED

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

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Mconi3\Windows_NT6_BSOD_jcgriff2\122611-31543-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`02c5f000 PsLoadedModuleList = 0xfffff800`02e9ce70
Debug session time: Mon Dec 26 15:27:00.915 2011 (UTC - 7:00)
System Uptime: 0 days 0:00:53.991
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {ef55e, e, 1, fffff80002cdb921}

Probably caused by : hardware ( nt!KiIpiInterrupt+b1 )

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

1: 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: 00000000000ef55e, memory referenced
Arg2: 000000000000000e, IRQL
Arg3: 0000000000000001, 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: fffff80002cdb921, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f070e0
 00000000000ef55e 

CURRENT_IRQL:  e

FAULTING_IP: 
nt!KiIpiInterrupt+b1
fffff800`02cdb921 80480000        or      byte ptr [rax],0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  CCC.exe

TRAP_FRAME:  fffff8800ae5ea90 -- (.trap 0xfffff8800ae5ea90)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000000ef55e rbx=0000000000000000 rcx=fffff880009e9180
rdx=0000003400000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002cdb921 rsp=fffff8800ae5ec20 rbp=fffff8800ae5eca0
 r8=fffffa800ab1c8c0  r9=000000001dfabfc8 r10=fffffa800ab1c8c0
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di pl nz na pe nc
nt!KiIpiInterrupt+0xb1:
fffff800`02cdb921 80480000        or      byte ptr [rax],0 ds:00000000`000ef55e=??
Resetting default scope

MISALIGNED_IP: 
nt!KiIpiInterrupt+b1
fffff800`02cdb921 80480000        or      byte ptr [rax],0

LAST_CONTROL_TRANSFER:  from fffff80002cceb29 to fffff80002ccf5c0

STACK_TEXT:  
fffff880`0ae5e948 fffff800`02cceb29 : 00000000`0000000a 00000000`000ef55e 00000000`0000000e 00000000`00000001 : nt!KeBugCheckEx
fffff880`0ae5e950 fffff800`02ccd7a0 : fffff8a0`031efb50 00000000`1be67f50 fffff8a0`032c1210 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`0ae5ea90 fffff800`02cdb921 : fffffa80`0ab1c8c0 fffffa80`0aaed260 00000000`1dfae110 00000000`00000001 : nt!KiPageFault+0x260
fffff880`0ae5ec20 00000000`74b65b44 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIpiInterrupt+0xb1
00000000`1dfab940 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74b65b44


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiIpiInterrupt+b1
fffff800`02cdb921 80480000        or      byte ptr [rax],0

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KiIpiInterrupt+b1

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED

BUCKET_ID:  X64_IP_MISALIGNED

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

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Mconi3\Windows_NT6_BSOD_jcgriff2\122611-29733-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`02c09000 PsLoadedModuleList = 0xfffff800`02e46e70
Debug session time: Mon Dec 26 15:43:33.122 2011 (UTC - 7:00)
System Uptime: 0 days 0:09:25.558
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 9, 1, fffff80002c86b5f}

Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_InterruptService+56 )

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

1: 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: 0000000000000000, memory referenced
Arg2: 0000000000000009, IRQL
Arg3: 0000000000000001, 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: fffff80002c86b5f, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eb10e0
 0000000000000000 

CURRENT_IRQL:  9

FAULTING_IP: 
nt!ExGetCurrentProcessorCounts+2b
fffff800`02c86b5f 418900          mov     dword ptr [r8],eax

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  chrome.exe

TRAP_FRAME:  fffff8800a929430 -- (.trap 0xfffff8800a929430)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff80002c7c700 rbx=0000000000000000 rcx=fffff8800a929de8
rdx=fffff8800a929650 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80000000293 rsp=fffff8800a9295c8 rbp=fffff8800a92ac20
 r8=fffff8800a929600  r9=fffff8800a9295b0 r10=fffff8800a929650
r11=fffff8800a929600 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
fffff800`00000293 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c78b29 to fffff80002c795c0

STACK_TEXT:  
fffff880`0a928f88 fffff800`02c78b29 : 00000000`0000000a 00000000`00000000 00000000`00000009 00000000`00000001 : nt!KeBugCheckEx
fffff880`0a928f90 fffff800`02c777a0 : 00000025`00000025 fffffa80`08f301a0 00000025`00000025 00000025`00000025 : nt!KiBugCheckDispatch+0x69
fffff880`0a9290d0 fffff800`02c86b5f : fffff880`046c431e 00000025`00000025 00000025`00000025 fffff800`02c51de2 : nt!KiPageFault+0x260
fffff880`0a929268 fffff880`046c431e : 00000025`00000025 00000025`00000025 fffff800`02c51de2 0000083a`0000083a : nt!ExGetCurrentProcessorCounts+0x2b
fffff880`0a929270 fffff800`02c753bc : fffff800`02e872b8 00000025`00000025 fffffa80`07687a80 00000025`00000025 : USBPORT!USBPORT_InterruptService+0x56
fffff880`0a9292a0 fffff800`02c7763f : 00000025`00000025 00000025`00000025 00000025`00000025 00000025`00000025 : nt!KiInterruptDispatch+0x16c
fffff880`0a929430 fffff800`00000293 : fffff800`02e872b8 fffff880`0a92ac20 fffff880`0a9296a0 0000083a`0000083a : nt!KiPageFault+0xff
fffff880`0a9295c8 fffff800`02e872b8 : fffff880`0a92ac20 fffff880`0a9296a0 0000083a`0000083a fffff800`02cb2381 : 0xfffff800`00000293
fffff880`0a9295d0 fffff880`0a92ac20 : fffff880`0a9296a0 0000083a`0000083a fffff800`02cb2381 00000000`00000001 : nt!BBTBuffer <PERF> (nt+0x27e2b8)
fffff880`0a9295d8 fffff880`0a9296a0 : 0000083a`0000083a fffff800`02cb2381 00000000`00000001 fffffa80`07113b00 : 0xfffff880`0a92ac20
fffff880`0a9295e0 0000083a`0000083a : fffff800`02cb2381 00000000`00000001 fffffa80`07113b00 00000000`c0000000 : 0xfffff880`0a9296a0
fffff880`0a9295e8 fffff800`02cb2381 : 00000000`00000001 fffffa80`07113b00 00000000`c0000000 00000000`0010001f : 0x83a`0000083a
fffff880`0a9295f0 fffff800`02cb3886 : fffff880`0a929de8 fffff880`0a929e90 fffff880`0a929e90 fffffa80`0742fac8 : nt!RtlInitializeExtendedContext+0x25
fffff880`0a929620 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x126


STACK_COMMAND:  kb

FOLLOWUP_IP: 
USBPORT!USBPORT_InterruptService+56
fffff880`046c431e 408af8          mov     dil,al

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  USBPORT!USBPORT_InterruptService+56

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: USBPORT

IMAGE_NAME:  USBPORT.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4d8c0a97

FAILURE_BUCKET_ID:  X64_0xA_USBPORT!USBPORT_InterruptService+56

BUCKET_ID:  X64_0xA_USBPORT!USBPORT_InterruptService+56

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

You should update Windows 7 to SP1:

Download Details - Microsoft Download Center - System Update Readiness Tool for Windows 7 (KB947821) [August 2011]

Download Details - Microsoft Download Center - System Update Readiness Tool for Windows 7 for x64-based Systems (KB947821) [August 2011]

Steps to follow before you install Windows 7 Service Pack 1 from the Microsoft Download Center

Service Pack 1 Download site

Links to Service Pack 1 (SP1) and preparation for SP1 courtesy of JMH

You have hardware blue screens; see Stop 0x124 - what it means and what to try

You also had a USB related blue screen. Follow the steps in USB Driver - General Fix for Problems

If you continue to have issues, disconnect all peripherals (externally connected hardware such as USB, firewire, memory cards, etc.) except the mouse, keyboard, and monitor. Run without these connected and see if you have issues. If you do not, connect one peripheral at a time to test each one individually until the problem resumes. Let us know what the trouble component is and we will further assist you with troubleshooting that component.

Mconi3 · 27 Dec 2011

Thanks for the help, still couldn't get it to work so decided to change the hard drive, use the old mouse and keyboard connectors and reboot a new version of Windows 7. if i still get problems ill be sure to comeback and get help since you guys are good for it :)

writhziden · 27 Dec 2011

Mconi3 said:

Thanks for the help, still couldn't get it to work so decided to change the hard drive, use the old mouse and keyboard connectors and reboot a new version of Windows 7. if i still get problems ill be sure to comeback and get help since you guys are good for it :)

Alright. Good luck. :)

writhziden · 17 Jan 2012

Did swapping out your hardware solve the problem? If so, please mark the thread as solved by clicking the green button next to Post Reply at the top or the bottom of the thread. If not, let us know if you need any help. :)