Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [E:\022811-61667-01.dmp]
BugCheck 7F, {8, 80050031, 6f8, fffff800046b3128}
Unable to load image \SystemRoot\system32\DRIVERS\NETw5s64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for NETw5s64.sys
*** ERROR: Module load completed but symbols could not be loaded for NETw5s64.sys
Probably caused by : NETw5s64.sys ( NETw5s64+218f )
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: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffff800046b3128
Debugging Details:
------------------
OVERLAPPED_MODULE: Address regions for 'BHDrvx64' and 'BHDrvx64.sys' overlap
BUGCHECK_STR: 0x7f_8
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff80004691be9 to fffff80004692640
STACK_TEXT:
fffff880`009efde8 fffff800`04691be9 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff880`009efdf0 fffff800`046900b2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`009eff30 fffff800`046b3128 : 00000000`00000000 00000000`4434475f fffff880`0ffff1b8 fffff800`047bd90e : nt!KiDoubleFaultAbort+0xb2
fffff880`0ffff000 fffff800`047bd90e : 00000000`00000000 00fcfcfc`00fcfcfc 00fcfcfc`00fcfcfc 00fcfcfc`00fcfcfc : nt!ExpAllocateBigPool+0x8
fffff880`0ffff020 fffff880`01a621bc : 00000000`00002711 fffff880`0ffff1b8 fffff800`0469e74c 00000000`00000011 : nt!ExAllocatePoolWithTag+0x82e
fffff880`0ffff110 fffff880`0805818f : 00000000`00000000 fffffa80`10ea0680 fffffa80`0c66e8b0 00001f80`00fc02fc : ndis!NdisAllocateMemoryWithTag+0x1c
fffff880`0ffff140 00000000`00000000 : fffffa80`10ea0680 fffffa80`0c66e8b0 00001f80`00fc02fc fffffa80`0c665ab0 : NETw5s64+0x218f
STACK_COMMAND: kb
FOLLOWUP_IP:
NETw5s64+218f
fffff880`0805818f ?? ???
SYMBOL_STACK_INDEX: 6
SYMBOL_NAME: NETw5s64+218f
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: NETw5s64
IMAGE_NAME: NETw5s64.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4aafedb7
FAILURE_BUCKET_ID: X64_0x7f_8_NETw5s64+218f
BUCKET_ID: X64_0x7f_8_NETw5s64+218f
Followup: MachineOwner
---------
