|
|
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [D:\Mini081509-01(ntoskrnl.exe).dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d8000 PsLoadedModuleList = 0x8055e720
Debug session time: Sat Aug 15 20:54:52.203 2009 (GMT+8)
System Uptime: 0 days 0:03:38.828
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
...........................................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000000A, {8cb1b9c, 1c, 0, 805033e5}
Probably caused by : ntoskrnl.exe ( nt!`string'+e5 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 08cb1b9c, memory referenced
Arg2: 0000001c, IRQL
Arg3: 00000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 805033e5, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: 08cb1b9c
CURRENT_IRQL: 1c
FAULTING_IP:
nt!`string'+e5
805033e5 83782400 cmp dword ptr [eax+24h],0
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
LAST_CONTROL_TRANSFER: from 804fdc44 to 805033e5
STACK_TEXT:
aefc2d40 804fdc44 9a5f4400 fffffffe 89e2d298 nt!`string'+0xe5
aefc2d74 8053975a 00000001 00000001 aefc2d94 nt!MmSetExecuteOptions+0x63
aefc2dac 805d0f70 89e2d298 00000000 00000000 nt!MiTrimPte+0x1db
aefc2ddc 805470ee 8053968e 80000000 00000000 nt!IopQueryReconfiguration+0x23
aefc2df8 00000000 00000000 00000000 00001f80 nt!ExpRemovePoolTracker+0x7b
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!`string'+e5
805033e5 83782400 cmp dword ptr [eax+24h],0
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!`string'+e5
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntoskrnl.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 498c11d3
FAILURE_BUCKET_ID: 0xA_nt!_string_+e5
BUCKET_ID: 0xA_nt!_string_+e5
Followup: MachineOwner
---------
请帮忙找原因，谢谢 请把rar改为dmp
[ 本帖最后由 zz_kevin 于 2009-8-15 23:22 编辑 ] |
|
发表于 2009-8-15 23:21:31
楼主