View Single Post
21 Mar 2012  
writhziden

Windows 7 Home Premium 64 Bit
 
 

Code:
  1. Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [D:\Kingston\BSODDmpFiles\Eblim\032012-20014-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330 Machine Name: Kernel base = 0xfffff800`0301a000 PsLoadedModuleList = 0xfffff800`0325e650 Debug session time: Tue Mar 20 17:19:44.479 2012 (UTC - 6:00) System Uptime: 0 days 19:34:57.931 Loading Kernel Symbols ............................................................... ................................................................ ........................ Loading User Symbols Loading unloaded module list ........ ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck FE, {5, fffffa80068c71a0, 808627cc, fffffa8005e375a8} ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: usbport!_DEVICE_EXTENSION *** *** *** ************************************************************************* Probably caused by : usbehci.sys ( usbehci!EHCI_sMode_PollEndpointSlot+6c ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* BUGCODE_USB_DRIVER (fe) USB Driver bugcheck, first parameter is USB bugcheck code. Arguments: Arg1: 0000000000000005, USBBUGCODE_INVALID_PHYSICAL_ADDRESS The host controller is using a physical memory address that was not allocated by the USBport driver. Arg2: fffffa80068c71a0, Device extension pointer of the host controller Arg3: 00000000808627cc, PCI Vendor,Product id for the controller Arg4: fffffa8005e375a8, Pointer to Endpoint data structure Debugging Details: ------------------ ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: usbport!_DEVICE_EXTENSION *** *** *** ************************************************************************* CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xFE PROCESS_NAME: System CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from fffff88002e4ff7e to fffff80003096d40 STACK_TEXT: fffff880`0318ca18 fffff880`02e4ff7e : 00000000`000000fe 00000000`00000005 fffffa80`068c71a0 00000000`808627cc : nt!KeBugCheckEx fffff880`0318ca20 fffff880`02e7dfac : 00000000`60eb5100 fffffa80`068c86a0 00000000`00000000 fffffa80`05e37720 : USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0x18a fffff880`0318ca60 fffff880`02e7db73 : fffffa80`05e375a8 fffff800`0301a000 fffffa80`05e37720 00000000`00000000 : usbehci!EHCI_sMode_PollEndpointSlot+0x6c fffff880`0318caf0 fffff880`02e82d91 : fffffa80`05e375a8 00000000`00000000 00000000`00000000 00000000`00000000 : usbehci!EHCI_PollPerAsyEndpoint+0x53 fffff880`0318cb30 fffff880`02e23e8b : 00000000`00000002 fffffa80`068c71a0 00000000`00000000 00000000`00000040 : usbehci!EHCI_PollEndpoint+0x41 fffff880`0318cb70 fffff880`02e289d1 : 00000000`00000040 00000000`00000004 fffffa80`05e37360 fffffa80`068c7050 : USBPORT!MPf_PollEndpoint+0x9b fffff880`0318cba0 fffff880`02e34077 : fffffa80`068c71a0 00000000`00000040 fffffa80`0000000e 00000000`00000000 : USBPORT!USBPORT_iSetGlobalEndpointStateTx+0x7c1 fffff880`0318cc00 fffff880`02e24f89 : fffffa80`068c7050 00000000`00000000 fffffa80`068c7a02 fffffa80`068c7a18 : USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x1c3 fffff880`0318cc60 fffff800`030a151c : fffff880`03164180 fffffa80`068c7a18 fffffa80`068c7a30 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9 fffff880`0318cc90 fffff800`0308ea6a : fffff880`03164180 fffff880`0316efc0 00000000`00000000 fffff880`02e24db0 : nt!KiRetireDpcList+0x1bc fffff880`0318cd40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a STACK_COMMAND: kb FOLLOWUP_IP: usbehci!EHCI_sMode_PollEndpointSlot+6c fffff880`02e7dfac 4533c9 xor r9d,r9d SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: usbehci!EHCI_sMode_PollEndpointSlot+6c FOLLOWUP_NAME: MachineOwner MODULE_NAME: usbehci IMAGE_NAME: usbehci.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4d8c0c00 FAILURE_BUCKET_ID: X64_0xFE_INVALID_PHYSICAL_ADDR_usbehci!EHCI_sMode_PollEndpointSlot+6c BUCKET_ID: X64_0xFE_INVALID_PHYSICAL_ADDR_usbehci!EHCI_sMode_PollEndpointSlot+6c Followup: MachineOwner ---------

  1. The crash was caused by a USB device. Microsoft does not seem to provide the symbols for the device causing the conflict. What USB devices do you have plugged in?

My System SpecsSystem Spec