BSOF MEMORY MANAGEMENT

Question

I am checking a computer that has periodic BSOD with Memory Dump and Memory Management errors. I tried running SFC and DISM, but computer crashed during the later. I checked the mini dump and one of them reads like so:

    ************* Preparing the environment for Debugger Extensions Gallery repositories **************
       ExtensionRepository : Implicit
       UseExperimentalFeatureForNugetShare : true
       AllowNugetExeUpdate : true
       NonInteractiveNuget : true
       AllowNugetMSCredentialProviderInstall : true
       AllowParallelInitializationOfLocalRepositories : true
       EnableRedirectToChakraJsProvider : false
    
       -- Configuring repositories
          ----> Repository : LocalInstalled, Enabled: true
          ----> Repository : UserExtensions, Enabled: true
    
    >>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds
    
    ************* Waiting for Debugger Extensions Gallery to Initialize **************
    
    >>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.094 seconds
       ----> Repository : UserExtensions, Enabled: true, Packages count: 0
       ----> Repository : LocalInstalled, Enabled: true, Packages count: 42
    
    Microsoft (R) Windows Debugger Version 10.0.27725.1000 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.

    Loading Dump File [D:\Karen Moreno Triaxial\Dumps\012825-28406-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: srv*
    Executable search path is: 
    Windows 10 Kernel Version 22621 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Edition build lab: 22621.1.amd64fre.ni_release.220506-1250
    Kernel base = 0xfffff800`74200000 PsLoadedModuleList = 0xfffff800`74e134f0
    Debug session time: Tue Jan 28 17:16:20.939 2025 (UTC - 7:00)
    System Uptime: 0 days 1:08:40.888
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ................................................................
    ...............
    Loading User Symbols
    PEB address is NULL !
    Loading unloaded module list
    ...........
    For analysis of this file, run !analyze -v
    nt!KeBugCheckEx:
    fffff800`74614f10 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffffb82`bf80a9c0=000000000000001a
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    MEMORY_MANAGEMENT (1a)
        # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 0000000000006001, The subtype of the BugCheck.
    Arg2: ffffffffc000009c
    Arg3: 00000188be4d5000
    Arg4: ffffe6095088cd90
    
    Debugging Details:
    ------------------

    KEY_VALUES_STRING: 1
    
        Key  : Analysis.CPU.mSec
        Value: 3468
    
        Key  : Analysis.Elapsed.mSec
        Value: 8112
    
        Key  : Analysis.IO.Other.Mb
        Value: 2
    
        Key  : Analysis.IO.Read.Mb
        Value: 1
    
        Key  : Analysis.IO.Write.Mb
        Value: 34
    
        Key  : Analysis.Init.CPU.mSec
        Value: 1875
    
        Key  : Analysis.Init.Elapsed.mSec
        Value: 30276
    
        Key  : Analysis.Memory.CommitPeak.Mb
        Value: 101
    
        Key  : Analysis.Version.DbgEng
        Value: 10.0.27725.1000
    
        Key  : Analysis.Version.Description
        Value: 10.2408.27.01 amd64fre
    
        Key  : Analysis.Version.Ext
        Value: 1.2408.27.1
    
        Key  : Bugcheck.Code.LegacyAPI
        Value: 0x1a
    
        Key  : Bugcheck.Code.TargetModel
        Value: 0x1a
    
        Key  : Failure.Bucket
        Value: 0x1a_6001_nt!MmStoreProbeAndLockPages
    
        Key  : Failure.Hash
        Value: {3e15d39b-3f7d-fc20-9139-c8a8ddc08425}
    
        Key  : WER.OS.Branch
        Value: ni_release
    
        Key  : WER.OS.Version
        Value: 10.0.22621.1

    BUGCHECK_CODE:  1a
    
    BUGCHECK_P1: 6001
    
    BUGCHECK_P2: ffffffffc000009c
    
    BUGCHECK_P3: 188be4d5000
    
    BUGCHECK_P4: ffffe6095088cd90
    
    FILE_IN_CAB:  012825-28406-01.dmp
    
    FAULTING_THREAD:  ffffe609437c8080
    
    BLACKBOXBSD: 1 (!blackboxbsd)

    BLACKBOXNTFS: 1 (!blackboxntfs)

    BLACKBOXPNP: 1 (!blackboxpnp)

    BLACKBOXWINLOGON: 1
    
    CUSTOMER_CRASH_COUNT:  1
    
    PROCESS_NAME:  MemCompression
    
    STACK_TEXT:  
    fffffb82`bf80a9b8 fffff800`7485a474     : 00000000`0000001a 00000000`00006001 ffffffff`c000009c 00000188`be4d5000 : nt!KeBugCheckEx
    fffffb82`bf80a9c0 fffff800`747c80d9     : 00000000`00040000 fffff800`00000000 ffffe609`461658d8 00000000`00000000 : nt!MmStoreProbeAndLockPages+0x178
    fffffb82`bf80aad0 fffff800`747c8b4b     : 00000000`00040000 fffff800`747c89f3 fffffb82`bf80ab40 00000000`00000080 : nt!SmKmProbeAndLockAddress+0x5d
    fffffb82`bf80ab00 fffff800`746d69da     : 00000000`00040000 00000000`00000004 00000188`be4d0000 00000000`00020000 : nt!SmKmStoreHelperCommandProcess+0x103
    fffffb82`bf80ab70 fffff800`7454d247     : ffffe609`437c8080 00000000`00000080 fffff800`7456a1b0 000f806f`b4bbbdff : nt!SmKmStoreHelperWorker+0x16c82a
    fffffb82`bf80abf0 fffff800`7461a084     : ffffbe01`f4c5b180 ffffe609`437c8080 fffff800`7454d1f0 ffffffff`ffffffff : nt!PspSystemThreadStartup+0x57
    fffffb82`bf80ac40 00000000`00000000     : fffffb82`bf80b000 fffffb82`bf805000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34

    SYMBOL_NAME:  nt!MmStoreProbeAndLockPages+178
    
    MODULE_NAME: nt
    
    IMAGE_VERSION:  10.0.22621.4746
    
    STACK_COMMAND:  .process /r /p 0xffffe609446f2040; .thread 0xffffe609437c8080 ; kb
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    BUCKET_ID_FUNC_OFFSET:  178
    
    FAILURE_BUCKET_ID:  0x1a_6001_nt!MmStoreProbeAndLockPages
    
    OS_VERSION:  10.0.22621.1
    
    BUILDLAB_STR:  ni_release
    
    OSPLATFORM_TYPE:  x64
    
    OSNAME:  Windows 10
    
    FAILURE_ID_HASH:  {3e15d39b-3f7d-fc20-9139-c8a8ddc08425}
    
    Followup:     MachineOwner
    ---------
    
    0: kd> lmvm nt
    Browse full module list
    start             end                 module name
    fffff800`74200000 fffff800`75247000   nt         (pdb symbols)          C:\ProgramData\Dbg\sym\ntkrnlmp.pdb\8E0154339DE8EA44AC65562262A984951\ntkrnlmp.pdb
        Loaded symbol image file: ntkrnlmp.exe
        Mapped memory image file: C:\ProgramData\Dbg\sym\ntkrnlmp.exe\E10F791C1047000\ntkrnlmp.exe
        Image path: ntkrnlmp.exe
        Image name: ntkrnlmp.exe
        Browse all global symbols  functions  data  Symbol Reload
        Image was built with /Brepro flag.
        Timestamp:        E10F791C (This is a reproducible build file hash, not a timestamp)
        CheckSum:         00B8E13C
        ImageSize:        01047000
        File version:     10.0.22621.4746
        Product version:  10.0.22621.4746
        File flags:       0 (Mask 3F)
        File OS:          40004 NT Win32
        File type:        1.0 App
        File date:        00000000.00000000
        Translations:     0409.04b0
        Information from resource tables:
            CompanyName:      Microsoft Corporation
            ProductName:      Microsoft® Windows® Operating System
            InternalName:     ntkrnlmp.exe
            OriginalFilename: ntkrnlmp.exe
            ProductVersion:   10.0.22621.4746
            FileVersion:      10.0.22621.4746 (WinBuild.160101.0800)
            FileDescription:  NT Kernel & System
            LegalCopyright:   © Microsoft Corporation. All rights reserved.
    NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2410.11001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\atlmfc.natvis'
    NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2410.11001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\concurrency.natvis'
    NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2410.11001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\cpp_rest.natvis'
    NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2410.11001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\Kernel.natvis'
    NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2410.11001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\ObjectiveC.natvis'
    NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2410.11001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\stl.natvis'
    NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2410.11001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\Usb4Kd.natvis'
    NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2410.11001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\Windows.Data.Json.natvis'
    NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2410.11001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\Windows.Devices.Geolocation.natvis'
    NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2410.11001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\Windows.Devices.Sensors.natvis'
    NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2410.11001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\Windows.Media.natvis'
    NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2410.11001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\windows.natvis'
    NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2410.11001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\winrt.natvis'
    
    ************* Preparing the environment for Debugger Extensions Gallery repositories **************
       ExtensionRepository : Implicit
       UseExperimentalFeatureForNugetShare : true
       AllowNugetExeUpdate : true
       NonInteractiveNuget : true
       AllowNugetMSCredentialProviderInstall : true
       AllowParallelInitializationOfLocalRepositories : true
       EnableRedirectToChakraJsProvider : false
    
       -- Configuring repositories
          ----> Repository : LocalInstalled, Enabled: true
          ----> Repository : UserExtensions, Enabled: true
    
    >>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds
    
    ************* Waiting for Debugger Extensions Gallery to Initialize **************
    
    >>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.078 seconds
       ----> Repository : UserExtensions, Enabled: true, Packages count: 0
       ----> Repository : LocalInstalled, Enabled: true, Packages count: 42
    
    Microsoft (R) Windows Debugger Version 10.0.27725.1000 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.

    Loading Dump File [D:\Karen Moreno Triaxial\Dumps\012825-28453-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 22621 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Edition build lab: 22621.1.amd64fre.ni_release.220506-1250
    Kernel base = 0xfffff807`45c00000 PsLoadedModuleList = 0xfffff807`468134f0
    Debug session time: Tue Jan 28 16:07:05.990 2025 (UTC - 7:00)
    System Uptime: 0 days 3:12:47.576
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ................................................................
    ................
    Loading User Symbols
    PEB address is NULL !
    Loading unloaded module list
    ....................
    For analysis of this file, run !analyze -v
    nt!KeBugCheckEx:
    fffff807`46014f10 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffd786`8e670f70=0000000000000154

Hope you can help me, thank you.

Answer 1

Hi, Brian Alonso Urrea

Welcome to Microsoft Community.

We understand that you are solving the blue screen problem of your computer.  According to the blue screen log you provided, there were two different types of blue screen errors. They are MEMORY_MANAGEMENT (1a) and UNEXPECTED_STORE_EXCEPTION (154). The following is a detailed analysis of these two blue screen errors and possible solutions:The first blue screen error: **MEMORY_MANAGEMENT (1a)**Faulty thread: MemCompressionThis error is usually related to memory management, which may involve memory damage, driver problems, hardware failures, etc.Second Blue Screen Error: **UNEXPECTED_STORE_EXCEPTION (154)**This error is usually storage-related, and may involve a hard disk failure, a drive problem, or a storage controller problem.However, because the log does not report the specific fault thread, it may be impossible to know the specific reason for the error.I suggest you try the following checks first:**1. Memory (RAM) detection:**Use the memory diagnostic tool that comes with Windows or the third-party tool (such as MemTest86) to check whether there is memory damage.**2. Hard disk detection:**Use hard disk diagnostic tools (such as CrystalDiskInfo or special tools provided by the manufacturer) to check the health status of the hard disk to ensure that there are no bad sectors or other hardware failures.**3. Check the hardware connection:**Check the physical connection between the memory module and the hard disk to ensure that it is not loose.**4. Drive and system update:**Especially the drivers related to memory, storage controller and hard disk, ensure that they are all the latest versions.Download the latest version of the driver through Device Manager and official website.5. Use MCT tool to repair the system. This is not a reinstallation of the system. It will repair your system without deleting files or applications. However, if there is important data in the computer, we still recommend backing it up in advance.Once the backup is completed, please follow the steps in the following guide:Download Windows 11Visit the site above and select Download Now Tool-Run Media Creation Tool-Select Yes-Select Accept-Select Create Installation Media for Another Computer-Select DVD ISO File-Save as Local File.Run the local WINDOWS. ISO file-right-click-mount-choose to run setup.exe-choose not to use it temporarily-choose to keep personal files and settings-choose Next-wait for WINDOWS Repair installation to complete-restart the WINDOWS computer.Disclaimer: At this point, we have exhausted all troubleshooting and I recommend that we try to perform a clean install to get your computer back into a working condition. Please ensure that you backup any important data, including Documents, Pictures, Videos, and more. After that, you can find instructions on how to install Windows 10/11 in the following article by MVP Andre: How to: Perform a Custom Installation of Windows 11 and Windows 10 - Microsoft CommunityIf the problem can't be solved through the above steps, it means that there is a serious hardware failure in the computer. I suggest you consider contacting the hardware provider for further technical support.

Best Regards

Nicholas.Z - MSFT | Microsoft Community Support Specialist