| 1 |
|
|---|
| 2 | Microsoft (R) Windows Debugger Version 6.7.0005.1
|
|---|
| 3 | Copyright (c) Microsoft Corporation. All rights reserved.
|
|---|
| 4 |
|
|---|
| 5 |
|
|---|
| 6 | Loading Dump File [C:\WINDOWS\Minidump\Mini072807-01.dmp]
|
|---|
| 7 | Mini Kernel Dump File: Only registers and stack trace are available
|
|---|
| 8 |
|
|---|
| 9 | Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
|
|---|
| 10 | Executable search path is:
|
|---|
| 11 | Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
|
|---|
| 12 | Product: WinNt, suite: TerminalServer SingleUserTS
|
|---|
| 13 | Built by: 2600.xpsp_sp2_qfe.070227-2300
|
|---|
| 14 | Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a820
|
|---|
| 15 | Debug session time: Sat Jul 28 10:36:14.241 2007 (GMT+2)
|
|---|
| 16 | System Uptime: 0 days 16:04:32.967
|
|---|
| 17 | Loading Kernel Symbols
|
|---|
| 18 | ..................................................................................................................................................................................................
|
|---|
| 19 | Loading User Symbols
|
|---|
| 20 | Loading unloaded module list
|
|---|
| 21 | ...............
|
|---|
| 22 | *******************************************************************************
|
|---|
| 23 | * *
|
|---|
| 24 | * Bugcheck Analysis *
|
|---|
| 25 | * *
|
|---|
| 26 | *******************************************************************************
|
|---|
| 27 |
|
|---|
| 28 | Use !analyze -v to get detailed debugging information.
|
|---|
| 29 |
|
|---|
| 30 | BugCheck 1000007E, {c0000005, 1, f790a8ec, f790a5e8}
|
|---|
| 31 |
|
|---|
| 32 | *** WARNING: Unable to verify timestamp for VBoxUSBFlt.sys
|
|---|
| 33 | *** ERROR: Module load completed but symbols could not be loaded for VBoxUSBFlt.sys
|
|---|
| 34 | Probably caused by : VBoxUSBFlt.sys ( VBoxUSBFlt+380 )
|
|---|
| 35 |
|
|---|
| 36 | Followup: MachineOwner
|
|---|
| 37 | ---------
|
|---|
| 38 |
|
|---|
| 39 | kd> !analyze -v
|
|---|
| 40 | *******************************************************************************
|
|---|
| 41 | * *
|
|---|
| 42 | * Bugcheck Analysis *
|
|---|
| 43 | * *
|
|---|
| 44 | *******************************************************************************
|
|---|
| 45 |
|
|---|
| 46 | SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
|
|---|
| 47 | This is a very common bugcheck. Usually the exception address pinpoints
|
|---|
| 48 | the driver/function that caused the problem. Always note this address
|
|---|
| 49 | as well as the link date of the driver/image that contains this address.
|
|---|
| 50 | Some common problems are exception code 0x80000003. This means a hard
|
|---|
| 51 | coded breakpoint or assertion was hit, but this system was booted
|
|---|
| 52 | /NODEBUG. This is not supposed to happen as developers should never have
|
|---|
| 53 | hardcoded breakpoints in retail code, but ...
|
|---|
| 54 | If this happens, make sure a debugger gets connected, and the
|
|---|
| 55 | system is booted /DEBUG. This will let us see why this breakpoint is
|
|---|
| 56 | happening.
|
|---|
| 57 | Arguments:
|
|---|
| 58 | Arg1: c0000005, The exception code that was not handled
|
|---|
| 59 | Arg2: 00000001, The address that the exception occurred at
|
|---|
| 60 | Arg3: f790a8ec, Exception Record Address
|
|---|
| 61 | Arg4: f790a5e8, Context Record Address
|
|---|
| 62 |
|
|---|
| 63 | Debugging Details:
|
|---|
| 64 | ------------------
|
|---|
| 65 |
|
|---|
| 66 |
|
|---|
| 67 | 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.
|
|---|
| 68 |
|
|---|
| 69 | FAULTING_IP:
|
|---|
| 70 | +1
|
|---|
| 71 | 00000001 ?? ???
|
|---|
| 72 |
|
|---|
| 73 | EXCEPTION_RECORD: f790a8ec -- (.exr 0xfffffffff790a8ec)
|
|---|
| 74 | ExceptionAddress: 00000001
|
|---|
| 75 | ExceptionCode: c0000005 (Access violation)
|
|---|
| 76 | ExceptionFlags: 00000000
|
|---|
| 77 | NumberParameters: 2
|
|---|
| 78 | Parameter[0]: 00000000
|
|---|
| 79 | Parameter[1]: 00000001
|
|---|
| 80 | Attempt to read from address 00000001
|
|---|
| 81 |
|
|---|
| 82 | CONTEXT: f790a5e8 -- (.cxr 0xfffffffff790a5e8)
|
|---|
| 83 | eax=00000004 ebx=8854ad50 ecx=00000000 edx=00220003 esi=87d00460 edi=8853a008
|
|---|
| 84 | eip=00000001 esp=f790a9b4 ebp=f790a9d8 iopl=0 nv up ei pl zr na pe nc
|
|---|
| 85 | cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
|
|---|
| 86 | 00000001 ?? ???
|
|---|
| 87 | Resetting default scope
|
|---|
| 88 |
|
|---|
| 89 | CUSTOMER_CRASH_COUNT: 1
|
|---|
| 90 |
|
|---|
| 91 | DEFAULT_BUCKET_ID: DRIVER_FAULT
|
|---|
| 92 |
|
|---|
| 93 | PROCESS_NAME: System
|
|---|
| 94 |
|
|---|
| 95 | 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.
|
|---|
| 96 |
|
|---|
| 97 | READ_ADDRESS: 00000001
|
|---|
| 98 |
|
|---|
| 99 | FAILED_INSTRUCTION_ADDRESS:
|
|---|
| 100 | +1
|
|---|
| 101 | 00000001 ?? ???
|
|---|
| 102 |
|
|---|
| 103 | BUGCHECK_STR: 0x7E
|
|---|
| 104 |
|
|---|
| 105 | LAST_CONTROL_TRANSFER: from bac8fae1 to 00000001
|
|---|
| 106 |
|
|---|
| 107 | STACK_TEXT:
|
|---|
| 108 | WARNING: Frame IP not in any known module. Following frames may be wrong.
|
|---|
| 109 | f790a9b0 bac8fae1 00000040 68627375 64657621 0x1
|
|---|
| 110 | f790a9d8 bac8d1d8 8930d3b8 8853a008 f790aa0c usbhub!USBH_PdoDispatch+0x1e9
|
|---|
| 111 | f790a9e8 804e37f7 87d003a8 8853a008 8853a008 usbhub!USBH_HubDispatch+0x48
|
|---|
| 112 | f790a9f8 f77b7380 00000000 89962c58 87c43030 nt!IopfCallDriver+0x31
|
|---|
| 113 | f790aa0c 804e37f7 00000000 8853a008 892e9230 VBoxUSBFlt+0x380
|
|---|
| 114 | f790aa1c f77f04db 00220003 8853a12c 80000000 nt!IopfCallDriver+0x31
|
|---|
| 115 | f790aa38 f77ef76b 87c62410 8853a008 89e2fda8 usbccgp!ParentInternalDeviceControl+0xbb
|
|---|
| 116 | f790aa5c f77ef5d3 87c62408 8853a008 0000000f usbccgp!USBC_InternalDeviceControl+0x3b
|
|---|
| 117 | f790aa98 804e37f7 87c62350 8853a008 892e9230 usbccgp!USBC_Dispatch+0x183
|
|---|
| 118 | f790aaa8 f77f1231 80000000 00000002 00220003 nt!IopfCallDriver+0x31
|
|---|
| 119 | f790aad8 f77ef786 892d37f8 8853a008 892d37f8 usbccgp!FunctionInternalDeviceControl+0x1c1
|
|---|
| 120 | f790aafc f77ef5d3 892d37f0 8853a008 0000000f usbccgp!USBC_InternalDeviceControl+0x56
|
|---|
| 121 | f790ab38 804e37f7 892d3738 8853a008 8853a008 usbccgp!USBC_Dispatch+0x183
|
|---|
| 122 | f790ab48 ba8e2fd7 87c4327c 8930d3b8 87c43030 nt!IopfCallDriver+0x31
|
|---|
| 123 | f790ab74 ba8e3609 87c43030 8930d3b8 00000002 hidusb!HumCallUSB+0x71
|
|---|
| 124 | f790ab8c ba8e365a 87c43030 00000000 89c8d008 hidusb!HumAbortPendingRequests+0x4b
|
|---|
| 125 | f790aba4 ba8e376f 87c43030 89c8d008 87c43218 hidusb!HumRemoveDevice+0x32
|
|---|
| 126 | f790abd4 f7407e91 87c43030 89c8d008 87c430fc hidusb!HumPnP+0x45
|
|---|
| 127 | f790abe8 f740ea5f 87c43030 89c8d008 87c430fc HIDCLASS!HidpCallDriver+0x3f
|
|---|
| 128 | f790ac04 f740cf1c 87c430fc 89c8d008 89c8d1bc HIDCLASS!HidpRemoveDevice+0xa1
|
|---|
| 129 | f790ac20 f740d076 87c430e8 89c8d008 f790ac40 HIDCLASS!HidpFdoPnp+0x72
|
|---|
| 130 | f790ac30 f740892b 87c430e8 89c8d008 f790ac7c HIDCLASS!HidpIrpMajorPnp+0x1e
|
|---|
| 131 | f790ac40 804e37f7 87c43030 89c8d008 f790accc HIDCLASS!HidpMajorHandler+0x79
|
|---|
| 132 | f790ac50 8059df8f 892d3738 892d3738 00000002 nt!IopfCallDriver+0x31
|
|---|
| 133 | f790ac7c 8061ad54 87c43030 f790aca8 00000000 nt!IopSynchronousCall+0xb7
|
|---|
| 134 | f790acd0 80531683 892d3738 00000002 00000000 nt!IopRemoveDevice+0x93
|
|---|
| 135 | f790acf8 8061becf e2c65078 00000018 e12f4c50 nt!IopRemoveLockedDeviceNode+0x160
|
|---|
| 136 | f790ad10 8061bf3b 89c9ca38 00000002 e12f4c50 nt!IopDeleteLockedDeviceNode+0x34
|
|---|
| 137 | f790ad44 8061bfe6 87d003a8 022f4c50 00000002 nt!IopDeleteLockedDeviceNodes+0x3f
|
|---|
| 138 | f790ad74 804e426b 89c84da8 00000000 89e2fda8 nt!IopDelayedRemoveWorker+0x4b
|
|---|
| 139 | f790adac 8057cfce 89c84da8 00000000 00000000 nt!ExpWorkerThread+0x100
|
|---|
| 140 | f790addc 804f88fa 804e4196 00000001 00000000 nt!PspSystemThreadStartup+0x34
|
|---|
| 141 | 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
|
|---|
| 142 |
|
|---|
| 143 |
|
|---|
| 144 | FOLLOWUP_IP:
|
|---|
| 145 | VBoxUSBFlt+380
|
|---|
| 146 | f77b7380 ?? ???
|
|---|
| 147 |
|
|---|
| 148 | SYMBOL_STACK_INDEX: 4
|
|---|
| 149 |
|
|---|
| 150 | SYMBOL_NAME: VBoxUSBFlt+380
|
|---|
| 151 |
|
|---|
| 152 | FOLLOWUP_NAME: MachineOwner
|
|---|
| 153 |
|
|---|
| 154 | MODULE_NAME: VBoxUSBFlt
|
|---|
| 155 |
|
|---|
| 156 | IMAGE_NAME: VBoxUSBFlt.sys
|
|---|
| 157 |
|
|---|
| 158 | DEBUG_FLR_IMAGE_TIMESTAMP: 45f6eb5d
|
|---|
| 159 |
|
|---|
| 160 | STACK_COMMAND: .cxr 0xfffffffff790a5e8 ; kb
|
|---|
| 161 |
|
|---|
| 162 | FAILURE_BUCKET_ID: 0x7E_BAD_IP_VBoxUSBFlt+380
|
|---|
| 163 |
|
|---|
| 164 | BUCKET_ID: 0x7E_BAD_IP_VBoxUSBFlt+380
|
|---|
| 165 |
|
|---|
| 166 | Followup: MachineOwner
|
|---|
| 167 | ---------
|
|---|
| 168 |
|
|---|
| 169 | kd> !analyze -v
|
|---|
| 170 | *******************************************************************************
|
|---|
| 171 | * *
|
|---|
| 172 | * Bugcheck Analysis *
|
|---|
| 173 | * *
|
|---|
| 174 | *******************************************************************************
|
|---|
| 175 |
|
|---|
| 176 | SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
|
|---|
| 177 | This is a very common bugcheck. Usually the exception address pinpoints
|
|---|
| 178 | the driver/function that caused the problem. Always note this address
|
|---|
| 179 | as well as the link date of the driver/image that contains this address.
|
|---|
| 180 | Some common problems are exception code 0x80000003. This means a hard
|
|---|
| 181 | coded breakpoint or assertion was hit, but this system was booted
|
|---|
| 182 | /NODEBUG. This is not supposed to happen as developers should never have
|
|---|
| 183 | hardcoded breakpoints in retail code, but ...
|
|---|
| 184 | If this happens, make sure a debugger gets connected, and the
|
|---|
| 185 | system is booted /DEBUG. This will let us see why this breakpoint is
|
|---|
| 186 | happening.
|
|---|
| 187 | Arguments:
|
|---|
| 188 | Arg1: c0000005, The exception code that was not handled
|
|---|
| 189 | Arg2: 00000001, The address that the exception occurred at
|
|---|
| 190 | Arg3: f790a8ec, Exception Record Address
|
|---|
| 191 | Arg4: f790a5e8, Context Record Address
|
|---|
| 192 |
|
|---|
| 193 | Debugging Details:
|
|---|
| 194 | ------------------
|
|---|
| 195 |
|
|---|
| 196 |
|
|---|
| 197 | 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.
|
|---|
| 198 |
|
|---|
| 199 | FAULTING_IP:
|
|---|
| 200 | +1
|
|---|
| 201 | 00000001 ?? ???
|
|---|
| 202 |
|
|---|
| 203 | EXCEPTION_RECORD: f790a8ec -- (.exr 0xfffffffff790a8ec)
|
|---|
| 204 | ExceptionAddress: 00000001
|
|---|
| 205 | ExceptionCode: c0000005 (Access violation)
|
|---|
| 206 | ExceptionFlags: 00000000
|
|---|
| 207 | NumberParameters: 2
|
|---|
| 208 | Parameter[0]: 00000000
|
|---|
| 209 | Parameter[1]: 00000001
|
|---|
| 210 | Attempt to read from address 00000001
|
|---|
| 211 |
|
|---|
| 212 | CONTEXT: f790a5e8 -- (.cxr 0xfffffffff790a5e8)
|
|---|
| 213 | eax=00000004 ebx=8854ad50 ecx=00000000 edx=00220003 esi=87d00460 edi=8853a008
|
|---|
| 214 | eip=00000001 esp=f790a9b4 ebp=f790a9d8 iopl=0 nv up ei pl zr na pe nc
|
|---|
| 215 | cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
|
|---|
| 216 | 00000001 ?? ???
|
|---|
| 217 | Resetting default scope
|
|---|
| 218 |
|
|---|
| 219 | CUSTOMER_CRASH_COUNT: 1
|
|---|
| 220 |
|
|---|
| 221 | DEFAULT_BUCKET_ID: DRIVER_FAULT
|
|---|
| 222 |
|
|---|
| 223 | PROCESS_NAME: System
|
|---|
| 224 |
|
|---|
| 225 | 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.
|
|---|
| 226 |
|
|---|
| 227 | READ_ADDRESS: 00000001
|
|---|
| 228 |
|
|---|
| 229 | FAILED_INSTRUCTION_ADDRESS:
|
|---|
| 230 | +1
|
|---|
| 231 | 00000001 ?? ???
|
|---|
| 232 |
|
|---|
| 233 | BUGCHECK_STR: 0x7E
|
|---|
| 234 |
|
|---|
| 235 | LAST_CONTROL_TRANSFER: from bac8fae1 to 00000001
|
|---|
| 236 |
|
|---|
| 237 | STACK_TEXT:
|
|---|
| 238 | WARNING: Frame IP not in any known module. Following frames may be wrong.
|
|---|
| 239 | f790a9b0 bac8fae1 00000040 68627375 64657621 0x1
|
|---|
| 240 | f790a9d8 bac8d1d8 8930d3b8 8853a008 f790aa0c usbhub!USBH_PdoDispatch+0x1e9
|
|---|
| 241 | f790a9e8 804e37f7 87d003a8 8853a008 8853a008 usbhub!USBH_HubDispatch+0x48
|
|---|
| 242 | f790a9f8 f77b7380 00000000 89962c58 87c43030 nt!IopfCallDriver+0x31
|
|---|
| 243 | f790aa0c 804e37f7 00000000 8853a008 892e9230 VBoxUSBFlt+0x380
|
|---|
| 244 | f790aa1c f77f04db 00220003 8853a12c 80000000 nt!IopfCallDriver+0x31
|
|---|
| 245 | f790aa38 f77ef76b 87c62410 8853a008 89e2fda8 usbccgp!ParentInternalDeviceControl+0xbb
|
|---|
| 246 | f790aa5c f77ef5d3 87c62408 8853a008 0000000f usbccgp!USBC_InternalDeviceControl+0x3b
|
|---|
| 247 | f790aa98 804e37f7 87c62350 8853a008 892e9230 usbccgp!USBC_Dispatch+0x183
|
|---|
| 248 | f790aaa8 f77f1231 80000000 00000002 00220003 nt!IopfCallDriver+0x31
|
|---|
| 249 | f790aad8 f77ef786 892d37f8 8853a008 892d37f8 usbccgp!FunctionInternalDeviceControl+0x1c1
|
|---|
| 250 | f790aafc f77ef5d3 892d37f0 8853a008 0000000f usbccgp!USBC_InternalDeviceControl+0x56
|
|---|
| 251 | f790ab38 804e37f7 892d3738 8853a008 8853a008 usbccgp!USBC_Dispatch+0x183
|
|---|
| 252 | f790ab48 ba8e2fd7 87c4327c 8930d3b8 87c43030 nt!IopfCallDriver+0x31
|
|---|
| 253 | f790ab74 ba8e3609 87c43030 8930d3b8 00000002 hidusb!HumCallUSB+0x71
|
|---|
| 254 | f790ab8c ba8e365a 87c43030 00000000 89c8d008 hidusb!HumAbortPendingRequests+0x4b
|
|---|
| 255 | f790aba4 ba8e376f 87c43030 89c8d008 87c43218 hidusb!HumRemoveDevice+0x32
|
|---|
| 256 | f790abd4 f7407e91 87c43030 89c8d008 87c430fc hidusb!HumPnP+0x45
|
|---|
| 257 | f790abe8 f740ea5f 87c43030 89c8d008 87c430fc HIDCLASS!HidpCallDriver+0x3f
|
|---|
| 258 | f790ac04 f740cf1c 87c430fc 89c8d008 89c8d1bc HIDCLASS!HidpRemoveDevice+0xa1
|
|---|
| 259 | f790ac20 f740d076 87c430e8 89c8d008 f790ac40 HIDCLASS!HidpFdoPnp+0x72
|
|---|
| 260 | f790ac30 f740892b 87c430e8 89c8d008 f790ac7c HIDCLASS!HidpIrpMajorPnp+0x1e
|
|---|
| 261 | f790ac40 804e37f7 87c43030 89c8d008 f790accc HIDCLASS!HidpMajorHandler+0x79
|
|---|
| 262 | f790ac50 8059df8f 892d3738 892d3738 00000002 nt!IopfCallDriver+0x31
|
|---|
| 263 | f790ac7c 8061ad54 87c43030 f790aca8 00000000 nt!IopSynchronousCall+0xb7
|
|---|
| 264 | f790acd0 80531683 892d3738 00000002 00000000 nt!IopRemoveDevice+0x93
|
|---|
| 265 | f790acf8 8061becf e2c65078 00000018 e12f4c50 nt!IopRemoveLockedDeviceNode+0x160
|
|---|
| 266 | f790ad10 8061bf3b 89c9ca38 00000002 e12f4c50 nt!IopDeleteLockedDeviceNode+0x34
|
|---|
| 267 | f790ad44 8061bfe6 87d003a8 022f4c50 00000002 nt!IopDeleteLockedDeviceNodes+0x3f
|
|---|
| 268 | f790ad74 804e426b 89c84da8 00000000 89e2fda8 nt!IopDelayedRemoveWorker+0x4b
|
|---|
| 269 | f790adac 8057cfce 89c84da8 00000000 00000000 nt!ExpWorkerThread+0x100
|
|---|
| 270 | f790addc 804f88fa 804e4196 00000001 00000000 nt!PspSystemThreadStartup+0x34
|
|---|
| 271 | 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
|
|---|
| 272 |
|
|---|
| 273 |
|
|---|
| 274 | FOLLOWUP_IP:
|
|---|
| 275 | VBoxUSBFlt+380
|
|---|
| 276 | f77b7380 ?? ???
|
|---|
| 277 |
|
|---|
| 278 | SYMBOL_STACK_INDEX: 4
|
|---|
| 279 |
|
|---|
| 280 | SYMBOL_NAME: VBoxUSBFlt+380
|
|---|
| 281 |
|
|---|
| 282 | FOLLOWUP_NAME: MachineOwner
|
|---|
| 283 |
|
|---|
| 284 | MODULE_NAME: VBoxUSBFlt
|
|---|
| 285 |
|
|---|
| 286 | IMAGE_NAME: VBoxUSBFlt.sys
|
|---|
| 287 |
|
|---|
| 288 | DEBUG_FLR_IMAGE_TIMESTAMP: 45f6eb5d
|
|---|
| 289 |
|
|---|
| 290 | STACK_COMMAND: .cxr 0xfffffffff790a5e8 ; kb
|
|---|
| 291 |
|
|---|
| 292 | FAILURE_BUCKET_ID: 0x7E_BAD_IP_VBoxUSBFlt+380
|
|---|
| 293 |
|
|---|
| 294 | BUCKET_ID: 0x7E_BAD_IP_VBoxUSBFlt+380
|
|---|
| 295 |
|
|---|
| 296 | Followup: MachineOwner
|
|---|
| 297 | ---------
|
|---|
| 298 |
|
|---|
| 299 | kd> !analyze -v
|
|---|
| 300 | *******************************************************************************
|
|---|
| 301 | * *
|
|---|
| 302 | * Bugcheck Analysis *
|
|---|
| 303 | * *
|
|---|
| 304 | *******************************************************************************
|
|---|
| 305 |
|
|---|
| 306 | SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
|
|---|
| 307 | This is a very common bugcheck. Usually the exception address pinpoints
|
|---|
| 308 | the driver/function that caused the problem. Always note this address
|
|---|
| 309 | as well as the link date of the driver/image that contains this address.
|
|---|
| 310 | Some common problems are exception code 0x80000003. This means a hard
|
|---|
| 311 | coded breakpoint or assertion was hit, but this system was booted
|
|---|
| 312 | /NODEBUG. This is not supposed to happen as developers should never have
|
|---|
| 313 | hardcoded breakpoints in retail code, but ...
|
|---|
| 314 | If this happens, make sure a debugger gets connected, and the
|
|---|
| 315 | system is booted /DEBUG. This will let us see why this breakpoint is
|
|---|
| 316 | happening.
|
|---|
| 317 | Arguments:
|
|---|
| 318 | Arg1: c0000005, The exception code that was not handled
|
|---|
| 319 | Arg2: 00000001, The address that the exception occurred at
|
|---|
| 320 | Arg3: f790a8ec, Exception Record Address
|
|---|
| 321 | Arg4: f790a5e8, Context Record Address
|
|---|
| 322 |
|
|---|
| 323 | Debugging Details:
|
|---|
| 324 | ------------------
|
|---|
| 325 |
|
|---|
| 326 |
|
|---|
| 327 | 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.
|
|---|
| 328 |
|
|---|
| 329 | FAULTING_IP:
|
|---|
| 330 | +1
|
|---|
| 331 | 00000001 ?? ???
|
|---|
| 332 |
|
|---|
| 333 | EXCEPTION_RECORD: f790a8ec -- (.exr 0xfffffffff790a8ec)
|
|---|
| 334 | ExceptionAddress: 00000001
|
|---|
| 335 | ExceptionCode: c0000005 (Access violation)
|
|---|
| 336 | ExceptionFlags: 00000000
|
|---|
| 337 | NumberParameters: 2
|
|---|
| 338 | Parameter[0]: 00000000
|
|---|
| 339 | Parameter[1]: 00000001
|
|---|
| 340 | Attempt to read from address 00000001
|
|---|
| 341 |
|
|---|
| 342 | CONTEXT: f790a5e8 -- (.cxr 0xfffffffff790a5e8)
|
|---|
| 343 | eax=00000004 ebx=8854ad50 ecx=00000000 edx=00220003 esi=87d00460 edi=8853a008
|
|---|
| 344 | eip=00000001 esp=f790a9b4 ebp=f790a9d8 iopl=0 nv up ei pl zr na pe nc
|
|---|
| 345 | cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
|
|---|
| 346 | 00000001 ?? ???
|
|---|
| 347 | Resetting default scope
|
|---|
| 348 |
|
|---|
| 349 | CUSTOMER_CRASH_COUNT: 1
|
|---|
| 350 |
|
|---|
| 351 | DEFAULT_BUCKET_ID: DRIVER_FAULT
|
|---|
| 352 |
|
|---|
| 353 | PROCESS_NAME: System
|
|---|
| 354 |
|
|---|
| 355 | 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.
|
|---|
| 356 |
|
|---|
| 357 | READ_ADDRESS: 00000001
|
|---|
| 358 |
|
|---|
| 359 | FAILED_INSTRUCTION_ADDRESS:
|
|---|
| 360 | +1
|
|---|
| 361 | 00000001 ?? ???
|
|---|
| 362 |
|
|---|
| 363 | BUGCHECK_STR: 0x7E
|
|---|
| 364 |
|
|---|
| 365 | LAST_CONTROL_TRANSFER: from bac8fae1 to 00000001
|
|---|
| 366 |
|
|---|
| 367 | STACK_TEXT:
|
|---|
| 368 | WARNING: Frame IP not in any known module. Following frames may be wrong.
|
|---|
| 369 | f790a9b0 bac8fae1 00000040 68627375 64657621 0x1
|
|---|
| 370 | f790a9d8 bac8d1d8 8930d3b8 8853a008 f790aa0c usbhub!USBH_PdoDispatch+0x1e9
|
|---|
| 371 | f790a9e8 804e37f7 87d003a8 8853a008 8853a008 usbhub!USBH_HubDispatch+0x48
|
|---|
| 372 | f790a9f8 f77b7380 00000000 89962c58 87c43030 nt!IopfCallDriver+0x31
|
|---|
| 373 | f790aa0c 804e37f7 00000000 8853a008 892e9230 VBoxUSBFlt+0x380
|
|---|
| 374 | f790aa1c f77f04db 00220003 8853a12c 80000000 nt!IopfCallDriver+0x31
|
|---|
| 375 | f790aa38 f77ef76b 87c62410 8853a008 89e2fda8 usbccgp!ParentInternalDeviceControl+0xbb
|
|---|
| 376 | f790aa5c f77ef5d3 87c62408 8853a008 0000000f usbccgp!USBC_InternalDeviceControl+0x3b
|
|---|
| 377 | f790aa98 804e37f7 87c62350 8853a008 892e9230 usbccgp!USBC_Dispatch+0x183
|
|---|
| 378 | f790aaa8 f77f1231 80000000 00000002 00220003 nt!IopfCallDriver+0x31
|
|---|
| 379 | f790aad8 f77ef786 892d37f8 8853a008 892d37f8 usbccgp!FunctionInternalDeviceControl+0x1c1
|
|---|
| 380 | f790aafc f77ef5d3 892d37f0 8853a008 0000000f usbccgp!USBC_InternalDeviceControl+0x56
|
|---|
| 381 | f790ab38 804e37f7 892d3738 8853a008 8853a008 usbccgp!USBC_Dispatch+0x183
|
|---|
| 382 | f790ab48 ba8e2fd7 87c4327c 8930d3b8 87c43030 nt!IopfCallDriver+0x31
|
|---|
| 383 | f790ab74 ba8e3609 87c43030 8930d3b8 00000002 hidusb!HumCallUSB+0x71
|
|---|
| 384 | f790ab8c ba8e365a 87c43030 00000000 89c8d008 hidusb!HumAbortPendingRequests+0x4b
|
|---|
| 385 | f790aba4 ba8e376f 87c43030 89c8d008 87c43218 hidusb!HumRemoveDevice+0x32
|
|---|
| 386 | f790abd4 f7407e91 87c43030 89c8d008 87c430fc hidusb!HumPnP+0x45
|
|---|
| 387 | f790abe8 f740ea5f 87c43030 89c8d008 87c430fc HIDCLASS!HidpCallDriver+0x3f
|
|---|
| 388 | f790ac04 f740cf1c 87c430fc 89c8d008 89c8d1bc HIDCLASS!HidpRemoveDevice+0xa1
|
|---|
| 389 | f790ac20 f740d076 87c430e8 89c8d008 f790ac40 HIDCLASS!HidpFdoPnp+0x72
|
|---|
| 390 | f790ac30 f740892b 87c430e8 89c8d008 f790ac7c HIDCLASS!HidpIrpMajorPnp+0x1e
|
|---|
| 391 | f790ac40 804e37f7 87c43030 89c8d008 f790accc HIDCLASS!HidpMajorHandler+0x79
|
|---|
| 392 | f790ac50 8059df8f 892d3738 892d3738 00000002 nt!IopfCallDriver+0x31
|
|---|
| 393 | f790ac7c 8061ad54 87c43030 f790aca8 00000000 nt!IopSynchronousCall+0xb7
|
|---|
| 394 | f790acd0 80531683 892d3738 00000002 00000000 nt!IopRemoveDevice+0x93
|
|---|
| 395 | f790acf8 8061becf e2c65078 00000018 e12f4c50 nt!IopRemoveLockedDeviceNode+0x160
|
|---|
| 396 | f790ad10 8061bf3b 89c9ca38 00000002 e12f4c50 nt!IopDeleteLockedDeviceNode+0x34
|
|---|
| 397 | f790ad44 8061bfe6 87d003a8 022f4c50 00000002 nt!IopDeleteLockedDeviceNodes+0x3f
|
|---|
| 398 | f790ad74 804e426b 89c84da8 00000000 89e2fda8 nt!IopDelayedRemoveWorker+0x4b
|
|---|
| 399 | f790adac 8057cfce 89c84da8 00000000 00000000 nt!ExpWorkerThread+0x100
|
|---|
| 400 | f790addc 804f88fa 804e4196 00000001 00000000 nt!PspSystemThreadStartup+0x34
|
|---|
| 401 | 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
|
|---|
| 402 |
|
|---|
| 403 |
|
|---|
| 404 | FOLLOWUP_IP:
|
|---|
| 405 | VBoxUSBFlt+380
|
|---|
| 406 | f77b7380 ?? ???
|
|---|
| 407 |
|
|---|
| 408 | SYMBOL_STACK_INDEX: 4
|
|---|
| 409 |
|
|---|
| 410 | SYMBOL_NAME: VBoxUSBFlt+380
|
|---|
| 411 |
|
|---|
| 412 | FOLLOWUP_NAME: MachineOwner
|
|---|
| 413 |
|
|---|
| 414 | MODULE_NAME: VBoxUSBFlt
|
|---|
| 415 |
|
|---|
| 416 | IMAGE_NAME: VBoxUSBFlt.sys
|
|---|
| 417 |
|
|---|
| 418 | DEBUG_FLR_IMAGE_TIMESTAMP: 45f6eb5d
|
|---|
| 419 |
|
|---|
| 420 | STACK_COMMAND: .cxr 0xfffffffff790a5e8 ; kb
|
|---|
| 421 |
|
|---|
| 422 | FAILURE_BUCKET_ID: 0x7E_BAD_IP_VBoxUSBFlt+380
|
|---|
| 423 |
|
|---|
| 424 | BUCKET_ID: 0x7E_BAD_IP_VBoxUSBFlt+380
|
|---|
| 425 |
|
|---|
| 426 | Followup: MachineOwner
|
|---|
| 427 | ---------
|
|---|
| 428 |
|
|---|
| 429 | kd> !analyze -v
|
|---|
| 430 | *******************************************************************************
|
|---|
| 431 | * *
|
|---|
| 432 | * Bugcheck Analysis *
|
|---|
| 433 | * *
|
|---|
| 434 | *******************************************************************************
|
|---|
| 435 |
|
|---|
| 436 | SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
|
|---|
| 437 | This is a very common bugcheck. Usually the exception address pinpoints
|
|---|
| 438 | the driver/function that caused the problem. Always note this address
|
|---|
| 439 | as well as the link date of the driver/image that contains this address.
|
|---|
| 440 | Some common problems are exception code 0x80000003. This means a hard
|
|---|
| 441 | coded breakpoint or assertion was hit, but this system was booted
|
|---|
| 442 | /NODEBUG. This is not supposed to happen as developers should never have
|
|---|
| 443 | hardcoded breakpoints in retail code, but ...
|
|---|
| 444 | If this happens, make sure a debugger gets connected, and the
|
|---|
| 445 | system is booted /DEBUG. This will let us see why this breakpoint is
|
|---|
| 446 | happening.
|
|---|
| 447 | Arguments:
|
|---|
| 448 | Arg1: c0000005, The exception code that was not handled
|
|---|
| 449 | Arg2: 00000001, The address that the exception occurred at
|
|---|
| 450 | Arg3: f790a8ec, Exception Record Address
|
|---|
| 451 | Arg4: f790a5e8, Context Record Address
|
|---|
| 452 |
|
|---|
| 453 | Debugging Details:
|
|---|
| 454 | ------------------
|
|---|
| 455 |
|
|---|
| 456 |
|
|---|
| 457 | 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.
|
|---|
| 458 |
|
|---|
| 459 | FAULTING_IP:
|
|---|
| 460 | +1
|
|---|
| 461 | 00000001 ?? ???
|
|---|
| 462 |
|
|---|
| 463 | EXCEPTION_RECORD: f790a8ec -- (.exr 0xfffffffff790a8ec)
|
|---|
| 464 | ExceptionAddress: 00000001
|
|---|
| 465 | ExceptionCode: c0000005 (Access violation)
|
|---|
| 466 | ExceptionFlags: 00000000
|
|---|
| 467 | NumberParameters: 2
|
|---|
| 468 | Parameter[0]: 00000000
|
|---|
| 469 | Parameter[1]: 00000001
|
|---|
| 470 | Attempt to read from address 00000001
|
|---|
| 471 |
|
|---|
| 472 | CONTEXT: f790a5e8 -- (.cxr 0xfffffffff790a5e8)
|
|---|
| 473 | eax=00000004 ebx=8854ad50 ecx=00000000 edx=00220003 esi=87d00460 edi=8853a008
|
|---|
| 474 | eip=00000001 esp=f790a9b4 ebp=f790a9d8 iopl=0 nv up ei pl zr na pe nc
|
|---|
| 475 | cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
|
|---|
| 476 | 00000001 ?? ???
|
|---|
| 477 | Resetting default scope
|
|---|
| 478 |
|
|---|
| 479 | CUSTOMER_CRASH_COUNT: 1
|
|---|
| 480 |
|
|---|
| 481 | DEFAULT_BUCKET_ID: DRIVER_FAULT
|
|---|
| 482 |
|
|---|
| 483 | PROCESS_NAME: System
|
|---|
| 484 |
|
|---|
| 485 | 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.
|
|---|
| 486 |
|
|---|
| 487 | READ_ADDRESS: 00000001
|
|---|
| 488 |
|
|---|
| 489 | FAILED_INSTRUCTION_ADDRESS:
|
|---|
| 490 | +1
|
|---|
| 491 | 00000001 ?? ???
|
|---|
| 492 |
|
|---|
| 493 | BUGCHECK_STR: 0x7E
|
|---|
| 494 |
|
|---|
| 495 | LAST_CONTROL_TRANSFER: from bac8fae1 to 00000001
|
|---|
| 496 |
|
|---|
| 497 | STACK_TEXT:
|
|---|
| 498 | WARNING: Frame IP not in any known module. Following frames may be wrong.
|
|---|
| 499 | f790a9b0 bac8fae1 00000040 68627375 64657621 0x1
|
|---|
| 500 | f790a9d8 bac8d1d8 8930d3b8 8853a008 f790aa0c usbhub!USBH_PdoDispatch+0x1e9
|
|---|
| 501 | f790a9e8 804e37f7 87d003a8 8853a008 8853a008 usbhub!USBH_HubDispatch+0x48
|
|---|
| 502 | f790a9f8 f77b7380 00000000 89962c58 87c43030 nt!IopfCallDriver+0x31
|
|---|
| 503 | f790aa0c 804e37f7 00000000 8853a008 892e9230 VBoxUSBFlt+0x380
|
|---|
| 504 | f790aa1c f77f04db 00220003 8853a12c 80000000 nt!IopfCallDriver+0x31
|
|---|
| 505 | f790aa38 f77ef76b 87c62410 8853a008 89e2fda8 usbccgp!ParentInternalDeviceControl+0xbb
|
|---|
| 506 | f790aa5c f77ef5d3 87c62408 8853a008 0000000f usbccgp!USBC_InternalDeviceControl+0x3b
|
|---|
| 507 | f790aa98 804e37f7 87c62350 8853a008 892e9230 usbccgp!USBC_Dispatch+0x183
|
|---|
| 508 | f790aaa8 f77f1231 80000000 00000002 00220003 nt!IopfCallDriver+0x31
|
|---|
| 509 | f790aad8 f77ef786 892d37f8 8853a008 892d37f8 usbccgp!FunctionInternalDeviceControl+0x1c1
|
|---|
| 510 | f790aafc f77ef5d3 892d37f0 8853a008 0000000f usbccgp!USBC_InternalDeviceControl+0x56
|
|---|
| 511 | f790ab38 804e37f7 892d3738 8853a008 8853a008 usbccgp!USBC_Dispatch+0x183
|
|---|
| 512 | f790ab48 ba8e2fd7 87c4327c 8930d3b8 87c43030 nt!IopfCallDriver+0x31
|
|---|
| 513 | f790ab74 ba8e3609 87c43030 8930d3b8 00000002 hidusb!HumCallUSB+0x71
|
|---|
| 514 | f790ab8c ba8e365a 87c43030 00000000 89c8d008 hidusb!HumAbortPendingRequests+0x4b
|
|---|
| 515 | f790aba4 ba8e376f 87c43030 89c8d008 87c43218 hidusb!HumRemoveDevice+0x32
|
|---|
| 516 | f790abd4 f7407e91 87c43030 89c8d008 87c430fc hidusb!HumPnP+0x45
|
|---|
| 517 | f790abe8 f740ea5f 87c43030 89c8d008 87c430fc HIDCLASS!HidpCallDriver+0x3f
|
|---|
| 518 | f790ac04 f740cf1c 87c430fc 89c8d008 89c8d1bc HIDCLASS!HidpRemoveDevice+0xa1
|
|---|
| 519 | f790ac20 f740d076 87c430e8 89c8d008 f790ac40 HIDCLASS!HidpFdoPnp+0x72
|
|---|
| 520 | f790ac30 f740892b 87c430e8 89c8d008 f790ac7c HIDCLASS!HidpIrpMajorPnp+0x1e
|
|---|
| 521 | f790ac40 804e37f7 87c43030 89c8d008 f790accc HIDCLASS!HidpMajorHandler+0x79
|
|---|
| 522 | f790ac50 8059df8f 892d3738 892d3738 00000002 nt!IopfCallDriver+0x31
|
|---|
| 523 | f790ac7c 8061ad54 87c43030 f790aca8 00000000 nt!IopSynchronousCall+0xb7
|
|---|
| 524 | f790acd0 80531683 892d3738 00000002 00000000 nt!IopRemoveDevice+0x93
|
|---|
| 525 | f790acf8 8061becf e2c65078 00000018 e12f4c50 nt!IopRemoveLockedDeviceNode+0x160
|
|---|
| 526 | f790ad10 8061bf3b 89c9ca38 00000002 e12f4c50 nt!IopDeleteLockedDeviceNode+0x34
|
|---|
| 527 | f790ad44 8061bfe6 87d003a8 022f4c50 00000002 nt!IopDeleteLockedDeviceNodes+0x3f
|
|---|
| 528 | f790ad74 804e426b 89c84da8 00000000 89e2fda8 nt!IopDelayedRemoveWorker+0x4b
|
|---|
| 529 | f790adac 8057cfce 89c84da8 00000000 00000000 nt!ExpWorkerThread+0x100
|
|---|
| 530 | f790addc 804f88fa 804e4196 00000001 00000000 nt!PspSystemThreadStartup+0x34
|
|---|
| 531 | 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
|
|---|
| 532 |
|
|---|
| 533 |
|
|---|
| 534 | FOLLOWUP_IP:
|
|---|
| 535 | VBoxUSBFlt+380
|
|---|
| 536 | f77b7380 ?? ???
|
|---|
| 537 |
|
|---|
| 538 | SYMBOL_STACK_INDEX: 4
|
|---|
| 539 |
|
|---|
| 540 | SYMBOL_NAME: VBoxUSBFlt+380
|
|---|
| 541 |
|
|---|
| 542 | FOLLOWUP_NAME: MachineOwner
|
|---|
| 543 |
|
|---|
| 544 | MODULE_NAME: VBoxUSBFlt
|
|---|
| 545 |
|
|---|
| 546 | IMAGE_NAME: VBoxUSBFlt.sys
|
|---|
| 547 |
|
|---|
| 548 | DEBUG_FLR_IMAGE_TIMESTAMP: 45f6eb5d
|
|---|
| 549 |
|
|---|
| 550 | STACK_COMMAND: .cxr 0xfffffffff790a5e8 ; kb
|
|---|
| 551 |
|
|---|
| 552 | FAILURE_BUCKET_ID: 0x7E_BAD_IP_VBoxUSBFlt+380
|
|---|
| 553 |
|
|---|
| 554 | BUCKET_ID: 0x7E_BAD_IP_VBoxUSBFlt+380
|
|---|
| 555 |
|
|---|
| 556 | Followup: MachineOwner
|
|---|
| 557 | ---------
|
|---|
| 558 |
|
|---|