Microsoft (R) Windows Debugger Version 6.7.0005.1 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\WINDOWS\Minidump\Mini072807-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 Executable search path is: Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 2600.xpsp_sp2_qfe.070227-2300 Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a820 Debug session time: Sat Jul 28 10:36:14.241 2007 (GMT+2) System Uptime: 0 days 16:04:32.967 Loading Kernel Symbols .................................................................................................................................................................................................. Loading User Symbols Loading unloaded module list ............... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000007E, {c0000005, 1, f790a8ec, f790a5e8} *** WARNING: Unable to verify timestamp for VBoxUSBFlt.sys *** ERROR: Module load completed but symbols could not be loaded for VBoxUSBFlt.sys Probably caused by : VBoxUSBFlt.sys ( VBoxUSBFlt+380 ) Followup: MachineOwner --------- kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) 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: 00000001, The address that the exception occurred at Arg3: f790a8ec, Exception Record Address Arg4: f790a5e8, Context Record Address Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in "0x%08lx" verweist auf Speicher in "0x%08lx". Der Vorgang "%s" konnte nicht auf dem Speicher durchgef hrt werden. FAULTING_IP: +1 00000001 ?? ??? EXCEPTION_RECORD: f790a8ec -- (.exr 0xfffffffff790a8ec) ExceptionAddress: 00000001 ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 00000000 Parameter[1]: 00000001 Attempt to read from address 00000001 CONTEXT: f790a5e8 -- (.cxr 0xfffffffff790a5e8) eax=00000004 ebx=8854ad50 ecx=00000000 edx=00220003 esi=87d00460 edi=8853a008 eip=00000001 esp=f790a9b4 ebp=f790a9d8 iopl=0 nv up ei pl zr na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246 00000001 ?? ??? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: DRIVER_FAULT PROCESS_NAME: System ERROR_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in "0x%08lx" verweist auf Speicher in "0x%08lx". Der Vorgang "%s" konnte nicht auf dem Speicher durchgef hrt werden. READ_ADDRESS: 00000001 FAILED_INSTRUCTION_ADDRESS: +1 00000001 ?? ??? BUGCHECK_STR: 0x7E LAST_CONTROL_TRANSFER: from bac8fae1 to 00000001 STACK_TEXT: WARNING: Frame IP not in any known module. Following frames may be wrong. f790a9b0 bac8fae1 00000040 68627375 64657621 0x1 f790a9d8 bac8d1d8 8930d3b8 8853a008 f790aa0c usbhub!USBH_PdoDispatch+0x1e9 f790a9e8 804e37f7 87d003a8 8853a008 8853a008 usbhub!USBH_HubDispatch+0x48 f790a9f8 f77b7380 00000000 89962c58 87c43030 nt!IopfCallDriver+0x31 f790aa0c 804e37f7 00000000 8853a008 892e9230 VBoxUSBFlt+0x380 f790aa1c f77f04db 00220003 8853a12c 80000000 nt!IopfCallDriver+0x31 f790aa38 f77ef76b 87c62410 8853a008 89e2fda8 usbccgp!ParentInternalDeviceControl+0xbb f790aa5c f77ef5d3 87c62408 8853a008 0000000f usbccgp!USBC_InternalDeviceControl+0x3b f790aa98 804e37f7 87c62350 8853a008 892e9230 usbccgp!USBC_Dispatch+0x183 f790aaa8 f77f1231 80000000 00000002 00220003 nt!IopfCallDriver+0x31 f790aad8 f77ef786 892d37f8 8853a008 892d37f8 usbccgp!FunctionInternalDeviceControl+0x1c1 f790aafc f77ef5d3 892d37f0 8853a008 0000000f usbccgp!USBC_InternalDeviceControl+0x56 f790ab38 804e37f7 892d3738 8853a008 8853a008 usbccgp!USBC_Dispatch+0x183 f790ab48 ba8e2fd7 87c4327c 8930d3b8 87c43030 nt!IopfCallDriver+0x31 f790ab74 ba8e3609 87c43030 8930d3b8 00000002 hidusb!HumCallUSB+0x71 f790ab8c ba8e365a 87c43030 00000000 89c8d008 hidusb!HumAbortPendingRequests+0x4b f790aba4 ba8e376f 87c43030 89c8d008 87c43218 hidusb!HumRemoveDevice+0x32 f790abd4 f7407e91 87c43030 89c8d008 87c430fc hidusb!HumPnP+0x45 f790abe8 f740ea5f 87c43030 89c8d008 87c430fc HIDCLASS!HidpCallDriver+0x3f f790ac04 f740cf1c 87c430fc 89c8d008 89c8d1bc HIDCLASS!HidpRemoveDevice+0xa1 f790ac20 f740d076 87c430e8 89c8d008 f790ac40 HIDCLASS!HidpFdoPnp+0x72 f790ac30 f740892b 87c430e8 89c8d008 f790ac7c HIDCLASS!HidpIrpMajorPnp+0x1e f790ac40 804e37f7 87c43030 89c8d008 f790accc HIDCLASS!HidpMajorHandler+0x79 f790ac50 8059df8f 892d3738 892d3738 00000002 nt!IopfCallDriver+0x31 f790ac7c 8061ad54 87c43030 f790aca8 00000000 nt!IopSynchronousCall+0xb7 f790acd0 80531683 892d3738 00000002 00000000 nt!IopRemoveDevice+0x93 f790acf8 8061becf e2c65078 00000018 e12f4c50 nt!IopRemoveLockedDeviceNode+0x160 f790ad10 8061bf3b 89c9ca38 00000002 e12f4c50 nt!IopDeleteLockedDeviceNode+0x34 f790ad44 8061bfe6 87d003a8 022f4c50 00000002 nt!IopDeleteLockedDeviceNodes+0x3f f790ad74 804e426b 89c84da8 00000000 89e2fda8 nt!IopDelayedRemoveWorker+0x4b f790adac 8057cfce 89c84da8 00000000 00000000 nt!ExpWorkerThread+0x100 f790addc 804f88fa 804e4196 00000001 00000000 nt!PspSystemThreadStartup+0x34 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16 FOLLOWUP_IP: VBoxUSBFlt+380 f77b7380 ?? ??? SYMBOL_STACK_INDEX: 4 SYMBOL_NAME: VBoxUSBFlt+380 FOLLOWUP_NAME: MachineOwner MODULE_NAME: VBoxUSBFlt IMAGE_NAME: VBoxUSBFlt.sys DEBUG_FLR_IMAGE_TIMESTAMP: 45f6eb5d STACK_COMMAND: .cxr 0xfffffffff790a5e8 ; kb FAILURE_BUCKET_ID: 0x7E_BAD_IP_VBoxUSBFlt+380 BUCKET_ID: 0x7E_BAD_IP_VBoxUSBFlt+380 Followup: MachineOwner --------- kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) 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: 00000001, The address that the exception occurred at Arg3: f790a8ec, Exception Record Address Arg4: f790a5e8, Context Record Address Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in "0x%08lx" verweist auf Speicher in "0x%08lx". Der Vorgang "%s" konnte nicht auf dem Speicher durchgef hrt werden. FAULTING_IP: +1 00000001 ?? ??? EXCEPTION_RECORD: f790a8ec -- (.exr 0xfffffffff790a8ec) ExceptionAddress: 00000001 ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 00000000 Parameter[1]: 00000001 Attempt to read from address 00000001 CONTEXT: f790a5e8 -- (.cxr 0xfffffffff790a5e8) eax=00000004 ebx=8854ad50 ecx=00000000 edx=00220003 esi=87d00460 edi=8853a008 eip=00000001 esp=f790a9b4 ebp=f790a9d8 iopl=0 nv up ei pl zr na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246 00000001 ?? ??? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: DRIVER_FAULT PROCESS_NAME: System ERROR_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in "0x%08lx" verweist auf Speicher in "0x%08lx". Der Vorgang "%s" konnte nicht auf dem Speicher durchgef hrt werden. READ_ADDRESS: 00000001 FAILED_INSTRUCTION_ADDRESS: +1 00000001 ?? ??? BUGCHECK_STR: 0x7E LAST_CONTROL_TRANSFER: from bac8fae1 to 00000001 STACK_TEXT: WARNING: Frame IP not in any known module. Following frames may be wrong. f790a9b0 bac8fae1 00000040 68627375 64657621 0x1 f790a9d8 bac8d1d8 8930d3b8 8853a008 f790aa0c usbhub!USBH_PdoDispatch+0x1e9 f790a9e8 804e37f7 87d003a8 8853a008 8853a008 usbhub!USBH_HubDispatch+0x48 f790a9f8 f77b7380 00000000 89962c58 87c43030 nt!IopfCallDriver+0x31 f790aa0c 804e37f7 00000000 8853a008 892e9230 VBoxUSBFlt+0x380 f790aa1c f77f04db 00220003 8853a12c 80000000 nt!IopfCallDriver+0x31 f790aa38 f77ef76b 87c62410 8853a008 89e2fda8 usbccgp!ParentInternalDeviceControl+0xbb f790aa5c f77ef5d3 87c62408 8853a008 0000000f usbccgp!USBC_InternalDeviceControl+0x3b f790aa98 804e37f7 87c62350 8853a008 892e9230 usbccgp!USBC_Dispatch+0x183 f790aaa8 f77f1231 80000000 00000002 00220003 nt!IopfCallDriver+0x31 f790aad8 f77ef786 892d37f8 8853a008 892d37f8 usbccgp!FunctionInternalDeviceControl+0x1c1 f790aafc f77ef5d3 892d37f0 8853a008 0000000f usbccgp!USBC_InternalDeviceControl+0x56 f790ab38 804e37f7 892d3738 8853a008 8853a008 usbccgp!USBC_Dispatch+0x183 f790ab48 ba8e2fd7 87c4327c 8930d3b8 87c43030 nt!IopfCallDriver+0x31 f790ab74 ba8e3609 87c43030 8930d3b8 00000002 hidusb!HumCallUSB+0x71 f790ab8c ba8e365a 87c43030 00000000 89c8d008 hidusb!HumAbortPendingRequests+0x4b f790aba4 ba8e376f 87c43030 89c8d008 87c43218 hidusb!HumRemoveDevice+0x32 f790abd4 f7407e91 87c43030 89c8d008 87c430fc hidusb!HumPnP+0x45 f790abe8 f740ea5f 87c43030 89c8d008 87c430fc HIDCLASS!HidpCallDriver+0x3f f790ac04 f740cf1c 87c430fc 89c8d008 89c8d1bc HIDCLASS!HidpRemoveDevice+0xa1 f790ac20 f740d076 87c430e8 89c8d008 f790ac40 HIDCLASS!HidpFdoPnp+0x72 f790ac30 f740892b 87c430e8 89c8d008 f790ac7c HIDCLASS!HidpIrpMajorPnp+0x1e f790ac40 804e37f7 87c43030 89c8d008 f790accc HIDCLASS!HidpMajorHandler+0x79 f790ac50 8059df8f 892d3738 892d3738 00000002 nt!IopfCallDriver+0x31 f790ac7c 8061ad54 87c43030 f790aca8 00000000 nt!IopSynchronousCall+0xb7 f790acd0 80531683 892d3738 00000002 00000000 nt!IopRemoveDevice+0x93 f790acf8 8061becf e2c65078 00000018 e12f4c50 nt!IopRemoveLockedDeviceNode+0x160 f790ad10 8061bf3b 89c9ca38 00000002 e12f4c50 nt!IopDeleteLockedDeviceNode+0x34 f790ad44 8061bfe6 87d003a8 022f4c50 00000002 nt!IopDeleteLockedDeviceNodes+0x3f f790ad74 804e426b 89c84da8 00000000 89e2fda8 nt!IopDelayedRemoveWorker+0x4b f790adac 8057cfce 89c84da8 00000000 00000000 nt!ExpWorkerThread+0x100 f790addc 804f88fa 804e4196 00000001 00000000 nt!PspSystemThreadStartup+0x34 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16 FOLLOWUP_IP: VBoxUSBFlt+380 f77b7380 ?? ??? SYMBOL_STACK_INDEX: 4 SYMBOL_NAME: VBoxUSBFlt+380 FOLLOWUP_NAME: MachineOwner MODULE_NAME: VBoxUSBFlt IMAGE_NAME: VBoxUSBFlt.sys DEBUG_FLR_IMAGE_TIMESTAMP: 45f6eb5d STACK_COMMAND: .cxr 0xfffffffff790a5e8 ; kb FAILURE_BUCKET_ID: 0x7E_BAD_IP_VBoxUSBFlt+380 BUCKET_ID: 0x7E_BAD_IP_VBoxUSBFlt+380 Followup: MachineOwner --------- kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) 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: 00000001, The address that the exception occurred at Arg3: f790a8ec, Exception Record Address Arg4: f790a5e8, Context Record Address Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in "0x%08lx" verweist auf Speicher in "0x%08lx". Der Vorgang "%s" konnte nicht auf dem Speicher durchgef hrt werden. FAULTING_IP: +1 00000001 ?? ??? EXCEPTION_RECORD: f790a8ec -- (.exr 0xfffffffff790a8ec) ExceptionAddress: 00000001 ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 00000000 Parameter[1]: 00000001 Attempt to read from address 00000001 CONTEXT: f790a5e8 -- (.cxr 0xfffffffff790a5e8) eax=00000004 ebx=8854ad50 ecx=00000000 edx=00220003 esi=87d00460 edi=8853a008 eip=00000001 esp=f790a9b4 ebp=f790a9d8 iopl=0 nv up ei pl zr na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246 00000001 ?? ??? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: DRIVER_FAULT PROCESS_NAME: System ERROR_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in "0x%08lx" verweist auf Speicher in "0x%08lx". Der Vorgang "%s" konnte nicht auf dem Speicher durchgef hrt werden. READ_ADDRESS: 00000001 FAILED_INSTRUCTION_ADDRESS: +1 00000001 ?? ??? BUGCHECK_STR: 0x7E LAST_CONTROL_TRANSFER: from bac8fae1 to 00000001 STACK_TEXT: WARNING: Frame IP not in any known module. Following frames may be wrong. f790a9b0 bac8fae1 00000040 68627375 64657621 0x1 f790a9d8 bac8d1d8 8930d3b8 8853a008 f790aa0c usbhub!USBH_PdoDispatch+0x1e9 f790a9e8 804e37f7 87d003a8 8853a008 8853a008 usbhub!USBH_HubDispatch+0x48 f790a9f8 f77b7380 00000000 89962c58 87c43030 nt!IopfCallDriver+0x31 f790aa0c 804e37f7 00000000 8853a008 892e9230 VBoxUSBFlt+0x380 f790aa1c f77f04db 00220003 8853a12c 80000000 nt!IopfCallDriver+0x31 f790aa38 f77ef76b 87c62410 8853a008 89e2fda8 usbccgp!ParentInternalDeviceControl+0xbb f790aa5c f77ef5d3 87c62408 8853a008 0000000f usbccgp!USBC_InternalDeviceControl+0x3b f790aa98 804e37f7 87c62350 8853a008 892e9230 usbccgp!USBC_Dispatch+0x183 f790aaa8 f77f1231 80000000 00000002 00220003 nt!IopfCallDriver+0x31 f790aad8 f77ef786 892d37f8 8853a008 892d37f8 usbccgp!FunctionInternalDeviceControl+0x1c1 f790aafc f77ef5d3 892d37f0 8853a008 0000000f usbccgp!USBC_InternalDeviceControl+0x56 f790ab38 804e37f7 892d3738 8853a008 8853a008 usbccgp!USBC_Dispatch+0x183 f790ab48 ba8e2fd7 87c4327c 8930d3b8 87c43030 nt!IopfCallDriver+0x31 f790ab74 ba8e3609 87c43030 8930d3b8 00000002 hidusb!HumCallUSB+0x71 f790ab8c ba8e365a 87c43030 00000000 89c8d008 hidusb!HumAbortPendingRequests+0x4b f790aba4 ba8e376f 87c43030 89c8d008 87c43218 hidusb!HumRemoveDevice+0x32 f790abd4 f7407e91 87c43030 89c8d008 87c430fc hidusb!HumPnP+0x45 f790abe8 f740ea5f 87c43030 89c8d008 87c430fc HIDCLASS!HidpCallDriver+0x3f f790ac04 f740cf1c 87c430fc 89c8d008 89c8d1bc HIDCLASS!HidpRemoveDevice+0xa1 f790ac20 f740d076 87c430e8 89c8d008 f790ac40 HIDCLASS!HidpFdoPnp+0x72 f790ac30 f740892b 87c430e8 89c8d008 f790ac7c HIDCLASS!HidpIrpMajorPnp+0x1e f790ac40 804e37f7 87c43030 89c8d008 f790accc HIDCLASS!HidpMajorHandler+0x79 f790ac50 8059df8f 892d3738 892d3738 00000002 nt!IopfCallDriver+0x31 f790ac7c 8061ad54 87c43030 f790aca8 00000000 nt!IopSynchronousCall+0xb7 f790acd0 80531683 892d3738 00000002 00000000 nt!IopRemoveDevice+0x93 f790acf8 8061becf e2c65078 00000018 e12f4c50 nt!IopRemoveLockedDeviceNode+0x160 f790ad10 8061bf3b 89c9ca38 00000002 e12f4c50 nt!IopDeleteLockedDeviceNode+0x34 f790ad44 8061bfe6 87d003a8 022f4c50 00000002 nt!IopDeleteLockedDeviceNodes+0x3f f790ad74 804e426b 89c84da8 00000000 89e2fda8 nt!IopDelayedRemoveWorker+0x4b f790adac 8057cfce 89c84da8 00000000 00000000 nt!ExpWorkerThread+0x100 f790addc 804f88fa 804e4196 00000001 00000000 nt!PspSystemThreadStartup+0x34 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16 FOLLOWUP_IP: VBoxUSBFlt+380 f77b7380 ?? ??? SYMBOL_STACK_INDEX: 4 SYMBOL_NAME: VBoxUSBFlt+380 FOLLOWUP_NAME: MachineOwner MODULE_NAME: VBoxUSBFlt IMAGE_NAME: VBoxUSBFlt.sys DEBUG_FLR_IMAGE_TIMESTAMP: 45f6eb5d STACK_COMMAND: .cxr 0xfffffffff790a5e8 ; kb FAILURE_BUCKET_ID: 0x7E_BAD_IP_VBoxUSBFlt+380 BUCKET_ID: 0x7E_BAD_IP_VBoxUSBFlt+380 Followup: MachineOwner --------- kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) 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: 00000001, The address that the exception occurred at Arg3: f790a8ec, Exception Record Address Arg4: f790a5e8, Context Record Address Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in "0x%08lx" verweist auf Speicher in "0x%08lx". Der Vorgang "%s" konnte nicht auf dem Speicher durchgef hrt werden. FAULTING_IP: +1 00000001 ?? ??? EXCEPTION_RECORD: f790a8ec -- (.exr 0xfffffffff790a8ec) ExceptionAddress: 00000001 ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 00000000 Parameter[1]: 00000001 Attempt to read from address 00000001 CONTEXT: f790a5e8 -- (.cxr 0xfffffffff790a5e8) eax=00000004 ebx=8854ad50 ecx=00000000 edx=00220003 esi=87d00460 edi=8853a008 eip=00000001 esp=f790a9b4 ebp=f790a9d8 iopl=0 nv up ei pl zr na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246 00000001 ?? ??? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: DRIVER_FAULT PROCESS_NAME: System ERROR_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in "0x%08lx" verweist auf Speicher in "0x%08lx". Der Vorgang "%s" konnte nicht auf dem Speicher durchgef hrt werden. READ_ADDRESS: 00000001 FAILED_INSTRUCTION_ADDRESS: +1 00000001 ?? ??? BUGCHECK_STR: 0x7E LAST_CONTROL_TRANSFER: from bac8fae1 to 00000001 STACK_TEXT: WARNING: Frame IP not in any known module. Following frames may be wrong. f790a9b0 bac8fae1 00000040 68627375 64657621 0x1 f790a9d8 bac8d1d8 8930d3b8 8853a008 f790aa0c usbhub!USBH_PdoDispatch+0x1e9 f790a9e8 804e37f7 87d003a8 8853a008 8853a008 usbhub!USBH_HubDispatch+0x48 f790a9f8 f77b7380 00000000 89962c58 87c43030 nt!IopfCallDriver+0x31 f790aa0c 804e37f7 00000000 8853a008 892e9230 VBoxUSBFlt+0x380 f790aa1c f77f04db 00220003 8853a12c 80000000 nt!IopfCallDriver+0x31 f790aa38 f77ef76b 87c62410 8853a008 89e2fda8 usbccgp!ParentInternalDeviceControl+0xbb f790aa5c f77ef5d3 87c62408 8853a008 0000000f usbccgp!USBC_InternalDeviceControl+0x3b f790aa98 804e37f7 87c62350 8853a008 892e9230 usbccgp!USBC_Dispatch+0x183 f790aaa8 f77f1231 80000000 00000002 00220003 nt!IopfCallDriver+0x31 f790aad8 f77ef786 892d37f8 8853a008 892d37f8 usbccgp!FunctionInternalDeviceControl+0x1c1 f790aafc f77ef5d3 892d37f0 8853a008 0000000f usbccgp!USBC_InternalDeviceControl+0x56 f790ab38 804e37f7 892d3738 8853a008 8853a008 usbccgp!USBC_Dispatch+0x183 f790ab48 ba8e2fd7 87c4327c 8930d3b8 87c43030 nt!IopfCallDriver+0x31 f790ab74 ba8e3609 87c43030 8930d3b8 00000002 hidusb!HumCallUSB+0x71 f790ab8c ba8e365a 87c43030 00000000 89c8d008 hidusb!HumAbortPendingRequests+0x4b f790aba4 ba8e376f 87c43030 89c8d008 87c43218 hidusb!HumRemoveDevice+0x32 f790abd4 f7407e91 87c43030 89c8d008 87c430fc hidusb!HumPnP+0x45 f790abe8 f740ea5f 87c43030 89c8d008 87c430fc HIDCLASS!HidpCallDriver+0x3f f790ac04 f740cf1c 87c430fc 89c8d008 89c8d1bc HIDCLASS!HidpRemoveDevice+0xa1 f790ac20 f740d076 87c430e8 89c8d008 f790ac40 HIDCLASS!HidpFdoPnp+0x72 f790ac30 f740892b 87c430e8 89c8d008 f790ac7c HIDCLASS!HidpIrpMajorPnp+0x1e f790ac40 804e37f7 87c43030 89c8d008 f790accc HIDCLASS!HidpMajorHandler+0x79 f790ac50 8059df8f 892d3738 892d3738 00000002 nt!IopfCallDriver+0x31 f790ac7c 8061ad54 87c43030 f790aca8 00000000 nt!IopSynchronousCall+0xb7 f790acd0 80531683 892d3738 00000002 00000000 nt!IopRemoveDevice+0x93 f790acf8 8061becf e2c65078 00000018 e12f4c50 nt!IopRemoveLockedDeviceNode+0x160 f790ad10 8061bf3b 89c9ca38 00000002 e12f4c50 nt!IopDeleteLockedDeviceNode+0x34 f790ad44 8061bfe6 87d003a8 022f4c50 00000002 nt!IopDeleteLockedDeviceNodes+0x3f f790ad74 804e426b 89c84da8 00000000 89e2fda8 nt!IopDelayedRemoveWorker+0x4b f790adac 8057cfce 89c84da8 00000000 00000000 nt!ExpWorkerThread+0x100 f790addc 804f88fa 804e4196 00000001 00000000 nt!PspSystemThreadStartup+0x34 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16 FOLLOWUP_IP: VBoxUSBFlt+380 f77b7380 ?? ??? SYMBOL_STACK_INDEX: 4 SYMBOL_NAME: VBoxUSBFlt+380 FOLLOWUP_NAME: MachineOwner MODULE_NAME: VBoxUSBFlt IMAGE_NAME: VBoxUSBFlt.sys DEBUG_FLR_IMAGE_TIMESTAMP: 45f6eb5d STACK_COMMAND: .cxr 0xfffffffff790a5e8 ; kb FAILURE_BUCKET_ID: 0x7E_BAD_IP_VBoxUSBFlt+380 BUCKET_ID: 0x7E_BAD_IP_VBoxUSBFlt+380 Followup: MachineOwner ---------