Get kernel mode heap corruption BSOD installing update 8

Discussion Hub General Discussion
1

I now get BSOD and kernel mode heap corruption whe trying to reinstall MSFS 2020

Microsoft (R) Windows Debugger Version 10.0.22549.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [E:\Minidump\030222-13531-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff80726600000 PsLoadedModuleList = 0xfffff8072722a2d0
Debug session time: Wed Mar 2 09:33:37.284 2022 (UTC + 0:00)
System Uptime: 0 days 0:37:16.957
Loading Kernel Symbols
…
…
…
.
Loading User Symbols
Loading unloaded module list
…
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff807269f7610 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffffb08597bb720=000000000000007e
6: kd> !analyze -v

  •                                                                         *

  •                    Bugcheck Analysis                                    *

  •                                                                         *

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common BugCheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but …
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8072845dc42, The address that the exception occurred at
Arg3: fffffb08597bc718, Exception Record Address
Arg4: fffffb08597bbf50, Context Record Address

Debugging Details:

*** WARNING: Unable to verify timestamp for xvdd.sys
*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

Key  : AV.Fault
Value: Read

Key  : Analysis.CPU.mSec
Value: 4952

Key  : Analysis.DebugAnalysisManager
Value: Create

Key  : Analysis.Elapsed.mSec
Value: 19624

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

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

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

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

FILE_IN_CAB: 030222-13531-01.dmp

BUGCHECK_CODE: 7e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8072845dc42

BUGCHECK_P3: fffffb08597bc718

BUGCHECK_P4: fffffb08597bbf50

EXCEPTION_RECORD: fffffb08597bc718 – (.exr 0xfffffb08597bc718)
ExceptionAddress: fffff8072845dc42 (storport!StorPortNotification+0x0000000000000422)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT: fffffb08597bbf50 – (.cxr 0xfffffb08597bbf50)
rax=0000000000000001 rbx=2bdfb47f819f8527 rcx=2bdfb47f819f8527
rdx=2bdfb47f819f8527 rsi=ffff8a8e86e091a0 rdi=ffff8a8e86e091a0
rip=fffff8072845dc42 rsp=fffffb08597bc950 rbp=fffff8072b368570
r8=0000000000000000 r9=0000000000000000 r10=fffffb08597bcb50
r11=fffffb08597bcae0 r12=0000000000000500 r13=0000000000000000
r14=ffff8a8e8e3c5fd0 r15=fffff80727324440
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
storport!StorPortNotification+0x422:
fffff8072845dc42 488b81a8000000 mov rax,qword ptr [rcx+0A8h] ds:002b:2bdfb47f819f85cf=???
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

READ_ADDRESS: fffff807272fa390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
ffffffffffffffff

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR: c0000005

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: ffffffffffffffff

EXCEPTION_STR: 0xc0000005

STACK_TEXT:
fffffb08597bc950 fffff8072845dbfd : ffff8a8e00000001 2bdfb47f819f8527 fffff8072b368570 fffff80726942b1b : storport!StorPortNotification+0x422
fffffb08597bc9a0 fffff8072845d883 : fffffb08597bca90 ffff8a8e87913328 0000000000000000 4faca7671526d95e : storport!StorPortNotification+0x3dd
fffffb08597bca70 fffff8072b3685b3 : fffff8072b391d08 ffff8a8e8628b520 ffff8a8e879149c0 0000000000000000 : storport!StorPortNotification+0x63
fffffb08597bcb40 fffff8072b391d08 : ffff8a8e8628b520 ffff8a8e879149c0 0000000000000000 ffff8a8e8e3c5fd0 : xvdd+0x585b3
fffffb08597bcb48 ffff8a8e8628b520 : ffff8a8e879149c0 0000000000000000 ffff8a8e8e3c5fd0 fffff807268b86c5 : xvdd+0x81d08
fffffb08597bcb50 ffff8a8e879149c0 : 0000000000000000 ffff8a8e8e3c5fd0 fffff807268b86c5 ffff8a8e74f2f040 : 0xffff8a8e8628b520 fffffb08597bcb58 0000000000000000 : ffff8a8e8e3c5fd0 fffff807268b86c5 ffff8a8e74f2f040 ffff8a8e654a08a0 : 0xffff8a8e879149c0

SYMBOL_NAME: xvdd+585b3

MODULE_NAME: xvdd

IMAGE_NAME: xvdd.sys

STACK_COMMAND: .cxr 0xfffffb08597bbf50 ; kb

BUCKET_ID_FUNC_OFFSET: 585b3

FAILURE_BUCKET_ID: AV_xvdd!unknown_function

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {d4f0644e-8138-0a75-0ccb-35df5ac13ead}

Followup: MachineOwner

I get this

Microsoft (R) Windows Debugger Version 10.0.22549.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\OWNER\Desktop\030222-12437-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff80717a00000 PsLoadedModuleList = 0xfffff8071862a2d0
Debug session time: Wed Mar 2 07:56:41.461 2022 (UTC + 0:00)
System Uptime: 0 days 4:06:19.441
Loading Kernel Symbols
…
…
…
Loading User Symbols
Loading unloaded module list
…
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff80717df7610 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffdb02e2253330=000000000000013a
5: kd> !analyze -v

  •                                                                         *

  •                    Bugcheck Analysis                                    *

  •                                                                         *

KERNEL_MODE_HEAP_CORRUPTION (13a)
The kernel mode heap manager has detected corruption in a heap.
Arguments:
Arg1: 0000000000000011, Type of corruption detected
Arg2: ffffdc8fb0602100, Address of the heap that reported the corruption
Arg3: ffffdc8fced84e60, Address at which the corruption was detected
Arg4: 0000000000000000

Debugging Details:

fffff807186fa390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
HeapDbgInitExtension Failed

I’m not that savvy to figure out what went on i’m afraid. The problem seems only to be MSFS2020 Xplane11 ok

2

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