minidumpy-vypisi z pamate.
priklad:
Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini022407-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 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 = 0x805531a0
Debug session time: Sat Feb 24 22:38:36.562 2007 (GMT+1)
System Uptime: 0 days 0:00:28.140
*********************************************************************
* 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 User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {c0000005, 804ef03b, bacdfa6c, bacdf768}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
Probably caused by : ntoskrnl.exe ( nt+1803b )
Followup: MachineOwner
---------
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 804ef03b, The address that the exception occurred at
Arg3: bacdfa6c, Exception Record Address
Arg4: bacdf768, Context Record Address
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
MODULE_NAME: nt
FAULTING_MODULE: 804d7000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 42250a1d
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
FAULTING_IP:
nt+1803b
804ef03b 83780400 cmp dword ptr [eax+4],0
EXCEPTION_RECORD: bacdfa6c -- (.exr ffffffffbacdfa6c)
ExceptionAddress: 804ef03b (nt+0x0001803b)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 20505652
Attempt to read from address 20505652
CONTEXT: bacdf768 -- (.cxr ffffffffbacdf768)
eax=2050564e ebx=00000000 ecx=00001000 edx=00000000 esi=bacdfb68 edi=88fb5ff0
eip=804ef03b esp=bacdfb34 ebp=bacdfb40 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt+0x1803b:
804ef03b 83780400 cmp dword ptr [eax+4],0 ds:0023:20505652=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WRONG_SYMBOLS
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from 8050b799 to 804ef03b
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
bacdfb40 8050b799 88fb5ff0 bacdfb68 bacdfbfc nt+0x1803b
bacdfc24 8050c13f e1e61388 e1e61390 e1e61390 nt+0x34799
bacdfc60 804e381e 88a80978 e1e61388 00000000 nt+0x3513f
bacdfce8 804e3b40 00001000 00000000 00000001 nt+0xc81e
bacdfd2c 804e616a 8a5ba288 8055a1c0 8a5bb8b8 nt+0xcb40
bacdfd74 80533dd0 8a5ba288 00000000 8a5bb8b8 nt+0xf16a
bacdfdac 805c4a06 8a5ba288 00000000 00000000 nt+0x5cdd0
bacdfddc 80540fa2 80533cd0 00000000 00000000 nt+0xeda06
00000000 00000000 00000000 00000000 00000000 nt+0x69fa2
FOLLOWUP_IP:
nt+1803b
804ef03b 83780400 cmp dword ptr [eax+4],0
SYMBOL_STACK_INDEX: 0
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: ntoskrnl.exe
SYMBOL_NAME: nt+1803b
STACK_COMMAND: .cxr 0xffffffffbacdf768 ; kb
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
_________________
Lenovo Thinpad Yoga T570 win 1O pro
Mobil: Apple Iphone 12 pro 256 GB | 
