Windows 10: BSOD PFN_LIST_CORRUP reoccuring despite new PC setup

Hi,I've been having an issue with BSOD with a PFN_LIST_CORRUPT error.The issue first appeared on my last PCAfter I couldn't figure out what was happening, I re-installed WindowsA few months later it started happening again at random timesI re-installed Windows again, had a few months of no errors and then it happened againNow I have my partners old PC, which has been running fine for almost a yearNow the issue resurfacedWhat I've done:Re-installed WindowsSwitched out an old HarddriveRan a memory diagnostic and removed a faulty RAMRan the driver verifier crashed twice before booting, started a

:)

 

Reoccurring BSOD's relating to bugcheck 0x1a

First time posting, so sorry in advance if I missed a thread policy. This started when I upgraded my rig from a i5 6400 to a Ryzen 5 3600. This also included a new Mobo to suport said cpu. Apart from the torturous 12 hours of errors setting up the system. Once I had it all setup I kept getting these BSOD's after some usage time. After using bugcheck and checking forums, most evidence pointed to the newest nvidia drivers and my crucial mx300 m-sata ssd both causing driver errors. I replaced the SSD, and reverted to the default nvidia driver, and the symptoms stopped showing for a while. This was until Memory_management BSOD's started showing up after I close any game. I read online that Nvidia knew about the errors with their current drivers and were rolling out a patch in the recent update, so i manually installed that driver. This still hasn't fixed the problem. Currently, my computer will work fine until I am either playing or closing a game, which it will then BSOD with different errors each time, but the most common two are System-Service-Exception and Memory_Management. Here is a screenshot of my event viewer:




Troubleshooting Steps I've Done:

• Updated CPU and chipset drivers, both from Mobo website and AMD website
• Updated BIOS to the latest version listed on MSI website
• ran 2 memory tests (one was memtest, the other was a stability test in windows, forgot the name) both finished clean
• installed, removed, and reinstalled nvidia drivers
• reinstalled windows 10
• rubber ducky debugging

I've looked at multiple forum posts online, but none seem to have my exact symptoms so maybe I'm missing something. Thanks in advance for any help! (log files attached)

 

NEW PC Setup

Ok NEW PC setup, had 1 BSOD already though, despite I did clean install system onto my Western Digital SSD, Did reinstall Avast could that be the cause of the Memory Management BSOD? otherwise it seems to be fairly stable, Temps are around 45-51C with one game open, so guess not too bad

Might Drop Avast in Favor of Defender later on

 

PC not blocking ads despite correct DNS configuration

winver: 22H2 19045.2965 I am seeking assistance regarding a peculiar issue I've been facing with my PC's ad-blocking setup. I have set up a Pi-hole server and have correctly configured my PC's DNS settings to point to the assigned DNS of the Pi-hole server. However, despite these settings, my PC still fails to block ads. Here are the troubleshooting steps I have already tried:

• Verified DNS Configuration: I have double-checked and confirmed that my PC's DNS settings are correctly pointing to the Pi-hole server's DNS IP address.
• Tested on Other Devices: To ensure it's not an issue with the Pi-hole server itself, I have tested ad-blocking functionality on other devices connected to the same network, such as another PC, both wired and wireless, and various cell phones. Ad-blocking works perfectly fine on these devices, confirming that the Pi-hole server is functioning as intended.
• Previous Configuration with Docker: It's worth noting that I initially had Pi-hole installed on my PC using Docker, and it worked flawlessly in that setup. However, I later switched to using a separate device (Orange 3 LTS) dedicated to running the Pi-hole server. This is when the issue with my PC not blocking ads started occurring.

Considering the steps I've taken and the fact that ad-blocking functions properly on other devices, it appears to be an isolated problem with my PC. I'm puzzled as to why the DNS configuration is not taking effect on my PC specifically.