BSOD: PFN list corrupt on brand new install

theridon · 26 Oct 2022

I have just installed Windows 10 on a brand new SSD, today randomly my computer froze up, with very loud buzzing coming from the speakers, BSOD that says PFN_LIST_CORRUPT. This is on my own built pc, haven't had this problem before install.

I used the V2 Log collector and followed instructions and attached the corresponding zip file.DESKTOP-JEQ91P0-(2022-10-26_20-54-45).zip

Not sure if relevant but I have two "other devices" that have yellow exclamation, "PCI memory controller" and "SM bus controller". Please advise. Thank you.

zbook · 27 Oct 2022

1) Uninstall the Nvidia GPU drivers nvlddmkm.sys using Display Driver Uninstaller (DDU)

Reinstall using the Nvidia website.

Make sure that a clean install is performed and if available install the physx driver.

DDU Guide / Tutorial | Wagnardsoft

Display Driver Uninstaller (DDU) | Wagnardsoft

Just a moment...

Official Drivers | NVIDIA

2) Upgrade the BIOS: (check the motherboard version)
GA-H170-Gaming 3 (rev. 1.0) Support | Motherboard - GIGABYTE Global
GA-H170-Gaming 3 (rev. 1.1) Overview | Motherboard - GIGABYTE U.S.A.

3) Install / reinstall chipset drivers:

4) Run the Intel Driver and Support Assistant:
Intel(R) Driver & Support Assistant (Intel(R) DSA) Basic...

5) Turn off Windows fast startup:
Turn On or Off Fast Startup in Windows 10

theridon · 29 Oct 2022

zbook said:

1) Uninstall the Nvidia GPU drivers nvlddmkm.sys using Display Driver Uninstaller (DDU)

Reinstall using the Nvidia website.

Make sure that a clean install is performed and if available install the physx driver.

DDU Guide / Tutorial | Wagnardsoft

Display Driver Uninstaller (DDU) | Wagnardsoft

Just a moment...

Official Drivers | NVIDIA

2) Upgrade the BIOS: (check the motherboard version)
GA-H170-Gaming 3 (rev. 1.0) Support | Motherboard - GIGABYTE Global
GA-H170-Gaming 3 (rev. 1.1) Overview | Motherboard - GIGABYTE U.S.A.

3) Install / reinstall chipset drivers:

4) Run the Intel Driver and Support Assistant:
Intel(R) Driver & Support Assistant (Intel(R) DSA) Basic...

5) Turn off Windows fast startup:
Turn On or Off Fast Startup in Windows 10

I went ahead and installed chipset drivers, the Intel INF installation, and the exclamation errors on my device manager went away. I'll update this thread again in some time, to see if the BSOD still occurs. But, do you (or anyone else) know a more specific reason as to what caused my BSOD?

EDIT

Just as I type this I get a Memory_Management BSOD, wonderful. I'll attach the report file here, if anyone can take a look at this too I'd greatly appreciate it. I don't know what's going on, I never had these problems until I reinstalled Windows on the new ssd recently. I'll run memtest tonight.DESKTOP-JEQ91P0-(2022-10-29_13-59-28).zip

ubuysa · 30 Oct 2022

The two devices missing drivers were chipset devices. One was the SMBus controller and the other was the power management controller. They are now sorted in your latest upload.

All three dumps look to me as though they might be RAM related. Here's an example stack text output from one of the dumps (this shows all the kernel function calls prior to the bugcheck)...

Code:

0: kd> knL
 # Child-SP          RetAddr               Call Site
00 ffff9c82`b5c76838 fffff804`761f0757     nt!KeBugCheckEx
01 ffff9c82`b5c76840 fffff804`760bd0cb     nt!MiBadShareCount+0x5b
02 ffff9c82`b5c76880 fffff804`7604b12e     nt!MiDeletePteList+0x8db
03 ffff9c82`b5c76960 fffff804`7648b62d     nt!MiDecommitPages+0x121e
04 ffff9c82`b5c77530 fffff804`7648ac93     nt!MiDecommitRegion+0x7d
05 ffff9c82`b5c775b0 fffff804`7648a585     nt!MmFreeVirtualMemory+0x6d3
06 ffff9c82`b5c77700 fffff804`7620aab5     nt!NtFreeVirtualMemory+0x95
07 ffff9c82`b5c77760 fffff804`761fcf80     nt!KiSystemServiceCopyEnd+0x25
08 ffff9c82`b5c778f8 fffff804`9a4f9fac     nt!KiServiceLinkage
09 ffff9c82`b5c77900 fffff804`9a4fd45a     dxgmms2!VIDMM_RECYCLE_RANGE::DebouncedDecommit+0x160
0a ffff9c82`b5c77950 fffff804`9a4fd506     dxgmms2!VIDMM_RECYCLE_HEAP_MGR::ProcessDebounceList+0x12a
0b ffff9c82`b5c779c0 fffff804`9a4fd321     dxgmms2!VIDMM_RECYCLE_HEAP_MGR::CurationThread+0x7a
0c ffff9c82`b5c77a40 fffff804`76052b65     dxgmms2!VidMmRangeCurationThread+0x11
0d ffff9c82`b5c77a70 fffff804`76071d25     nt!ExpWorkerThread+0x105
0e ffff9c82`b5c77b10 fffff804`76200778     nt!PspSystemThreadStartup+0x55
0f ffff9c82`b5c77b60 00000000`00000000     nt!KiStartSystemThread+0x28

Notice that just before the bugcheck we're freeing virtual memory and decommiting pages, which might suggest a RAM issue. I'm wondering whether, in fitting the new SSD (especially if it was an M.2 SSD), you may have disturbed a RAM card a tad? I would suggest first removing and reseating both RAM cards. If that doesn't help then try running with just one RAM card at a time for a while.

ubuysa · 06 Nov 2022

theridon said:

I never had these problems until I reinstalled Windows on the new ssd recently. I'll run memtest tonight.

I've been reviewing my open threads and I just noticed this that you said in your last post. When you reinstalled, from where did you source all the drivers? Have you checked in Device Manager that no devices have a yellow triangle with a black exclamation mark next to them?

BTW. How did the Memtest run go?

theridon · 08 Nov 2022

ubuysa said:

I've been reviewing my open threads and I just noticed this that you said in your last post. When you reinstalled, from where did you source all the drivers? Have you checked in Device Manager that no devices have a yellow triangle with a black exclamation mark next to them?

BTW. How did the Memtest run go?

Windows installed most of my drivers automatically-as stated in the OP there were two "other devices" in device manager that had yellow exclamation, "PCI memory controller" and "SM bus controller"-I downloaded the chipset drivers, "Intel INF installation" from my motherboard manufacturer's website (gigabyte)" and the exclamation errors on my device manager went away. I think that is the only driver I've installed manually.

As per your previous advice, I reseated my ram. Memtest went to Pass:26 and no errors.

Since reseating the RAM I haven't had a blue screen, but I really don't know if that's fixed it as the BSOD do not occur very frequently. I'd like to hold a high hope, but it would be best to find out what exactly was causing my BSODs. Thanks for taking an interest to helping me.

ubuysa · 08 Nov 2022

Well that's encouraging. I'll keep watching this thread just in case.

theridon · 10 Nov 2022

Aaaaaaaand another BSOD crash. "memory management".
I'm a novice but I used BlueScreenView, and it says "ntoskrnl.exe" highlighted in red. I don't know what this means.

Here's the error report, would appreciate anyone looking again.DESKTOP-JEQ91P0-(2022-11-09_21-22-46).zip

Zbook said:

stuff

I've tried most of this, I can try reinstalling my GPU driver's using DDU, but can you give me a reason as to why you suspect this to be a cause?

As for upgrading the bios, I understand that can cause problems sometimes and I'd rather not do it unless there is a real strong reason to do so. I would prefer exploring other venues.

Thanks again all.

zbook · 10 Nov 2022

1) Turn off Windows fast startup:
Turn On or Off Fast Startup in Windows 10

2) Run Memtest86 free version for two tests of four passes each (total eight passes).

Please note that this is different software from Memtest86+.

For each test take pictures and post share links into this thread.

Memtest86 has a feature to create text reports.

If possible please include the text reports with the share links.

MemTest86 - Official Site of the x86 and ARM Memory Testing Tool

Memtest86 can run overnight while sleeping.

3) Run OCCT
There are multiple one hour tests.
Run each and post share links into this thread.
OCBASE/OCCT : Free, all-in-one stability, stress test, benchmark and monitoring tool for your PC

For share links please use one drive, drop box, or google drive.

ubuysa · 11 Nov 2022

All three dumps in your latest upload were caused by a corrupted page table entry (PTE) and I don't think the cause is in the dumps. I rather think now that a rogue driver is corrupting a PTE and the BSOD is occurring the next time that PTE is referenced. The dumps you're getting are for the thread that fell over the corrupted PTE, not for the thread that corrupted it.

We thus need to look elsewhere for clues to what is corrupting the PTE.

I looked through your system log for the 'critical' event 41 messages, indicating an non-clean shutdown/restart and then looked to see what messages were written immediately before it. In ALL cases, your event 41 messages are preceded by the same set of 'information' messages relating to 'Enhanced Storage Trusted Computing Group' (EhStorTcg). Here is an example (my highlighting)...
[cod=rich]Event[5330]:
Log Name: System
Source: Microsoft-Windows-EnhancedStorage-EhStorTcgDrv
Date: 2022-11-09T21:15:38.5000000Z
Event ID: 100
Task: Driver
Level: Information
Opcode: General
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: DESKTOP-JEQ91P0
Description:
The following informational event has occurred (0x0, 0x5, 0x0, 0x0).
D0Entry

Event[5331]:
Log Name: System
Source: Microsoft-Windows-EnhancedStorage-EhStorTcgDrv
Date: 2022-11-09T21:15:38.5300000Z
Event ID: 12
Task: Driver
Level: Information
Opcode: General
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: DESKTOP-JEQ91P0
Description:
A TCG Silo has returned the capabilities value of 0x7. <== I don't know how significant this is

Event[5332]:
Log Name: System
Source: Microsoft-Windows-EnhancedStorage-EhStorTcgDrv
Date: 2022-11-09T21:15:38.5420000Z
Event ID: 100
Task: Driver
Level: Information
Opcode: General
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: DESKTOP-JEQ91P0
Description:
The following informational event has occurred (0x0, 0x0, 0x0, 0x0).
DeviceStart

Event[5333]:
Log Name: System
Source: Microsoft-Windows-Ntfs
Date: 2022-11-09T21:15:39.4840000Z
Event ID: 98
Task: N/A
Level: Information
Opcode: Info
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: DESKTOP-JEQ91P0
Description:
Volume C: (\Device\HarddiskVolume3) is healthy. No action is needed.

Event[5334]:
Log Name: System
Source: Microsoft-Windows-FilterManager
Date: 2022-11-09T21:15:39.5800000Z
Event ID: 6
Task: N/A
Level: Information
Opcode: Info
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: DESKTOP-JEQ91P0
Description:
File System Filter 'FileCrypt' (10.0, ?2002?-?03?-?01T03:12:42.000000000Z) has successfully loaded and registered with Filter Manager.

Event[5335]:
Log Name: System
Source: Microsoft-Windows-FilterManager
Date: 2022-11-09T21:15:39.7360000Z
Event ID: 6
Task: N/A
Level: Information
Opcode: Info
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: DESKTOP-JEQ91P0
Description:
File System Filter 'npsvctrig' (10.0, ?2025?-?01?-?05T18:41:12.000000000Z) has successfully loaded and registered with Filter Manager.

Event[5336]:
Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 2022-11-09T21:15:39.7810000Z
Event ID: 41
Task: N/A
Level: Critical
Opcode: Info
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: DESKTOP-JEQ91P0
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
[/code]

The FileCrypt.sys and npsvctrig.sys driver loads can be discounted because they are Microsoft drivers.

I don't know very much about TCG or storage silos, but from what I've been reading they seem to be related to USB devices(?). In your MsInfo32 output, under the Disks section, you have a USB SD card reader with a card inserted and you have a USB flash drive inserted...
[code=rich][Disks]

Description Disk drive
Manufacturer (Standard disk drives)
Model SanDisk Cruzer Facet USB Device
Bytes/Sector 512
Media Loaded Yes
Media Type Removable Media
Partitions 1
SCSI Bus 0
SCSI Logical Unit 0
SCSI Port 0
SCSI Target ID 0
Sectors/Track 63
Size 29.81 GB (32,012,789,760 bytes)
Total Cylinders 3,892
Total Sectors 62,524,980
Total Tracks 992,460
Tracks/Cylinder 255
Partition Disk #2, Partition #0
Partition Size 29.82 GB (32,015,663,104 bytes)
Partition Starting Offset 16,384 bytes

Description Disk drive
Manufacturer (Standard disk drives)
Model SD Card Reader USB Device
Bytes/Sector 512
Media Loaded Yes
Media Type Removable Media
Partitions 1
SCSI Bus 0
SCSI Logical Unit 0
SCSI Port 0
SCSI Target ID 0
Sectors/Track 63
Size 3.70 GB (3,972,810,240 bytes)
Total Cylinders 483
Total Sectors 7,759,395
Total Tracks 123,165
Tracks/Cylinder 255
Partition Disk #3, Partition #0
Partition Size 3.70 GB (3,976,200,192 bytes)
Partition Starting Offset 4,194,304 bytes
[/code]

I'm wondering whether the PTE corruption is coming from one of these devices? It seems curious that you see those EhStorTcg messages before every error 41 message in your log. Could you try running with these two USB devices disconnected for a while?

I also see from your drivers that you're running the Virtual Gamepad Emulation Framework, which seems from my reading to be related to establishing virtual USB devices? It's the virtual USB nature that concerns me a little, could you do without it for a while? The driver for it (ViGEmBus.sys) is quite old too...
[code=rich]2: kd> lmDvmViGEmBus
Browse full module list
start end module name
fffff804`77f00000 fffff804`77f16000 ViGEmBus (deferred)
Image path: \SystemRoot\System32\drivers\ViGEmBus.sys
Image name: ViGEmBus.sys
Browse all global symbols functions data
Timestamp: Wed Oct 17 21:02:19 2018 (5BC7792B)
CheckSum: 00018AAC
ImageSize: 00016000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Information from resource tables:
[/code]

I think I would also close VirtualBox completely too just to be sure none of its drivers are causing the PTE corruption. TBH it would be wise to shutdown and disconnect everything that you can do without for a few days whilst you see whether any of them might be causing the PTE corruption.

One other, possibly unrelated, driver issue. Your networking drivers are old...
[code=rich]2: kd> lmDvmathw8x
Browse full module list
start end module name
fffff804`781c0000 fffff804`785e7000 athw8x (deferred)
Mapped memory image file: c:\symbols\athw8x.sys\56A9E4F6427000\athw8x.sys
Image path: \SystemRoot\System32\drivers\athw8x.sys
Image name: athw8x.sys
Browse all global symbols functions data
Timestamp: Thu Jan 28 11:52:54 2016 (56A9E4F6)
CheckSum: 0040EC70
ImageSize: 00427000
File version: 3.0.2.201
Product version: 3.0.2.201
File flags: 8 (Mask 3F) Private
File OS: 40004 NT Win32
File type: 3.6 Driver
File date: 00000000.00000000
Translations: 0409.04b0
Information from resource tables:
CompanyName: Qualcomm Atheros Communications, Inc.
ProductName: Driver for Qualcomm Atheros CB42/CB43/MB42/MB43 Network Adapter
InternalName: ATHR.SYS
OriginalFilename: ATHR.SYS
ProductVersion: 3.0.2.201
FileVersion: 3.0.2.201
FileDescription: Qualcomm Atheros Extensible Wireless LAN device driver
LegalCopyright: Copyright (C) 2001-2010 Qualcomm Atheros Communications, Inc.

2: kd> lmDvme2xw10x64
Browse full module list
start end module name
fffff804`77e00000 fffff804`77e29000 e2xw10x64 (deferred)
Mapped memory image file: c:\symbols\e2xw10x64.sys\57D9B88A29000\e2xw10x64.sys
Image path: \SystemRoot\System32\drivers\e2xw10x64.sys
Image name: e2xw10x64.sys
Browse all global symbols functions data
Timestamp: Wed Sep 14 23:52:26 2016 (57D9B88A)
CheckSum: 00026842
ImageSize: 00029000
File version: 9.0.0.42
Product version: 9.0.0.42
File flags: 8 (Mask 3F) Private
File OS: 40004 NT Win32
File type: 3.6 Driver
File date: 00000000.00000000
Translations: 0409.04b0
Information from resource tables:
CompanyName: Qualcomm Atheros, Inc.
ProductName: Killer e2400 PCI-E Gigabit Ethernet Controller
InternalName: A2400.SYS
OriginalFilename: A2400.SYS
ProductVersion: 9.0.0.42
FileVersion: 9.0.0.42
FileDescription: Killer e2400 PCI-E Gigabit Ethernet Controller
LegalCopyright: 2015 Rivet Networks, LLC. All Rights Reserved.
[/code]