C:\Users\Ден>Kdfe -v "D:\MEMORY.DMP"
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [D:\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
Symbol search path is: srv*c:\symbols *
http://msdl.microsoft.com/download/symbol
s
Executable search path is: srv*c:\symbols *
http://msdl.microsoft.com/download/s
ymbols
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17727.x86fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0x8304b000 PsLoadedModuleList = 0x831944d0
Debug session time: Fri Apr 6 20:05:46.968 2012 (UTC + 6:00)
System Uptime: 0 days 0:08:49.140
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {8000, ff, 8, 8000}
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sy
s
Probably caused by : hardware
Followup: MachineOwner
---------
*** Possible invalid call from 9392ff19 ( intelppm+0x2f19 )
*** Expected target 9392f6e6 ( intelppm+0x26e6 )
1: kd> kd: Reading initial command '!analyze -v; q'
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00008000, memory referenced
Arg2: 000000ff, IRQL
Arg3: 00000008, value 0 = read operation, 1 = write operation
Arg4: 00008000, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: 00008000
CURRENT_IRQL: 2
FAULTING_IP:
+624e2faf000ed904
00008000 ?? ???
PROCESS_NAME: System
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
TRAP_FRAME: 807e7c14 -- (.trap 0xffffffff807e7c14)
ErrCode = 00000010
eax=00000001 ebx=859462b8 ecx=85dd9c60 edx=85dfe8f0 esi=93932a1c edi=807cb120
eip=00008000 esp=807e7c88 ebp=9392f708 iopl=0 nv up di ng nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010082
00008000 ?? ???
Resetting default scope
LAST_CONTROL_TRANSFER: from 9392ff1e to 00008000
FAILED_INSTRUCTION_ADDRESS:
+624e2faf000ed904
00008000 ?? ???
POSSIBLE_INVALID_CONTROL_TRANSFER: from 9392ff19 to 9392f6e6
STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
807e7c84 9392ff1e 93932a1c 859462b8 807cb120 0x8000
807e7c98 830cb308 85e01030 807d0800 807cb000 intelppm+0x2f1e
807e7d20 830c2e0d 00000000 0000000e 000000a0 nt!PoIdle+0x4d3
807e7d24 00000000 0000000e 000000a0 11000026 nt!KiIdleLoop+0xd
STACK_COMMAND: .trap 0xffffffff807e7c14 ; kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hardware
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
BUCKET_ID: CPU_CALL_ERROR
Followup: MachineOwner
---------
*** Possible invalid call from 9392ff19 ( intelppm+0x2f19 )
*** Expected target 9392f6e6 ( intelppm+0x26e6 )
quit:
