我单位的一台电脑经常有蓝屏现象，获取dump文件如下：
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: bf80d9fa, The address that the exception occurred at
Arg3: f72a9b0c, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - "0x%08lx"
FAULTING_IP:
win32k!xxxLoadUserApiHook+4f
bf80d9fa ffb694010000 push dword ptr [esi+194h]
TRAP_FRAME: f72a9b0c -- (.trap 0xfffffffff72a9b0c)
ErrCode = 00000000
eax=01000000 ebx=00000000 ecx=00000000 edx=00000001 esi=00544718 edi=e20331c8
eip=bf80d9fa esp=f72a9b80 ebp=f72a9b94 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
win32k!xxxLoadUserApiHook+0x4f:
bf80d9fa ffb694010000 push dword ptr [esi+194h] ds:0023:005448ac=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: RsReport.exe
LAST_CONTROL_TRANSFER: from bf845599 to bf80d9fa
STACK_TEXT:
f72a9b94 bf845599 f72a9ce0 e1559a98 0000c038 win32k!xxxLoadUserApiHook+0x4f
f72a9c6c bf843703 00000000 00000000 bc6a56a8 win32k!xxxCreateWindowEx+0x470
f72a9d20 804df7ec 00000000 0000c038 0000c038 win32k!NtUserCreateWindowEx+0x1c1
f72a9d20 7c92eb94 00000000 0000c038 0000c038 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012f068 00000000 00000000 00000000 00000000 0x7c92eb94
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!xxxLoadUserApiHook+4f
bf80d9fa ffb694010000 push dword ptr [esi+194h]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: win32k!xxxLoadUserApiHook+4f
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 48ce4da7
FAILURE_BUCKET_ID: 0x8E_win32k!xxxLoadUserApiHook+4f
BUCKET_ID: 0x8E_win32k!xxxLoadUserApiHook+4f
Followup: MachineOwner
请问该如何分析这个dump文件呢？谢谢！
