Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\New folder\101910-54943-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*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
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e0e000 PsLoadedModuleList = 0xfffff800`0304be50
Debug session time: Mon Oct 18 22:10:59.719 2010 (GMT-4)
System Uptime: 0 days 1:32:12.639
Loading Kernel Symbols
.
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
..............................................................
................................................................
....................................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000009F, {4, 258, fffffa80036df680, fffff80000b9c510}
Unable to load image \SystemRoot\system32\DRIVERS\VBoxNetFlt.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for VBoxNetFlt.sys
*** ERROR: Module load completed but symbols could not be loaded for VBoxNetFlt.sys
[COLOR=Red][B]Probably caused by : VBoxNetFlt.sys ( VBoxNetFlt+938f )[/B][/COLOR]
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
subsystem.
Arg2: 0000000000000258, Timeout in seconds.
Arg3: fffffa80036df680, The thread currently holding on to the Pnp lock.
Arg4: fffff80000b9c510
Debugging Details:
------------------
DRVPOWERSTATE_SUBCODE: 4
FAULTING_THREAD: fffffa80036df680
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff80002e85992 to fffff80002e845da
STACK_TEXT:
fffff880`031df1f0 fffff800`02e85992 : fffffa80`036df680 fffffa80`036df680 00000000`00000000 00000000`0000000c : nt!KiSwapContext+0x7a
fffff880`031df330 fffff800`02e87cff : 00000000`00000246 fffff800`02e8624a fffff800`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x1d2
fffff880`031df3c0 fffff800`02edc906 : fffff880`018dc100 fffff880`00000000 00000000`00000000 fffff880`031df600 : nt!KeWaitForSingleObject+0x19f
fffff880`031df460 fffff880`019362b3 : fffffa80`0813d010 fffff880`031df6e8 fffff880`01967fe0 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x13066
fffff880`031df4d0 fffff880`016c491e : fffffa80`0813d840 fffffa80`05bc31a0 fffffa80`041e9860 fffffa80`0813d840 : tcpip!FlUnbindAdapter+0x83
fffff880`031df530 fffff880`016c560f : fffffa80`05bc31a0 00000000`00000000 fffffa80`05add6c0 00000000`00000000 : ndis!ndisUnbindProtocol+0x1fe
fffff880`031df640 fffff880`016c6c6b : 00000000`00000001 fffffa80`05bc31a0 fffff880`031df6d0 fffffa80`05add6c0 : ndis!ndisCloseMiniportBindings+0x2df
fffff880`031df750 fffff880`016923df : fffffa80`05bc31a0 fffffa80`05bc31a0 00000000`00000001 00000000`00000000 : ndis!ndisPnPRemoveDevice+0x25b
fffff880`031df8f0 fffff880`0400938f : fffffa80`08126bd0 fffffa80`05bae100 fffff880`031dfb28 00000000`00000000 : ndis!NdisIMDeInitializeDeviceInstance+0x8f
fffff880`031df930 fffffa80`08126bd0 : fffffa80`05bae100 fffff880`031dfb28 00000000`00000000 fffffa80`08126bd0 : VBoxNetFlt+0x938f
fffff880`031df938 fffffa80`05bae100 : fffff880`031dfb28 00000000`00000000 fffffa80`08126bd0 fffff880`04007f6c : 0xfffffa80`08126bd0
fffff880`031df940 fffff880`031dfb28 : 00000000`00000000 fffffa80`08126bd0 fffff880`04007f6c 00000000`00000000 : 0xfffffa80`05bae100
fffff880`031df948 00000000`00000000 : fffffa80`08126bd0 fffff880`04007f6c 00000000`00000000 00000000`00000001 : 0xfffff880`031dfb28
STACK_COMMAND: .thread 0xfffffa80036df680 ; kb
FOLLOWUP_IP:
VBoxNetFlt+938f
fffff880`0400938f ?? ???
SYMBOL_STACK_INDEX: 9
SYMBOL_NAME: VBoxNetFlt+938f
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: VBoxNetFlt
IMAGE_NAME: VBoxNetFlt.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4c24afec
FAILURE_BUCKET_ID: X64_0x9F_VBoxNetFlt+938f
BUCKET_ID: X64_0x9F_VBoxNetFlt+938f
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
subsystem.
Arg2: 0000000000000258, Timeout in seconds.
Arg3: fffffa80036df680, The thread currently holding on to the Pnp lock.
Arg4: fffff80000b9c510
Debugging Details:
------------------
DRVPOWERSTATE_SUBCODE: 4
FAULTING_THREAD: fffffa80036df680
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff80002e85992 to fffff80002e845da
STACK_TEXT:
fffff880`031df1f0 fffff800`02e85992 : fffffa80`036df680 fffffa80`036df680 00000000`00000000 00000000`0000000c : nt!KiSwapContext+0x7a
fffff880`031df330 fffff800`02e87cff : 00000000`00000246 fffff800`02e8624a fffff800`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x1d2
fffff880`031df3c0 fffff800`02edc906 : fffff880`018dc100 fffff880`00000000 00000000`00000000 fffff880`031df600 : nt!KeWaitForSingleObject+0x19f
fffff880`031df460 fffff880`019362b3 : fffffa80`0813d010 fffff880`031df6e8 fffff880`01967fe0 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x13066
fffff880`031df4d0 fffff880`016c491e : fffffa80`0813d840 fffffa80`05bc31a0 fffffa80`041e9860 fffffa80`0813d840 : tcpip!FlUnbindAdapter+0x83
fffff880`031df530 fffff880`016c560f : fffffa80`05bc31a0 00000000`00000000 fffffa80`05add6c0 00000000`00000000 : ndis!ndisUnbindProtocol+0x1fe
fffff880`031df640 fffff880`016c6c6b : 00000000`00000001 fffffa80`05bc31a0 fffff880`031df6d0 fffffa80`05add6c0 : ndis!ndisCloseMiniportBindings+0x2df
fffff880`031df750 fffff880`016923df : fffffa80`05bc31a0 fffffa80`05bc31a0 00000000`00000001 00000000`00000000 : ndis!ndisPnPRemoveDevice+0x25b
fffff880`031df8f0 fffff880`0400938f : fffffa80`08126bd0 fffffa80`05bae100 fffff880`031dfb28 00000000`00000000 : ndis!NdisIMDeInitializeDeviceInstance+0x8f
fffff880`031df930 fffffa80`08126bd0 : fffffa80`05bae100 fffff880`031dfb28 00000000`00000000 fffffa80`08126bd0 : VBoxNetFlt+0x938f
fffff880`031df938 fffffa80`05bae100 : fffff880`031dfb28 00000000`00000000 fffffa80`08126bd0 fffff880`04007f6c : 0xfffffa80`08126bd0
fffff880`031df940 fffff880`031dfb28 : 00000000`00000000 fffffa80`08126bd0 fffff880`04007f6c 00000000`00000000 : 0xfffffa80`05bae100
fffff880`031df948 00000000`00000000 : fffffa80`08126bd0 fffff880`04007f6c 00000000`00000000 00000000`00000001 : 0xfffff880`031dfb28
STACK_COMMAND: .thread 0xfffffa80036df680 ; kb
FOLLOWUP_IP:
VBoxNetFlt+938f
fffff880`0400938f ?? ???
SYMBOL_STACK_INDEX: 9
SYMBOL_NAME: VBoxNetFlt+938f
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: VBoxNetFlt
IMAGE_NAME: VBoxNetFlt.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4c24afec
FAILURE_BUCKET_ID: X64_0x9F_VBoxNetFlt+938f
BUCKET_ID: X64_0x9F_VBoxNetFlt+938f
Followup: MachineOwner
---------