Question Blue Screen of Death-MEMORY_MANAGEMENT (1a)

[SammyEK]

So I had been having blue screen issues for an month at this point and I'm about to send in my RAMs to be replaced. But to make sure the rams are the not the problem, I just got this another blue screen and this was the detail:

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


Loading Dump File [C:\Minidumps\101221-9828-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 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff80574000000 PsLoadedModuleList = 0xfffff80574c2a230
Debug session time: Tue Oct 12 16:23:32.212 2021 (UTC - 5:00)
System Uptime: 0 days 6:00:41.834
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...........
Loading User Symbols
Loading unloaded module list
...................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff805743f71c0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffffd88d9a7e960=000000000000001a
0: 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: ffffdb000007b3b0
Arg3: 0080000000000000
Arg4: 0000000000000000

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

*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2515

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 6023

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

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

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

Key : MemoryManagement.PFN
Value: 0

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


BUGCHECK_CODE: 1a

BUGCHECK_P1: 41792

BUGCHECK_P2: ffffdb000007b3b0

BUGCHECK_P3: 80000000000000

BUGCHECK_P4: 0

MEMORY_CORRUPTOR: ONE_BIT

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: steam.exe

STACK_TEXT:
fffffd88d9a7e958 fffff8057424423a : 000000000000001a 0000000000041792 ffffdb000007b3b0 0080000000000000 : nt!KeBugCheckEx
fffffd88d9a7e960 fffff80574242a6f : ffffde837c324740 0000000000000000 0000000000000002 0000000000000000 : nt!MiDeleteVa+0x153a
fffffd88d9a7ea60 fffff80574212c10 : 0000000000000001 fffffd8800000000 ffffde837c324590 ffffffffffffffff : nt!MiDeletePagablePteRange+0x48f
fffffd88d9a7ed70 fffff80574252277 : 000000000000f6af 0000000000000000 ffffde8300000000 fffff80500000000 : nt!MiDeleteVad+0x360
fffffd88d9a7ee80 fffff805745f908c : fffffd8800000000 0000000000000000 fffffd88d9a7efe0 000000000f670000 : nt!MiFreeVadRange+0xa3
fffffd88d9a7eee0 fffff805745f8b65 : ffffde8300000000 fffff80574207bae 0000000000000001 0000000000000000 : nt!MmFreeVirtualMemory+0x4ec
fffffd88d9a7f030 fffff80574408bb5 : ffffde8385896040 0000000000000000 ffffde836fad34b0 fffffd88d9a7f0f9 : nt!NtFreeVirtualMemory+0x95
fffffd88d9a7f090 fffff805743fb020 : fffff805746b0207 ffffde8385896040 ffffde8377c9fdf0 0000000000000001 : nt!KiSystemServiceCopyEnd+0x25
fffffd88d9a7f228 fffff805746b0207 : ffffde8385896040 ffffde8377c9fdf0 0000000000000001 0000000000000000 : nt!KiServiceLinkage
fffffd88d9a7f230 fffff805746b3333 : 0000000000000000 ffffde838545e700 0000000000000000 00000000003c6000 : nt!PspExitThread+0x387
fffffd88d9a7f330 fffff805746b32ba : 0000000000000000 0000000000000000 ffffde8385896040 ffffde838545e7e0 : nt!PspTerminateThreadByPointer+0x53
fffffd88d9a7f370 fffff80574408bb5 : 0000000000000000 ffffde8385896040 fffffd88d9a7f440 ffffde8300000000 : nt!NtTerminateThread+0x4a
fffffd88d9a7f3c0 0000000077b41cfc : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x25
000000000f6aed88 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x77b41cfc


MODULE_NAME: hardware

IMAGE_NAME: memory_corruption

STACK_COMMAND: .thread ; .cxr ; 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
---------

Can anyone helped me with this?

 

[popatim]

If you are overclocked, have you reset the bios to defaults and run memory testing?