New
#1
BSODs Windows 10 20H2 19042.867 - I'm at my wits end...
Hi everyone,
Thanks in advance for your help.
I'm running Windows 10 20H2 19042.867, and I've literally exhausted all options with these damn BSODs. (I'll definietly be uploading a BSOD log once it generates a new one).
In a nutshell, I built a PC about 8 months ago. It's an AMD Ryzen 7 3800XT, 64GB RAM 4x 16G RAM G.Skill Aegis at 3200Mhz, 1TB M2 970 EVO Plus, 4TB HDD, MSI MAG B550M, Zotac Gaming 1660 Super, TP-Link 1Gbps PCI Express card. Before this I actually used different RAM and a different motherboard. I experienced BSODs on the Gigabyte motherboard and managed to narrow this down to the RAM, this was refunded to me and new RAM purchased. Since then I replaced the MB to the MSI MAG B550M, upgrade the BIOS to the latest stable version, reset Windows twice now, updated all drivers, firmware etc.
I didn't build this PC for gaming hence the lackluster GPU, but I wanted to be sure there was no performance impact from the GPU on the CPU/RAM etc so a 1660 was a happy medium. I use the PC heavly for work, compiling software, virtual machines and at times I can have up to 6 to 8 VMs on the go. I've also got Plex Media Server running on this as well (I doubt this is the issue).
Nonetheless, Windows has been throwing constant BSODs, these can range from NON_PAGEFILE_FAULT_IN_NON_PAGEFILE_AREA, HYPERVISOR_ERROR (this is probably just Hyper-V being stupid but only occured once, MEMORY_MANAGEMENT (this is an interesting one, it's only happened once), SYSTEM_THREAT_EXCEPTION, there was also an error that was pointed directly to Razer Cortex which I've since uninstalld, sometimes the PC can be on for 9 days straight with no issues, but all of a sudden over night it'll go through multiple reboots with multiple different errors.
The BSODs are random, mostly they happen when the PC is not phsically in use, I could have multiple applications open and be physically using it and it will be fine, but then you leave it over night and it reboots. It does it even when there are no applications open after a fresh restart and no VMs powered on.
I've literally replaced every part except for the CPU, I've even replaced the SSD prior to this I was using a 512GB M2 Samsung drive from my old laptop on the Gigabyte motherboard. On the GB MB I experienced similar if not the same BSODs on roughly the same version of Windows.
Short of now replacing the CPU or even getting an independent assessment of all the parts, I'm not sure what to do. I have an unreliable PC that will sometimes stay on for two weeks or more without issues but then, throw a tanturm for a day or so. The CPU is the last part that hasn't been replaced, it's been reseated obviously in the new MB and new thermal paste applied generously but not excessively, I've made sure there is no leakage, temps are fine in that regard.
I will post a BSOD log once it inevitably does it again, in terms of performance the PC runs fine, I don't experience your typical memory issues that are evident of failing RAM. I've also attempted to run memory diagnostics, this is interesting because when ever I try to do this Windows won't boot to the memory management console, it did once, passed the test and that was that. I honestly think this is Windows 10, since I've basically replaced all the parts except for the CPU (what are the chances of the CPU being faulty?). My last two resorts now are to 1. reset and go back to v1909 or v2004, which is still currently LTS I think? and 2. metorphically throw this thing at a PC repair place and say 'fix and send me the bill'.
I'm tempted to try Linux, I've got 2x M2 ports on the MB, so trying Linux and running some tests and seeing if I get any errors might help? I'm not good a Linux but I guess Google will help.
Please, any advice would be fantastic. I love this PC I built, but it's giving me grey hairs now. I can't afford for it to be constantly crashing, if it is Windows and downgrading to stable version or even installing Hyper-V server is my only option I'll do it.
Last edited by adzysim; 21 Mar 2021 at 03:39.
Quote