Restart komputera


(Bajapl) #1

nawiązuje temat do mojego wcześniejszego postu.zainstalowałem to co napisałeś i nic nie pomogło,myślę że chyba zrobiłem coś nie tak,więc postanowiłem wymienić system ,ale znowu to samo.podczas włączania urządzenia wielofunkcyjnego lub włożenia pendraifa do usb:restart kompa,myślę że to sterowniki ale nie wiem jakie zainstalować. potrzebuje pomocy. chciałbym też dodać że ostatnio dołożyłem kontroler usb 2.0 uniwersalny.oto moje zasoby sprzętowe:

System operacyjny Microsoft Windows XP Professional

Dodatek service pack systemu operacyjnego Dodatek Service Pack. 1

DirectX 4.08.01.0810 (DirectX 8.1)

Płyta główna

Typ procesora Intel Pentium 4, 1500 MHz (15 x 100)

Nazwa płyty głównej VIA P4X266 VL33-S (5 PCI, 1 AGP, 3 DIMM, Audio)

Mikroukład płyty głównej VIA VT8753 Apollo P4X266

Pamięć fizyczna 640 MB (DDR SDRAM)

Typ BIOS'u Award Modular (10/22/01)

Port komunikacyjny Port komunikacyjny (COM1)

Port komunikacyjny Port komunikacyjny (COM2)

Port komunikacyjny Port drukarki (LPT1)

Multimedia

Karta dźwiękowa VIA AC'97 Enhanced Audio Controller

Magazyn

Kontroler IDE Kontroler VIA Bus Master IDE

Napęd dyskietek Stacja dyskietek

Dysk fizyczny SAMSUNG SV4002H (40 GB, 5400 RPM, Ultra-ATA/100)

Napęd dysków optycznych AOPEN DVD1648/AAP (16x/48x DVD-ROM)

Napęd dysków optycznych HL-DT-ST CD-RW GCE-8525B (52x/32x/52x CD-RW)

Status dysków SMART OK

Partycje

C: (NTFS) 19006 MB (15560 MB wolne)

D: (FAT32) 19185 MB (6505 MB wolne)

Rozmiar całkowity 37.3 GB (21.5 GB wolne)

Urządzenia wejściowe

Klawiatura Standardowa klawiatura 101/102 klawisze lub Microsoft Natural Keyboard PS/2

Mysz Mysz zgodna z HID

Urządzenia zewnętrzne

Kontroler USB1 VIA VT83C572 PCI-USB Controller

Kontroler USB1 VIA VT83C572 PCI-USB Controller

Kontroler USB1 VIA VT83C572 PCI-USB Controller

Kontroler USB1 VIA VT83C572 PCI-USB Controller

Kontroler USB2 VIA USB 2.0 Enhanced Host Controller

Urządzenie USB SpeedTouch 330 ADSL Modem

Urządzenie USB Urządzenie USB interfejsu HID

ętowe:


(adam749) #2

Zainstaluj Dodatek SP3 do Xpeka i najnowszego Directx'a. Po tym resetu powinny ustać.


(Bajapl) #3

Zainstalowałem Dodatek SP3 do Xpeka i najnowszego Directx'a,ale nic nie pomogło, ale zauwarzyłem jak podłącze do USB 1.1,które jest z płytą główną to się nie wyłącza,a jak podłącze do nowo podłączonego kontrolera USB 2.0 to następuje restart.


(Seba800) #4

sprópuj pobrać wszystkie sterowniki do urządzeń i je wgraj


(Cosik Ktosik) #5

Może Masz bluescreeny, tylko za szybko znikają i o tym nie wiesz?

Aby BSOD pozostał na ekranie, wejdź do panelu sterowania->system->zaawansowane->uruchamianie i odzyskiwanie->ustawienia->odznacz automatyczny restart po awarii. Napisz na forum, jaki kod błędu został wygenerowany oraz jaką podano przyczynę.

Aby dowiedzieć się więcej, czego dotyczył bluescreen, odczytaj plik DMP. Zrób to wg tej instrukcji :arrow: Czytanie plików DMP

Sprawdź rozwiązanie (także w linkach): kody błędów.

Jeżeli nie rozwiążesz problemu, to daj raport na forum. Wklej go na http://wklej.org a tu daj tylko link do niego.

Sprawdź teraz, czy są jakieś pliki DMP.


(system) #6

Możliwe że jest jakiś konflikt pomiędzy USB płyty głównej a USB które dokupiłeś, spróbuj wyłączyc w BIOSie USB na płycie i zobacz czy się będzie wyłączać przy podłączeniu pod te nowe. Przed tym sprawdź czy masz jakieś konflikty, msinfo32 albo msinfo. Poszukaj tam gdzieś sekcji konflikty


(system) #7

przy sp1 jest starsza obsługa sprzętu a w sp3 najnowsza ktora obsługuje usb 2.0 z nowszysmi sterami


(Bajapl) #8

odczyt pliku DMP:Microsoft ® Windows Debugger Version 6.10.0003.233 X86

Copyright © Microsoft Corporation. All rights reserved.

Loading Dump File [C]

Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\WINDOWS\Minidump\Mini030309-01.dmp

Executable search path is:

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 3) UP Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS

Machine Name:

Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0

Debug session time: Tue Mar 3 22:05:54.290 2009 (GMT+1)

System Uptime: 0 days 0:22:01.890

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

..........

Unable to load image 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, 829370e0, 11063104, 82225420}

***** 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: 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 ***

*** ***

*************************************************************************

*** WARNING: Unable to verify timestamp for usbehci.sys

*** ERROR: Module load completed but symbols could not be loaded for usbehci.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 ***

*** ***

*************************************************************************

Probably caused by : usbehci.sys ( usbehci+3c69 )

Followup: MachineOwner


kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

BUGCODE_USB_DRIVER (fe)

USB Driver bugcheck, first parameter is USB bugcheck code.

Arguments:

Arg1: 00000005, USBBUGCODE_INVALID_PHYSICAL_ADDRESS The host controller is

using a physical memory address that was not allocated by

the USBport driver.

Arg2: 829370e0, Device extension pointer of the host controller

Arg3: 11063104, PCI Vendor,Product id for the controller

Arg4: 82225420, 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: 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 ***

*** ***

*************************************************************************

MODULE_NAME: usbehci

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 480254ce

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

BUGCHECK_STR: 0xFE

LAST_CONTROL_TRANSFER: from f875ee7b to 8053380e

STACK_TEXT:

WARNING: Stack unwind information not available. Following frames may be wrong.

80550d78 f875ee7b 000000fe 00000005 829370e0 nt+0x5c80e

80550d98 f876b7b9 82937028 00000fd0 82191000 USBPORT+0xee7b

80550dcc f8ea3c69 5650706d 829379dc 82225420 USBPORT+0x1b7b9

80550df0 f8ea4192 829379dc 82225420 82225420 usbehci+0x3c69

80550e4c f8ea5f1d 829379dc 82225420 80550e7c usbehci+0x4192

80550e5c f87584aa 829379dc 82225420 804e2eb4 usbehci+0x5f1d

80550e7c f8759768 026c6f50 829370e0 822252a8 USBPORT+0x84aa

80550ea4 f875d0a0 82937028 50457270 804e2eb4 USBPORT+0x9768

80550ed4 f876b24b 82937028 804e2eb4 82937028 USBPORT+0xd0a0

80550f10 f876b3c2 82937028 00000001 80559c20 USBPORT+0x1b24b

80550f2c 804dbbd4 8293764c 6b755044 00000000 USBPORT+0x1b3c2

80550f30 8293764c 6b755044 00000000 829370ec nt+0x4bd4

80550f34 6b755044 00000000 829370ec ffdff980 0x8293764c

80550f38 00000000 829370ec ffdff980 00000000 0x6b755044

STACK_COMMAND: kb

FOLLOWUP_IP:

usbehci+3c69

f8ea3c69 ?? ???

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: usbehci+3c69

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: usbehci.sys

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner