Skocz do zawartości


Zdjęcie

Restart kompa kod błędu 1000000a


  • Zaloguj się, aby dodać odpowiedź
1 odpowiedź w tym temacie

#1 ralfi

ralfi

    Nowy

  • 2 postów

Napisano 27 02 2008 - 16:02

Witam
Mam nie mały problem z kompem. Konfiguracja kompa to:
Typ procesora AMD Athlon XP, 1466 MHz (5.5 x 267) 1700+
Nazwa płyty głównej Epox EP-8KMM3I (3 PCI, 1 AGP, 2 DIMM, Audio, Video, LAN)
Karta wideo VIA/S3G KM400 (64 MB) (zintegrowana)
Dysk fizyczny ST340014A (40 GB, 7200 RPM, Ultra-ATA/100)
Napęd dysków optycznych HL-DT-ST CD-ROM GCR-8523B (52x CD-ROM)
System win xp pro
zasilacz 350W

Jak w temacie komp w pewnym momencie się restartuje i nie zauważyłem żadnych powtarzalności w momencie kiedy się restartuję, robi to różnie :)
RAM jest OK testowałem memtestem przez 8 godzin.

a teraz o błędzie
to co znalazłem w dzienniku

Typ zdarzenia:	Błąd
Źródło zdarzenia:	System Error
Kategoria zdarzenia:	(102)
Identyfikator zdarzenia:	1003
Data:		2008-02-26
Godzina:		07:04:23
Użytkownik:		Brak
Komputer:	AGNIESZKA1
Opis:
Kod błędu 1000000a, parametr 1 00000028, parametr 2 00000002, parametr 3 00000000, parametr 4 804ea566.

Aby znaleźć więcej informacji, zobacz http://go.microsoft.com/fwlink/events.asp w Centrum pomocy i obsługi technicznej.
Dane:
0000: 53 79 73 74 65 6d 20 45   System E
0008: 72 72 6f 72 20 20 45 72   rror  Er
0010: 72 6f 72 20 63 6f 64 65   ror code
0018: 20 31 30 30 30 30 30 30	1000000
0020: 61 20 20 50 61 72 61 6d   a  Param
0028: 65 74 65 72 73 20 30 30   eters 00
0030: 30 30 30 30 32 38 2c 20   000028, 
0038: 30 30 30 30 30 30 30 32   00000002
0040: 2c 20 30 30 30 30 30 30   , 000000
0048: 30 30 2c 20 38 30 34 65   00, 804e
0050: 61 35 36 36			   a566

debug zrzutu pamięci z tego zdarzenia (choć nic z tego nie rozumiem)

Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [A:\Mini022608-01.dmp]
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 <symbol_path> 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: Tue Feb 26 02:13:06.359 2008 (GMT+1)
System Uptime: 0 days 10:11:26.906
*********************************************************************
* 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+									*
*********************************************************************
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 1000000A, {28, 2, 0, 804ea566}

***** 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 <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 : ntoskrnl.exe ( nt+13566 )

Followup: MachineOwner
---------

i drugi błąd z dziś

Typ zdarzenia:	Błąd
Źródło zdarzenia:	System Error
Kategoria zdarzenia:	(102)
Identyfikator zdarzenia:	1003
Data:		2008-02-27
Godzina:		11:19:37
Użytkownik:		Brak
Komputer:	AGNIESZKA1
Opis:
Kod błędu 1000000a, parametr 1 62683031, parametr 2 00000002, parametr 3 00000000, parametr 4 804dc25d.

Aby znaleźć więcej informacji, zobacz http://go.microsoft.com/fwlink/events.asp w Centrum pomocy i obsługi technicznej.
Dane:
0000: 53 79 73 74 65 6d 20 45   System E
0008: 72 72 6f 72 20 20 45 72   rror  Er
0010: 72 6f 72 20 63 6f 64 65   ror code
0018: 20 31 30 30 30 30 30 30	1000000
0020: 61 20 20 50 61 72 61 6d   a  Param
0028: 65 74 65 72 73 20 36 32   eters 62
0030: 36 38 33 30 33 31 2c 20   683031, 
0038: 30 30 30 30 30 30 30 32   00000002
0040: 2c 20 30 30 30 30 30 30   , 000000
0048: 30 30 2c 20 38 30 34 64   00, 804d
0050: 63 32 35 64			   c25d

Zrzut z dziś

Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [A:\Mini022708-01.dmp]
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 <symbol_path> 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: Wed Feb 27 11:17:13.093 2008 (GMT+1)
System Uptime: 0 days 0:03:41.640
*********************************************************************
* 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+									*
*********************************************************************
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 1000000A, {62683031, 2, 0, 804dc25d}

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

*** WARNING: Unable to verify timestamp for fltMgr.sys
*** ERROR: Module load completed but symbols could not be loaded for fltMgr.sys
*** WARNING: Unable to verify timestamp for Ntfs.sys
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.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 <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 : ntoskrnl.exe ( nt+525d )

Followup: MachineOwner
---------

Ktoś ma jakieś pomysły bo ja nic z tego nie rozumiem. Szukałem po necie ale nic Ciekawego nie znalazłem.
A czy w ogule z tego idzie wyczytać co konkretnie powoduje błąd czy można się tylko domyślać i próbować wszystkiego po kolej. Licze na was.

  • 0

#2 Nadril

Nadril

    Początkujący

  • 36 postów

Napisano 28 02 2008 - 01:12

niezly strzal z RAMem, byla szansa ze to, to :)

Jesli to nowy komp, to dalbym do sklepu zeby sprawdzili o co chodzi (o ile jest ze sklepu :))

Jesli nie, moze ten temat pomoze: http://forums.techarena.in/showthread.php?t=756528 a moze ten link: http://www.google.pl/search?q=error+100000...lient=firefox-a nie wierze, ze sprawdziles wszystko.

Jak nie pomoze, zawsze mozesz sie skontaktowac z microsoftem, powinni znac rozwiazanie.


Strzelalbym ze plyta jest zla, skoro ram dobry, ale sprobuj wpierw podane wyzej linki (i linki wewnetrze, w zasadzie tylko :)).

  • 0

Zobacz więcej tematów z tagiem: Memtest86+ testowanie pamięci



Użytkownicy przeglądający ten temat: 0

0 użytkowników, 0 gości, 0 anonimowych