General Tips for Stop Errors (BSOD)

Firstly, you can follow the Microsoft online Blue Screen wizard here.

Check the System Log in Event Viewer for additional error messages that might help identify the device or driver that is causing this bug check.
If a driver is identified as faulty from this report, disable the driver or check with the manufacturer for driver updates.
Ensure all motherboard/chipset drivers are up to date, as well as any other software drivers (GPU etc.)
Check if your BIOS is up to date.
Confirm that any new hardware that is installed is compatible with the installed version of Windows.
If you are running any overclocks or XMP profiles, remove them, and see if the problem persists.
If you have recently changed hardware, try removing it to see if the problem persists.
You can try running the hardware diagnostics supplied by the system manufacturer. To test memory, memtest can be used for at least 4 passes.

Hardware Diagnostic / Testing Tools

What are Stop Errors?

Firstly, it is worth clarifying that a BSOD is only attributed to Windows, for example, where Windows has a Blue Screen, Linux actually has something known as a System Panic. However, you’ll find Linux is much less prone to them.

Microsoft defines a blue screen very well:

“When Microsoft Windows encounters a condition that compromises safe system operation, the system halts. This condition is called a bug check. It is also commonly referred to as a system crash, a kernel error, a Stop error, or BSOD. A hardware device, its driver, or related software might have caused this error.”

In simple terms – it’s when Windows has detected a problem that could have caused damage or corruption to the operating system, or your computer itself, and therefore needed to STOP.

That’s why technically it’s called a stop error, stop code, or a bug check. They are more indicative of a fatal system crash. For the purpose of standardisation, we will call this a bug check (Bugcheck = BSOD).

So, there are some important considerations to take before continuing:

A BSOD is a more community slang name for a stop code, stop error, or bug check.
You cannot typically debug through the information on a bug check screen alone.
No bug check is the same, everyone has a different meaning, and every system has a different cause
There is NO generic “Fix” for a bugcheck!
A bugcheck can be indicative of software and hardware, but is commonly driver (software) based.
Even using guides, there is no “answer”, debugging is a combination of knowing how to debug, but also experience on what could be causing the problem.

Summary

BugCheck 4E ----- PFN_LIST_CORRUPT

Probably caused by : memory_corruption ( nt!MiDeletePteList+15e843 )

Arg1: 0000000000000099, A PTE or PFN is corrupt

Arg2: 0000000000137007, page frame number

Arg3: 0000000000000004, current page state

Arg4: 0000000000330001, 0

PROCESS_NAME: MsMpEng.exe

MODULE_NAME: nt

IMAGE_NAME: memory_corruption ----->

Bugcheck Description:

PFN_LIST_CORRUPT

"This indicates that the page frame number (PFN) list is corrupted. The PFN is in effect an address database, to know where data is being kept in physical memory. Each PFN will contain information about the state of the page in physical memory. It also identifies if the page is in use, or invalid, when the PFN becomes invalid, a PFN CORRUPTION occurs."

About your bugcheck / typical cause:

This tends to occur for 2 reasons, either memory corruption from a misbehaving driver, or incorrect MDL handling. For this reason, you should view the loaded modules section to identify potential misbehaving drivers.

System Information

This includes BIOS, Motherboard, Processor, and Memory. Not all dump files will contain hardware information, and therefore this will not always be complete

BIOS Information

No data

Mainboard Information

No Data

Processor Information

No data

Memory Information

Slot	Size	Speed	Part Number
Memory Slot 1	No Data
Memory Slot 2	No Data
Memory Slot 3	No Data
Memory Slot 4	No Data

Loaded Modules

To disable third party modules, use Autoruns (Microsoft Program)

Modules are listed from OLDEST to NEWEST - typically out of drivers should be looked at first. Total Modules Loaded = Total 12

1- ModuleName 2- Time Stamp 3- Company 4- Description

RTKVHD64.sys 11/02/2014 Realtek Realtek HD Audio Driver

amdgpio3.sys 14/03/2016 AMD AMD GPIO Controller Driver

amdpsp.sys 05/06/2017 AMD AMD Chipset Driver

rt640x64.sys 14/11/2017 Realtek Realtek Audio Driver

AMDPCIDev.sys 12/04/2018 AMD AMD Ryzen OC Utility

amdgpio2.sys 12/11/2018 AMD AMD GPIO Controller Driver

UcmCxUcsiNvppc.sys 15/05/2019 NVIDIA USB Type C Port Controller Driver

rtwlanu.sys 28/05/2019 Realtek Realtek Wirless USB 2.0 Adapter Driver

ROGKB.sys 17/06/2019 UNKNOWN Unknown

ROGMS.sys 17/06/2019 UNKNOWN Unknown

nvhda64v.sys 21/06/2019 NVIDIA NVIDIA Audio HDMI Driver (nForce Chip)

nvlddmkm.sys 05/09/2019 NVIDIA NVIDIA Video Drivers

1- ModuleName	2- Time Stamp	3- Company	4- Description
RTKVHD64.sys	11/02/2014	Realtek	Realtek HD Audio Driver
amdgpio3.sys	14/03/2016	AMD	AMD GPIO Controller Driver
amdpsp.sys	05/06/2017	AMD	AMD Chipset Driver
rt640x64.sys	14/11/2017	Realtek	Realtek Audio Driver
AMDPCIDev.sys	12/04/2018	AMD	AMD Ryzen OC Utility
amdgpio2.sys	12/11/2018	AMD	AMD GPIO Controller Driver
UcmCxUcsiNvppc.sys	15/05/2019	NVIDIA	USB Type C Port Controller Driver
rtwlanu.sys	28/05/2019	Realtek	Realtek Wirless USB 2.0 Adapter Driver
ROGKB.sys	17/06/2019	UNKNOWN	Unknown
ROGMS.sys	17/06/2019	UNKNOWN	Unknown
nvhda64v.sys	21/06/2019	NVIDIA	NVIDIA Audio HDMI Driver (nForce Chip)
nvlddmkm.sys	05/09/2019	NVIDIA	NVIDIA Video Drivers

Dump File

Microsoft (R) Windows Debugger Version 10.0.18362.1 X86

Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*

Executable search path is:

Windows 10 Kernel Version 17763 MP (12 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 17763.1.amd64fre.rs5_release.180914-1434

Machine Name:

Kernel base = 0xfffff803`4dea7000 PsLoadedModuleList = 0xfffff803`4e2c2630

Debug session time: Thu Sep 12 09:09:46.416 2019 (UTC + 1:00)

System Uptime: 0 days 0:19:19.130

Loading Kernel Symbols

...............................................................

................................................................

......................................................

Loading User Symbols

Loading unloaded module list

.......................

For analysis of this file, run !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 137007, 4, 330001}

Probably caused by : memory_corruption ( nt!MiDeletePteList+15e843 )

Followup: MachineOwner

---------

*******************************************************************************

* *

* 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: 0000000000000099, A PTE or PFN is corrupt

Arg2: 0000000000137007, page frame number

Arg3: 0000000000000004, current page state

Arg4: 0000000000330001, 0

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: 17763.1.amd64fre.rs5_release.180914-1434

DUMP_TYPE: 2

BUGCHECK_P1: 99

BUGCHECK_P2: 137007

BUGCHECK_P3: 4

BUGCHECK_P4: 330001

BUGCHECK_STR: 0x4E_99

CPU_COUNT: c

CPU_MHZ: d42

CPU_VENDOR: AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 8

CPU_STEPPING: 2

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: MsMpEng.exe

CURRENT_IRQL: 2

ANALYSIS_SESSION_HOST: DESKTOP-CL34DUR

ANALYSIS_SESSION_TIME: 09-12-2019 11:51:32.0866

ANALYSIS_VERSION: 10.0.18362.1 x86fre

LAST_CONTROL_TRANSFER: from fffff8034e0c0ee3 to fffff8034e05af50

STACK_TEXT:

fffff90c`e9c59e08 fffff803`4e0c0ee3 : 00000000`0000004e 00000000`00000099 00000000`00137007 00000000`00000004 : nt!KeBugCheckEx

fffff90c`e9c59e10 fffff803`4df54a12 : fffff90c`e9c5a050 ffffd086`cb1bd0c0 000002ba`cac73000 fffff90c`e9c5a930 : nt!MiDeletePteList+0x15e843

fffff90c`e9c59ed0 fffff803`4e4c06db : ffffd086`d01f0080 ffffd086`cf292f28 00000000`00000000 ffffd086`00000000 : nt!MiDecommitPages+0x8a2

fffff90c`e9c5a8f0 fffff803`4e43454f : 00000000`00000000 ffffd086`cf292f00 00000000`00016000 00000000`00004000 : nt!MiDecommitRegion+0x6b

fffff90c`e9c5a970 fffff803`4e43425b : 00000000`00000000 000000f7`8f27ed88 000000f7`8f27f110 000002ba`00000000 : nt!MmFreeVirtualMemory+0x2bf

fffff90c`e9c5aaa0 fffff803`4e06c208 : ffffd086`d01f0080 fffff90c`e9c5ab80 fffff90c`e9c5ab80 ffffd086`d20cde60 : nt!NtFreeVirtualMemory+0x8b

fffff90c`e9c5ab00 00007ffe`a055fb24 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28

000000f7`8f27ec78 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`a055fb24

THREAD_SHA1_HASH_MOD_FUNC: e590de88e85cb8941c6f606fe85f9e8fec83dd13

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 82d1440060fd0400dce65b6f5592dd4a8fbe293a

THREAD_SHA1_HASH_MOD: 30a3e915496deaace47137d5b90c3ecc03746bf6

FOLLOWUP_IP:

nt!MiDeletePteList+15e843

fffff803`4e0c0ee3 cc int 3

FAULT_INSTR_CODE: cf8b44cc

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!MiDeletePteList+15e843

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 0

IMAGE_VERSION: 10.0.17763.678

STACK_COMMAND: .thread ; .cxr ; kb

IMAGE_NAME: memory_corruption

BUCKET_ID_FUNC_OFFSET: 15e843

FAILURE_BUCKET_ID: 0x4E_99_nt!MiDeletePteList

BUCKET_ID: 0x4E_99_nt!MiDeletePteList

PRIMARY_PROBLEM_CLASS: 0x4E_99_nt!MiDeletePteList

TARGET_TIME: 2019-09-12T08:09:46.000Z

OSBUILD: 17763

OSSERVICEPACK: 678

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: unknown_date

BUILDDATESTAMP_STR: 180914-1434

BUILDLAB_STR: rs5_release

BUILDOSVER_STR: 10.0.17763.1.amd64fre.rs5_release.180914-1434

ANALYSIS_SESSION_ELAPSED_TIME: 372f

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x4e_99_nt!mideleteptelist

FAILURE_ID_HASH: {1f8b0d72-5d77-2dd7-2465-be01295c354a}

Followup: MachineOwner

---------

@ win32kfull.sys 47c2299b

@ win32kbase.sys c66d5a41

@ cdd.dll 00000000

@ E:\WinDBG\Debuggers\x86\sym\win32k.pdb\5FC948DFBCBB1D235917205222B345C61\win32k.pdb b0321e5e

@ hal.dll ac153306

@ E:\WinDBG\Debuggers\x86\sym\ntkrnlmp.pdb\9A729548AB1A93E90D0A48528CE30B7A1\ntkrnlmp.pdb e555a2c9

@ kd.dll 7a776dcd

@ werkernel.sys 030a7cce

@ msrpc.sys ad3c8c27

@ tm.sys f1ac5a2f

@ CLFS.SYS 65900277

@ PSHED.dll 79fb7d7e

@ cmimcext.sys 4c6db670

@ ntosext.sys 6d6b5a0e

@ CI.dll 71370732

@ cng.sys 85008090

@ clipsp.sys 5d04b944

@ Wdf01000.sys af1cedd2

@ WDFLDR.SYS 47a236e4

@ WppRecorder.sys e67c59ba

@ SleepStudyHelper.sys d42abccc

@ mcupdate_AuthenticAMD.dll f26dbe88

@ ksecdd.sys c0930b22

@ BOOTVID.dll 30b650ad

@ FLTMGR.SYS 9697298f

@ acpiex.sys 0a439b7f

@ mssecflt.sys d07e4e59

@ SgrmAgent.sys f7ca286d

@ msisadrv.sys 418dc2e9

@ pci.sys 830a8a17

@ vdrvroot.sys 8ed5f3a9

@ pdc.sys 1368f445

@ CEA.sys 9b4697b8

@ partmgr.sys 2fe6062f

@ spaceport.sys a069c343

@ volmgr.sys 91784a41

@ volmgrx.sys 50da1ded

@ mountmgr.sys a8481dd2

@ storahci.sys e94316b7

@ storport.sys d6a4ba31

@ EhStorClass.sys f26184eb

@ fileinfo.sys 85b4f747

@ Wof.sys 237f6dfd

@ WdFilter.sys bdd671f8

@ Ntfs.sys 3885b4cf

@ Fs_Rec.sys cff89b5e

@ ndis.sys 0307a6f2

@ ACPI.sys a49a6357

@ WMILIB.SYS 7710989f

@ intelpep.sys ae0e514f

@ WindowsTrustedRT.sys bd0b79f0

@ WindowsTrustedRTProxy.sys 5192684a

@ pcw.sys c6c870f7

@ tcpip.sys f2e36ca1

@ fwpkclnt.sys 204b6f56

@ wfplwfs.sys 0aa4b522

@ fvevol.sys b5cd826b

@ volume.sys cb3f72cf

@ volsnap.sys ac1c69a4

@ rdyboost.sys 5b832bf2

@ mup.sys d5074ba1

@ iorate.sys a096cd2d

@ disk.sys eb969297

@ NETIO.SYS c0e588af

@ ksecpkg.sys 1b3cb9d8

@ amdpsp.sys 5935cc3c

@ CLASSPNP.SYS ac33998d

@ crashdmp.sys fef3c415

@ Beep.SYS e2569389

@ dxgkrnl.sys 02b3f361

@ watchdog.sys 8d7a0df0

@ BasicDisplay.sys d39d4b86

@ BasicRender.sys 500b5138

@ Npfs.SYS bbac2737

@ Msfs.SYS c2dfb7c4

@ tdx.sys afdabf6d

@ TDI.SYS e9708b47

@ netbt.sys 6bf64710

@ afunix.sys ce69ff46

@ afd.sys c0b0d284

@ cdrom.sys 590e43df

@ filecrypt.sys 798a13f4

@ tbs.sys 7de0f3e4

@ Null.SYS 23dc46f7

@ pacer.sys bd6e6ba5

@ netbios.sys ba5b5fb4

@ rdbss.sys 021097cf

@ csc.sys 71977cc0

@ nsiproxy.sys 050877bf

@ npsvctrig.sys 7e4d1a78

@ E:\WinDBG\Debuggers\x86\sym\mssmbios.pdb\6AEB55D4626165B2915516C094CDA9681\mssmbios.pdb a51d1a67

@ gpuenergydrv.sys da1c403f

@ dfsc.sys e60cddbc

@ fastfat.SYS eb9fc2e9

@ bam.sys 1653310c

@ ahcache.sys 2f11a0dc

@ Vid.sys f42473ac

@ winhvr.sys 8836b629

@ CompositeBus.sys dd86440a

@ kdnic.sys 05131801

@ umbus.sys 83197d71

@ USBXHCI.SYS fdacad1e

@ ucx01000.sys 7e0a5f72

@ rt640x64.sys 5a0a844e

@ HDAudBus.sys 121b41c6

@ portcls.sys 8dfe43a2

@ drmk.sys 394317ab

@ ks.sys f785d292

@ UcmCxUcsiNvppc.sys 5cdb7679

@ UcmCx.sys 26609ad2

@ AMDPCIDev.sys 5acef961

@ serial.sys 3d30e0f0

@ serenum.sys 604b8a02

@ amdgpio2.sys 5be94cbf

@ msgpioclx.sys 4b2a44e1

@ amdppm.sys f2b45e34

@ wmiacpi.sys f2622d42

@ amdgpio3.sys 56e69038

@ UEFI.sys b5d8263e

@ NdisVirtualBus.sys 333ae742

@ swenum.sys 8b90f92a

@ rdpbus.sys 7b2e1a48

@ UsbHub3.sys 4b5abbef

@ USBD.SYS c7e3b3e8

@ ksthunk.sys d43d6b7c

@ RTKVHD64.sys 52fa036f

@ HIDPARSE.SYS 2aa4ebb4

@ vwififlt.sys b1239f86

@ dxgmms2.sys 0c7b8e50

@ luafv.sys 637f4174

@ wcifs.sys 22d58be9

@ cldflt.sys f1aae47f

@ storqosflt.sys 29923efb

@ lltdio.sys f5108909

@ mslldp.sys a36249fa

@ rspndr.sys c42f95a5

@ wanarp.sys 08c5c028

@ nwifi.sys 6c547e92

@ ndisuio.sys 117f9087

@ winquic.sys 6e5c0414

@ HTTP.sys f6495506

@ bowser.sys 30059e68

@ mpsdrv.sys 4e67ce41

@ mrxsmb.sys 1e562dc2

@ mrxsmb20.sys 0d59a79b

@ srvnet.sys 4e6f5832

@ mmcss.sys d143bb7e

@ peauth.sys 857dc62d

@ Ndu.sys 18babc47

@ tcpipreg.sys 42abe6c4

@ srv2.sys 7ff4aff4

@ usbccgp.sys 82d4cb5c

@ hidusb.sys 02e73966

@ HIDCLASS.SYS 1255155c

@ mouhid.sys 45af4341

@ ROGMS.sys 5d073c26

@ mouclass.sys 80f98b92

@ kbdhid.sys 5e1d49fd

@ ROGKB.sys 5d073bfe

@ kbdclass.sys db4b5540

@ rassstp.sys 6c3c4681

@ NDProxy.sys 78f862cf

@ dump_diskdump.sys a0767573

@ dump_storahci.sys e94316b7

@ dump_dumpfve.sys 3511e596

@ vwifimp.sys 172f45a0

@ AgileVpn.sys 5459b0dc

@ rasl2tp.sys ca2a942b

@ raspptp.sys 340ea9a3

@ raspppoe.sys a6ba0271

@ ndistapi.sys d2b2edc9

@ ndiswan.sys 1596b64d

@ WdNisDrv.sys 65b5d483

@ wcnfs.sys 45669b7d

@ condrv.sys 314bacf1

@ rtwlanu.sys 5cecd33f

@ wdiwifi.sys 63bdaa31

@ vwifibus.sys 623d4a3f

@ nvlddmkm.sys 5d716596

@ MpKsla8bc7090.sys 2409fbe1

@ monitor.sys 41fa7930

@ nvhda64v.sys 5d0d318d

sysinfo: could not find necessary interfaces.

sysinfo: note that mssmbios.sys must be loaded (XPSP2+).

sysinfo: could not find necessary interfaces.

sysinfo: note that mssmbios.sys must be loaded (XPSP2+).

Additional Commands

9: kd> !memusage

fffff8034e3e9390: Unable to get MiVisibleState

Unable to get NonPagedPoolStart

Unable to get NonPagedPoolEnd

Unable to get PagedPoolStart

Unable to get PagedPoolEnd

Search: READ_PVOID error

InitTypeRead(nt!MmPhysicalMemoryBlock, nt!_PHYSICAL_MEMORY_DESCRIPTOR) error 1

9: kd> !pfn

Unable to get NonPagedPoolStart

Unable to get NonPagedPoolEnd

Unable to get PagedPoolStart

Unable to get PagedPoolEnd

Unable to get PFN database address fffff8034e3ea390

9: kd> k

# Child-SP RetAddr Call Site

00 fffff90c`e9c59e08 fffff803`4e0c0ee3 nt!KeBugCheckEx

01 fffff90c`e9c59e10 fffff803`4df54a12 nt!MiDeletePteList+0x15e843

02 fffff90c`e9c59ed0 fffff803`4e4c06db nt!MiDecommitPages+0x8a2

03 fffff90c`e9c5a8f0 fffff803`4e43454f nt!MiDecommitRegion+0x6b

04 fffff90c`e9c5a970 fffff803`4e43425b nt!MmFreeVirtualMemory+0x2bf

05 fffff90c`e9c5aaa0 fffff803`4e06c208 nt!NtFreeVirtualMemory+0x8b

06 fffff90c`e9c5ab00 00007ffe`a055fb24 nt!KiSystemServiceCopyEnd+0x28

07 000000f7`8f27ec78 00000000`00000000 0x00007ffe`a055fb24

Stop Error Dump File Analysis - Dump file analysed: 091219-24937-01.dmp] on 12/09/19

General Tips for Stop Errors (BSOD)

Firstly, you can follow the Microsoft online Blue Screen wizard here.

Hardware Diagnostic / Testing Tools

What are Stop Errors?

Summary

BugCheck 4E ----- PFN_LIST_CORRUPT

Probably caused by : memory_corruption ( nt!MiDeletePteList+15e843 )

Bugcheck Description:

About your bugcheck / typical cause:

System Information

This includes BIOS, Motherboard, Processor, and Memory. Not all dump files will contain hardware information, and therefore this will not always be complete

BIOS Information

Mainboard Information

Processor Information

Memory Information

Loaded Modules

Dump File

Additional Commands