Windows 10: Random Bugcheck 4e Happens Freqently

My PC keeps getting this BSOD since late December 2020. Sometimes I can go a day or two, and sometimes it happens about every 10 minutes. It's very frustrating. I've checked pretty much everything, memory, hard drive, driver updates, Windows updates, BIOS/UEFI updates, scanned for malware. I'm thinking a possible Windows update at this point, but I really don't know. Would appreciate any suggestions.


MiniDumps are attached and here is the output of WinDGBusing !analyze /v

<code>

Microsoft R Windows Debugger Version 10.0.19041.685 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 6 procs Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff800`19800000 PsLoadedModuleList = 0xfffff800`1a42a2b0
Debug session time: Mon Jan 11 08:53:44.829 2021 UTC - 5:00
System Uptime: 0 days 0:03:20.593
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...........
Loading User Symbols

Loading unloaded module list
.........
For analysis of this file, run !analyze -v
1: kd> !analyze
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

PFN_LIST_CORRUPT 4e
Typically caused by drivers passing bad memory descriptor lists ie: calling
MmUnlockPages twice with the same list, etc. If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 000000000000009a,
Arg2: 0000000000125860
Arg3: 0000000000000006
Arg4: 0000000000000002

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


BUGCHECK_CODE: 4e

BUGCHECK_P1: 9a

BUGCHECK_P2: 125860

BUGCHECK_P3: 6

BUGCHECK_P4: 2

PROCESS_NAME: System

SYMBOL_NAME: nt!MiDeleteNonPagedPoolPte+16f0c7

MODULE_NAME: nt

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0x4E_9a_nt!MiDeleteNonPagedPoolPte

FAILURE_ID_HASH: {aec87dc6-8e5e-ffb2-0aed-142948a6cbb3}

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

PFN_LIST_CORRUPT 4e
Typically caused by drivers passing bad memory descriptor lists ie: calling
MmUnlockPages twice with the same list, etc. If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 000000000000009a,
Arg2: 0000000000125860
Arg3: 0000000000000006
Arg4: 0000000000000002

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 2

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on SERVER

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 2

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

Key : Analysis.System
Value: CreateObject


BUGCHECK_CODE: 4e

BUGCHECK_P1: 9a

BUGCHECK_P2: 125860

BUGCHECK_P3: 6

BUGCHECK_P4: 2

PROCESS_NAME: System

STACK_TEXT:
fffff58d`6e8a53b8 fffff800`19c61127 : 00000000`0000004e 00000000`0000009a 00000000`00125860 00000000`00000006 : nt!KeBugCheckEx
fffff58d`6e8a53c0 fffff800`19af1f2e : ffff89c5`03344fa0 fffff58d`6e8a5530 00000000`00000002 ffff89c4`00000000 : nt!MiDeleteNonPagedPoolPte+0x16f0c7
fffff58d`6e8a5430 fffff800`19aac256 : ffff8a06`6d084700 fffff800`2ad382b9 ffff8a06`64769f60 fffff800`29650871 : nt!MiClearNonPagedPtes+0x162
fffff58d`6e8a5660 fffff800`19aac07a : 00000000`00000000 fffff58d`6e8a57d1 ffffffff`ffffffc0 00000000`00004000 : nt!MmFreePoolMemory+0x1aa
fffff58d`6e8a56e0 fffff800`19aab5c6 : ffffb701`f1502180 fffff800`19bfc992 000fa4ef`bd9bbfff 00000000`00000001 : nt!RtlpHpEnvFreeVA+0x12
fffff58d`6e8a5710 fffff800`19ab0d33 : 00000000`00000000 fffff800`19bfc506 00000000`00000000 00000000`00000000 : nt!RtlpHpFreeVA+0x3a
fffff58d`6e8a5750 fffff800`19ab09de : 00000000`00000000 00000000`ffffffc0 00000000`00000000 00000000`ffffffb5 : nt!RtlpHpSegMgrCommit+0x1e3
fffff58d`6e8a5820 fffff800`19ab2e01 : 00000000`00000001 ffff8a06`689016a0 00000000`00000000 fffff800`00000040 : nt!RtlpHpSegPageRangeCommit+0x1ee
fffff58d`6e8a58c0 fffff800`19b5dd4d : ffff8a06`689016a0 00000000`00000076 ffff8a06`689016a0 ffff8a06`4c600340 : nt!RtlpHpSegPageRangeCoalesce+0x1b1
fffff58d`6e8a5940 fffff800`19b5dbe0 : ffff8a06`4c600000 ffff8a06`4c600000 00000000`00000000 ffff8a06`4c600280 : nt!RtlpHpSegContextCompact+0x13d
fffff58d`6e8a59b0 fffff800`19aac637 : 00000000`00000001 ffff8a06`4c600000 ffff8a06`00000000 ffff8a06`00000000 : nt!RtlpHpHeapCompact+0x84
fffff58d`6e8a59e0 fffff800`19a25975 : 00000000`00000001 fffff800`23d162e0 ffff8a06`00000000 00000000`00000000 : nt!ExpHpCompactionRoutine+0x207
fffff58d`6e8a5a70 fffff800`19b17e25 : ffff8a06`4e780040 00000000`00000080 ffff8a06`4cac7080 000fa4ef`bd9bbfff : nt!ExpWorkerThread+0x105
fffff58d`6e8a5b10 fffff800`19bfcdd8 : ffffb701`f1396180 ffff8a06`4e780040 fffff800`19b17dd0 00230031`00300032 : nt!PspSystemThreadStartup+0x55
fffff58d`6e8a5b60 00000000`00000000 : fffff58d`6e8a6000 fffff58d`6e89f000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: nt!MiDeleteNonPagedPoolPte+16f0c7

MODULE_NAME: nt

STACK_COMMAND: .thread ; .cxr ; kb

IMAGE_NAME: memory_corruption

BUCKET_ID_FUNC_OFFSET: 16f0c7

FAILURE_BUCKET_ID: 0x4E_9a_nt!MiDeleteNonPagedPoolPte

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {aec87dc6-8e5e-ffb2-0aed-142948a6cbb3}

Followup: MachineOwner
---------

</code>

:)

 

Window Server 2016 - Random reboots - Bugcheck D1 / TCPIP.sys

Hi Dexter,

Thanks for your advice.

I've posted as suggested:

Window Server 2016 - Random reboots - Bugcheck D1 / TCPIP.sys

Thanks,

Michael

 

random restarts

Hi,

If a Windows computer random restarts, the device usually have some damaged system components. For us to provide an accurate solution, we would need you to answer the following questions:

• Which build, version and edition of Windows is installed on your computer?
• What changes have you made to the device before this issue occurred?
• What troubleshooting steps was already performed to your laptop?

In the meantime, it will be best to make sure that the latest update of Windows is installed on your device. If the same issue happens after installing Windows Update, we suggest running the power troubleshooter. To do so, follow these steps:

• Open the Control Panel.
• Using the search bar at the upper-right corner, type troubleshooting.
• From the search results, click on Troubleshooting and then select System and Security.
  
• Click on Power and then follow the prompts to successfully run the tool.

We are looking forward to your response.

 

Random BSOD while browsing internet


BitDefender is nothing special. mwac.sys causes BSODs anywhere.
A tiny documentation can be found here: Solved Random BSODs - Windows 10 Forums
In that very thread, the suggested action apparently worked.

The storage and network filters of any third party antivirus can cause BSODs. Neither MBAM nor BitDefender is any special. For a regular antivirus, it may be shifted to an alternative; but MBAM has no alternative. So a clean install of the said program is the most feasible first step.
As far as the first step is not failing, it is better to not think for the second step. Because the BSODs are not universal, failure at the first step is not universal; and success at the second step is also not universal.
That is why I posted that my suggestion may work, or may not. Let us see where it goes.