Bug 检查 0x13A:KERNEL_MODE_HEAP_CORRUPTIONBug Check 0x13A: KERNEL_MODE_HEAP_CORRUPTION

KERNEL_MODE_HEAP_CORRUPTION bug 检查的值为 0x0000013A。The KERNEL_MODE_HEAP_CORRUPTION bug check has a value of 0x0000013A. 这表示内核模式堆管理器检测到堆中存在损坏。This indicates that the kernel mode heap manager has detected corruption in a heap.

重要

本主题面向程序员。This topic is for programmers. 如果您是在使用计算机时收到蓝屏错误代码的客户,请参阅蓝屏错误疑难解答If you are a customer who has received a blue screen error code while using your computer, see Troubleshoot blue screen errors.

KERNEL_MODE_HEAP_CORRUPTION ParametersKERNEL_MODE_HEAP_CORRUPTION Parameters

参数Parameter 说明Description
11

检测到的损坏类型 - 请参阅下面的列表Type of corruption detected- see list below

22 报告损坏的堆的地址Address of the heap that reported the corruption
33 检测到损坏的地址Address at which the corruption was detected
44 保留Reserved

参数 1 - 堆损坏的类型Parameter 1 - Type of heap corruption

0x3:检测到损坏的条目标头。0x3 : A corrupt entry header was detected.

0x4:检测到多个损坏的条目标头。0x4 : Multiple corrupt entry headers were detected.

0x5:检测到大分配中的损坏条目标头。0x5 : A corrupt entry header in a large allocation was detected.

0x6:检测到与缓冲区溢出一致的功能损坏。0x6 : A corruption was detected with features consistent with a buffer overrun.

0x7:检测到与缓冲区不足一致的功能损坏。0x7 : A corruption was detected with features consistent with a buffer underrun.

0x8:将可用块传递到仅对繁忙块有效的操作。0x8 : A free block was passed to an operation that is only valid for busy blocks.

0x9:为当前操作指定的参数无效。0x9 : An invalid argument was specified for the current operation.

0xA:检测到无效的分配类型。0xA : An invalid allocation type was detected.

0xB:检测到与“可用后使用”错误一致的功能损坏。0xB : A corruption was detected with features consistent with a use-after-free error.

0XC:为当前操作指定了错误的堆。0xC : The wrong heap was specified for the current operation.

0xD:检测到可用列表已损坏。0xD : A corrupt free list was detected.

0xE:堆在可用列表以外的列表中检测到列表损坏。0xE : The heap detected list corruption in a list other than the free list.

0xF:将可用块传递到仅对繁忙块有效的操作。0xF : A free block was passed to an operation that is only valid for busy blocks.

0x10:堆在当前操作期间检测到无效的内部状态。0x10 : The heap detected invalid internal state during the current operation. 这通常是缓冲区溢出的结果。This is usually the result of a buffer overflow.

0x11:堆在当前操作期间检测到无效的内部状态。0x11 : The heap detected invalid internal state during the current operation. 这通常是缓冲区溢出的结果。This is usually the result of a buffer overflow.

0x12:堆在当前操作期间检测到无效的内部状态。0x12 : The heap detected invalid internal state during the current operation. 这通常是缓冲区溢出的结果。This is usually the result of a buffer overflow.

0x13:向堆 API 传递一个空堆句柄。0x13 : The heap API was passed a NULL heap handle. 查看调用堆栈并确定为堆提供错误句柄的原因。Look at the call stack and to determine why a bad handle was supplied to the heap.

0x14:请求堆分配大于当前分配限制。0x14 : The requested heap allocation is larger then the current allocation limit.

0x15:在执行提交请求的过程中,已确定该请求将超过当前提交限制。0x15 : In the process of performing a commit request, it was determined that the request would exceed the current commit limit.

0x16:在检查给定 VA 管理器分配的大小的过程中,确定查询无效。0x16 : In the process of checking the size of the given VA Manager allocation, it was determined that the query was invalid.

解决方法Resolution

!analyze 调试扩展显示有关 bug 检查的信息,并有助于确定根本原因 。The !analyze debug extension displays information about the bug check and can be helpful in determining the root cause.

!heap 扩展显示堆使用信息、控制堆管理器中的断点、检测泄漏的堆块、搜索堆块或显示页堆信息。The !heap extension displays heap usage information, controls breakpoints in the heap manager, detects leaked heap blocks, searches for heap blocks, or displays page heap information.