Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\DMP\042411-18127-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02817000 PsLoadedModuleList = 0xfffff800`02a54e50
Debug session time: Sat Apr 23 11:57:36.848 2011 (UTC - 4:00)
System Uptime: 0 days 0:12:35.002
Loading Kernel Symbols
...............................................................
................................................................
...............
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 19, {3, fffffa80043df3f0, fffffa80043df3f0, 27c9bb4303d1c2de}
Probably caused by : Pool_Corruption ( nt!ExFreePool+780 )
Followup: Pool_corruption
---------
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000003, the pool freelist is corrupt.
Arg2: fffffa80043df3f0, the pool entry being checked.
Arg3: fffffa80043df3f0, the read back flink freelist value (should be the same as 2).
Arg4: 27c9bb4303d1c2de, the read back blink freelist value (should be the same as 2).
Debugging Details:
------------------
BUGCHECK_STR: 0x19_3
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: SearchFilterHo
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff800029ba130 to fffff80002888f00
STACK_TEXT:
fffff880`09c257d8 fffff800`029ba130 : 00000000`00000019 00000000`00000003 fffffa80`043df3f0 fffffa80`043df3f0 : nt!KeBugCheckEx
fffff880`09c257e0 fffff800`029bc4c1 : fffffa80`04613150 fffffa80`0437eb00 00000000`00000000 00000000`00000000 : nt!ExFreePool+0x780
fffff880`09c25870 fffff800`0288e0bc : fffffa80`0437eb30 00000000`00000000 fffff8a0`65726854 fffffa80`03f6cde0 : nt!ExFreePoolWithTag+0x411
fffff880`09c25920 fffff800`02b9c194 : fffff8a0`03441760 00000000`00000000 fffffa80`06922060 00000000`00000000 : nt!ObfDereferenceObject+0xdc
fffff880`09c25980 fffff800`02b45870 : 00000000`00000128 fffff8a0`03441760 fffff8a0`035a44a0 00000000`00000128 : nt!ObpCloseHandleTableEntry+0xc4
fffff880`09c25a10 fffff800`02b457e4 : 00000000`00000004 00000000`00000000 fffffa80`0465b060 fffff800`02b2ef21 : nt!ObpCloseHandleProcedure+0x30
fffff880`09c25a50 fffff800`02b446ae : fffff8a0`03130001 00000000`00000001 fffffa80`0465b060 fffffa80`0465b101 : nt!ExSweepHandleTable+0x74
fffff880`09c25a90 fffff800`02b6b724 : fffff8a0`03130060 00000000`00000000 00000000`00000000 fffffa80`068b7960 : nt!ObKillProcess+0x62
fffff880`09c25ad0 fffff800`02b44cb8 : 00000000`00000000 00000000`00000001 000007ff`fffde000 00000000`00000000 : nt!PspExitThread+0x3f4
fffff880`09c25ba0 fffff800`02888153 : fffffa80`0465b060 00000000`00000000 fffffa80`06922060 fffffa80`04622860 : nt!NtTerminateProcess+0x138
fffff880`09c25c20 00000000`7701017a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0020fb08 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7701017a
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!ExFreePool+780
fffff800`029ba130 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!ExFreePool+780
FOLLOWUP_NAME: Pool_corruption
IMAGE_NAME: Pool_Corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: Pool_Corruption
FAILURE_BUCKET_ID: X64_0x19_3_nt!ExFreePool+780
BUCKET_ID: X64_0x19_3_nt!ExFreePool+780
Followup: Pool_corruption
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\DMP\042411-19546-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`0284e000 PsLoadedModuleList = 0xfffff800`02a8be50
Debug session time: Sat Apr 23 19:40:27.610 2011 (UTC - 4:00)
System Uptime: 0 days 0:02:35.811
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff800028b29eb, fffff880031db908, fffff880031db170}
Probably caused by : ntkrnlmp.exe ( nt!ExpScanGeneralLookasideList+a0 )
Followup: MachineOwner
---------
2: 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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff800028b29eb, The address that the exception occurred at
Arg3: fffff880031db908, Exception Record Address
Arg4: fffff880031db170, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
nt!ExpScanGeneralLookasideList+a0
fffff800`028b29eb 418b40d8 mov eax,dword ptr [r8-28h]
EXCEPTION_RECORD: fffff880031db908 -- (.exr 0xfffff880031db908)
ExceptionAddress: fffff800028b29eb (nt!ExpScanGeneralLookasideList+0x00000000000000a0)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff880031db170 -- (.cxr 0xfffff880031db170)
rax=0000000000000000 rbx=fffff80002a63760 rcx=0000000073e4a9de
rdx=000000003108dfa0 rsi=fffffa80018c2040 rdi=000000000000ffff
rip=fffff800028b29eb rsp=fffff880031dbb40 rbp=0000000000000001
r8=251de5e735429917 r9=0000000000005c41 r10=000000003108dfa0
r11=000000000000abdc r12=0000000000000000 r13=fffff80002a63750
r14=0000000000000000 r15=fffff88002f67f40
iopl=0 nv up ei pl nz na po cy
cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010207
nt!ExpScanGeneralLookasideList+0xa0:
fffff800`028b29eb 418b40d8 mov eax,dword ptr [r8-28h] ds:002b:251de5e7`354298ef=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 2
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002af60e0
ffffffffffffffff
FOLLOWUP_IP:
nt!ExpScanGeneralLookasideList+a0
fffff800`028b29eb 418b40d8 mov eax,dword ptr [r8-28h]
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff800028d20e0 to fffff800028b29eb
STACK_TEXT:
fffff880`031dbb40 fffff800`028d20e0 : 00000000`00000001 00000000`00000008 00000000`00000001 fffff800`02af6900 : nt!ExpScanGeneralLookasideList+0xa0
fffff880`031dbba0 fffff800`028d316e : 00000000`00000008 fffff880`031dbc10 00000000`00000001 fffffa80`00000000 : nt!ExAdjustLookasideDepth+0x40
fffff880`031dbbd0 fffff800`02b617c6 : fffffa80`018e8040 00000000`00000080 fffffa80`018c2040 00000000`00000001 : nt!KeBalanceSetManager+0x1be
fffff880`031dbd40 fffff800`0289cc26 : fffff880`02f63180 fffffa80`018e8040 fffff880`02f6dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031dbd80 00000000`00000000 : fffff880`031dc000 fffff880`031d6000 fffff880`031db710 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!ExpScanGeneralLookasideList+a0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4cc791bd
STACK_COMMAND: .cxr 0xfffff880031db170 ; kb
FAILURE_BUCKET_ID: X64_0x7E_nt!ExpScanGeneralLookasideList+a0
BUCKET_ID: X64_0x7E_nt!ExpScanGeneralLookasideList+a0
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\DMP\042411-21387-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`02856000 PsLoadedModuleList = 0xfffff800`02a93e50
Debug session time: Sat Apr 23 21:07:10.373 2011 (UTC - 4:00)
System Uptime: 0 days 0:35:57.574
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff800028d2670, fffff88003fc8cc0, 0}
Probably caused by : ntkrnlmp.exe ( nt!IofCallDriver+50 )
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: fffff800028d2670, Address of the instruction which caused the bugcheck
Arg3: fffff88003fc8cc0, 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:
nt!IofCallDriver+50
fffff800`028d2670 49ff64c070 jmp qword ptr [r8+rax*8+70h]
CONTEXT: fffff88003fc8cc0 -- (.cxr 0xfffff88003fc8cc0)
rax=000000000000000e rbx=0000000000000000 rcx=fffffa8004650a10
rdx=fffffa8002ae6b40 rsi=0000000000070048 rdi=0000000000000000
rip=fffff800028d2670 rsp=fffff88003fc9698 rbp=fffffa8004650a10
r8=b133cb0d0233f5bd r9=000000000000000e r10=fffff880009ebfa0
r11=fffffa8002a133b0 r12=0000000000000000 r13=fffffa800464fcd0
r14=fffffa8002274e30 r15=0000000000000001
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
nt!IofCallDriver+0x50:
fffff800`028d2670 49ff64c070 jmp qword ptr [r8+rax*8+70h] ds:002b:b133cb0d`0233f69d=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: taskhost.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff800028d2670
STACK_TEXT:
fffff880`03fc9698 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IofCallDriver+0x50
FOLLOWUP_IP:
nt!IofCallDriver+50
fffff800`028d2670 49ff64c070 jmp qword ptr [r8+rax*8+70h]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!IofCallDriver+50
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4cc791bd
STACK_COMMAND: .cxr 0xfffff88003fc8cc0 ; kb
FAILURE_BUCKET_ID: X64_0x3B_nt!IofCallDriver+50
BUCKET_ID: X64_0x3B_nt!IofCallDriver+50
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\DMP\042411-21777-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`0281b000 PsLoadedModuleList = 0xfffff800`02a58e50
Debug session time: Sat Apr 23 21:12:55.913 2011 (UTC - 4:00)
System Uptime: 0 days 0:03:04.113
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}
Unable to load image \SystemRoot\system32\DRIVERS\athrxusb.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for athrxusb.sys
*** ERROR: Module load completed but symbols could not be loaded for athrxusb.sys
Probably caused by : athrxusb.sys ( athrxusb+5af17 )
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:
+3332313336383065
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: 2
EXCEPTION_RECORD: fffff80003c95728 -- (.exr 0xfffff80003c95728)
ExceptionAddress: fffff880048e0f17 (athrxusb+0x000000000005af17)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
TRAP_FRAME: fffff80003c957d0 -- (.trap 0xfffff80003c957d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000099 rbx=0000000000000000 rcx=0000000000000099
rdx=fffffa800306a0ac rsi=0000000000000000 rdi=0000000000000000
rip=fffff880048e0f17 rsp=fffff80003c95960 rbp=0000000000000000
r8=00000000000000a3 r9=fffffa800306a0ac r10=fffff80002a06880
r11=fffff80003c95b18 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
athrxusb+0x5af17:
fffff880`048e0f17 ?? ???
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff8000288346e to fffff8000288b710
STACK_TEXT:
fffff800`03c94818 fffff800`0288346e : fffff880`0195b800 fffff880`0152205b fffff800`03c94f90 fffff800`028b8668 : nt!KeBugCheck
fffff800`03c94820 fffff800`028b140d : fffff800`02a99b7c fffff800`029d3ea4 fffff800`0281b000 fffff800`03c95728 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`03c94850 fffff800`028b8a90 : fffff800`029dab34 fffff800`03c948c8 fffff800`03c95728 fffff800`0281b000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`03c94880 fffff800`028c59ef : fffff800`03c95728 fffff800`03c94f90 fffff800`00000000 25a47428`394ea9ff : nt!RtlDispatchException+0x410
fffff800`03c94f60 fffff800`0288ad82 : fffff800`03c95728 fffffa80`046bffbb fffff800`03c957d0 fffff880`0490c265 : nt!KiDispatchException+0x16f
fffff800`03c955f0 fffff800`0288968a : 00000000`00000000 fffffa80`03ea4168 00000000`00000000 fffffa80`03ea4060 : nt!KiExceptionDispatch+0xc2
fffff800`03c957d0 fffff880`048e0f17 : 00000000`00000000 fffffa80`030e4050 fffffa80`030e4050 fffff880`042d1ba2 : nt!KiGeneralProtectionFault+0x10a
fffff800`03c95960 00000000`00000000 : fffffa80`030e4050 fffffa80`030e4050 fffff880`042d1ba2 ffff0099`0000000c : athrxusb+0x5af17
STACK_COMMAND: kb
FOLLOWUP_IP:
athrxusb+5af17
fffff880`048e0f17 ?? ???
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: athrxusb+5af17
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: athrxusb
IMAGE_NAME: athrxusb.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 45bdef26
FAILURE_BUCKET_ID: X64_0x1E_0_athrxusb+5af17
BUCKET_ID: X64_0x1E_0_athrxusb+5af17
Followup: MachineOwner
---------