BSOD - zrzut pamięci

Czy może ktoś pomóc odczytać ten zrzut i podpowiedzieć jaki może byc problem?

Microsoft (R) Windows Debugger  Version 6.5.0003.7

Copyright (c) Microsoft Corporation. All rights reserved.

 

 

Loading Dump File [C:\WINDOWS\Minidump\Mini110606-03.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 2

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

Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420

Debug session time: Mon Nov  6 22:16:28.018 2006 (GMT+1)

System Uptime: 0 days 0:06:07.588

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

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

*** 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 unloaded module list

........

Loading User Symbols

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

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

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

 

Use !analyze -v to get detailed debugging information.

 

BugCheck 10000050, {fff10003, 0, 8059e7a5, 0}

 

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

 

 

Followup: MachineOwner

---------

 Doczytałem się, że jeśli BSOD wskazuje na plik systemowy np. ntoskrnl.exe . jak w moim przypadku - to jest wina sprzętu - ale którego?

 

 

 

Odpowiedzi: 1

A może napiszesz jaki masz problem z kompem i więcej danych o kompie.


 

JNJN
Dodano
11.11.2006 19:15:33
lacomp
Dodano:
11.11.2006 12:37:52
Komentarzy:
1
Strona 1 / 1