Windows 10: MEMORY MANAGEMENT BSoD keeps happening

Discus and support MEMORY MANAGEMENT BSoD keeps happening in Windows 10 BSOD Crashes and Debugging to solve the problem; I keep getting BSoDs multiple times a day and I have no idea why. The error code is "Memory Management". I've tried various methods which I've seen... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by Dermil, Mar 4, 2019.

  1. DERMIL
    Dermil Win User

    MEMORY MANAGEMENT BSoD keeps happening


    I keep getting BSoDs multiple times a day and I have no idea why. The error code is "Memory Management". I've tried various methods which I've seen suggested online but I think this is a more specialized issue. I've tried the built in memory analyzer in windows and that shows no issues every time, updated all my drivers, uninstalled old ones. Please help me. I'm gonna post the crash dump that I've found. I changed windows to show the full one, hopefully it helps!


    Here's hopefully all the info from the dump:


    MEMORY_MANAGEMENT (1a)

    # Any other values for parameter 1 must be individually examined.

    Arguments:

    Arg1: 0000000000003453, The subtype of the bugcheck.

    Arg2: ffffac0fc5b0a580

    Arg3: 00000000000cd900

    Arg4: 0000000000000003



    Debugging Details:

    ------------------





    KEY_VALUES_STRING: 1





    STACKHASH_ANALYSIS: 1



    TIMELINE_ANALYSIS: 1





    DUMP_CLASS: 1



    DUMP_QUALIFIER: 402



    BUILD_VERSION_STRING: 17134.1.amd64fre.rs4_release.180410-1804



    SYSTEM_PRODUCT_NAME: To Be Filled By O.E.M.



    SYSTEM_SKU: To Be Filled By O.E.M.



    SYSTEM_VERSION: To Be Filled By O.E.M.



    BIOS_VENDOR: American Megatrends Inc.



    BIOS_VERSION: P2.00



    BIOS_DATE: 12/18/2018



    BASEBOARD_MANUFACTURER: ASRock



    BASEBOARD_PRODUCT: B450M Pro4



    BASEBOARD_VERSION:



    DUMP_TYPE: 0



    BUGCHECK_P1: 3453



    BUGCHECK_P2: ffffac0fc5b0a580



    BUGCHECK_P3: cd900



    BUGCHECK_P4: 3



    BUGCHECK_STR: 0x1a_3453



    CPU_COUNT: c



    CPU_MHZ: da5



    CPU_VENDOR: AuthenticAMD



    CPU_FAMILY: 17



    CPU_MODEL: 1



    CPU_STEPPING: 1



    BLACKBOXBSD: 1 (!blackboxbsd)





    BLACKBOXPNP: 1 (!blackboxpnp)





    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT



    PROCESS_NAME: steamwebhelper



    CURRENT_IRQL: 0



    ANALYSIS_SESSION_HOST: DESKO



    ANALYSIS_SESSION_TIME: 03-04-2019 14:53:28.0660



    ANALYSIS_VERSION: 10.0.17763.132 amd64fre



    LAST_CONTROL_TRANSFER: from fffff802b7e8c29c to fffff802b7e3e0c0



    STACK_TEXT:

    ffff900a`0533d318 fffff802`b7e8c29c : 00000000`0000001a 00000000`00003453 ffffac0f`c5b0a580 00000000`000cd900 : nt!KeBugCheckEx

    ffff900a`0533d320 fffff802`b8204e8f : ffffac0f`c5b0a580 00000000`00000000 00000000`00000000 ffffac0f`c5b0ab40 : nt!MiDeleteFinalPageTables+0xfd358

    ffff900a`0533d3d0 fffff802`b7d8cbcf : ffffac0f`c5b0a580 00000000`00000000 ffffac0f`c70e4080 ffffac0f`6e497350 : nt!MmDeleteProcessAddressSpace+0x5f

    ffff900a`0533d420 fffff802`b8192c00 : ffffac0f`bf140a50 ffffac0f`c5b0a550 00000000`00000000 00000000`00000000 : nt!PspProcessDelete+0x13f

    ffff900a`0533d4b0 fffff802`b7d290a6 : 00000000`00000000 00000000`00000000 00000000`00000000 ffffac0f`c5b0a5****cbbc0 00000000`00000001 00000000`00000080 : nt!ObCloseHandleTableEntry+0x259

    ffff900a`0533d690 fffff802`b81e78d9 : 00000000`00000000 00000000`00000000 ffffac0f`c3c5d378 ffffffff`ffffff01 : nt!ExSweepHandleTable+0xc5

    ffff900a`0533d740 fffff802`b813b331 : ffffffff`ffffffff ffffac0f`c3c5d080 ffffffff`00000000 ffffac0f`00000000 : nt!ObKillProcess+0x35

    ffff900a`0533d770 fffff802`b8149d8c : ffffac0f`c3c5d080 ffffd08f`6012e060 ffff900a`0533d988 00000000`00000000 : nt!PspRundownSingleProcess+0x121

    ffff900a`0533d7f0 fffff802`b822e843 : 00000000`00000000 ffffbc81`6df79101 000000e2`ac3e7000 fffff802`b7d2abbb : nt!PspExitThread+0x5ac

    ffff900a`0533d8f0 fffff802`b7d2e390 : ffff6115`00001000 ffffac0f`00000004 ffff900a`00000000 00000000`00000000 : nt!KiSchedulerApcTerminate+0x33

    ffff900a`0533d930 fffff802`b7e42170 : 00000000`000005b8 ffff900a`0533d9c0 00000000`0533db00 ffff9381`00000000 : nt!KiDeliverApc+0x3a0

    ffff900a`0533d9c0 fffff802`b7e4e7ea : ffffac0f`c70e4080 00000000`00000000 00000000`00000000 ffffac0f`c3f0a5c0 : nt!KiInitiateUserApc+0x70

    ffff900a`0533db00 00007ff8`63cfaa24 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9f

    000000e2`adbff618 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`63cfaa24





    THREAD_SHA1_HASH_MOD_FUNC: 9d5af0ebd06843cf176ac2a72bb10130e43a97a3



    THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 46cb8b5512dd137b2e210a460d3a79ba65f046bc



    THREAD_SHA1_HASH_MOD: 38bc5fec3f0409c265cf5c87da6f8f8859d0711c



    FOLLOWUP_IP:

    nt!MiDeleteFinalPageTables+fd358

    fffff802`b7e8c29c cc int 3



    FAULT_INSTR_CODE: 6483cccc



    SYMBOL_STACK_INDEX: 1



    SYMBOL_NAME: nt!MiDeleteFinalPageTables+fd358



    FOLLOWUP_NAME: MachineOwner



    MODULE_NAME: nt



    DEBUG_FLR_IMAGE_TIMESTAMP: 5c5a45ab



    STACK_COMMAND: .thread ; .cxr ; kb



    IMAGE_NAME: memory_corruption



    BUCKET_ID_FUNC_OFFSET: fd358



    FAILURE_BUCKET_ID: 0x1a_3453_nt!MiDeleteFinalPageTables



    BUCKET_ID: 0x1a_3453_nt!MiDeleteFinalPageTables



    PRIMARY_PROBLEM_CLASS: 0x1a_3453_nt!MiDeleteFinalPageTables



    TARGET_TIME: 2019-03-04T18:37:18.000Z



    OSBUILD: 17134



    OSSERVICEPACK: 0



    SERVICEPACK_NUMBER: 0



    OS_REVISION: 0



    SUITE_MASK: 272



    PRODUCT_TYPE: 1



    OSPLATFORM_TYPE: x64



    OSNAME: Windows 10



    OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS



    OS_LOCALE:



    USER_LCID: 0



    OSBUILD_TIMESTAMP: 2019-02-05 22:25:47



    BUILDDATESTAMP_STR: 180410-1804



    BUILDLAB_STR: rs4_release



    BUILDOSVER_STR: 10.0.17134.1.amd64fre.rs4_release.180410-1804



    ANALYSIS_SESSION_ELAPSED_TIME: 616



    ANALYSIS_SOURCE: KM



    FAILURE_ID_HASH_STRING: km:0x1a_3453_nt!mideletefinalpagetables



    FAILURE_ID_HASH: {5341b5a0-5b02-2da1-51b3-df124a48f6f9}



    Followup: MachineOwner

    ---------

    :)
     
    Dermil, Mar 4, 2019
    #1
  2. CHILLIP001
    Chillip001 Win User

    MEMORY MANAGEMENT BSOD

    Keep receiving the memory management BSOD and must reboot by holding the power button down, this is happening multiple times a day.
     
    Chillip001, Mar 4, 2019
    #2
  3. ARGEL OBM
    Argel Obm Win User
    BSOD- memory management

    Upon checking the dump file, the issue is being caused by ntoskrnl.exe. Ntoskrnl.exe is the one responsible for memory management that is why you're having the Memory Management error. We suggest that you follow the steps found in the link that we provided
    in our last reply to resolve the issue. Please take note that if you're overclocking your processor or video card, kindly reset their settings to default.

    Let us know the outcome after performing the provided steps.
     
    Argel Obm, Mar 4, 2019
    #3
  4. COLD STORM
    Cold Storm Win User

    MEMORY MANAGEMENT BSoD keeps happening

    IRQ memory BSODS, device manager, memory range?

    The only time I've seen that type of BSOD for myself is when I fried the PCI-e slots on my Striker 2 board... There wasn't anything that I could do, try and rma and go on.. I would suggest the steps that MilkyWay has said.. But, if you really don't know much about Bios's... I wouldn't play with Irq's... That can mess up everything on your board. USB, ethernet, ram, chip... But, that's just me on playing with irq's... To much of a hassle IMHO..
     
    Cold Storm, Mar 4, 2019
    #4
Thema:

MEMORY MANAGEMENT BSoD keeps happening

Loading...

  1. MEMORY MANAGEMENT BSoD keeps happening - Similar Threads - MEMORY MANAGEMENT BSoD

  2. Memory Management BSOD

    in Windows 10 Gaming
    Memory Management BSOD: I just got a BSOD maybe 30 seconds after waking from sleep, here is the dump file. Any help is appreciated. Thanks.Dump filehttps://easyupload.io/1l3sl7 https://answers.microsoft.com/en-us/windows/forum/all/memory-management-bsod/d54c3525-bfc7-49c7-b9fb-00d1a08283da

  3. BSoD memory management

    in Windows 10 BSOD Crashes and Debugging
    BSoD memory management: I Keep Getting BSoD memory management and I don't know what to do sfc /scannow keeps giving me an error with something like windows resource protection couldn't perform the requested operation and chkdsk won't work! I've tried sfc scannow even is safe mode. I can barley use...

  4. Memory Management BSoD

    in Windows 10 Software and Apps
    Memory Management BSoD: I often get the Memory Management BSoD. But only in Call of Duty and i cant explain why. I tried various methods, i found online, but nothing worked. Changed every Ram too. Updated all drivers.... please help me i dont know what to do..All Infos from the...

  5. BSOD: Memory Management

    in Windows 10 BSOD Crashes and Debugging
    BSOD: Memory Management: I am having issues with the aforementioned error for Windows 10. The motherboard and CPU are new but the RAM is from a different mobo/CPU that I have had for 4 years now.I first encounter the BSOD when changing after a user name but 'sfscan /scannow' fixed that. Yet, after an...

  6. Memory Management BSOD

    in Windows 10 BSOD Crashes and Debugging
    Memory Management BSOD: Hi, I've started getting Memory Management BSOD randomly. I've tried all the usual troubleshooting methods e.g. memory diagnostic, sfc and chkdsk all found no issues. I finally gave up and did a Windows reset however this has not fixed my issue. please find attached the...

  7. Memory Management BSOD

    in Windows 10 BSOD Crashes and Debugging
    Memory Management BSOD: I know there have been tons of Q and A about this situation. re: the Memory Management BSOD Mine usually occurs (but not exclusively) when I reboot or shut down the PC. So let me list what I've done so far: Microsoft Memory Diagnostics Tool (tested clean) Dell Memory...

  8. BSOD Memory Management

    in Windows 10 BSOD Crashes and Debugging
    BSOD Memory Management: For the past week I've had a BSOD Memory Management when I turn my PC off, but not while it's running otherwise. I've attached the report generated by "log collector v2-beta17". What advice can you give me, please? Cheers Ralph 128150

  9. MEMORY MANAGEMENT BSOD

    in Windows 10 BSOD Crashes and Debugging
    MEMORY MANAGEMENT BSOD: Keep receiving the memory management BSOD and must reboot by holding the power button down, this is happening multiple times a day. https://answers.microsoft.com/en-us/windows/forum/all/memory-management-bsod/10a0fd4f-6176-46a8-ab20-035fa86762a2

  10. BSOD Memory management ?

    in Windows 10 BSOD Crashes and Debugging
    BSOD Memory management ?: Been getting this weird bluescreen just in the last few days, I don't think it's ram because I've ran memtest and 0 errors 47492