hnaciu utworzono 19 października 2009 utworzono 19 października 2009 Ostatnio po reinstalacji systemu pojawił mi się problem. Otóż po włożeniu do portu usb odtwarzacza mp3 komputer się resetuje i gdy go nie wyjmę to windows nie chce sie załadować, restaruje sie w kołko bez końca. Niezależnie czy jest to usb z przodu czy też z tyłu. Wcześniej takiego problemu nie miałem, więc myśłę, ze jest to problem z windowsem, a mam XP + SP3.
Psycholandia komentarz 19 października 2009 komentarz 19 października 2009 Wykonaj: http://www.forumpc.pl/index.php?showtopic=16074
hnaciu komentarz 23 października 2009 Autor komentarz 23 października 2009 [code]Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 100000D1, {ffffdd74, ff, 0, f897c8ee} ***** 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 USBPORT.SYS *** ERROR: Module load completed but symbols could not be loaded for USBPORT.SYS *** WARNING: Unable to verify timestamp for usbhub.sys *** ERROR: Module load completed but symbols could not be loaded for usbhub.sys *** WARNING: Unable to verify timestamp for hal.dll *** ERROR: Module load completed but symbols could not be loaded for hal.dll ************************************************************************* *** *** *** *** *** 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 <symbol_path> 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 <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Probably caused by : USBPORT.SYS ( USBPORT+18649 ) Followup: MachineOwner --------- Już pozbyłem się tego problemu. Problem tkwił w Service Pack. Otóż ściągnąłem i zainstalowałem Service Pack 3 i teraz wszystko śmiga(chociaż wcześniej też miałem SP3). Ale znów zrobiłem tą analizę i wyszło coś takiego. Dodam jeszcze, że wtedy, kiedy ten błąd jeszce występował i wkładałem coś do portu USB, komputer sie resetował, ale bez pojawiania się blue screen'a(myszak nie stwarzała tego problemu, czyli nie powodował restartu) a winda z podłączonym np. odtwarzaczem mp3 nie mogła wstać. Gdy już po raz pierwszy zrobiłem tą Bugcheck Analysis, to zaczął się pojawiać blue scrren z tym oto błędem 1000007E i dzięki temu doszedłem, żeby zainstalować SP3. Teraz podaje Bugcheck Analysis i mam pytanie czy coś jest nie tak? Chodzi mi o to czy już wszystko gra, czy mam znów winde stawiać? Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000007E, {c0000005, f89848e5, f89847ec, f89844e8} ***** 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 USBPORT.SYS *** ERROR: Module load completed but symbols could not be loaded for USBPORT.SYS *** WARNING: Unable to verify timestamp for usbhub.sys *** ERROR: Module load completed but symbols could not be loaded for usbhub.sys *** WARNING: Unable to verify timestamp for Ntfs.sys *** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys *** WARNING: Unable to verify timestamp for hal.dll *** ERROR: Module load completed but symbols could not be loaded for hal.dll ************************************************************************* *** *** *** *** *** 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 <symbol_path> 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 <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Probably caused by : USBPORT.SYS ( USBPORT+18649 ) Followup: MachineOwner ---------[/code]
Psycholandia komentarz 23 października 2009 komentarz 23 października 2009 Podaj konfigurację sprzętu, nie zapomnij o zasilaczu. Zainstaluj sterowniki od chipsetu.
hnaciu komentarz 23 października 2009 Autor komentarz 23 października 2009 Typ procesora Intel Pentium 4, 2400 MHz (18 x 133) Nazwa płyty głównej Gigabyte GA-8PE800 (5 PCI, 1 AGP, 3 DDR DIMM, Audio) Pamięć fizyczna 512 MB (PC3200 DDR SDRAM) Typ BIOS'u Award Modular (03/01/04) Karta wideo ATI Radeon 9550 / X1050 Series Secondary (128 MB) Karta dźwiękowa Creative SB Live! Sound Card Dysk fizyczny WDC WD400EB-00CPF0 (37 GB, IDE) Karta sieciowa ASUS NX1001 Network Adapter zasilacz Megabajt chyba 350W(o ile pamiętam)
Psycholandia komentarz 23 października 2009 komentarz 23 października 2009 Zasilacz jest z czarnej listy, do wymiany na jakiś markowy, tu masz listę polecanych: http://www.forumpc.pl/index.php?showtopic=122742 , starczy Ci jakiś 300-350 W, np. taki: http://www.ceneo.pl/2007355 Zainstaluj te sterowniki od chipsetu: http://download.gigabyte.ru/driver/motherboard_driver_chipset_intel_inf.exe następnie reset i podłącz coś do USB i sprawdź czy dalej resetuje komputer
hnaciu komentarz 23 października 2009 Autor komentarz 23 października 2009 Wiem, że zasilacz jest z czarnej listy, ale nie zamierzam go wymieniać bo na tym kompie co aktualnie mam to juz długo nie będe pracował. Chipsety zainstalowałem, ale problem juz wcześniej rozwiązałem. Nie wiem czy to czytałaś: Już pozbyłem się tego problemu. Problem tkwił w Service Pack. Otóż ściągnąłem i zainstalowałem Service Pack 3 i teraz wszystko śmiga(chociaż wcześniej też miałem SP3). Ale znów zrobiłem tą analizę i wyszło coś takiego. Dodam jeszcze, że wtedy, kiedy ten błąd jeszce występował i wkładałem coś do portu USB, komputer sie resetował, ale bez pojawiania się blue screen'a(myszak nie stwarzała tego problemu, czyli nie powodował restartu) a winda z podłączonym np. odtwarzaczem mp3 nie mogła wstać. Gdy już po raz pierwszy zrobiłem tą Bugcheck Analysis, to zaczął się pojawiać blue scrren z tym oto błędem 1000007E i dzięki temu doszedłem, żeby zainstalować SP3. Teraz podaje Bugcheck Analysis i mam pytanie czy coś jest nie tak? Chodzi mi o to czy już wszystko gra, czy mam znów winde stawiać?
Wciąż szukasz rozwiązania problemu? Napisz teraz na forum!
Możesz zadać pytanie bez konieczności rejestracji - wystarczy, że wypełnisz formularz.