Błąd systemu


(Andrzej Jura) #1

Witam, komp mi sie sam resetuje, po uruchomieniu wysjkakuje info że system zostałuruchomiony po poważnym błędzie.

Kod błędu:

1000000a BCP1: 00000166 BCP2 00000002 BCP3: 00000000 BCP4: 804E5433 OSVer: 5_1_2600 SP: 3_0 PRODUCT 256_1

Raport błedu:

C:\DOCUME~1\a\USTAWI~\Temp\WER0906.dir00\Mini032609-01.dmp

C:\DOCUME~1\a\USTAWI~\Temp\WER0906.dir00\sysdata.xml

Raport z DMP:

Microsoft ® Windows Debugger Version 6.11.0001.404 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: *** 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 3) UP Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS

Machine Name:

Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0

Debug session time: Thu Mar 26 14:24:45.406 2009 (GMT+1)

System Uptime: 0 days 0:19:34.958

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

* 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 afd.sys, Win32 error 0n2

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

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

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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {166, 2, 0, 804e5433}

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

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

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

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

*** ERROR: Module load completed but symbols could not be loaded for tcpip.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 : avgtdix.sys ( avgtdix+1cb1 )

Followup: MachineOwner


Z GÓRY DZIĘKUJĘ ZA POMOC.


(Skit32) #2

to było na niebieskim czy czarnym tle (w tym przypadku jest to ważne)

jeżeli czarne to masz uszkodzony system lub coś pomieszane a jeżeli niebieskie tło to niewiem


(Cosik Ktosik) #3

Błąd 0x0000000A: Błędy systemu Windows (kody BSOD)

Zapewne plik od AVG


(Skit32) #4

oco chodzi z tym że 0 days 0:19:24


(Andrzej Jura) #5

Chyba chodzi o to ile minęło od ostatniego restartu.

Jaki wniosek, mam zmienić antywira??


(Cosik Ktosik) #6

Uaktualnić go, potem ewentualnie przeinstalować Prawidłowa reinstalacja oprogramowania