Witamy na forum PC Format Zapraszamy do REJESTRACJI


Użytkownicy przeglądający ten wątek: 1 gości

blue screen "bugcodec_usb_driver" Windows 8

#1
blue screen "bugcodec_usb_driver" Windows 8
któryś raz z kolei przywitał mnie niebieski ekran w moim Windows 8 o treści:

bugcode_usb_driver

mini dump jest:

Cytat:Microsoft ® Windows Debugger Version 6.2.9200.20512 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Filipos\Desktop\031213-47065-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
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 8 Kernel Version 9200 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9200.16496.x86fre.win8_gdr.130108-1504
Machine Name:
Kernel base = 0x81261000 PsLoadedModuleList = 0x8144be68
Debug session time: Tue Mar 12 22:13:20.397 2013 (UTC + 1:00)
System Uptime: 0 days 4:28:47.359
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
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
...............
Unable to load image \SystemRoot\System32\drivers\USBPORT.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for USBPORT.SYS
*** ERROR: Module load completed but symbols could not be loaded for USBPORT.SYS
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck FE, {5, 871180e0, 10de03f1, 8760934c}

*** WARNING: Unable to verify timestamp for usbohci.sys
*** ERROR: Module load completed but symbols could not be loaded for usbohci.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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+257e )

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

Może ktoś mi podpowiedzieć co może powodować problem? Nazwa wskazuje że cos ze sterownikiem USB ale nie jestem pewien
Nigdy nie kłóć się z głupcem - ludzie mogą nie dostrzec różnicy.
 System operacyjny: windows_xp_2003 Przeglądarka: firefox
Programy: Polecane / Nowe / Inne




Podobne wątki (blue screen "bugcodec_usb_driver" Windows 8)
Wątek: Autor Odpowiedzi: Wyświetleń: Ostatni post
  Blue screen Memory Management na nowym komputerze varenoth 12 5711 25.07.2019, 21:25
Ostatni post: pieterman09
  Blue Screen 0x100000ea Laptop HP piotrekk881 1 3163 21.03.2019, 15:31
Ostatni post: Kurp55
  Instalacja systemu Windows 7 - wyskakujący blue screen DAROSTV 5 4710 06.10.2018, 17:49
Ostatni post: Officer Crabtree

Skocz do:


Wybrane wątki (blue screen "bugcodec_usb_driver" Windows 8)
Wątek: Autor Odpowiedzi: Wyświetleń: Ostatni post
  Windows 7 - długie uruchamianie po instalacji SSD oraz Steam jogus48 3 1550 07.08.2018 16:18
Ostatni post: Armo
  MSI GT70 2oc - wolny internet po lan Win10 maminek92 0 3781 06.08.2018 15:34
Ostatni post: maminek92
  Windows 7 się nie włącza - brak nawet splash screen ~Anonim 2 4363 06.08.2018 14:00
Ostatni post: ~Anonim
Ściana Czarny pulpit po włączeniu 238SAMIxD 0 3880 04.08.2018 12:05
Ostatni post: 238SAMIxD
Scared Skaczący FPS gracz4432 5 4986 03.08.2018 15:26
Ostatni post: gracz4432
  acer występuje skakanie pamięci aż do 80% RZUW 0 4069 03.08.2018 00:04
Ostatni post: RZUW
  Mozilla Firefox na windowsie home 10 ~Anonim 0 3816 02.08.2018 07:19
Ostatni post: ~Anonim
Exclamation Problem z programem radiosure i screamer radio ~Anonim 0 3847 02.08.2018 07:01
Ostatni post: ~Anonim
  Odzyskiwanie Windows 10 z folderu Windows.old Squeazz 1 5416 01.08.2018 07:25
Ostatni post: stens
  Problem z Oracle VM VirtualBox bita_śmietanka32 0 3843 30.07.2018 21:06
Ostatni post: bita_śmietanka32
  Windows 10 po upgrade a zmiana PC. krakow2000 2 1041 29.07.2018 10:37
Ostatni post: krakow2000
  VLC rozjechane napisy Radar 0 3768 28.07.2018 18:12
Ostatni post: Radar
  NET.Framework 3.5 Windows 10 krzysiek3542 1 4147 26.07.2018 21:54
Ostatni post: Michu_PL
  Dysk obciążenie 100% maze20lb 0 4304 24.07.2018 12:54
Ostatni post: maze20lb
  C i D cloud14 4 4190 23.07.2018 14:47
Ostatni post: cloud14