Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\a\Minidump\D M P\DMP\012511-24211-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`03206000 PsLoadedModuleList = 0xfffff800`03443e50
Debug session time: Tue Jan 25 02:06:39.428 2011 (UTC - 5:00)
System Uptime: 0 days 0:11:25.270
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 19, {20, fffffa8006a16bb0, fffffa8006a16cc0, 4110003}
Unable to load image \SystemRoot\system32\DRIVERS\wg111v3.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for wg111v3.sys
*** ERROR: Module load completed but symbols could not be loaded for wg111v3.sys
Probably caused by : wg111v3.sys ( wg111v3+57a85 )
Followup: MachineOwner
---------
0: 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: 0000000000000020, a pool block header size is corrupt.
Arg2: fffffa8006a16bb0, The pool entry we were looking for within the page.
Arg3: fffffa8006a16cc0, The next pool entry.
Arg4: 0000000004110003, (reserved)
Debugging Details:
------------------
BUGCHECK_STR: 0x19_20
POOL_ADDRESS: GetPointerFromAddress: unable to read from fffff800034ae0e0
fffffa8006a16bb0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff800033a96d3 to fffff80003276740
STACK_TEXT:
fffff880`031fc108 fffff800`033a96d3 : 00000000`00000019 00000000`00000020 fffffa80`06a16bb0 fffffa80`06a16cc0 : nt!KeBugCheckEx
fffff880`031fc110 fffff880`016ee695 : 00000000`00000000 00000000`00000000 fffff880`37383138 00000000`37383138 : nt!ExDeferredFreePool+0x12c4
fffff880`031fc1c0 fffff880`05057a85 : fffffa80`06a27d30 fffffa80`06a1cfe8 00000000`0000001b fffffa80`03d691b0 : ndis!NdisFreeMemory+0x15
fffff880`031fc1f0 fffffa80`06a27d30 : fffffa80`06a1cfe8 00000000`0000001b fffffa80`03d691b0 fffffa80`0742f000 : wg111v3+0x57a85
fffff880`031fc1f8 fffffa80`06a1cfe8 : 00000000`0000001b fffffa80`03d691b0 fffffa80`0742f000 fffff880`050397d0 : 0xfffffa80`06a27d30
fffff880`031fc200 00000000`0000001b : fffffa80`03d691b0 fffffa80`0742f000 fffff880`050397d0 fffffa80`06a0f820 : 0xfffffa80`06a1cfe8
fffff880`031fc208 fffffa80`03d691b0 : fffffa80`0742f000 fffff880`050397d0 fffffa80`06a0f820 00000000`00000000 : 0x1b
fffff880`031fc210 fffffa80`0742f000 : fffff880`050397d0 fffffa80`06a0f820 00000000`00000000 fffffa80`0742f000 : 0xfffffa80`03d691b0
fffff880`031fc218 fffff880`050397d0 : fffffa80`06a0f820 00000000`00000000 fffffa80`0742f000 fffffa80`03d691b0 : 0xfffffa80`0742f000
fffff880`031fc220 fffffa80`06a0f820 : 00000000`00000000 fffffa80`0742f000 fffffa80`03d691b0 fffffa80`0762e000 : wg111v3+0x397d0
fffff880`031fc228 00000000`00000000 : fffffa80`0742f000 fffffa80`03d691b0 fffffa80`0762e000 fffff880`0501282e : 0xfffffa80`06a0f820
STACK_COMMAND: kb
FOLLOWUP_IP:
wg111v3+57a85
fffff880`05057a85 ?? ???
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: wg111v3+57a85
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: wg111v3
IMAGE_NAME: wg111v3.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4b03c2c2
FAILURE_BUCKET_ID: X64_0x19_20_wg111v3+57a85
BUCKET_ID: X64_0x19_20_wg111v3+57a85
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\a\Minidump\D M P\DMP\012511-25272-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`03214000 PsLoadedModuleList = 0xfffff800`03451e50
Debug session time: Tue Jan 25 01:54:34.419 2011 (UTC - 5:00)
System Uptime: 0 days 8:57:49.261
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff80003290670, fffff880037c9bf0, 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: fffff80003290670, Address of the instruction which caused the bugcheck
Arg3: fffff880037c9bf0, 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`03290670 49ff64c070 jmp qword ptr [r8+rax*8+70h]
CONTEXT: fffff880037c9bf0 -- (.cxr 0xfffff880037c9bf0)
rax=0000000000000000 rbx=fffff88000e7b850 rcx=fffffa8007b67050
rdx=fffffa8004137240 rsi=fffffa8004137240 rdi=fffffa800893e1a0
rip=fffff80003290670 rsp=fffff880037ca5c8 rbp=0000000000000000
r8=fffffa800885d8e0 r9=0000000000000000 r10=fffff880009e8ac0
r11=fffffa800827fad0 r12=0000000000000000 r13=fffffa800760ae70
r14=fffffa8007744070 r15=fffffa8004128000
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`03290670 49ff64c070 jmp qword ptr [r8+rax*8+70h] ds:002b:fffffa80`0885d950=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff80003290670
STACK_TEXT:
fffff880`037ca5c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IofCallDriver+0x50
FOLLOWUP_IP:
nt!IofCallDriver+50
fffff800`03290670 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: 4c1c44a9
STACK_COMMAND: .cxr 0xfffff880037c9bf0 ; kb
FAILURE_BUCKET_ID: X64_0x3B_nt!IofCallDriver+50
BUCKET_ID: X64_0x3B_nt!IofCallDriver+50
Followup: MachineOwner
---------