Błąd systemowy, samoistne wyłączanie się komputera

[Kruk_I]

Witam jakiś czas temu wyświetlił mi sie komunikat, że wystąpił poważny błąd systemowy i system odzyskał sprawność po poważnym błędzie i się wyłączył. Niestety co kilka włączeń wyłączał sie sam automatycznie. Miałem troche czasu więc go sformatowałem i wszystko pięknie łaziło aż do dzisiaj. Wyświetlił się znowu ten sam komunikat ale teraz nawet na FF nie da sie wejść musze to pisać z innego kompa(chwała że mam dwa). Ktoś wie jak temu zaradzić? Z góry dziękuje za pomoc

Sygnatura błędu:

BCCode : d0 BCP1 : 00000008 BCP2 : 00000002 BCP3 : 00000000

BCP4 : 8053B425 OSVer : 5_1_2600 SP : 1_0 Product : 256_1

Raport:

C:\WINDOWS\Minidump\Mini121607-03.dmp

C:\DOCUME~1\nidys\USTAWI~1\Temp\WER1.tmp.dir00\sysdata.xml

może to być spowodowane antyvirusem??

[matio]

możesz wkleić zawartośc pliku

C:\WINDOWS\Minidump\Mini121607-03.dmp

[Kaka2 (Kaka_117827603)]

Mienta

Proszę nie podczepiaj się pod tematy innych userów.

[Kruk_I]

bardzo proszę o pomoc

[system]

Miałeś wkleić zawartość pliku Mini. dmp (chyba ich trochę już przybyło), a nie zrzut ekranu tych plików.

Jak się to robi - poczytaj.

[Kruk_I]

Microsoft ® Windows Debugger Version 6.8.0004.0 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 1) UP Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Kernel base = 0x804d4000 PsLoadedModuleList = 0x8054be30 Debug session time: Sun Dec 16 10:27:10.616 2007 (GMT+1) System Uptime: 0 days 0:03:33.199 ********************************************************************* * 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 … ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck C5, {4, 2, 1, 8053cbb8} ANALYSIS: Kernel with unknown size. Will force reload symbols with known size. ANALYSIS: Force reload command: .reload /f ntoskrnl.exe=FFFFFFFF804D4000,1F2700,3D6DE35C ***** 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 : ntoskrnl.exe ( nt+68bb8 ) Followup: MachineOwner ---------

nikt nei wie ;>?