y*****2
发帖数: 412 | 1 T400 基本没装什么乱七八糟的东西，或者太高深的东西
Dump log
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\010712-13930-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 argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for
ntkrnlpa.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86
compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505
Machine Name:
Kernel base = 0x8400c000 PsLoadedModuleList = 0x841554d0
Debug session time: Sat Jan 7 22:51:00.327 2012 (UTC - 8:00)
System Uptime: 0 days 3:46:09.904
*********************************************************************
* 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 \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for
ntkrnlpa.exe
Loading Kernel Symbols
...............................................................
................................................................
..........................................
Loading User Symbols
Loading unloaded module list
........ | y*****2
发帖数: 412 | 2 搜了半天也不知道 ntkrnlpa.exe 是啥玩意 | G*****h
发帖数: 33134 | | v******n
发帖数: 421 | 4 windows nt kernel with support for PAE...
【在 y*****2 的大作中提到】
: 搜了半天也不知道 ntkrnlpa.exe 是啥玩意
| m****c
发帖数: 252 | 5 你symbol都没有设，根本没法看。
如果是内网，用 !findthebuild /r 然后.reload /f 然后 !analyze -v你就大概知
道哪儿出错了。
如果是外网，
照这个blog来做。
http://blog.chinaunix.net/space.php?uid=20754300&do=blog&id=698 | y*****2
发帖数: 412 | | w*****n
发帖数: 25 | 7 There is no much infomation in the minidump file.
1: kd> !analyze -v
****************************************************************************
***
*
*
* Bugcheck Analysis
*
*
*
****************************************************************************
***
KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in. Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: c0420e58, lock type that was held (value 1,2,3, or PTE address)
Arg2: c000000e, error status (normally i/o status code)
Arg3: 11d92860, current process (virtual address for lock type 3, or PTE)
Arg4: 841cbde3, virtual address that could not be in-paged (or PTE contents
if arg1 is a PTE address)
Debugging Details:
------------------
MARKER_MODULE_NAME: IBM_ibmpmdrv
ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was
specified.
DISK_HARDWARE_ERROR: There was error with disk hardware
BUGCHECK_STR: 0x7a_c000000e
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
FOLLOWUP_NAME: ntmsd
MODULE_NAME: hardware_disk
IMAGE_NAME: hardware_disk
DEBUG_FLR_IMAGE_TIMESTAMP: 0
STACK_COMMAND: kb
FAILURE_BUCKET_ID: 0x7a_c000000e
BUCKET_ID: 0x7a_c000000e
Followup: ntmsd
---------
And I found another dump reported similar issue.I think you probably could
check the system eventlog to see if there was any clue. I would check my
disk driver or h/w if I saw this issue on my PC.
Good luck. |
|
