顺便贴上 DUMP 文件分析
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: 00000000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, 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: 804fad26, address which referenced memory

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

OVERLAPPED_MODULE: Address regions for 'msdirectx' and 'msdirectx.sy' overlap

WRITE_ADDRESS:  00000000

CURRENT_IRQL:  2

FAULTING_IP:
nt!KeWaitForSingleObject+186
804fad26 8939            mov     dword ptr [ecx],edi

CUSTOMER_CRASH_COUNT:  17

DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  svchost.exe

LAST_CONTROL_TRANSFER:  from 806d376e to 804fad26

STACK_TEXT:  
b8821af8 806d376e 00000000 00000000 00000000 nt!KeWaitForSingleObject+0x186
b8821b18 80639c31 000d0801 86702f68 00000000 hal!ExAcquireFastMutex+0x2a
b8821be4 8063ad63 86702d20 863a7020 b8821c2c nt!DbgkpQueueMessage+0x11f
b8821c08 8063b343 b8821c2c 00000001 86702d20 nt!DbgkpSendApiMessage+0x45
b8821d08 805c705f 7c8106e9 00000000 00000000 nt!DbgkCreateThread+0x391
b8821d50 80542dd2 00000000 7c8106e9 00000001 nt!PspUserThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

STACK_COMMAND:  kb

FOLLOWUP_IP:
nt!KeWaitForSingleObject+186
804fad26 8939            mov     dword ptr [ecx],edi

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!KeWaitForSingleObject+186

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlpa.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4802516a

FAILURE_BUCKET_ID:  0xA_nt!KeWaitForSingleObject+186

BUCKET_ID:  0xA_nt!KeWaitForSingleObject+186

Followup: MachineOwner

没人看自己先慢慢解决了
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.

IRQL太高  

跟进
Arg4: 804fad26, address which referenced memory

STACK_TEXT:  
b8821af8 806d376e 00000000 00000000 00000000 nt!KeWaitForSingleObject+0x186
b8821b18 80639c31 000d0801 86702f68 00000000 hal!ExAcquireFastMutex+0x2a
b8821be4 8063ad63 86702d20 863a7020 b8821c2c nt!DbgkpQueueMessage+0x11f
b8821c08 8063b343 b8821c2c 00000001 86702d20 nt!DbgkpSendApiMessage+0x45
b8821d08 805c705f 7c8106e9 00000000 00000000 nt!DbgkCreateThread+0x391
b8821d50 80542dd2 00000000 7c8106e9 00000001 nt!PspUserThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

看了下堆栈 原因大概是这里了  DbgkCreateThread  跟DbgkpQueueMessage 这两个函数的原因 再看看DbgkCreateThread 用到的偏移
DbgkCreateThread
8063b0d7 399ebc000000    cmp     dword ptr [esi+0BCh],ebx

也玩了一下

也是蓝是蓝

不知楼主解决没

我的也是蓝屏了，不知道楼主怎么解决的啊

顶...我也关注这个问题

学习中

看晕了

这个我解决不掉，对我来说很有难度！学习一下！

顶上去....

小白路过，～～～～～～

事隔一年了，这个问题有解决没？

时隔一年多了，这个问题解决了么，同样遇到DbgkpQueueMessage一改就蓝屏

同求解决方法

我也想知道原因~希望有高手回答一下这个问题

为了不让沉，继续关注~~~~~~~~~

学习中    看的头都晕了

确实很难懂，来学习的

等待答案

我擦，这不是吓唬新人吗，这么难？

这个我也不懂

我也被这个问题困惑，楼主找到方法了么