Dziwne zachowanie kompa.
Witam, mam mały problem. Z przodu obudowy mam dwa wejścia USB, jedno z lewej drugie z prawej strony. Gdy podłączę aparat przez kabel USB do lewego portu wszystko jest OK ale gdy chociaż delikatnie dotknę końcówką kabla do prawego portu to monitor od razu sie wyłącza dysk jakby nagle zaczyna intensywnie pracować (widzę to po zapalonej ciągle lampce restartu) następnie przestaje pracować i komputer nie reaguje, np. włączam capslock albo chociaż "trzech króli" czyli CTRL+ALT+DEL i nic, muszę restartować kompa przyciskiem restart. Oczywiście nie jest to jakiś wielki problem ale chciałbym mimo wszystko jakoś to naprawić.
Odpowiedzi: 3
Ok debugowałem i wyskoczyło:
Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini011208-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 argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image 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 XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Sat Jan 12 00:48:11.625 2008 (GMT+1)
System Uptime: 0 days 8:28:04.332
*********************************************************************
* 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 argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image 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
..........................
*** WARNING: Unable to verify timestamp for hal.dll
*** ERROR: Module load completed but symbols could not be loaded for hal.dll
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000000A, {e8, 2, 1, 806e4a16}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*** WARNING: Unable to verify timestamp for USBPORT.SYS
*** ERROR: Module load completed but symbols could not be loaded for USBPORT.SYS
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*********************************************************************
* 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 argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* 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 argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Probably caused by : USBPORT.SYS ( USBPORT+9ee5 )
Followup: MachineOwner
---------
Czyli coś nie tak z portami USB, czy mam ściągnąć jakieś nowe sterowniki, ewentualnie skąd?
No ale ja mam w obudowie płytkę z portami USB którą podłącza się kablem do płyty głównej. Nie wiem czy dobrze mnie zrozumiałeś. Mi nie chodzi o porty USB na płycie.
Miałem coś podobnego. Skończyło się na tym, że gniazda z przodu zostały zamknięte na amen, bo płytka, na których są osadzone "sama z siebie" od nowości była dziwnie luźna a w efekcie - przy wkładaniu wtyku - potrafiła mi nawet zaiskrzyć :/
Podejrzewam, że to problem fizyczny. Skontaktuj się ze swoim sprzedawcą. Niech to zobaczy. Zanim się coś nabroi.
Strona 1 / 1