The exception to known good files is kwwdapod.sys which is almost certainly malware. Normally when we see a lot of known good files in BSODs it's heat related or perhaps bad memory Avast still will not do a full system scan after I boot, even after I reinstall Avast. I also tried using Avast's aswmbr.exe, but my PC instantly crashes when I click 'Yes' when prompted if I wish to use Virtualization Technology for rootkit detection, which seems strange. I know that might have been normal, but I rewrote it to default using a Windows 10 installation disc and command prompt from the boot menu. I noticed some odd behavior when I booted up the laptop that made me decide to do an MBR check on my desktop PC, which detected nonstandard code. I found several suspicious things with Pchunter and Gmer, which seem to be mostly gone now, but the BSODs persist - perhaps slightly less frequently, unless I'm imagining it. I have otherwise tried to avoid touching any system files too much. I understand the risks of deleting files like this, but I held my breath and decided to carefully remove it. I did a scan with tdsskiller and found a very suspicious driver that was hidden and had been created the same day I had started work on the laptop, called amdfx.sys.
