Restarty Z Niewiadomego Powodu

Haladdin · 21 Października 2007

Od jakiegoś czasu (sam nie wiem jakiego) restartuje mi się komputer. Dzieje się to w nieregularnych odstępach czasu. Nieraz po 3 godzinach pracy, nieraz po kilkunastu godzinach. W sumie to rzadko. Raz na 3-4 dni. Ale fakt jest faktem, tak byc nie powinno.

Sprawdzałem RAM programem MemTest86 3.3. Działał całą noc. Nie wykazał żadnych błędów. Sprzęt nie był nigdy podkręcany. Hula pod WinXP MCE 2005 Edition. "Format C:" nie pomógł. Żadnego malware nie ma. Na wszystkie porady z przyczepionego topicu czasu nie mam (typu wyjmij wszystie niepotrzebne części)

Proszę o pomoc. Z góry dzięki.

Crash Dump z WinDbg:

Microsoft ® Windows Debugger Version 6.7.0005.1

Loading Dump File [C:\WINDOWS\Minidump\Mini102007-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: Sat Oct 20 23:10:17.991 2007 (GMT+2)

System Uptime: 0 days 1:40:51.562

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

* 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 4E, {99, 0, 0, 0}

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

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

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

*** ***

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

Probably caused by : ntoskrnl.exe ( nt+5c54e )

Followup: MachineOwner

---------

kd> !analyze -v

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

* *

* Bugcheck Analysis *

* *

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

PFN_LIST_CORRUPT (4e)

Typically caused by drivers passing bad memory descriptor lists (ie: calling

MmUnlockPages twice with the same list, etc). If a kernel debugger is

available get the stack trace.

Arguments:

Arg1: 00000099, A PTE or PFN is corrupt

Arg2: 00000000, page frame number

Arg3: 00000000, current page state

Arg4: 00000000, 0

Debugging Details:

------------------

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

*** ***

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

MODULE_NAME: nt

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 45e54711

BUGCHECK_STR: 0x4E_99

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

LAST_CONTROL_TRANSFER: from 80524c7e to 8053354e

STACK_TEXT:

WARNING: Stack unwind information not available. Following frames may be wrong.

efb8687c 80524c7e 0000004e 00000099 00000000 nt+0x5c54e

efb868bc 804eb07e c0002000 00800000 00000000 nt+0x4dc7e

efb86980 804f5244 e2248800 0090ffff 00000000 nt+0x1407e

efb86a2c 80571e96 81e0c6e0 81fd4e60 82c5d298 nt+0x1e244

efb86a70 80574bb5 829c66c8 81efaea8 00000000 nt+0x9ae96

efb86a84 bf8c0c90 81e0c6e0 00610000 82c5d298 nt+0x9dbb5

efb86ab8 bf8c0d79 81e0c6e0 00000000 82c5d280 win32k+0xc0c90

efb86ad4 8058206d efb86b18 82c5d280 82fae730 win32k+0xc0d79

efb86b00 80584518 bf8c0d37 efb86b18 00000000 nt+0xab06d

efb86b2c 80566b01 81e0c6e0 82c5d298 000f01ff nt+0xad518

efb86b5c 80566cab 81e0c6e0 82c5d298 82fae730 nt+0x8fb01

efb86b84 80566d1c e16746c0 82c5d298 00000024 nt+0x8fcab

efb86bcc 8056a0b1 00000024 00000001 00000001 nt+0x8fd1c

efb86be0 bf8c1037 00000024 00000001 00000000 nt+0x930b1

efb86c00 bf820e52 e1709970 e1709970 81eab770 win32k+0xc1037

efb86c28 bf820efa e1709970 00000000 81eab770 win32k+0x20e52

efb86c44 8058491d 81e0c6e0 00000000 829f7e38 win32k+0x20efa

efb86cf0 80584c65 c0000005 efb86d4c 804e60e9 nt+0xad91d

efb86cfc 804e60e9 829f7e38 efb86d48 efb86d3c nt+0xadc65

efb86d4c 804de9dd 00000001 00000000 efb86d64 nt+0xf0e9

efb86d64 7c90eb94 badb0d00 0012e658 efeadd98 nt+0x79dd

efb86d68 badb0d00 0012e658 efeadd98 efeaddcc 0x7c90eb94

efb86d6c 0012e658 efeadd98 efeaddcc 00000000 0xbadb0d00

efb86d70 efeadd98 efeaddcc 00000000 00000000 0x12e658

efb86d74 efeaddcc 00000000 00000000 00000000 0xefeadd98

efb86d78 00000000 00000000 00000000 00000000 0xefeaddcc

STACK_COMMAND: kb

FOLLOWUP_IP:

nt+5c54e

8053354e 5d pop ebp

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ntoskrnl.exe

SYMBOL_NAME: nt+5c54e

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner

dem · 21 Października 2007

Może się przegrzewa procek. Wyczyść radiator z kurzu. Jeśli masz, nałóż nową pastę.

Haladdin · 21 Października 2007

Spróbuję. Może dorwę gdzieś nową pastę. Nałożę, jak będę miał czas i sprwadzę, czy pomaga. Ale to dopiero w nast. weekendzik.

Jakie mogą być jeszcze ewentualności?? Co jeszcze może być nie tak??

Zaloguj się

Restarty Z Niewiadomego Powodu

Rekomendowane odpowiedzi

Haladdin

Udostępnij tę odpowiedź

Odnośnik do odpowiedzi

Udostępnij na innych stronach

dem

Udostępnij tę odpowiedź

Odnośnik do odpowiedzi

Udostępnij na innych stronach

Haladdin

Udostępnij tę odpowiedź

Odnośnik do odpowiedzi

Udostępnij na innych stronach

Dołącz do dyskusji

Przeglądaj

Cała aktywność