[Windows 7] Problem mit Bluescreen Bugcode_usb_driver

Dieses Thema im Forum "Windows" wurde erstellt von taker875, 23. Februar 2011 .

Schlagworte:
  1. 23. Februar 2011
    Problem mit Bluescreen Bugcode_usb_driver

    Hey

    hab nen Problem mit einem Pc auf dem das Dj-Programm Trakstor läuft und die Lichtsteuerungssoftware DasLight. Sobald man beide Programme zusammen ausführt bricht der pc nach 5 min ab und hat einen bluescreen. danach startet er wieder neu.
    hab mit dem windows debugging tool mal den crash dump ausgelesen. aber kann damit relativ wenig anfangen...

    Spoiler
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Windows\Minidump\022311-24367-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:
    Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Windows 7 Kernel Version 7600 MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
    Machine Name:
    Kernel base = 0xfffff800`02a0f000 PsLoadedModuleList = 0xfffff800`02c4ce50
    Debug session time: Wed Feb 23 20:28:49.331 2011 (UTC + 1:00)
    System Uptime: 0 days 0:13:01.001
    Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ......................
    Loading User Symbols
    Loading unloaded module list
    ......
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck FE, {5, fffffa80030c31a0, 10de07fe, fffffa8003b93f60}

    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    *************************************************************************
    *** ***
    *** ***
    *** 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 ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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: nt!KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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: nt!KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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: nt!_KPRCB ***
    *** ***
    *************************************************************************
    Probably caused by : usbohci.sys ( usbohci!OHCI_PollAsyncEndpoint+99 )

    Followup: MachineOwner
    ---------

    0: 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: fffffa80030c31a0, Device extension pointer of the host controller
    Arg3: 0000000010de07fe, PCI Vendor,Product id for the controller
    Arg4: fffffa8003b93f60, Pointer to Endpoint data structure

    Debugging Details:
    ------------------

    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    *************************************************************************
    *** ***
    *** ***
    *** 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 ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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: nt!KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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: nt!KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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: nt!_KPRCB ***
    *** ***
    *************************************************************************

    ADDITIONAL_DEBUG_TEXT:
    Use '!findthebuild' command to search for the target build information.
    If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

    MODULE_NAME: usbohci

    FAULTING_MODULE: fffff80002a0f000 nt

    DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bcc06

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0xFE

    CURRENT_IRQL: 0

    LAST_CONTROL_TRANSFER: from fffff88003d4be4e to fffff80002a7f740

    STACK_TEXT:
    fffff800`0406e988 fffff880`03d4be4e : 00000000`000000fe 00000000`00000005 fffffa80`030c31a0 00000000`10de07fe : nt+0x70740
    fffff800`0406e990 fffff880`03d15a45 : 00000000`ff8dc080 fffffa80`05dce7e8 fffffa80`05dce7e8 fffffa80`03edc000 : USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0x18a
    fffff800`0406e9d0 fffff880`03d17825 : fffffa80`030c4168 fffffa80`05dce7e8 fffffa80`05dce7e8 fffffa80`030c46a0 : usbohci!OHCI_PollAsyncEndpoint+0x99
    fffff800`0406ea30 fffff880`03d24a9a : fffffa80`030c4168 00000000`00000006 fffffa80`03b93d20 00000000`00000002 : usbohci!OHCI_AbortTransfer+0x41
    fffff800`0406ea80 fffff880`03d32f1e : fffffa80`030c31a0 00000000`00000000 00000000`00000000 fffffa80`05dce450 : USBPORT!USBPORT_iSetGlobalEndpointStateTx+0x8aa
    fffff800`0406eae0 fffff880`03d338f3 : fffffa80`03b93d20 fffff880`00000000 fffffa80`030c4068 00000000`00000050 : USBPORT!USBPORT_Core_iCancelPriorityTransfer+0xea
    fffff800`0406eb20 fffff880`03d24dfa : 00000000`00000070 00000000`00000008 fffffa80`03b93d20 fffffa80`030c3050 : USBPORT!USBPORT_Core_iEndpointPaused+0x1d3
    fffff800`0406eb60 fffff880`03d25800 : fffffa80`030c31a0 00000000`00000070 00000000`00000006 00000000`00000000 : USBPORT!USBPORT_iSetGlobalEndpointStateTx+0xc0a
    fffff800`0406ebc0 fffff880`03d4b4ef : fffffa80`030c3102 fffffa80`00000006 00000000`000b9f57 fffffa80`030c31a0 : USBPORT!USBPORT_ProcessNeoStateChangeList+0x398
    fffff800`0406ec30 fffff800`02a8abfc : fffff800`02bf9e80 fffffa80`030c3050 fffffa80`030c4178 00000000`00000000 : USBPORT!USBPORT_IsrDpc+0x1f3
    fffff800`0406ec90 fffff800`02bf9e80 : fffffa80`030c3050 fffffa80`030c4178 00000000`00000000 fffffa80`0245a520 : nt+0x7bbfc
    fffff800`0406ec98 fffffa80`030c3050 : fffffa80`030c4178 00000000`00000000 fffffa80`0245a520 400000c2`400000c1 : nt+0x1eae80
    fffff800`0406eca0 fffffa80`030c4178 : 00000000`00000000 fffffa80`0245a520 400000c2`400000c1 fffffa80`400000c3 : 0xfffffa80`030c3050
    fffff800`0406eca8 00000000`00000000 : fffffa80`0245a520 400000c2`400000c1 fffffa80`400000c3 00000000`48fd5dcd : 0xfffffa80`030c4178


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    usbohci!OHCI_PollAsyncEndpoint+99
    fffff880`03d15a45 8bd3 mov edx,ebx

    SYMBOL_STACK_INDEX: 2

    SYMBOL_NAME: usbohci!OHCI_PollAsyncEndpoint+99

    FOLLOWUP_NAME: MachineOwner

    IMAGE_NAME: usbohci.sys

    BUCKET_ID: WRONG_SYMBOLS

    Followup: MachineOwner
    ---------

    Kann mir jemand sagen was diese Fehlermeldung zu bedeuten hat?


    Vielen Dank
     

  2. Videos zum Thema
    Video Script
Die Seite wird geladen...

Ähnliche Themen mit den Stichworten: Windows Problem Bluescreen

  1. Antworten:
    1
    Aufrufe:
    1.107
  2. Antworten:
    5
    Aufrufe:
    1.080
  3. [Windows 7] 32-Bit Bluescreen und Reboot Problem
    ku5h1337, 20. September 2011 , im Forum: Windows
    Antworten:
    10
    Aufrufe:
    913
  4. [Windows 7] Bluescreen-Probleme en masse
    Simple Jack, 21. Juli 2011 , im Forum: Windows
    Antworten:
    6
    Aufrufe:
    1.523
  5. [Windows 7] Bluescreen problem Hilfe
    T-man, 25. Februar 2011 , im Forum: Windows
    Antworten:
    8
    Aufrufe:
    820