Kernel heap corruption subcode 17

Hello,

Anyone know what subcode 17 is for this bugcheck? It is not yet listed online.

Regards, Dejan.

Is this a Canary/Preview build? You can dump the type and see if it's listed. On my Win11 system it only goes up to 0x16:

0: kd> dt nt!_HEAP_FAILURE_TYPE
   heap_failure_internal = 0n0
   heap_failure_unknown = 0n1
   heap_failure_generic = 0n2
   heap_failure_entry_corruption = 0n3
   heap_failure_multiple_entries_corruption = 0n4
   heap_failure_virtual_block_corruption = 0n5
   heap_failure_buffer_overrun = 0n6
   heap_failure_buffer_underrun = 0n7
   heap_failure_block_not_busy = 0n8
   heap_failure_invalid_argument = 0n9
   heap_failure_invalid_allocation_type = 0n10
   heap_failure_usage_after_free = 0n11
   heap_failure_cross_heap_operation = 0n12
   heap_failure_freelists_corruption = 0n13
   heap_failure_listentry_corruption = 0n14
   heap_failure_lfh_bitmap_mismatch = 0n15
   heap_failure_segment_lfh_bitmap_corruption = 0n16
   heap_failure_segment_lfh_double_free = 0n17
   heap_failure_vs_subsegment_corruption = 0n18
   heap_failure_null_heap = 0n19
   heap_failure_allocation_limit = 0n20
   heap_failure_commit_limit = 0n21
   heap_failure_invalid_va_mgr_query = 0n22
0: kd> ?wo(nt!NtBuildNumber)
Evaluate expression: 22631 = 00000000`00005867

It's a Preview, yes. Thanks!

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.