BSOD Memory Management


  1. Posts : 2
    Windows 10 Home 64 bit
       #1

    BSOD Memory Management


    About a month ago i bought a brand new computer. Spec available on my profile. RAM Memory has been running on XMP Profile since then. Since 3 last days i've got this problem (no problems before). When i type sfc /scannow in CMD, it says there are corrupt files it cannot repair (but i don't know when has this problem started and if it's related to BSOD). Windows 10 and graphic card drivers are actual.
    DMP file:

    Code:
    Microsoft (R) Windows Debugger Version 10.0.18362.1 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Windows\minidump\081019-7421-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 18362 MP (12 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 18362.1.amd64fre.19h1_release.190318-1202
    Machine Name:
    Kernel base = 0xfffff801`15200000 PsLoadedModuleList = 0xfffff801`156432f0
    Debug session time: Sat Aug 10 21:23:01.936 2019 (UTC + 2:00)
    System Uptime: 0 days 1:12:29.662
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...........................................................
    Loading User Symbols
    Loading unloaded module list
    ........
    For analysis of this file, run !analyze -v
    8: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    MEMORY_MANAGEMENT (1a)
        # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 0000000000041792, A corrupt PTE has been detected. Parameter 2 contains the address of
        the PTE. Parameters 3/4 contain the low/high parts of the PTE.
    Arg2: ffff81bffc5ae848
    Arg3: 0000000000000008
    Arg4: 0000000000000000
    
    Debugging Details:
    ------------------
    
    
    KEY_VALUES_STRING: 1
    
    
    PROCESSES_ANALYSIS: 1
    
    SERVICE_ANALYSIS: 1
    
    STACKHASH_ANALYSIS: 1
    
    TIMELINE_ANALYSIS: 1
    
    
    DUMP_CLASS: 1
    
    DUMP_QUALIFIER: 400
    
    BUILD_VERSION_STRING:  18362.1.amd64fre.19h1_release.190318-1202
    
    DUMP_TYPE:  2
    
    BUGCHECK_P1: 41792
    
    BUGCHECK_P2: ffff81bffc5ae848
    
    BUGCHECK_P3: 8
    
    BUGCHECK_P4: 0
    
    MEMORY_CORRUPTOR:  ONE_BIT
    
    BUGCHECK_STR:  0x1a_41792
    
    CPU_COUNT: c
    
    CPU_MHZ: d48
    
    CPU_VENDOR:  AuthenticAMD
    
    CPU_FAMILY: 17
    
    CPU_MODEL: 8
    
    CPU_STEPPING: 2
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    PROCESS_NAME:  svchost.exe
    
    CURRENT_IRQL:  2
    
    ANALYSIS_SESSION_HOST:  DESKTOP-MCOFKVD
    
    ANALYSIS_SESSION_TIME:  08-10-2019 21:30:46.0128
    
    ANALYSIS_VERSION: 10.0.18362.1 amd64fre
    
    STACK_TEXT:  
    ffff8805`65716da8 fffff801`154279ed : 00000000`0000001a 00000000`00041792 ffff81bf`fc5ae848 00000000`00000008 : nt!KeBugCheckEx
    ffff8805`65716db0 fffff801`152b41a7 : 00000000`00000000 ffff81bf`fc5ae848 00000000`00000000 00000000`00000000 : nt!MiDeleteVa+0x171a4d
    ffff8805`65716ec0 fffff801`152b4661 : ffff8805`65717310 ffff81c0`dffe2d70 00000000`00000000 0a000000`c11ae867 : nt!MiWalkPageTablesRecursively+0x1e7
    ffff8805`65716f80 fffff801`152b4661 : ffff8805`65717310 ffff81c0`e06fff10 00000000`00000000 0a000000`38f38867 : nt!MiWalkPageTablesRecursively+0x6a1
    ffff8805`65717040 fffff801`152b4661 : ffff8805`65717310 ffff81c0`e07037f8 ffff81c0`00000000 0a000000`38e22867 : nt!MiWalkPageTablesRecursively+0x6a1
    ffff8805`65717100 fffff801`152b3dec : ffff8805`65717310 ffff81c0`e0703818 ffff8805`00000000 ffff8805`65717289 : nt!MiWalkPageTablesRecursively+0x6a1
    ffff8805`657171c0 fffff801`152b2258 : ffff8805`65717310 00000000`00000002 00000000`00000001 00000000`00000000 : nt!MiWalkPageTables+0x36c
    ffff8805`657172c0 fffff801`152c03b0 : ffffffff`ffffffff ffff9184`7bd633f8 ffff8805`00000001 00000000`00000000 : nt!MiDeletePagablePteRange+0x268
    ffff8805`65717660 fffff801`157c9c9d : ffff9184`78ac5080 ffff9184`78ac5080 ffff9184`7c0371e0 ffff9184`7bd633f0 : nt!MiDeleteVad+0x860
    ffff8805`65717820 fffff801`157dc084 : ffff9184`7c0371e0 ffff9184`7818aba0 ffff9184`78ac5080 00000000`00000000 : nt!MiUnmapVad+0x49
    ffff8805`65717850 fffff801`157dbb3f : ffff9184`7c03a0c0 ffff9184`7c03a0c0 ffff9184`7bd63080 fffff801`156651c0 : nt!MiCleanVad+0x30
    ffff8805`65717880 fffff801`15835551 : ffffffff`00000000 ffffffff`ffffffff ffff8805`65717b01 ffff9184`7bd63080 : nt!MmCleanProcessAddressSpace+0x137
    ffff8805`65717900 fffff801`1585c313 : ffff9184`7bd63080 ffffb707`0a941060 ffff8805`65717b80 00000000`00000000 : nt!PspRundownSingleProcess+0x139
    ffff8805`65717980 fffff801`15836bcb : 00000000`00000000 ffff8805`65717b01 00000056`e2c16000 ffff9184`78ac5080 : nt!PspExitThread+0x60b
    ffff8805`65717a90 fffff801`153ce118 : ffff9184`00000a64 ffff9184`78ac5080 ffff9184`7bd63080 00000000`00000000 : nt!NtTerminateProcess+0xeb
    ffff8805`65717b00 00007ff8`b8d3c5e4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
    00000056`e2b8f878 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`b8d3c5e4
    
    
    THREAD_SHA1_HASH_MOD_FUNC:  28819333630b094e437e8f4b5f5cbb772be47b43
    
    THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  460d7a0a420c873d1f1a0396811c26cb39aebad5
    
    THREAD_SHA1_HASH_MOD:  9eef8c7ca0ce66f8b8b34848179f303828cff762
    
    SYMBOL_NAME:  ONE_BIT
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: hardware
    
    IMAGE_NAME:  memory_corruption
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    STACK_COMMAND:  .thread ; .cxr ; kb
    
    FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT
    
    BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT
    
    PRIMARY_PROBLEM_CLASS:  MEMORY_CORRUPTION_ONE_BIT
    
    TARGET_TIME:  2019-08-10T19:23:01.000Z
    
    OSBUILD:  18362
    
    OSSERVICEPACK:  239
    
    SERVICEPACK_NUMBER: 0
    
    OS_REVISION: 0
    
    SUITE_MASK:  784
    
    PRODUCT_TYPE:  1
    
    OSPLATFORM_TYPE:  x64
    
    OSNAME:  Windows 10
    
    OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS Personal
    
    OS_LOCALE:  
    
    USER_LCID:  0
    
    OSBUILD_TIMESTAMP:  1972-02-02 09:33:06
    
    BUILDDATESTAMP_STR:  190318-1202
    
    BUILDLAB_STR:  19h1_release
    
    BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202
    
    ANALYSIS_SESSION_ELAPSED_TIME:  2349
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:memory_corruption_one_bit
    
    FAILURE_ID_HASH:  {e3faf315-c3d0-81db-819a-6c43d23c63a7}
    
    Followup:     MachineOwner
    ---------
    Last edited by Brink; 1 Week Ago at 15:13. Reason: code box
      My ComputerSystem Spec


  2. Posts : 271
    Windows 8.1 Enterprise x64
       #2
      My ComputerSystem Spec


 

Related Threads
Solved BSOD Memory Management in BSOD Crashes and Debugging
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
Memory Management BSOD in BSOD Crashes and Debugging
Hello guys, My sister asked me to clean her computer... just scan for viruses, update everything, delete old files, defrag the hdd and it is what I did... now we are getting this memory management BSOD I already tried the mdsched.exe , sfc...
Lenovo Ideapad 720s - crashes started about a month ago. Things I have tried: Memtest x86 - 3 successful passes All hardware tests available - all passed Clean install of windows - problems persisted Blue Screens include:...
Solved Bsod - Memory Management in BSOD Crashes and Debugging
Hi I just build a new pc and I keep getting memory Management bsod. My Mobo only supports 2133 and I bought a 2400mhz ddr4 ram(it was cheap). From the bios it does underclock the speed but I am getting this bsod.. Anything I can do before I change...
BSOD Memory management ? in BSOD Crashes and Debugging
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
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 16:02.
Find Us