Headset usb KERNEL_MODE_HEAP_CORRUPTION

Question

Hi,

Im having some trouble with windows 10. I plugged in my usb headset (razer blackshark) and got a bsod. Might not be related but was quite a coincidence. My PC also randomly froze a few hours after this and I had to force restart.
Any help here would be much appreciated!

Heres the dump (sorry for the formatting couldnt figure out the wysiwyg):

KERNEL_MODE_HEAP_CORRUPTION (13a) The kernel mode heap manager has detected corruption in a heap. Arguments: Arg1: 0000000000000008, A free block was passed to an operation that is only valid for busy blocks. Arg2: ffffa886f1010100, Address of the heap that reported the corruption Arg3: ffffa886f77d5a10, Address at which the corruption was detected Arg4: 0000000000000000

Debugging Details:

fffff80036efb390: Unable to get MiVisibleState Unable to get NonPagedPoolStart Unable to get NonPagedPoolEnd Unable to get PagedPoolStart Unable to get PagedPoolEnd HeapDbgInitExtension Failed *** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec
Value: 5592

Key  : Analysis.DebugAnalysisManager
Value: Create

Key  : Analysis.Elapsed.mSec
Value: 11857

Key  : Analysis.Init.CPU.mSec
Value: 358

Key  : Analysis.Init.Elapsed.mSec
Value: 3754

Key  : Analysis.Memory.CommitPeak.Mb
Value: 93

Key  : WER.OS.Branch
Value: vb\_release

Key  : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key  : WER.OS.Version
Value: 10.0.19041.1

BUGCHECK_CODE: 13a

BUGCHECK_P1: 8

BUGCHECK_P2: ffffa886f1010100

BUGCHECK_P3: ffffa886f77d5a10

BUGCHECK_P4: 0

POOL_ADDRESS: Unable to get NonPagedPoolStart Unable to get NonPagedPoolEnd Unable to get PagedPoolStart Unable to get PagedPoolEnd unable to get nt!MmSpecialPagesInUse ffffa886f77d5a10

FREED_POOL_TAG: ____

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffff8408841fc428 fffff8003678d1c8 : 000000000000013a 0000000000000008 ffffa886f1010100 ffffa886f77d5a10 : nt!KeBugCheckEx ffff8408841fc430 fffff8003678d228 : 0000000000000008 ffff8408841fc540 ffffa886f1010100 0000000000000000 : nt!RtlpHeapHandleError+0x40 ffff8408841fc470 fffff8003678ce55 : ffffa886f77d5a00 ffffa886f1010280 0000000000000000 00000000c0000120 : nt!RtlpHpHeapHandleError+0x58 ffff8408841fc4a0 fffff80036667d52 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!RtlpLogHeapFailure+0x45 ffff8408841fc4d0 fffff800364c73d4 : ffffa886f1010000 0000000000000000 ffffa886f77d5a20 0000000000000000 : nt!RtlpHpVsContextFree+0x19f492 ffff8408841fc570 fffff80036bb1019 : 0000000000000000 0000000000000000 0000000000000000 0100000000100000 : nt!ExFreeHeapPool+0x4d4 ffff8408841fc650 fffff8003a1b5676 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!ExFreePool+0x9 ffff8408841fc680 fffff8003a1b2a5b : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : Wdf01000!FxPoolFree+0x3e [minkernel\wdf\framework\shared\object\wdfpool.cpp @ 456] ffff8408841fc6c0 fffff8003a1c66a8 : 0000000000000000 ffffa886f77d5ec8 ffff8408841fc7f8 fffff800469e0500 : Wdf01000!FxObject::Release+0x11b [minkernel\wdf\framework\shared\inc\private\common\fxobject.hpp @ 881] ffff8408841fc710 fffff80046988312 : ffffa886f77d5b80 000000000000000f ffff8408841fc7b8 ffffa886f77d5ec8 : Wdf01000!imp_WdfObjectDereferenceActual+0x48 [minkernel\wdf\framework\shared\object\fxobjectapi.cpp @ 118] ffff8408841fc750 fffff80046987f6b : 000000000000000f 0000000000000000 000000000000001f fffff800469869c8 : USBXHCI!ESM_RunStateMachine+0x372 ffff8408841fc7b0 fffff800469b592d : ffffa886f83bdb10 0000000000000000 ffffa886ff748b90 0000000000000004 : USBXHCI!ESM_AddEvent+0xfb ffff8408841fc7f0 fffff800469b1c1c : ffffa886f83d57d0 0000000000000000 0000000000000000 fffff80046a2762f : USBXHCI!DeviceSlot_ControllerResetPreReset+0x61 ffff8408841fc820 fffff800469b37d8 : ffffa886f83c9bf0 fffff800469d2901 00000000ebe40011 0000577907c364b8 : USBXHCI!Controller_InternalReset+0x124 ffff8408841fc880 fffff80046a3d5d1 : 0000000000000000 0000000000000000 0000000000000050 00000000000005fa : USBXHCI!Controller_UcxEvtReset+0x58 ffff8408841fc8e0 fffff80046a2757a : 00000000ebe40011 0000000000000000 0000000000000004 0000000000000000 : ucx01000!ControllerResetStateEntryFunc_CallHCDToReset1+0x11 ffff8408841fc910 fffff80046a3c777 : 0000000000000002 fffff800469d2998 fffff800469e0460 ffffa886f73ebae0 : ucx01000!StateMachineEngine_EventAdd+0x26a ffff8408841fc970 fffff800469b190c : 0000000000000002 fffff800469d2998 fffff800469e0460 0000000000000000 : ucx01000!UcxControllerNeedsReset+0x37 ffff8408841fc9a0 fffff800469b2fa7 : ffffa886f73ebae0 ffff8408841fca80 ffffa886f73ebae0 ffff8408841fca80 : USBXHCI!Controller_InitiateRecovery+0x16c ffff8408841fca40 fffff8003a1bc6a7 : ffffa886f73eb9e0 ffffa88600000004 0000000000000004 0000000000000000 : USBXHCI!Controller_TelemetryReportWorker+0x317 ffff8408841fcac0 fffff8003641aad5 : ffffa886f7af8d50 0000000000000000 ffffa886f83ca060 fffff8003a1bc5c0 : Wdf01000!FxWorkItem::WorkItemThunk+0xe7 [minkernel\wdf\framework\shared\core\fxworkitem.cpp @ 431] ffff8408841fcb00 fffff800365034b5 : ffffa886fcf0f040 ffffa886fcf0f040 fffff8003641a9a0 000834e100000000 : nt!IopProcessWorkItem+0x135 ffff8408841fcb70 fffff800364a29a5 : ffffa886fcf0f040 0000000000000080 ffffa886f22a9080 0000000000000001 : nt!ExpWorkerThread+0x105 ffff8408841fcc10 fffff800365fc868 : fffff80033a30180 ffffa886fcf0f040 fffff800364a2950 000834e10804047d : nt!PspSystemThreadStartup+0x55 ffff8408841fcc60 0000000000000000 : ffff8408841fd000 ffff8408841f7000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x28

SYMBOL_NAME: USBXHCI!ESM_RunStateMachine+372

MODULE_NAME: USBXHCI

IMAGE_NAME: USBXHCI.SYS

IMAGE_VERSION: 10.0.19041.867

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 372

FAILURE_BUCKET_ID: 0x13a_8______USBXHCI!ESM_RunStateMachine

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {57dc62e5-2222-b734-d2cc-8a6748326625}

Followup: MachineOwner

Answer 1

Hi,

Thank you for writing to Microsoft Community Forums.

In order to get clarity and to assist you accordingly, please reply with the answers to the questions below:

• What is the Version and Build of Windows 10 installed on the PC? (Type winver in Windows search/Run command)
• What is the make and model of the PC?
• Did you overclock the CPU or GPU?
• Are you aware of any changes on the PC prior to this issue?

Please help us with the latest minidump file. You can locate the dump files in the location C:\Windows\MiniDump, then upload them on OneDrive and share the link with us.

Meanwhile, let us try few methods.

Method 1: Run Driver verifier

Driver Verifier monitors Windows kernel-mode drivers and graphics drivers to detect illegal function calls or actions that might corrupt the system. Driver Verifier can subject Windows drivers to a variety of stresses and tests to find improper behavior. You can configure which tests to run, which allows you to put a driver through heavy stress loads or through more streamlined testing. Please refer this article: Driver verifier

Method 2: Safe mode

Try booting your PC in safe mode. Refer to the article on how to Start your PC in safe mode in Windows 10

Safe mode starts Windows in a basic state, using a limited set of files and drivers. If a problem doesn't happen in safe mode, this means that default settings and basic device drivers aren't causing the issue. Observing Windows in safe mode enables you to narrow down the source of a problem, and can help you troubleshoot problems on your PC.

Method 3: Perform software clean boot

If the issue persists, then try booting your PC in clean boot. Refer to the article on How to perform a clean boot in Windows

---

If performing a clean boot fixes the issue then, please refer to the section How to determine what is causing the problem after you do a clean boot to check which program is causing the issue.

**Note:**Clean Boot starts Windows with a minimal set of drivers and startup programs, so that you can determine whether a background program is interfering with your game or program. Also, you may not be able to use some programs in clean boot. 

Note: Please refer the section Reset the computer to start normally after clean boot troubleshooting to boot the computer in to normal mode after troubleshooting.

Additionally, refer the steps as mention in this article: Troubleshoot blue screen errors **** refer (While using my device)

Let us know the results. If the issue persists, we will certainly assist you further.

Aditya Roy

Microsoft Community – Moderator