Błąd w systemie

system · 18 Lipiec 2008 10:25

Witam

Oglądałem film na plejada.pl i nagle komputer się zrestartował po ujżeniu pulpitu pokazał mi się raport " System Windows odzyskał sprawność po poważnym błędzie.

Treść raportu o błędach

C:\DOCUME~1\Piotr\USTAWI~1\Temp\WERa092.dir00\Mini071908-01.dmp

C:\DOCUME~1\Piotr\USTAWI~1\Temp\WERa092.dir00\sysdata.xml

Sygnatura błędu

BCCode : 100000d1 BCP1 : FE642000 BCP2 : 00000002 BCP3 : 00000001

BCP4 : F7E6FFC0 OSVer : 5_1_2600 SP : 2_0 Product : 256_1

W dniu 18.07.2008 , o godzinie 12:25 został dopisany post przez piotrek9550

Co powoduje ten błąd???

cosik_ktosik · 18 Lipiec 2008 10:27

Odczytaj DMP i daj raport (cały): Klik

system · 18 Lipiec 2008 10:41

Microsoft ® Windows Debugger Version 6.9.0003.113 X86

Loading Dump File [C]

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

Product: WinNt, suite: TerminalServer SingleUserTS

Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055ab20

Debug session time: Sat Jul 19 12:12:45.078 2008 (GMT+2)

System Uptime: 0 days 1:18:44.670

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

* 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

…

Unable to load image cmuda.sys, Win32 error 0n2

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

*** ERROR: Module load completed but symbols could not be loaded for cmuda.sys

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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {fe642000, 2, 1, f7e6ffc0}

ANALYSIS: Kernel with unknown size. Will force reload symbols with known size.

ANALYSIS: Force reload command: .reload /f ntoskrnl.exe=FFFFFFFF804D7000,214600,41108004

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

*** ***

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

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

* 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 : cmuda.sys ( cmuda+5dfc0 )

Followup: MachineOwner

cosik_ktosik · 18 Lipiec 2008 10:47

To jest błąd ze sterownikiem CMedii (dźwięk). W evereście komputer->podsumowanie->multimedia, spisz dane o karcie: http://dobreprogramy.pl/index.php?dz=2& … +4.50.1330

system · 18 Lipiec 2008 10:52

Może byś Everest Ultimate

W dniu 18.07.2008 , o godzinie 12:52 został dopisany post przez piotrek9550

Karta dźwiękowa C-Media CMI9739A/9761 @ SiS 7012 Audio Device

cosik_ktosik · 18 Lipiec 2008 10:57

Zobacz te: http://www.download.net.pl/8468/C-Media … E-2000-XP/

lub pobierz stąd: http://drivers-download-center.org/c-me … -download/

system · 18 Lipiec 2008 11:46

te 1-sze są dobre ale jakim cudem te stery były niedobre przecież z płyty oryginalnej

robertm91 · 20 Lipiec 2008 08:43

Witam… mam podobny problem jak piotrek9550 ale to nie jest CMedia chyba ;/

Móglbys sprawdzić co i jak i dać znać jak to naprawić?

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, f7a41b40, b08cfa88, 0}

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

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

*** ERROR: Module load completed but symbols could not be loaded for klif.sys

*** WARNING: Unable to verify timestamp for FDCENT.SYS

*** ERROR: Module load completed but symbols could not be loaded for FDCENT.SYS

Z góry dzięki…

cosik_ktosik · 20 Lipiec 2008 08:44

robertm91 , to odczytaj także plik DMP: Klik

Dodatkowo: http://support.microsoft.com/?scid=kb%3 … 51&x=8&y=2

robertm91 · 20 Lipiec 2008 09:00

Microsoft ® Windows Debugger Version 6.9.0003.113 X86

Loading Dump File [C]

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

Product: WinNt, suite: TerminalServer SingleUserTS

Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a620

Debug session time: Sat Jul 19 21:58:46.528 2008 (GMT+2)

System Uptime: 0 days 4:18:12.524

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

* 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

…

Unable to load image sr.sys, Win32 error 0n2

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

*** ERROR: Module load completed but symbols could not be loaded for sr.sys

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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, f7a41b40, b08cfa88, 0}

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

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

*** ERROR: Module load completed but symbols could not be loaded for klif.sys

*** WARNING: Unable to verify timestamp for FDCENT.SYS

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

*** ***

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

*** ***

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

*** ***

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

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

* 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 : hardware ( klif+154e3 )

Followup: MachineOwner

cosik_ktosik · 20 Lipiec 2008 09:08

Zapoznaj się z tym: http://support.microsoft.com/kb/930916/en-us

W razie czego tłumacz: http://www.google.com/translate_t

robertm91 · 20 Lipiec 2008 21:40

Ok dzięki ;] teraz tylko czekać… czy znowu mi się komp sam zresetuje itp. mam nadzieje że NIE

W dniu 20.07.2008 , o godzinie 23:40 został dopisany post przez robertm91

hmmm ok przed chwilą wyskoczyła mi taka ikonka koło godziny i info że jest uszkodzony plik lub folder $mft hmm i pozniej się komp zresetował po jakiejś chwili :((

Aha dodam że od jakiegoś czasu jak mi się resetowal to wyskakuje za każdym razem gdy uruchamiam kompa takie niebieskie okno i sprawdza pliki na dysku E: wszystkie dyski mam w NTFS… rozumiem że we FAT32 wyskakuje takie coś jak sie wyłaczy kompa np. z listwy anie przez START-> WYŁACZ KOMPUTER, ale myslalem ze w NTFS takiego czegoś już nie będzie… ;/ no dobra i po sprawdzeniu tych plików podczas uruchomienia włacza się normalnie wszystko… ale i tak jak uruchomię ponownie to znowu to samo sprawdza i na tym samym dysku ;/ ten dysk ma tylko niecale 5gb pojemnosci… nie wiem co robić HELP

Microsoft ® Windows Debugger Version 6.9.0003.113 X86

Loading Dump File [C]

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

Product: WinNt, suite: TerminalServer SingleUserTS

Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a620

Debug session time: Sun Jul 20 23:28:49.953 2008 (GMT+2)

System Uptime: 0 days 7:21:47.563

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

* 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

…

Unable to load image Ntfs.sys, Win32 error 0n2

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

*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys

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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {d, ff, 0, 804e35e9}

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

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

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

*** ***

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

*** ***

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

*** ***

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

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

* 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 : klif.sys ( klif+154e3 )

Followup: MachineOwner

cosik_ktosik · 20 Lipiec 2008 21:47

Co do klif.sys: http://www.kaspersky.pl/about.html?s=news&newsid=1030

Co do pierwszego: to normalne, jak się wyłącza w taki sposób.

robertm91 · 21 Lipiec 2008 09:26

Kiedys tak wyłączyłem pare razy bezpośrednio z listwy bo nie chciało mi się czekać i mi padł system ;/

aha co do tego klif.sys to własnie znalazłem tą stronke http://www.kaspersky.pl/about.html?s=news&newsid=1030

ale i tak nie wiedziałem co zrobić ;/ mam kaspersky 7.0.1.325 i chyba nie powinno być już problemu z tym plikiem, jak piszą:

“Błąd przetwarzania danych w sterowniku klif.sys zostanie usunięty w uaktualnieniu produktów Kaspersky Lab, które pojawi się w listopadzie 2007.”

Więc nie wiem nadal… zostawić tak to?

A ten uszkodzony plik lub folder $mft co z tym zrobić?

cosik_ktosik · 21 Lipiec 2008 09:31

W start->uruchom wpisz cmd

w nowych oknie chkdsk /f /r

Niech jeszcze raz sprawdzi dysk, ale dokładniej.

Co do klif… może zainstaluj jeszcze raz kasperskyego.

robertm91 · 21 Lipiec 2008 09:47

Zainstaluje jeszcze raz… ale jak uruchamiam tą komende to:

Typ systemu plików NTFS

Nie można zablokować bieżącego dysku.

Program nie może działać bo wolumin jest używany przez inny proces . Czy ma być sprawdzony przy nastepnym uruchomieniu kompa? T/N

Takie coś wyskoczyło…

W dniu 21.07.2008 , o godzinie 11:47 został dopisany post przez robertm91

Rozumiem że jak wpisze że tak to po uruchomieniu od razu zacznie sprawdzać…

Jeżeli tak to najpierw ściagne innego kasperskyego a pozniej tak zrobie… wpisze ze tak i niech sprawdzi…

cosik_ktosik · 21 Lipiec 2008 09:49

Tam wybierasz na tak, czyli , a sprawdzi po ponownym uruchomieniu komputera.

robertm91 · 21 Lipiec 2008 10:35

Ok zrobie tak ale to za chwilę…

W dniu 21.07.2008 , o godzinie 12:35 został dopisany post przez robertm91

Zrobiłem wszystko… zainstalowałem Kasperskuego na nowo i wpisałem tą komende i uruchomiłem ponownie… ale nadal jest to sprawdzanie dysku E: ;/ wkurza to troche… bo sprawdzi i niby OK wszystko i na nowo to samo jak uruchamiam kompa… ;/

cosik_ktosik · 21 Lipiec 2008 10:45

w menu start->uruchom->wpisz fsutil dirty query e:

Potem wpisz:

chkdsk E: /f

robertm91 · 21 Lipiec 2008 10:53

Pyta czy chce wymusic dezinstalacje tego woluminum E: ?? tzn ze mi wszystko usunie na tym dysku??

W dniu 21.07.2008 , o godzinie 12:53 został dopisany post przez robertm91

Nie można uruchomić programu poniewaz wluminum jest uzywany przez inny proces, mozna go uruchomić po uprzedniej DEZINSTALACJI woluminum. WSZYSTKIE OTWARTE DOJSCIA DO TEGO WOLUMINUM PRZESTANĄ BYĆ PRAWIDŁOWE. I czy wymusić dezinstalacje T/N ;/