阅读:3300回复:7
请问这是怎么回事: Error Message: STOP 0x000000C5 DRIVER_CORRUPTED_EXPOOL
*******************************************************************************
* * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_CORRUPTED_EXPOOL (c5) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is caused by drivers that have corrupted the system pool. Run the driver verifier against any new (or suspect) drivers, and if that doesn't turn up the culprit, then use gflags to enable special pool. Arguments: Arg1: e131b000, memory referenced Arg2: 00000002, IRQL Arg3: 00000001, value 0 = read operation, 1 = write operation Arg4: 80536d4e, address which referenced memory Debugging Details: ------------------ ***** Kernel symbols are WRONG. Please fix symbols to do analysis. DEFAULT_BUCKET_ID: DRIVER_FAULT BUGCHECK_STR: 0xC5 LAST_CONTROL_TRANSFER: from 80522dea to 8050d064 STACK_TEXT: WARNING: Stack unwind information not available. Following frames may be wrong. fcc028f8 80522dea 00000003 e131b000 80536d4e nt!DbgBreakPointWithStatus+0x4 fcc02cc0 804fc1bb 000000c5 e131b000 00000002 nt!KeDeregisterBugCheckCallback+0x52d fcc02ce0 804d7c50 0000000a e131b000 00000002 nt!KeBugCheckEx+0x19 fcc02cfc 804eefb4 0000000a 00000001 80545f20 nt!Kei386EoiHelper+0x2596 fcc02d14 80534ffa 8053500a 80eb0008 0000031b nt!RtlFindClearBitsAndSet+0x25 00000001 00000000 00000000 00000000 00000000 nt!wcstombs+0x4d3d FOLLOWUP_IP: nt!DbgBreakPointWithStatus+4 8050d064 cc int 3 SYMBOL_STACK_INDEX: 0 FOLLOWUP_NAME: MachineOwner SYMBOL_NAME: nt!DbgBreakPointWithStatus+4 MODULE_NAME: nt IMAGE_NAME: ntoskrnl.exe DEBUG_FLR_IMAGE_TIMESTAMP: 3b7de38f STACK_COMMAND: kb BUCKET_ID: WRONG_SYMBOLS Followup: MachineOwner --------- kd> kb ChildEBP RetAddr Args to Child WARNING: Stack unwind information not available. Following frames may be wrong. fcc028f8 80522dea 00000003 e131b000 80536d4e nt!DbgBreakPointWithStatus+0x4 fcc02cc0 804fc1bb 000000c5 e131b000 00000002 nt!KeDeregisterBugCheckCallback+0x52d fcc02ce0 804d7c50 0000000a e131b000 00000002 nt!KeBugCheckEx+0x19 fcc02cfc 804eefb4 0000000a 00000001 80545f20 nt!Kei386EoiHelper+0x2596 fcc02d14 80534ffa 8053500a 80eb0008 0000031b nt!RtlFindClearBitsAndSet+0x25 00000001 00000000 00000000 00000000 00000000 nt!wcstombs+0x4d3d |
|
|
沙发#
发布于:2004-11-16 13:11
可能是你使用了不当的分页内存:
ExAllocatePool(PagedPool, size); 如果是,试着改为非分页内存试试。 |
|
|
板凳#
发布于:2004-11-16 17:09
请问一下你这种系统崩溃信息是在哪里得到的 用什么方法得到的? 我的系统经常蓝屏,如何能得到崩溃信息 |
|
|
地板#
发布于:2004-11-17 14:51
用串口调试 |
|
地下室#
发布于:2004-11-17 14:57
调试的时候load你的pdb文件就可以定位具体是那条命令了,
某些函数只能在较低的irql下调用,看看你用得对不对 |
|
5楼#
发布于:2004-11-18 19:52
[quote] 用串口调试 [/quote] 不明白,能否讲一讲详细的步骤,都使用了哪些工具啊? |
|
6楼#
发布于:2004-11-25 03:44
1. You didn't use the right symbol. Please use symbol server if you are not debugging a beta version Windows. Check if you use the right symbol with command lm or through menu debug\Modules. (I suppose you are using WinDbg from your output)
2.to cicada. Download free WinDbg from MS website or install it from DDK cd/resouce CD, and read the help. You'll need (1) a development machine and a testing machine (2) a NULL modem cable to connect 2 machines COM ports. OR if you have fireware(1394) card/port in both machines, you can use a 1394 cable. (3) Change boot.ini in your testing machine. Add boot options "/debug /debugport=COM1 /baudrate=115200" for serial debugging and "/debug /debugport=1394 /channel=10" for 1394 debugging. (4) Start WinDbg and select File\Kernel Debugging.., select connection option accoding to your testing machine settings. Restart your testing machine. You can get all these information in help of WinDbg. |
|
7楼#
发布于:2004-11-25 08:26
感谢xqchen!
|
|