Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\DMP\040111-32307-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 x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.x86fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0x82a12000 PsLoadedModuleList = 0x82b5a810
Debug session time: Fri Apr 1 11:47:14.177 2011 (UTC - 4:00)
System Uptime: 0 days 1:08:59.410
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7F, {0, 0, 0, 0}
*** WARNING: Unable to verify timestamp for avgtdix.sys
*** ERROR: Module load completed but symbols could not be loaded for avgtdix.sys
Unable to load image \SystemRoot\system32\DRIVERS\avgfwd6x.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for avgfwd6x.sys
*** ERROR: Module load completed but symbols could not be loaded for avgfwd6x.sys
Probably caused by : avgtdix.sys ( avgtdix+4ec )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 00000000, EXCEPTION_DIVIDED_BY_ZERO
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
BUGCHECK_STR: 0x7f_0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from 88424184 to 82a5629b
STACK_TEXT:
a4bff864 88424184 badb0d00 0000a9d4 a4bff890 nt!KiTrap00+0x8b
WARNING: Frame IP not in any known module. Following frames may be wrong.
a4bff8d4 a4bff9d0 a4bff969 a4bff96a a4bffa7c 0x88424184
a4bff8f4 82e27ba9 00000000 87bf5302 a4bff94c 0xa4bff9d0
a4bff904 82e257ab 8b7154ec 80000000 8b7190b3 hal!KfLowerIrql+0x61
a4bff908 8b7154ec 80000000 8b7190b3 8809fb50 hal!KfReleaseSpinLock+0xb
a4bff950 8fc02e72 8809f840 00000000 a4bff968 avgtdix+0x4ec
a4bff954 8809f840 00000000 a4bff968 a4bffa9c avgfwd6x+0x2e72
a4bff958 00000000 a4bff968 a4bffa9c 00000000 0x8809f840
STACK_COMMAND: kb
FOLLOWUP_IP:
avgtdix+4ec
8b7154ec ?? ???
SYMBOL_STACK_INDEX: 5
SYMBOL_NAME: avgtdix+4ec
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: avgtdix
IMAGE_NAME: avgtdix.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4cdd1f96
FAILURE_BUCKET_ID: 0x7f_0_avgtdix+4ec
BUCKET_ID: 0x7f_0_avgtdix+4ec
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\DMP\040111-33992-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 x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82a0c000 PsLoadedModuleList = 0x82b54810
Debug session time: Thu Mar 31 20:38:38.673 2011 (UTC - 4:00)
System Uptime: 0 days 0:21:16.906
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {f, 2, 0, 82e209d4}
Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Core_iMapTransfer+21e )
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: 0000000f, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, 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: 82e209d4, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from 82b74718
Unable to read MiSystemVaType memory at 82b54160
0000000f
CURRENT_IRQL: 2
FAULTING_IP:
hal!HalBuildScatterGatherList+160
82e209d4 85f6 test esi,esi
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: 82b32b20 -- (.trap 0xffffffff82b32b20)
ErrCode = 00000000
eax=89886498 ebx=00000000 ecx=898864a8 edx=00000000 esi=00000000 edi=897b2370
eip=82e209d4 esp=82b32b94 ebp=82b32ba8 iopl=0 nv up ei ng nz ac po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010292
hal!HalBuildScatterGatherList+0x160:
82e209d4 85f6 test esi,esi
Resetting default scope
LAST_CONTROL_TRANSFER: from 82e209d4 to 82a527eb
STACK_TEXT:
82b32b20 82e209d4 badb0d00 00000000 82b2c466 nt!KiTrap0E+0x2cf
82b32ba8 82e20c16 89886490 87e8d028 897b2350 hal!HalBuildScatterGatherList+0x160
82b32bd8 8f32ae70 87bd4490 87e8d028 897b2350 hal!HalGetScatterGatherList+0x26
82b32c24 8f32a807 87e8d028 87e8d970 00000008 USBPORT!USBPORT_Core_iMapTransfer+0x21e
82b32c54 8f324d18 87e8d028 87e8d970 87e8d002 USBPORT!USBPORT_Core_UsbMapDpc_Worker+0x1e3
82b32c78 82a743b5 87e8d97c 87e8d002 00000000 USBPORT!USBPORT_Xdpc_Worker+0x173
82b32cd4 82a74218 82b35d20 82b3f280 00000000 nt!KiExecuteAllDpcs+0xf9
82b32d20 82a74038 00000000 0000000e 00000000 nt!KiRetireDpcList+0xd5
82b32d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38
STACK_COMMAND: kb
FOLLOWUP_IP:
USBPORT!USBPORT_Core_iMapTransfer+21e
8f32ae70 8945f4 mov dword ptr [ebp-0Ch],eax
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: USBPORT!USBPORT_Core_iMapTransfer+21e
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: USBPORT
IMAGE_NAME: USBPORT.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc871
FAILURE_BUCKET_ID: 0xA_USBPORT!USBPORT_Core_iMapTransfer+21e
BUCKET_ID: 0xA_USBPORT!USBPORT_Core_iMapTransfer+21e
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\DMP\033111-31090-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 x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82a0b000 PsLoadedModuleList = 0x82b53810
Debug session time: Thu Mar 31 15:57:18.603 2011 (UTC - 4:00)
System Uptime: 0 days 0:46:16.836
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 82c8a762, 9bf4744c, 0}
Probably caused by : hardware ( nt!MiProtectVirtualMemory+15 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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: c0000005, The exception code that was not handled
Arg2: 82c8a762, The address that the exception occurred at
Arg3: 9bf4744c, Trap Frame
Arg4: 00000000
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!MiProtectVirtualMemory+15
82c8a762 8b1d24010000 mov ebx,dword ptr ds:[124h]
TRAP_FRAME: 9bf4744c -- (.trap 0xffffffff9bf4744c)
ErrCode = 00000000
eax=9bf47514 ebx=890f27c8 ecx=01b7c000 edx=ffffffff esi=9bf47628 edi=00000000
eip=82c8a762 esp=9bf474c0 ebp=37e8e981 iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
nt!MiProtectVirtualMemory+0x15:
82c8a762 8b1d24010000 mov ebx,dword ptr ds:[124h] ds:0023:00000124=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: aaHMSvc.exe
CURRENT_IRQL: 0
MISALIGNED_IP:
nt!MiProtectVirtualMemory+15
82c8a762 8b1d24010000 mov ebx,dword ptr ds:[124h]
LAST_CONTROL_TRANSFER: from 82c8ad6f to 82c8a762
STACK_TEXT:
9bf474c0 82c8ad6f 890f27c8 9bf47514 9bf47518 nt!MiProtectVirtualMemory+0x15
9bf47534 82a4e42a ffffffff 9bf47634 9bf47628 nt!NtProtectVirtualMemory+0x12e
9bf47534 82a4ca71 ffffffff 9bf47634 9bf47628 nt!KiFastCallEntry+0x12a
9bf475c0 82c6ebfe ffffffff 9bf47634 9bf47628 nt!ZwProtectVirtualMemory+0x11
9bf47654 82c69f5c 00000000 00000000 00000000 nt!RtlCreateUserStack+0x1e4
9bf47704 82c818a1 890f27c8 8595825c 00000000 nt!PspAllocateThread+0x2c2
9bf478cc 82c43f5c 0187fc38 001fffff 00000000 nt!PspCreateThread+0x1b7
9bf47d00 82a4e42a 0187fc38 001fffff 00000000 nt!NtCreateThreadEx+0x20b
9bf47d00 776e64f4 0187fc38 001fffff 00000000 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0187fe54 00000000 00000000 00000000 00000000 0x776e64f4
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiProtectVirtualMemory+15
82c8a762 8b1d24010000 mov ebx,dword ptr ds:[124h]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!MiProtectVirtualMemory+15
FOLLOWUP_NAME: MachineOwner
DEBUG_FLR_IMAGE_TIMESTAMP: 0
IMAGE_NAME: hardware
MODULE_NAME: hardware
FAILURE_BUCKET_ID: IP_MISALIGNED
BUCKET_ID: IP_MISALIGNED
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\DMP\040211-23322-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 x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.x86fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0x82a02000 PsLoadedModuleList = 0x82b4a810
Debug session time: Sat Apr 2 14:19:24.735 2011 (UTC - 4:00)
System Uptime: 0 days 2:25:58.062
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {ffff2302, 2, 0, 8b6a7afd}
Probably caused by : tcpip.sys ( tcpip!IppRouteSetTimeout+1b )
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: ffff2302, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 8b6a7afd, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from 82b6a718
Unable to read MiSystemVaType memory at 82b4a160
ffff2302
CURRENT_IRQL: 2
FAULTING_IP:
tcpip!IppRouteSetTimeout+1b
8b6a7afd 83780400 cmp dword ptr [eax+4],0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
TRAP_FRAME: 82b28984 -- (.trap 0xffffffff82b28984)
ErrCode = 00000000
eax=ffff22fe ebx=82b28ac0 ecx=8b6aa22c edx=88b7f170 esi=8b6aa370 edi=8b6aa1ac
eip=8b6a7afd esp=82b289f8 ebp=82b28a14 iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
tcpip!IppRouteSetTimeout+0x1b:
8b6a7afd 83780400 cmp dword ptr [eax+4],0 ds:0023:ffff2302=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from 8b6a7afd to 82a4881b
STACK_TEXT:
82b28984 8b6a7afd badb0d00 88b7f170 82b6a8c8 nt!KiTrap0E+0x2cf
82b28a14 82b28a44 8b6aa1ac 82b28a34 8883312c tcpip!IppRouteSetTimeout+0x1b
82b28a18 8b6aa1ac 82b28a34 8883312c 00000000 nt!KiDoubleFaultStack+0x2a44
82b28a44 8b6aa7b2 00000000 0000446c 00000001 tcpip!TtFireTimerEx+0x71
82b28ad8 8b6aa497 88998968 8b7114ac 875c3350 tcpip!IppAddressSetTimeout+0x4f
82b28af4 8b6a9f11 875c3388 01b2d900 82b28b00 tcpip!Ipv4pInterfaceSetTimeout+0x52
82b28b20 8b6a99d2 8b70ed98 00000000 82b28b7c tcpip!IppCompartmentSetTimeout+0x8a
82b28b30 8b6a99a8 8b70ed98 82a6c16d 8b71fb00 tcpip!IppProtocolTimeout+0xf
82b28b38 82a6c16d 8b71fb00 00000000 7ed7d4e7 tcpip!IppTimeout+0x3c
82b28b7c 82a6c111 82b2bd20 82b28ca8 00000001 nt!KiProcessTimerDpcTable+0x50
82b28c68 82a6bfce 82b2bd20 82b28ca8 00000000 nt!KiProcessExpiredTimerList+0x101
82b28cdc 82a6a34e 00089102 895e5a68 82b35280 nt!KiTimerExpiration+0x25c
82b28d20 82a6a178 00000000 0000000e 00000000 nt!KiRetireDpcList+0xcb
82b28d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38
STACK_COMMAND: kb
FOLLOWUP_IP:
tcpip!IppRouteSetTimeout+1b
8b6a7afd 83780400 cmp dword ptr [eax+4],0
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: tcpip!IppRouteSetTimeout+1b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: tcpip
IMAGE_NAME: tcpip.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4c15a3db
FAILURE_BUCKET_ID: 0xD1_tcpip!IppRouteSetTimeout+1b
BUCKET_ID: 0xD1_tcpip!IppRouteSetTimeout+1b
Followup: MachineOwner
---------