machine check exeption, odczyt pliku dmp

[tk0882tk]

Witam!

Od niedawna mam problem, polegający na tym, że objawia mi się blue screen z błędem machine chceck exeption 0x0000009C.
Nie zmieniałem nic w sprzęcie, nie podkręcałem żadnego podzespłu, w tych sprawach jestem laikiem, więc wogóle tego nie ruszam. po prostu zaczęło się to pojawiać od około tygodnia.

Poniżej załaczam odczytany raport z programu Debugging Tools for Windows, proszę o pomoc w odczytaniu go i zdiagnozowaniu problemu.

Wyczytałem, że błąd z tą sygnaturą oznacza problem sprzętowy dotyczący przegrzewania się podzespołów.
Jeśli to jest prawda, to w jaki najlepszy sposób mógłbym sprawdzić które podzespoły się przegrzewają, dlaczego, jakimi programami diagnostycznymi moge to ustalić ?

Zastanawia mnie jeszcze jedna sprawa. Ostatni plik dmp jaki mi się wygenerował w systemie pochodzi z 08 kwietnia, i ten załączam poniżej, natomiast problem zaczął objawiać mi się dużo później, czy mam właściwego pliku szukać jeszcze w innym katalogu? Ten znalazłem w %SystemRoot%\Minidump i taką lokalizację mam też podanę we właściwosciach uruchamiania i odzyskiwania.



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

Loading Dump File [C:\WINDOWS\Minidump\Mini040811-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 Personal
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055ab20
Debug session time: Fri Apr 8 09:18:36.703 2011 (GMT+2)
System Uptime: 0 days 0:25:50.262
*********************************************************************
* 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 19, {20, e3409a53, e3409df3, c744e04}

***** 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!PVOID ***
*** ***
*************************************************************************
*** WARNING: Unable to verify timestamp for Ntfs.sys
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
*** WARNING: Unable to verify timestamp for sr.sys
*** ERROR: Module load completed but symbols could not be loaded for sr.sys
*** WARNING: Unable to verify timestamp for eamon.sys
*** ERROR: Module load completed but symbols could not be loaded for eamon.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 : sptd.sys ( sptd+2cf9c )

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

kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 00000020, a pool block header size is corrupt.
Arg2: e3409a53, The pool entry we were looking for within the page.
Arg3: e3409df3, The next pool entry.
Arg4: 0c744e04, (reserved)

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

ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

MODULE_NAME: sptd

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4ad245ea

BUGCHECK_STR: 0x19_20

POOL_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
e3409a53

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

LAST_CONTROL_TRANSFER: from 8054be41 to 805339ae

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
f79fe5a0 8054be41 00000019 00000020 e3409a53 nt+0x5c9ae
f79fe5f0 f75c9c50 e3409a5b 00000000 f75c50cc nt+0x74e41
f79fe800 f75c5f72 f79fe824 85588080 f79fe954 Ntfs+0x28c50
f79fe9ac f7747f9c 85588080 f79fec00 8669b020 Ntfs+0x24f72
f79fe9c4 f764cf70 8676d008 85588080 f79fec00 sptd+0x2cf9c
f79fe9e8 b7cc4aea 85588080 f79fec00 866c6dd0 sr+0x7f70
f79fea08 80571e16 85588080 f79fec00 86494020 eamon+0x4aea
f79feaf4 8056386c 86738c98 00000000 85e95700 nt+0x9ae16
f79feb7c 80567c63 00000000 f79febbc 00000040 nt+0x8c86c
f79febd0 80571fbc 00000000 00000000 f79fec01 nt+0x90c63
f79fed54 804df06b 0117e780 0117e758 0117e7ac nt+0x9afbc
f79fed64 7c90eb94 badb0d00 0117e744 00000000 nt+0x806b
f79fed68 badb0d00 0117e744 00000000 00000000 0x7c90eb94
f79fed6c 0117e744 00000000 00000000 00000000 0xbadb0d00
f79fed70 00000000 00000000 00000000 00000000 0x117e744


STACK_COMMAND: kb

FOLLOWUP_IP:
sptd+2cf9c
f7747f9c ?? ???

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: sptd+2cf9c

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: sptd.sys

BUCKET_ID: WRONG_SYMBOLS

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

[deFco247]

1. Nie wklejaj takich raportów bez użycia tagów Code.
2. Odinstaluj Daemon Tools, gdyż używany przez niego sterownik spowodował błąd.

[tk0882tk]

Dzieki wielkie za pomoc, program odinstalowalem, zobaczymy co będzie dalej

-- 24 cze 2011, 15:42 --

niestety problem nie został rozwiązany, odinstalowałem Daemon Tools, jednak pojawia mi się nadal ten sam komunikat i blue screen, nie mam w katalogu windows, żadnego nowego pliku zrzutu zeby podesłac do analizy, gdzie dalej moge szukac problemu ?

[cosik_ktosik]

Ściągnij SPTD standalone installer i odinstaluj sterownik sptd.sys