蓝屏问题！！！

kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED (8e)
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: f89f60c2, The address that the exception occurred at
Arg3: b29f4be4, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - "0x%08lx"

FAULTING_IP:
HelloWDM+40c2
f89f60c2 3900            cmp     dword ptr [eax],eax

TRAP_FRAME:  b29f4be4 -- (.trap ffffffffb29f4be4)
ErrCode = 00000000
eax=00000000 ebx=804eee90 ecx=80527ed0 edx=00000016 esi=81f9e550 edi=81ed80e8
eip=f89f60c2 esp=b29f4c58 ebp=00000000 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
HelloWDM+0x40c2:
f89f60c2 3900            cmp     dword ptr [eax],eax  ds:0023:00000000=????????
Resetting default scope

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  AppOfHelloWDM.e

LAST_CONTROL_TRANSFER:  from 804fd973 to 804f9925

STACK_TEXT:  
b29f47ac 804fd973 0000008e c0000005 f89f60c2 nt!KeBugCheckEx+0x1b
b29f4b74 8053e251 b29f4b90 00000000 b29f4be4 nt!KiDispatchException+0x3b1
b29f4bdc 8053e202 00000000 f89f60c2 badb0d00 nt!CommonDispatchException+0x4d
b29f4c00 804f0be1 00000000 821eb040 00000002 nt!Kei386EoiHelper+0x18a
b29f4c60 804eedf9 81ed8030 81d91b90 81d91b90 nt!IopAllocateIrpPrivate+0x1e1
b29f4c70 80578ade 81d79a00 821eb040 00000001 nt!IopfCallDriver+0x31
81d91ba0 81d38c98 00000000 00000000 02020000 nt!IopCloseFile+0x27c
WARNING: Frame IP not in any known module. Following frames may be wrong.
81d91bb8 b29f4c84 00000000 00000000 00000000 0x81d38c98
81d91bbc 00000000 00000000 00000000 00000000 0xb29f4c84


STACK_COMMAND:  kb

FOLLOWUP_IP:
HelloWDM+40c2
f89f60c2 3900            cmp     dword ptr [eax],eax

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  HelloWDM+40c2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: HelloWDM

IMAGE_NAME:  HelloWDM.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c7b5e31

FAILURE_BUCKET_ID:  0x8E_HelloWDM+40c2

BUCKET_ID:  0x8E_HelloWDM+40c2

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

分析一下啊！！！