+- Windows 7 Forum: konfiguracja, optymalizacja, porady, gadżety • (https://windows7forum.pl)
+-- Dział: Pomoc i wsparcie, Windows 7 (/pomoc-i-wsparcie-windows-7-26-f)
+--- Dział: Konfiguracja i optymalizacja Windows 7 (/konfiguracja-i-optymalizacja-windows-7-9-f)
+--- Wątek: Bluescreeny i prośna o analize Minidump (/bluescreeny-i-prosna-o-analize-minidump-19066-t)
Bluescreeny i prośna o analize Minidump - sybic - 07.10.2011 17:23
Zdarzają mi się coraz częste bluescreeny
Stawiam na hardware, ale to tylko przypuszczenie...
Jak właściwie analizuje się pliki, które gromadzą się w katalogu Minidump?
A tak na szybko to bym miał prośbę o rozszyfrowanie tego pliku, bo być może tak jest odpowiedź co dolega w systemie lub sprzęcie.
http://tgv.neostrada.pl/tmp/100711-8408-01.zip
RE: Bluescreeny i prośna o analize Minidump - jacek-placek - 07.10.2011 18:17
Te pliki odczytuje się za pomocą DebuggingTools_forWindows- http://www.Vista.pl/download/1607_debugging_tools_for_windows_6_10_3_233.html
Zapodaj na forum odczyt minidump, takk będzie prościej
RE: Bluescreeny i prośna o analize Minidump - sybic - 07.10.2011 18:46
takie coś :
Loading Dump File [C:\Windows\Minidump\100711-8408-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 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0x82c08000 PsLoadedModuleList = 0x82d514d0
Debug session time: Fri Oct 7 16:41:36.200 2011 (GMT+2)
System Uptime: 0 days 10:53:54.667
*********************************************************************
* 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
............
RE: Bluescreeny i prośna o analize Minidump - thermalfake - 07.10.2011 20:05
Symbol search path is: *** Invalid ***
Nie masz ustawionej ścieżki dostępu do symboli, druga sprawa - nie ma jej jak pobrać debugger z internetu. W takim wypadku nie da się niczego dowiedzieć.
Wpisz sobie w konsoli taki ciąg:
Set _NT_SYMBOL_PATH = symsrv*symsrv.dll*c:\symbols*http://msdl.microsoft.com/download/symbols
gdzie katalog symbols musi istnieć na dysku.
Patrząc w minidumpa widzę błąd dysku/kontrolera na płycie - ogólnie błąd I/O
Diagnostyka HDD i archiwizacja na początek. Zmień też kabel sygnałowy i upewnij się, że dysk ma dostarczone prawidłowe zasilanie.
Kod:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C: \Users\user\Desktop\100711-8408-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: symsrv*symsrv.dll*c: \symb*http: //msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17592.x86fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0x82c08000 PsLoadedModuleList = 0x82d514d0
Debug session time: Fri Oct 7 16: 41: 36.200 2011 (UTC + 2: 00)
System Uptime: 0 days 10: 53: 54.667
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
............
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 00000003, Process
Arg2: 87777030, Terminating object
Arg3: 8777719c, Process image file name
Arg4: 82e20ce0, Explanatory message (ascii)
Debugging Details:
------------------
PROCESS_OBJECT: 87777030
IMAGE_NAME: hardware_disk
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAULTING_MODULE: 00000000
PROCESS_NAME: wininit.exe
EXCEPTION_RECORD: 9c751c7c -- (.exr 0xffffffff9c751c7c)
ExceptionAddress: 00850083
ExceptionCode: c0000006 (In-page I/O error)
ExceptionFlags: 00000000
NumberParameters: 3
Parameter[0]: 00000008
Parameter[1]: 00850083
Parameter[2]: c000000e
Inpage operation failed at 00850083, due to I/O error c000000e
EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - Instrukcja spod 0x%p odwo
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000006 - Instrukcja spod 0x%p odwo
EXCEPTION_PARAMETER1: 00000008
EXCEPTION_PARAMETER2: 00850083
EXCEPTION_PARAMETER3: c000000e
IO_ERROR: (NTSTATUS) 0xc000000e - Okre
EXCEPTION_STR: 0xc0000006_c000000e
FAULTING_IP:
+12a
00850083 ? ?
BUGCHECK_STR: 0xF4_IOERR_C000000E
STACK_TEXT:
9c751448 82ee609f 000000f4 00000003 87777030 nt!KeBugCheckEx+0x1e
9c75146c 82e63c22 82e20ce0 8777719c 877772a0 nt!PspCatchCriticalBreak+0x71
9c75149c 82e63b65 87777030 877fe5a8 c0000006 nt!PspTerminateAllThreads+0x2d
9c7514d0 82c461ea ffffffff c0000006 9c751964 nt!NtTerminateProcess+0x1a2
9c7514d0 82c4544d ffffffff c0000006 9c751964 nt!KiFastCallEntry+0x12a
9c751550 82cbd379 ffffffff c0000006 0001003f nt!ZwTerminateProcess+0x11
9c751964 82c34fe7 9c751c7c 00000000 9c751d34 nt!KiDispatchException+0x497
9c751d04 82c49d87 9c751c7c 0033e958 00000000 nt!KiRaiseException+0x18a
9c751d20 82c461ea 0033e938 0033e958 00000000 nt!NtRaiseException+0x33
9c751d20 00850083 0033e938 0033e958 00000000 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0033ecc0 00000000 00000000 00000000 00000000 0x850083
STACK_COMMAND: kb
FOLLOWUP_IP:
+12a
00850083 ? ?
SYMBOL_STACK_INDEX: a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hardware_disk
SYMBOL_NAME: +12a
FAILURE_BUCKET_ID: 0xF4_IOERR_C000000E_+12a
BUCKET_ID: 0xF4_IOERR_C000000E_+12a
Followup: MachineOwner
---------