Well... have you been able to figure it out?
Frequently Memory Management
I get memory management BSOD pretty often lately and having trouble by figure it out what actually cause it. I have swapped the RAM's about 4-5 times without success, checked the SSD for faults without having it and everything was fine when having Windows 7 for some years ago. By the time I got Windows 10 it happens pretty often and no matter what I do I can't figure it out. Here's the log:
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: ffffaa80ef8021b8
Arg3: 8000000000000000
Arg4: 0000000000000000
Debugging Details:
------------------
*** WARNING: Check Image - Checksum mismatch - Dump: 0xd94f, File: 0x72fd - C:\ProgramData\Dbg\sym\hal.dll\1A7BE8E96000\hal.dll
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 6421
Key : Analysis.Elapsed.mSec
Value: 6657
Key : Analysis.IO.Other.Mb
Value: 0
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 0
Key : Analysis.Init.CPU.mSec
Value: 1734
Key : Analysis.Init.Elapsed.mSec
Value: 6546
Key : Analysis.Memory.CommitPeak.Mb
Value: 93
Key : Bugcheck.Code.KiBugCheckData
Value: 0x1a
Key : Bugcheck.Code.LegacyAPI
Value: 0x1a
Key : Bugcheck.Code.TargetModel
Value: 0x1a
Key : Failure.Bucket
Value: MEMORY_CORRUPTION_ONE_BIT
Key : Failure.Hash
Value: {e3faf315-c3d0-81db-819a-6c43d23c63a7}
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 : MemoryManagement.PFN
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: 41792
BUGCHECK_P2: ffffaa80ef8021b8
BUGCHECK_P3: 8000000000000000
BUGCHECK_P4: 0
FILE_IN_CAB: MEMORY.DMP
MEMORY_CORRUPTOR: ONE_BIT
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
PROCESS_NAME: msedge.exe
STACK_TEXT:
ffffab05`0d172108 fffff806`55a82faa : 00000000`0000001a 00000000`00041792 ffffaa80`ef8021b8 80000000`00000000 : nt!KeBugCheckEx
ffffab05`0d172110 fffff806`55a1b2f6 : 00000000`00000000 00000000`00000000 00000000`0000043d ffffaa80`ef8021b8 : nt!MiDeleteVa+0x153a
ffffab05`0d172210 fffff806`55a1b40b : ffffaad5`00000000 ffff9081`ebd67700 ffffab05`00000000 ffffab05`0d172680 : nt!MiWalkPageTablesRecursively+0x776
ffffab05`0d1722b0 fffff806`55a1b40b : ffffaad5`6aa03be0 ffff9081`ebd67700 ffffab05`00000001 ffffab05`0d172690 : nt!MiWalkPageTablesRecursively+0x88b
ffffab05`0d172350 fffff806`55a1b40b : ffffaad5`6aa03000 ffff9081`ebd67700 ffffab05`00000002 ffffab05`0d1726a0 : nt!MiWalkPageTablesRecursively+0x88b
ffffab05`0d1723f0 fffff806`55a1840b : 00000000`c0000016 ffff9081`ebd67700 00000000`00000003 ffffab05`0d1726b0 : nt!MiWalkPageTablesRecursively+0x88b
ffffab05`0d172490 fffff806`55a81841 : ffffab05`0d172630 ffff9081`00000000 00000000`00000002 00000000`00000000 : nt!MiWalkPageTables+0x36b
ffffab05`0d172590 fffff806`55a2b548 : 00000000`00000001 ffff9081`00000000 ffff9081`ebd67550 ffff9081`e7f2c080 : nt!MiDeletePagablePteRange+0x4f1
ffffab05`0d1728a0 fffff806`55e86119 : ffffab05`00000000 00000000`00000000 aaaaaaaa`00000000 ffff9081`ebd67080 : nt!MiDeleteVad+0x378
ffffab05`0d1729a0 fffff806`55e85ef2 : ffff9081`ee66dd80 00000000`00000000 ffff9081`ebd67080 00000000`00000000 : nt!MiUnmapVad+0x49
ffffab05`0d1729d0 fffff806`55e85d69 : 00000003`007ff518 7fffffff`00000004 aaaaaaaa`aaaaaaaa 00000000`00000000 : nt!MiUnmapViewOfSection+0x152
ffffab05`0d172ab0 fffff806`55c119c8 : ffff9081`e7f2c080 000001df`00000000 ffffab05`0d172b80 ffff9081`ebd67080 : nt!NtUnmapViewOfSectionEx+0x99
ffffab05`0d172b00 00007ffc`ddb90a64 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000003`007ff448 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`ddb90a64
MODULE_NAME: hardware
IMAGE_NAME: memory_corruption
STACK_COMMAND: .cxr; .ecxr ; kb
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {e3faf315-c3d0-81db-819a-6c43d23c63a7}
Followup: MachineOwner
---------
I assume that it has something to do with PROCESS_NAME: msedge.exe as it regards specifically to it, but I'm not sure if that is the one that cause it as it change to something else from time to time.
Does someone here actually knows what causes it?
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.
6 answers
Sort by: Most helpful
-
Anonymous
2024-07-02T08:21:52+00:00 -
Deleted
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
-
DYARI BARHAM 34,936 Reputation points Independent Advisor
2024-06-08T14:12:41+00:00 No problem. Please keep me posted.
-
Anonymous
2024-06-08T13:05:28+00:00 I was a bit fast by deleting it in the "Clean up system files". I have to wait to it happens again.
-
DYARI BARHAM 34,936 Reputation points Independent Advisor
2024-06-08T10:29:16+00:00 Hi Andreas,
I'm Dyari. Thanks for reaching out. I will be happy to assist you in this regard.
Please go to C:\Windows\Minidump and copy any minidump files you find to your desktop. Afterward, share these files through OneDrive or Google Drive so we can analyze them and identify the specific file that's causing the crash.