cosik_ktosik ,
tym drugim testuje
jest tylko ten jeden dmp
W dniu 12.07.2008 , o godzinie 16:39 został dopisany post przez shadow&dust
cosik_ktosik ,
Microsoft ® Windows Debugger Version 6.9.0003.113 X86
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [C]
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 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 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Sat Jul 12 15:45:39.984 2008 (GMT+2)
System Uptime: 0 days 1:28:43.715
*********************************************************************
* 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 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 1A, {1234, baa914e2, 0, 0}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*** WARNING: Unable to verify timestamp for AmdK8.sys
*** ERROR: Module load completed but symbols could not be loaded for AmdK8.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 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 argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Probably caused by : AmdK8.sys ( AmdK8+95a9 )
Followup: MachineOwner
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
MEMORY_MANAGEMENT (1a)
Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00001234, The caller is trying lock a nonexistent pageable section.
Arg2: baa914e2
Arg3: 00000000
Arg4: 00000000
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 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 argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
MODULE_NAME: AmdK8
FAULTING_MODULE: 804d7000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4496462b
BUGCHECK_STR: 0x1a_1234
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WRONG_SYMBOLS
LAST_CONTROL_TRANSFER: from 805a8568 to 804f9f33
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
ba9b7aa8 805a8568 0000001a 00001234 baa914e2 nt+0x22f33
ba9b7ad4 baa915a9 baa914e2 ba9b7b08 80537250 nt+0xd1568
ba9b7ae0 80537250 00000000 00000003 00000000 AmdK8+0x95a9
ba9b7b08 80652ef5 00bb63b8 00000003 00000000 nt+0x60250
ba9b7be4 8054161c 00000005 00000004 c0000004 nt+0x17bef5
ba9b7bf8 80501011 badb0d00 ba9b7c70 0006fc70 nt+0x6a61c
ba9b7d44 80612676 00000005 00000004 c0000004 nt+0x2a011
ba9b7d58 8054161c 00000001 0006fc7c 7c90e4f4 nt+0x13b676
ba9b7d64 7c90e4f4 badb0d00 0006fc6c 0065006c nt+0x6a61c
ba9b7d68 badb0d00 0006fc6c 0065006c 0065006d 0x7c90e4f4
ba9b7d6c 0006fc6c 0065006c 0065006d 00000001 0xbadb0d00
ba9b7d70 0065006c 0065006d 00000001 00000002 0x6fc6c
ba9b7d74 0065006d 00000001 00000002 00000001 0x65006c
ba9b7d78 00000000 00000002 00000001 0000000a 0x65006d
STACK_COMMAND: kb
FOLLOWUP_IP:
AmdK8+95a9
baa915a9 a374d1a8ba mov dword ptr [AmdK8+0x5174 (baa8d174)],eax
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: AmdK8+95a9
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: AmdK8.sys
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner