Crash due to ntkrnlmp.exe

I am still learning debugging. I cannot analyze this dump
file and need your assistance. I cannot find the root cause of the issue. I
see some exception but cannot really find the root cause. Here is the log
file below.

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000000031, The subtype of the BugCheck.
Arg2: ffffd58978509800
Arg3: ffff84017d687000
Arg4: ffffbe8b8fe5e597

Debugging Details:
------------------


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2624

    Key  : Analysis.Elapsed.mSec
    Value: 2517

    Key  : Analysis.IO.Other.Mb
    Value: 19

    Key  : Analysis.IO.Read.Mb
    Value: 3

    Key  : Analysis.IO.Write.Mb
    Value: 37

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

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

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

    Key  : Bugcheck.Code.KiBugCheckData
    Value: 0x1a

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x1a

    Key  : Failure.Bucket
    Value: 0x1a_31_nt!MiApplyCompressedFixups

    Key  : Failure.Hash
    Value: {c331f2d1-f573-4955-bed6-0e48314e3a31}

    Key  : Hypervisor.Enlightenments.Value
    Value: 0

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 0

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 0

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 0

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 0

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 0

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 0

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 0

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 0

    Key  : Hypervisor.Flags.HardwareMbecAvailable
    Value: 0

    Key  : Hypervisor.Flags.MaxBankNumber
    Value: 0

    Key  : Hypervisor.Flags.MemoryZeroingControl
    Value: 0

    Key  : Hypervisor.Flags.NoExtendedRangeFlush
    Value: 0

    Key  : Hypervisor.Flags.NoNonArchCoreSharing
    Value: 0

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 0

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 0

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 0

    Key  : Hypervisor.Flags.ValueHex
    Value: 0

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 0

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 0

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 0

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 0

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 0

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 0

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 0

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 0

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 0

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 0

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 0

    Key  : Hypervisor.RootFlags.Value
    Value: 0

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 0

    Key  : SecureKernel.HalpHvciEnabled
    Value: 0

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  1a

BUGCHECK_P1: 31

BUGCHECK_P2: ffffd58978509800

BUGCHECK_P3: ffff84017d687000

BUGCHECK_P4: ffffbe8b8fe5e597

FILE_IN_CAB:  MEMORY.DMP

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME:  explorer.exe

STACK_TEXT:  
ffff948b`e26294d8 fffff802`583fd4fd     : 00000000`0000001a 00000000`00000031 ffffd589`78509800 ffff8401`7d687000 : nt!KeBugCheckEx
ffff948b`e26294e0 fffff802`58235850     : ffff8401`7d687000 ffffbe8b`8fe5e4a2 00000000`000001c3 00000000`00000000 : nt!MiApplyCompressedFixups+0x1c7b2d
ffff948b`e2629540 fffff802`582355fd     : 00000000`00000000 ffffd589`78509800 00000000`07ee0000 00000000`000001c3 : nt!MiPerformFixups+0x88
ffff948b`e26295e0 fffff802`57e8f8c1     : ffffed42`00beb400 ffffd589`78509800 00000000`00000008 ffff948b`e2629750 : nt!MiRelocateImagePfn+0x18d
ffff948b`e2629650 fffff802`582eee89     : 00007ffd`03f10000 00000000`00000000 00007ffb`83f10000 ffffbe8b`8f10fa80 : nt!MiWalkEntireImage+0x521
ffff948b`e2629880 fffff802`582aa304     : ffffd589`78509800 00007ffd`0bdf0000 00000000`00000000 ffffbe8b`8fe5d000 : nt!MiSwitchBaseAddress+0x5d
ffff948b`e26298b0 fffff802`582a9d9d     : 00007ffd`0bdf0000 ffff948b`e2629b80 ffffd589`7578b080 00000000`00000000 : nt!MiRelocateImageAgain+0x188
ffff948b`e2629940 fffff802`582a980f     : ffff948b`e2629b80 ffff948b`00000000 ffffd589`795cf8f0 ffff948b`e2629b80 : nt!MiValidateExistingImage+0x81
ffff948b`e26299e0 fffff802`581fcffd     : 00000000`00000000 ffff948b`e2629b80 ffffd589`7578b080 ffffd589`795cf8f0 : nt!MiShareExistingControlArea+0xc7
ffff948b`e2629a10 fffff802`581fe374     : ffffd589`78509800 00000000`00000000 ffffd589`795cf8f0 00000000`00000000 : nt!MiCreateImageOrDataSection+0x1ad
ffff948b`e2629b00 fffff802`581fcc17     : 00000000`01000000 ffff948b`e2629ec0 00000000`00000001 00000000`00000010 : nt!MiCreateSection+0xf4
ffff948b`e2629c80 fffff802`581fc99c     : 00000000`0364c568 00000000`0000000d 00000000`00000000 00000000`00000001 : nt!MiCreateSectionCommon+0x207
ffff948b`e2629d60 fffff802`58011d08     : 00000000`00000000 00000000`00000001 00000000`04f677e0 00000000`00000000 : nt!NtCreateSection+0x5c
ffff948b`e2629dd0 00007ffd`234edea4     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000000`0364c518 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`234edea4


SYMBOL_NAME:  nt!MiApplyCompressedFixups+1c7b2d

MODULE_NAME: nt

STACK_COMMAND:  .cxr; .ecxr ; kb

IMAGE_NAME:  ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET:  1c7b2d

FAILURE_BUCKET_ID:  0x1a_31_nt!MiApplyCompressedFixups

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {c331f2d1-f573-4955-bed6-0e48314e3a31}

Followup:     MachineOwner
---------

This is sure that its a memory management issue but what is causing a fault in memory ?? Several people on other forums says change RAM but I am not convinced. I wish
Mark Roddy to see this and help me

I wish everyone to please learn to use Markdown when you post something like this, so it's easier for folks to read.

(yes, I edited the dump output so that it starts and ends with triple backticks ``` which are "code" markers)

Did you Google this even once? According to the Microsoft page on bugcheck 0x1a (Bug Check 0x1A MEMORY_MANAGEMENT - Windows drivers | Microsoft Learn):

The image relocation fix-up table or code stream has been corrupted. The error probably is a hardware error.

I did checked if you see the above comments. How ever I did more research and found

The first parameter indicates that image relocation fix-up table has become corrupt, the image relocation table is a table of pointers for a program, which are used to assign memory addresses to parts of the program. Each pointer is called a fix-up. Pointers are basically used in programming, to assign or use memory addresses in programs.

The MSDN documentation points out, that this issue is more hardware related, and therefore the only valid reasons I could think of are - corrupt memory addresses are being assigned or maybe the MMU wasn't translating virtual pages to physical pages, resulting in invalid memory addresses.

Thanks for the help

Apologies Peter, i will take care next time before posting.