Share via

BSOD Memory management

Anonymous
2021-12-07T03:23:29+00:00

Getting random BSOD Errors Memory management, anyone can help, been dealing with this for months, even switched out ram still didnt work Motherboard ASUS x570 Pro NEW RAM Cosair DDR4 32000 MHZ 2 Pack 16GB (I got 2 2 Packs) = 32GB

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

Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 19041 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff801`5cc00000 PsLoadedModuleList = 0xfffff801`5d82a270
Debug session time: Mon Dec  6 17:17:20.196 2021 (UTC - 8:00)
System Uptime: 0 days 6:48:52.827
Loading Kernel Symbols
...............................................................
................................................................
.......................................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000000ac`2e95f018).  Type ".hh dbgerr001" for details
Loading unloaded module list
......
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff801`5cff71b0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffa58a`27ac9dc0=000000000000001a
3: 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: ffffa53ffe467f80
Arg3: 0000004c00000000
Arg4: 0000000000000000

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2249

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 2306

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

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

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

    Key  : MemoryManagement.PFN
    Value: 4c00000

    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:  MEMORY.DMP

BUGCHECK_CODE:  1a

BUGCHECK_P1: 41792

BUGCHECK_P2: ffffa53ffe467f80

BUGCHECK_P3: 4c00000000

BUGCHECK_P4: 0

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXWINLOGON: 1

PROCESS_NAME:  msedge.exe

STACK_TEXT:  
ffffa58a`27ac9db8 fffff801`5ce440ca     : 00000000`0000001a 00000000`00041792 ffffa53f`fe467f80 0000004c`00000000 : nt!KeBugCheckEx
ffffa58a`27ac9dc0 fffff801`5ce9e416     : 00000000`00000000 00000000`00000000 00000000`00000679 ffffa53f`fe467f80 : nt!MiDeleteVa+0x153a
ffffa58a`27ac9ec0 fffff801`5ce9e52b     : ffffa552`9fff2338 ffffd108`92db1700 ffffa58a`00000000 ffffa58a`27aca330 : nt!MiWalkPageTablesRecursively+0x776
ffffa58a`27ac9f60 fffff801`5ce9e52b     : ffffa552`00000000 ffffd108`92db1700 ffffa58a`00000001 ffffa58a`27aca340 : nt!MiWalkPageTablesRecursively+0x88b
ffffa58a`27aca000 fffff801`5ce9e52b     : ffffa552`a94ff000 ffffd108`92db1700 ffffa58a`00000002 ffffa58a`27aca350 : nt!MiWalkPageTablesRecursively+0x88b
ffffa58a`27aca0a0 fffff801`5ce04f4b     : 00000000`00000000 ffffd108`92db1700 00000000`00000003 ffffa58a`27aca360 : nt!MiWalkPageTablesRecursively+0x88b
ffffa58a`27aca140 fffff801`5ce42961     : ffffa58a`27aca2e0 ffffd108`00000000 ffffa53e`00000002 00000000`00000000 : nt!MiWalkPageTables+0x36b
ffffa58a`27aca240 fffff801`5ce12aa0     : 00000000`00000001 ffffa58a`00000000 ffffd108`92db1550 ffffd108`8c6bf080 : nt!MiDeletePagablePteRange+0x4f1
ffffa58a`27aca550 fffff801`5d201149     : ffffd108`9cc1b260 00000000`00000000 ffffd108`00000000 ffffd108`00000000 : nt!MiDeleteVad+0x360
ffffa58a`27aca660 fffff801`5d2007e0     : ffffd108`9cc1b260 ffffd108`9cc6da20 ffffd108`8c6bf080 00000000`00000000 : nt!MiUnmapVad+0x49
ffffa58a`27aca690 fffff801`5d1feaaf     : ffffd108`9cc366a0 ffffd108`9cc366a0 ffffd108`9cc1b260 ffffd108`92db1080 : nt!MiCleanVad+0x30
ffffa58a`27aca6c0 fffff801`5d25c5a8     : ffffffff`00000000 ffffffff`ffffffff 00000000`00000001 ffffd108`92db1080 : nt!MmCleanProcessAddressSpace+0x137
ffffa58a`27aca740 fffff801`5d2b0ab6     : ffffd108`92db1080 ffffe20c`b0e947b0 ffffa58a`27aca990 00000000`00000000 : nt!PspRundownSingleProcess+0x20c
ffffa58a`27aca7d0 fffff801`5d2f53c8     : ffffd108`00000000 00000000`00000001 ffffa58a`27aca9e0 000000ac`2e968000 : nt!PspExitThread+0x5f6
ffffa58a`27aca8d0 fffff801`5ce0ef67     : 00000000`40190088 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSchedulerApcTerminate+0x38
ffffa58a`27aca910 fffff801`5cffb750     : 000000ac`311ff468 ffffa58a`27aca9c0 ffffa58a`27acab80 00000000`00000000 : nt!KiDeliverApc+0x487
ffffa58a`27aca9c0 fffff801`5d008c5f     : ffffd108`8c6bf080 00000000`00000000 ffffa58a`27acab18 ffffffff`eced3000 : nt!KiInitiateUserApc+0x70
ffffa58a`27acab00 00007ffc`e20ccdf4     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9f
000000ac`311ff438 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`e20ccdf4

SYMBOL_NAME:  nt!MiDeleteVa+153a

MODULE_NAME: nt

STACK_COMMAND:  .cxr; .ecxr ; kb

IMAGE_NAME:  ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET:  153a

FAILURE_BUCKET_ID:  0x1a_41792_nt!MiDeleteVa

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {ad6dfca3-101b-35a8-d6e1-12de9ecbc1f5}

Followup:     MachineOwner
---------
Windows for home | Windows 10 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

2 answers

Sort by: Most helpful
  1. Anonymous
    2021-12-07T04:17:09+00:00

    More troubleshooting methods:

    Memory tests do not catch all errors such as mismatched memory (possible even for sticks that appear to be identical) and when faster memory is placed in the system behind slower memory. So it is best to also swap sticks in and out to check for those even if all memory tests fail to show a problem.

    To test RAM check here - let it run 4+ hours or so - overnight is best. <-- best method

    www.memtest.org

    MemTestX86 - Test RAM With

    http://www.tenforums.com/tutorials/14201-memtes...

    ================================================

    After doing ALL the updates you can, and if the issue continues, then run Driver Verifier.

    Driver Verifier can help find some BSOD issues :

    Driver Verifier-- tracking down a misbehaving driver.

    https://answers.microsoft.com/en-us/windows/for...

    Driver Verifier - Enable and Disable in Windows 10

    https://www.tenforums.com/tutorials/5470-enable...

    Using Driver Verifier to identify issues with Windows drivers for advanced users

    http://support.microsoft.com/kb/244617

    How To Troubleshoot Driver Problems in Windows Vista or 7. (8/8.1 and 10

    are essentially the same).

    http://www.winvistaclub.com/t79.html

    Using Driver Verifier

    https://msdn.microsoft.com/en-us/library/window...

    WINKEY + X - RUN - type in -> verifier /reset hit enter to disable

    If Driver Verifier creates a minidump upload it and post the link here so we can analyze it.

    ======

    Please note that consumer-level troubleshooting software rarely specifies a particular piece of hardware so a lot of close observation is required.

    PassMark Burnin Test - Free Trial - note the trial version will only run for 15 minutes and it really needs to be used for many hours. So if you use this you will need to faithfully and quickly restart it every 15 minutes.

    PassMark - BurninTest - Free Trial

    https://www.passmark.com/products/burnintest/

    Running OCCT for Home Use (Free) and the Stress Tests may help indicate a cause.

    OCCT - Free for Home use

    https://www.ocbase.com/

    Running Stress Tests might help indicate a cause - use ALL of these.

    PC Stress Test free software for Windows 10

    https://www.thewindowsclub.com/pc-stress-test-f...

    Here to help,

    Rob


    Standard Disclaimer: Those may be non-Microsoft websites. The pages appear to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the site before you decide to download and install it.

    Please let us know the results and if you need further assistance. Feedback definitely helps us help all.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2021-12-07T04:14:12+00:00

    Hi PrideCui, I am Rob, an Independent Advisor not affiliated with Microsoft and a 15 time and dual award Microsoft MVP specializing in Windows troubleshooting and Bluescreen analysis. Please remember as independents we are not responsible for the development of Windows or the computer hardware and drivers. If you will work with me I will be here to help until the issue is resolved.

    The BugCheck 1A is most often a driver/software issue though it can be caused by hardware problems.

    IMAGE_NAME: ntkrnlmp.exe <-- is a Windows component which means something else drove it into Fault.

    Below are methods to upload the DMP file(s) and other data as well as to troubleshoot.

    Troubleshoot blue screen errors <-- read this link

    http://windows.microsoft.com/en-us/windows-10/t...

    ==================================================

    Go here and download this tool - check ONLY these TWO Boxes -->

    check "Last 10 Event Viewer errors"

    AND

    check the "List Devices" with option "ALL" checked.

    MiniToolBox - Free https://www.bleepingcomputer.com/download/minit... Running the tool will open a readout in NotePad - on the top left menu select "File" - "Save As" ( CTRL + SHIFT +S) - name it what you will, in the folder you wish. and upload the file as you do the minidumps (see below) and paste the link in a reply in this thread.


    Look in C:\Windows for memory.dmp and in C:\Windows\minidump for xxxxxxxxx.dmp files.

    We can analyze the DMP files if you make them available from the OneDrive or other file sharing sites (such as MediaFire). If you have problems uploading the minidumps copy them to the Desktop or the Documents folder and upload them from there.

    One-Drive - Share files and folders and change permissions

    http://windows.microsoft.com/en-us/onedrive/sha...

    Upload photos and files

    http://windows.microsoft.com/en-us/onedrive/add...

    Zip or RAR the files then upload them - the Memory.DMP individually and/or minidumps up to the last 5 altogether.

    Use OneDrive to upload collected files

    https://support.microsoft.com/en-us/office/uplo...

    ====================================================

    A. Are you overclocking anything? If so STOP! OC can not only cause BSOD it can make troubleshooting virtually impossible.

    B. Have you installed any performance or OC software such as MSI Afterburner, AMDRyzenMaster. Intel's Extreme Tuning or Performance Maximizer, or CPU-Z? Some of those and others change system settings during installation which are still in effect even when the program is not running. Even iCUE or other RGB hardware and/or software may be involved.

    C. After both A. & B. reset the BIOS back to the system/motherboard maker's recommendations.


    D. Be sure the SSD's have the latest firmware from their makers.

    E. Try removing and reseating all cards, memory, and cables (both ends when possible) - actually remove and replace - do not just snug (on a PC) and clean out the dust bunnies and vents. (Of course, remove ALL power prior to opening the case.) <-- Please do this as it is the number one cause of the issues you are experiencing (by far).

    F. Try adding a fan blowing on high onto the motherboard's CPU & GPU areas. The point is to increase airflow to maximize heat dissipation. <-- Please do this no matter how much cooling you have now.

    ====================================================

    This utility makes it easy to see which major device driver versions are loaded :

    Run DriverView - set VIEW to Hide Microsoft drivers - update those without Dump in their names (and update BIOS and chipset drivers).

    DriverView - Free - utility displays the list of all device drivers currently loaded on your system. For each driver in the list, additional useful information is displayed: load address of the driver, description, version, product name, company that created the driver, and more.

    http://www.nirsoft.net/utils/driverview.html

    For Drivers check System Maker as fallbacks and Device Maker's which are the most current. Right Click the Start Button - Device Manager - Display Adapter - write down the make and complete model of your video adapter - double click - Driver's tab - write down the version info. Now click Update Driver (this may not do anything as MS is far behind certifying drivers) - then Right Click - Uninstall - REBOOT this will refresh the driver stack.

    Repeat that for Network - Network Card (NIC), Wifi, Sound, Mouse, and Keyboard if 3rd party with their own software and drivers and any other major device drivers you have.

    Now go to System Maker's site (Dell, HP, Toshiba as examples) (as rollback) and then Device Maker's site (Realtek, Intel, Nvidia, ATI as examples) and get their latest versions. (Look for BIOS, Chipset, and software updates at System Maker's site while there.)

    Download - SAVE - go to where you put them - Right Click - RUN AD ADMIN -

    REBOOT after each installation.

    Always check in Device Manager - Drivers tab to be sure the version you are installing actually shows up. This is because some drivers roll back before the latest is installed (sound drivers particularly do this) so install a driver - reboot - check to be sure it is installed and repeat as needed.

    Repeat at Device Makers - BTW at Device Makers DO NOT RUN THEIR SCANNER - check manually by model.

    Manually look at manufacturer's sites for drivers - and Device Maker's sites.

    http://pcsupport.about.com/od/driverssupport/ht...

    ====================================================

    More troubleshooting methods are in the next message below.

    Here to help,

    Rob


    Standard Disclaimer: Those may be non-Microsoft websites. The pages appear to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the site before you decide to download and install it.

    Please let us know the results and if you need further assistance. Feedback definitely helps us help all.

    Was this answer helpful?

    0 comments No comments