vista下出现APC_INDEX_MISMATCH蓝屏信息

我得文件系统驱动在ｘｐ下从来没有出现过APC_INDEX_MISMATCH 这个蓝屏信息，但到ｖｉｓｔａ下会出现这个错误，导致蓝屏。请问什么情况下会导致这个错误？如何跟踪到导致这个错误得地方，如何解决？

Bug Check 0x1: APC_INDEX_MISMATCH
The APC_INDEX_MISMATCH bug check has a value of 0x00000001. This indicates that there has been a mismatch in the APC state index.


Parameters
The following parameters are displayed on the blue screen.

Parameter Description
1 The address of the system function (system call)  
2 The value of the following bit computation:

Thread->ApcStateIndex << 8 | Previous ApcStateIndex

 
3 The value of Thread->KernelApcDisable  
4 The value of the previous KernelApcDisable  


Cause
The most common cause of this bug check is when a file system has a mismatched sequence of KeEnterCriticalRegion calls and KeLeaveCriticalRegion calls.

Comments
This is a kernel internal error which can occur only on a checked build. This error occurs on exit from a system call.

DDK稳当上说得

如何跟踪到导致这个错误得地方，如何解决？，用wingdb调吧，找个232线，如果你不会，请参考http://www.wintoolspro.com/?p=32

对不起，我搞错，，跟踪到位置

1 The address of the system function (system call)  

进来先找这位address是个什么函数，闭上眼睛，想想堆栈上层的函数，到底是谁调用了他

Cause
The most common cause of this bug check is when a file system has a mismatched sequence of KeEnterCriticalRegion calls and KeLeaveCriticalRegion calls.
／／这条有用吗？我不太懂，很想帮你
Comments
This is a kernel internal error which can occur only on a checked build. This error occurs on exit from a system call.

如果一句有用的都没有，就当我帮你顶吧，
对于上边“用wingdb调吧，找个232线，如果你不会，请参考”我很抱歉，没注意您是中牛

OK，终于想明白了windbg 自己写个脚本，打出每个eip 值，

Cause
The most common cause of this bug check is when a file system has a mismatched sequence of KeEnterCriticalRegion calls and KeLeaveCriticalRegion calls.
这个有用

OK，终于想明白了windbg 自己写个脚本，打出每个eip 值，记住最后一个EIP的值，和倒数第二个EIP的值

在driverentry上设一断点，停住以后，直接在你刚才记的倒数第二个EIP上设一断点，，或者倒数几个都设上，然后停住，看堆栈信息，不就知道在哪出的问题了么，直接找到位置了