BSOD al risveglio dall'ibernazione. Non avviene spesso, di media una volta a settimana:
Codice:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\Mini041509-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\Windows\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.18145.x86fre.vistasp1_gdr.080917-1612
Machine Name:
Kernel base = 0x82015000 PsLoadedModuleList = 0x8212cc70
Debug session time: Wed Apr 15 16:50:41.281 2009 (GMT+2)
System Uptime: 5 days 5:28:39.900
Loading Kernel Symbols
...............................................................
................................................................
.............................................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C2, {7, 110b, 80d0007, 8467df08}
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
Unable to load image \SystemRoot\system32\DRIVERS\VMNetSrv.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for VMNetSrv.sys
*** ERROR: Module load completed but symbols could not be loaded for VMNetSrv.sys
GetPointerFromAddress: unable to read from 8214c868
Unable to read MiSystemVaType memory at 8212c420
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
*** WARNING: Unable to verify timestamp for msrpc.sys
*** ERROR: Module load completed but symbols could not be loaded for msrpc.sys
*** WARNING: Unable to verify timestamp for avipbb.sys
*** ERROR: Module load completed but symbols could not be loaded for avipbb.sys
*** WARNING: Unable to verify timestamp for vmm.sys
*** ERROR: Module load completed but symbols could not be loaded for vmm.sys
*** WARNING: Unable to verify timestamp for VBoxDrv.sys
*** ERROR: Module load completed but symbols could not be loaded for VBoxDrv.sys
*** WARNING: Unable to verify timestamp for ATKACPI.sys
*** ERROR: Module load completed but symbols could not be loaded for ATKACPI.sys
*** ERROR: Module load completed but symbols could not be loaded for spldr.sys
*** WARNING: Unable to verify timestamp for avgntflt.sys
*** ERROR: Module load completed but symbols could not be loaded for avgntflt.sys
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
*** WARNING: Unable to verify timestamp for Rtlh86.sys
*** ERROR: Module load completed but symbols could not be loaded for Rtlh86.sys
*** WARNING: Unable to verify timestamp for VBoxUSBMon.sys
*** ERROR: Module load completed but symbols could not be loaded for VBoxUSBMon.sys
*** WARNING: Unable to verify timestamp for xpvcom.sys
*** ERROR: Module load completed but symbols could not be loaded for xpvcom.sys
*** WARNING: Unable to verify timestamp for NETw4v32.sys
*** ERROR: Module load completed but symbols could not be loaded for NETw4v32.sys
*** WARNING: Unable to verify timestamp for rimmptsk.sys
*** ERROR: Module load completed but symbols could not be loaded for rimmptsk.sys
*** WARNING: Unable to verify timestamp for rimsptsk.sys
*** ERROR: Module load completed but symbols could not be loaded for rimsptsk.sys
*** WARNING: Unable to verify timestamp for al9b0j30.SYS
*** ERROR: Module load completed but symbols could not be loaded for al9b0j30.SYS
*** WARNING: Unable to verify timestamp for tap0901.sys
*** ERROR: Module load completed but symbols could not be loaded for tap0901.sys
*** WARNING: Unable to verify timestamp for avgio.sys
*** ERROR: Module load completed but symbols could not be loaded for avgio.sys
*** WARNING: Unable to verify timestamp for RTKVHDA.sys
*** ERROR: Module load completed but symbols could not be loaded for RTKVHDA.sys
*** WARNING: Unable to verify timestamp for drmk.sys
*** ERROR: Module load completed but symbols could not be loaded for drmk.sys
*** WARNING: Unable to verify timestamp for ssmdrv.sys
*** ERROR: Module load completed but symbols could not be loaded for ssmdrv.sys
*** WARNING: Unable to verify timestamp for smserial.sys
*** ERROR: Module load completed but symbols could not be loaded for smserial.sys
*** WARNING: Unable to verify timestamp for Fs_Rec.SYS
*** ERROR: Module load completed but symbols could not be loaded for Fs_Rec.SYS
*** WARNING: Unable to verify timestamp for Null.SYS
*** ERROR: Module load completed but symbols could not be loaded for Null.SYS
*** WARNING: Unable to verify timestamp for Msfs.SYS
*** ERROR: Module load completed but symbols could not be loaded for Msfs.SYS
*** WARNING: Unable to verify timestamp for SynMini.sys
*** ERROR: Module load completed but symbols could not be loaded for SynMini.sys
*** WARNING: Unable to verify timestamp for SYNSAM.SYS
*** ERROR: Module load completed but symbols could not be loaded for SYNSAM.SYS
*** WARNING: Unable to verify timestamp for SynCamd.sys
*** ERROR: Module load completed but symbols could not be loaded for SynCamd.sys
*** WARNING: Unable to verify timestamp for SynPin.sys
*** ERROR: Module load completed but symbols could not be loaded for SynPin.sys
*** WARNING: Unable to verify timestamp for SynPipe.sys
*** ERROR: Module load completed but symbols could not be loaded for SynPipe.sys
*** WARNING: Unable to verify timestamp for SynScan.sys
*** ERROR: Module load completed but symbols could not be loaded for SynScan.sys
*** WARNING: Unable to verify timestamp for HIDPARSE.SYS
*** ERROR: Module load completed but symbols could not be loaded for HIDPARSE.SYS
*** WARNING: Unable to verify timestamp for asyncmac.sys
*** ERROR: Module load completed but symbols could not be loaded for asyncmac.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
*** WARNING: Unable to verify timestamp for TSDDD.dll
*** ERROR: Module load completed but symbols could not be loaded for TSDDD.dll
*** WARNING: Unable to verify timestamp for cdd.dll
*** ERROR: Module load completed but symbols could not be loaded for cdd.dll
*** WARNING: Unable to verify timestamp for spsys.sys
*** ERROR: Module load completed but symbols could not be loaded for spsys.sys
*** WARNING: Unable to verify timestamp for nwifi.sys
*** ERROR: Module load completed but symbols could not be loaded for nwifi.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for peauth.sys -
*** WARNING: Unable to verify timestamp for secdrv.SYS
*** ERROR: Module load completed but symbols could not be loaded for secdrv.SYS
*** WARNING: Unable to verify timestamp for RaInfo.sys
*** ERROR: Module load completed but symbols could not be loaded for RaInfo.sys
*** WARNING: Unable to verify timestamp for lmimirr.sys
*** ERROR: Module load completed but symbols could not be loaded for lmimirr.sys
*** WARNING: Unable to verify timestamp for LMIRfsDriver.sys
*** ERROR: Module load completed but symbols could not be loaded for LMIRfsDriver.sys
*** WARNING: Unable to verify timestamp for hiber_dumpata.sys
*** ERROR: Module load completed but symbols could not be loaded for hiber_dumpata.sys
*** WARNING: Unable to verify timestamp for hiber_atapi.sys
*** ERROR: Module load completed but symbols could not be loaded for hiber_atapi.sys
Probably caused by : VBoxNetFlt.sys ( VBoxNetFlt+2b6d )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BAD_POOL_CALLER (c2)
The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 00000007, Attempt to free pool which was already freed
Arg2: 0000110b, (reserved)
Arg3: 080d0007, Memory contents of the pool block
Arg4: 8467df08, Address of the block of pool being deallocated
Debugging Details:
------------------
GetPointerFromAddress: unable to read from 8214c868
Unable to read MiSystemVaType memory at 8212c420
POOL_ADDRESS: GetPointerFromAddress: unable to read from 8214c868
Unable to read MiSystemVaType memory at 8212c420
8467df08
BUGCHECK_STR: 0xc2_7
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 8210300c to 820e20e3
STACK_TEXT:
88f636d4 8210300c 000000c2 00000007 0000110b nt!KeBugCheckEx+0x1e
88f63748 88012370 8467df08 00000000 88f63774 nt!ExFreePoolWithTag+0x17f
88f63758 8c790b6d 8467df08 00000000 00000000 ndis!NdisFreeMemory+0x16
WARNING: Stack unwind information not available. Following frames may be wrong.
88f63774 8c790ff8 81199074 81199280 81199018 VBoxNetFlt+0x2b6d
88f63794 8c791447 8c79d630 00000000 81199018 VBoxNetFlt+0x2ff8
88f637b8 8c78f20d 81199018 88f638e8 88f63814 VBoxNetFlt+0x3447
88f637d8 8c78f349 8c79d630 88f63814 88f63804 VBoxNetFlt+0x120d
88f637fc 8c791d04 8c79d630 88f63814 88f6390c VBoxNetFlt+0x1349
88f638fc 8c7922ad 88f6391c 84b2ca88 00000000 VBoxNetFlt+0x3d04
88f63924 880e14b1 88f639c0 88f6394c 860802cc VBoxNetFlt+0x42ad
88f639b8 880e1129 00000000 84043f00 88041918 ndis!ndisInitializeBinding+0x23b
88f63a44 880eff67 860522a8 00000000 00000000 ndis!ndisCheckAdapterBindings+0x170
88f63a68 880f01e1 00000000 856ce3a0 00000000 ndis!ndisIMInitializeDeviceInstance+0x93
88f63a88 8cb58a83 86080708 87b23850 856ce3a0 ndis!NdisIMInitializeDeviceInstanceEx+0x100
88f63b58 880e14b1 88f63bf4 88f63b80 85f3a734 VMNetSrv+0x2a83
88f63be0 845ce6a0 01f63c78 88f63c78 880e1129 ndis!ndisInitializeBinding+0x23b
88f63bec 880e1129 00000000 84e7e578 00000000 0x845ce6a0
88f63c78 880f6e89 85f4f438 00000000 00000000 ndis!ndisCheckAdapterBindings+0x170
88f63d34 880df013 8504e0f8 85f4f438 88f63d7c ndis!ndisDevicePowerOn+0x515
88f63d44 8204d445 8504e0f8 00000000 840a6020 ndis!ndisWorkItemHandler+0xe
88f63d7c 821eab18 8504e0f8 6301e6f5 00000000 nt!ExpWorkerThread+0xfd
88f63dc0 82043a2e 8204d348 00000001 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
VBoxNetFlt+2b6d
8c790b6d ?? ???
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: VBoxNetFlt+2b6d
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: VBoxNetFlt
IMAGE_NAME: VBoxNetFlt.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 497765d0
FAILURE_BUCKET_ID: 0xc2_7_VBoxNetFlt+2b6d
BUCKET_ID: 0xc2_7_VBoxNetFlt+2b6d
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BAD_POOL_CALLER (c2)
The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 00000007, Attempt to free pool which was already freed
Arg2: 0000110b, (reserved)
Arg3: 080d0007, Memory contents of the pool block
Arg4: 8467df08, Address of the block of pool being deallocated
Debugging Details:
------------------
GetPointerFromAddress: unable to read from 8214c868
Unable to read MiSystemVaType memory at 8212c420
POOL_ADDRESS: GetPointerFromAddress: unable to read from 8214c868
Unable to read MiSystemVaType memory at 8212c420
8467df08
BUGCHECK_STR: 0xc2_7
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 8210300c to 820e20e3
STACK_TEXT:
88f636d4 8210300c 000000c2 00000007 0000110b nt!KeBugCheckEx+0x1e
88f63748 88012370 8467df08 00000000 88f63774 nt!ExFreePoolWithTag+0x17f
88f63758 8c790b6d 8467df08 00000000 00000000 ndis!NdisFreeMemory+0x16
WARNING: Stack unwind information not available. Following frames may be wrong.
88f63774 8c790ff8 81199074 81199280 81199018 VBoxNetFlt+0x2b6d
88f63794 8c791447 8c79d630 00000000 81199018 VBoxNetFlt+0x2ff8
88f637b8 8c78f20d 81199018 88f638e8 88f63814 VBoxNetFlt+0x3447
88f637d8 8c78f349 8c79d630 88f63814 88f63804 VBoxNetFlt+0x120d
88f637fc 8c791d04 8c79d630 88f63814 88f6390c VBoxNetFlt+0x1349
88f638fc 8c7922ad 88f6391c 84b2ca88 00000000 VBoxNetFlt+0x3d04
88f63924 880e14b1 88f639c0 88f6394c 860802cc VBoxNetFlt+0x42ad
88f639b8 880e1129 00000000 84043f00 88041918 ndis!ndisInitializeBinding+0x23b
88f63a44 880eff67 860522a8 00000000 00000000 ndis!ndisCheckAdapterBindings+0x170
88f63a68 880f01e1 00000000 856ce3a0 00000000 ndis!ndisIMInitializeDeviceInstance+0x93
88f63a88 8cb58a83 86080708 87b23850 856ce3a0 ndis!NdisIMInitializeDeviceInstanceEx+0x100
88f63b58 880e14b1 88f63bf4 88f63b80 85f3a734 VMNetSrv+0x2a83
88f63be0 845ce6a0 01f63c78 88f63c78 880e1129 ndis!ndisInitializeBinding+0x23b
88f63bec 880e1129 00000000 84e7e578 00000000 0x845ce6a0
88f63c78 880f6e89 85f4f438 00000000 00000000 ndis!ndisCheckAdapterBindings+0x170
88f63d34 880df013 8504e0f8 85f4f438 88f63d7c ndis!ndisDevicePowerOn+0x515
88f63d44 8204d445 8504e0f8 00000000 840a6020 ndis!ndisWorkItemHandler+0xe
88f63d7c 821eab18 8504e0f8 6301e6f5 00000000 nt!ExpWorkerThread+0xfd
88f63dc0 82043a2e 8204d348 00000001 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
VBoxNetFlt+2b6d
8c790b6d ?? ???
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: VBoxNetFlt+2b6d
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: VBoxNetFlt
IMAGE_NAME: VBoxNetFlt.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 497765d0
FAILURE_BUCKET_ID: 0xc2_7_VBoxNetFlt+2b6d
BUCKET_ID: 0xc2_7_VBoxNetFlt+2b6d
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BAD_POOL_CALLER (c2)
The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 00000007, Attempt to free pool which was already freed
Arg2: 0000110b, (reserved)
Arg3: 080d0007, Memory contents of the pool block
Arg4: 8467df08, Address of the block of pool being deallocated
Debugging Details:
------------------
GetPointerFromAddress: unable to read from 8214c868
Unable to read MiSystemVaType memory at 8212c420
POOL_ADDRESS: GetPointerFromAddress: unable to read from 8214c868
Unable to read MiSystemVaType memory at 8212c420
8467df08
BUGCHECK_STR: 0xc2_7
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 8210300c to 820e20e3
STACK_TEXT:
88f636d4 8210300c 000000c2 00000007 0000110b nt!KeBugCheckEx+0x1e
88f63748 88012370 8467df08 00000000 88f63774 nt!ExFreePoolWithTag+0x17f
88f63758 8c790b6d 8467df08 00000000 00000000 ndis!NdisFreeMemory+0x16
WARNING: Stack unwind information not available. Following frames may be wrong.
88f63774 8c790ff8 81199074 81199280 81199018 VBoxNetFlt+0x2b6d
88f63794 8c791447 8c79d630 00000000 81199018 VBoxNetFlt+0x2ff8
88f637b8 8c78f20d 81199018 88f638e8 88f63814 VBoxNetFlt+0x3447
88f637d8 8c78f349 8c79d630 88f63814 88f63804 VBoxNetFlt+0x120d
88f637fc 8c791d04 8c79d630 88f63814 88f6390c VBoxNetFlt+0x1349
88f638fc 8c7922ad 88f6391c 84b2ca88 00000000 VBoxNetFlt+0x3d04
88f63924 880e14b1 88f639c0 88f6394c 860802cc VBoxNetFlt+0x42ad
88f639b8 880e1129 00000000 84043f00 88041918 ndis!ndisInitializeBinding+0x23b
88f63a44 880eff67 860522a8 00000000 00000000 ndis!ndisCheckAdapterBindings+0x170
88f63a68 880f01e1 00000000 856ce3a0 00000000 ndis!ndisIMInitializeDeviceInstance+0x93
88f63a88 8cb58a83 86080708 87b23850 856ce3a0 ndis!NdisIMInitializeDeviceInstanceEx+0x100
88f63b58 880e14b1 88f63bf4 88f63b80 85f3a734 VMNetSrv+0x2a83
88f63be0 845ce6a0 01f63c78 88f63c78 880e1129 ndis!ndisInitializeBinding+0x23b
88f63bec 880e1129 00000000 84e7e578 00000000 0x845ce6a0
88f63c78 880f6e89 85f4f438 00000000 00000000 ndis!ndisCheckAdapterBindings+0x170
88f63d34 880df013 8504e0f8 85f4f438 88f63d7c ndis!ndisDevicePowerOn+0x515
88f63d44 8204d445 8504e0f8 00000000 840a6020 ndis!ndisWorkItemHandler+0xe
88f63d7c 821eab18 8504e0f8 6301e6f5 00000000 nt!ExpWorkerThread+0xfd
88f63dc0 82043a2e 8204d348 00000001 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
VBoxNetFlt+2b6d
8c790b6d ?? ???
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: VBoxNetFlt+2b6d
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: VBoxNetFlt
IMAGE_NAME: VBoxNetFlt.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 497765d0
FAILURE_BUCKET_ID: 0xc2_7_VBoxNetFlt+2b6d
BUCKET_ID: 0xc2_7_VBoxNetFlt+2b6d
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BAD_POOL_CALLER (c2)
The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 00000007, Attempt to free pool which was already freed
Arg2: 0000110b, (reserved)
Arg3: 080d0007, Memory contents of the pool block
Arg4: 8467df08, Address of the block of pool being deallocated
Debugging Details:
------------------
GetPointerFromAddress: unable to read from 8214c868
Unable to read MiSystemVaType memory at 8212c420
POOL_ADDRESS: GetPointerFromAddress: unable to read from 8214c868
Unable to read MiSystemVaType memory at 8212c420
8467df08
BUGCHECK_STR: 0xc2_7
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 8210300c to 820e20e3
STACK_TEXT:
88f636d4 8210300c 000000c2 00000007 0000110b nt!KeBugCheckEx+0x1e
88f63748 88012370 8467df08 00000000 88f63774 nt!ExFreePoolWithTag+0x17f
88f63758 8c790b6d 8467df08 00000000 00000000 ndis!NdisFreeMemory+0x16
WARNING: Stack unwind information not available. Following frames may be wrong.
88f63774 8c790ff8 81199074 81199280 81199018 VBoxNetFlt+0x2b6d
88f63794 8c791447 8c79d630 00000000 81199018 VBoxNetFlt+0x2ff8
88f637b8 8c78f20d 81199018 88f638e8 88f63814 VBoxNetFlt+0x3447
88f637d8 8c78f349 8c79d630 88f63814 88f63804 VBoxNetFlt+0x120d
88f637fc 8c791d04 8c79d630 88f63814 88f6390c VBoxNetFlt+0x1349
88f638fc 8c7922ad 88f6391c 84b2ca88 00000000 VBoxNetFlt+0x3d04
88f63924 880e14b1 88f639c0 88f6394c 860802cc VBoxNetFlt+0x42ad
88f639b8 880e1129 00000000 84043f00 88041918 ndis!ndisInitializeBinding+0x23b
88f63a44 880eff67 860522a8 00000000 00000000 ndis!ndisCheckAdapterBindings+0x170
88f63a68 880f01e1 00000000 856ce3a0 00000000 ndis!ndisIMInitializeDeviceInstance+0x93
88f63a88 8cb58a83 86080708 87b23850 856ce3a0 ndis!NdisIMInitializeDeviceInstanceEx+0x100
88f63b58 880e14b1 88f63bf4 88f63b80 85f3a734 VMNetSrv+0x2a83
88f63be0 845ce6a0 01f63c78 88f63c78 880e1129 ndis!ndisInitializeBinding+0x23b
88f63bec 880e1129 00000000 84e7e578 00000000 0x845ce6a0
88f63c78 880f6e89 85f4f438 00000000 00000000 ndis!ndisCheckAdapterBindings+0x170
88f63d34 880df013 8504e0f8 85f4f438 88f63d7c ndis!ndisDevicePowerOn+0x515
88f63d44 8204d445 8504e0f8 00000000 840a6020 ndis!ndisWorkItemHandler+0xe
88f63d7c 821eab18 8504e0f8 6301e6f5 00000000 nt!ExpWorkerThread+0xfd
88f63dc0 82043a2e 8204d348 00000001 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
VBoxNetFlt+2b6d
8c790b6d ?? ???
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: VBoxNetFlt+2b6d
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: VBoxNetFlt
IMAGE_NAME: VBoxNetFlt.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 497765d0
FAILURE_BUCKET_ID: 0xc2_7_VBoxNetFlt+2b6d
BUCKET_ID: 0xc2_7_VBoxNetFlt+2b6d
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BAD_POOL_CALLER (c2)
The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 00000007, Attempt to free pool which was already freed
Arg2: 0000110b, (reserved)
Arg3: 080d0007, Memory contents of the pool block
Arg4: 8467df08, Address of the block of pool being deallocated
Debugging Details:
------------------
GetPointerFromAddress: unable to read from 8214c868
Unable to read MiSystemVaType memory at 8212c420
POOL_ADDRESS: GetPointerFromAddress: unable to read from 8214c868
Unable to read MiSystemVaType memory at 8212c420
8467df08
BUGCHECK_STR: 0xc2_7
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 8210300c to 820e20e3
STACK_TEXT:
88f636d4 8210300c 000000c2 00000007 0000110b nt!KeBugCheckEx+0x1e
88f63748 88012370 8467df08 00000000 88f63774 nt!ExFreePoolWithTag+0x17f
88f63758 8c790b6d 8467df08 00000000 00000000 ndis!NdisFreeMemory+0x16
WARNING: Stack unwind information not available. Following frames may be wrong.
88f63774 8c790ff8 81199074 81199280 81199018 VBoxNetFlt+0x2b6d
88f63794 8c791447 8c79d630 00000000 81199018 VBoxNetFlt+0x2ff8
88f637b8 8c78f20d 81199018 88f638e8 88f63814 VBoxNetFlt+0x3447
88f637d8 8c78f349 8c79d630 88f63814 88f63804 VBoxNetFlt+0x120d
88f637fc 8c791d04 8c79d630 88f63814 88f6390c VBoxNetFlt+0x1349
88f638fc 8c7922ad 88f6391c 84b2ca88 00000000 VBoxNetFlt+0x3d04
88f63924 880e14b1 88f639c0 88f6394c 860802cc VBoxNetFlt+0x42ad
88f639b8 880e1129 00000000 84043f00 88041918 ndis!ndisInitializeBinding+0x23b
88f63a44 880eff67 860522a8 00000000 00000000 ndis!ndisCheckAdapterBindings+0x170
88f63a68 880f01e1 00000000 856ce3a0 00000000 ndis!ndisIMInitializeDeviceInstance+0x93
88f63a88 8cb58a83 86080708 87b23850 856ce3a0 ndis!NdisIMInitializeDeviceInstanceEx+0x100
88f63b58 880e14b1 88f63bf4 88f63b80 85f3a734 VMNetSrv+0x2a83
88f63be0 845ce6a0 01f63c78 88f63c78 880e1129 ndis!ndisInitializeBinding+0x23b
88f63bec 880e1129 00000000 84e7e578 00000000 0x845ce6a0
88f63c78 880f6e89 85f4f438 00000000 00000000 ndis!ndisCheckAdapterBindings+0x170
88f63d34 880df013 8504e0f8 85f4f438 88f63d7c ndis!ndisDevicePowerOn+0x515
88f63d44 8204d445 8504e0f8 00000000 840a6020 ndis!ndisWorkItemHandler+0xe
88f63d7c 821eab18 8504e0f8 6301e6f5 00000000 nt!ExpWorkerThread+0xfd
88f63dc0 82043a2e 8204d348 00000001 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
VBoxNetFlt+2b6d
8c790b6d ?? ???
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: VBoxNetFlt+2b6d
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: VBoxNetFlt
IMAGE_NAME: VBoxNetFlt.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 497765d0
FAILURE_BUCKET_ID: 0xc2_7_VBoxNetFlt+2b6d
BUCKET_ID: 0xc2_7_VBoxNetFlt+2b6d
Followup: MachineOwner
---------
Sembrerebbe VirtualBox. Voi che dite?
Non ho capito come si fa l'analyze -v
