用windbg加载dump文件,再把!analyze -v的输出贴上来

kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: f7a9f399, memory referenced
Arg2: 000000ff, IRQL
Arg3: 00000008, value 0 = read operation, 1 = write operation
Arg4: f7a9f399, address which referenced memory

Debugging Details:
------------------

READ_ADDRESS:  f7a9f399

CURRENT_IRQL:  ff

FAULTING_IP:
apic+399
f7a9f399 ??              ???

CUSTOMER_CRASH_COUNT:  5

DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  Idle

IP_MODULE_UNLOADED:
apic+399
f7a9f399 ??              ???

LAST_CONTROL_TRANSFER:  from 80541ee2 to f7a9f399

FAILED_INSTRUCTION_ADDRESS:
apic+399
f7a9f399 ??              ???

STACK_TEXT:  
WARNING: Frame IP not in any known module. Following frames may be wrong.
8054a048 80541ee2 00000008 00000202 00000000 <Unloaded_apic.sys>+0x399
8054a04c 00000000 00000202 00000000 0000000e nt!KiIdleLoop+0x12

STACK_COMMAND:  kb

FOLLOWUP_IP:
apic+399
f7a9f399 ??              ???

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  apic+399

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: apic

IMAGE_NAME:  apic.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  0xD1_CODE_AV_BAD_IP_apic+399

BUCKET_ID:  0xD1_CODE_AV_BAD_IP_apic+399

Followup: MachineOwner
---------

老Y,还在吗?帮忙分析下!非常感激

自己顶下....

再次顶下...

问题依然没有解决,再再次顶下