Daily BSOD - - - ntoskrnl.exe (+416980) issue?
Daily BSOD - - - ntoskrnl.exe (+416980) issue?
Hello everyone,
I've been experiencing BSODs for several months now, mostly triggered by ntoskrnl.exe (+416980). It doesn't matter if the PC is idle or active; it can happen during shutdowns or restarts, sometimes even once a day or more.
The minidumps are available here: https://ufile.io/f/kvoic
Initially, the first BSODs were linked to memory management issues. Later, a range of other causes emerged. I tried running memtest86 on my G.Skill RAM and stopped after a few minutes because of excessive errors. I also experimented with different configurations, including without XMP profiles.
I suspected the RAM was faulty, so I sent it in for replacement and received new units. Meanwhile, I purchased additional RAM from another brand, which allowed me to complete a build. Those were 2x Patriot 8GB DDR4 2666MHz CL19 units, and I ran memtest86 without any problems.
However, the issue persisted daily. I repeated memtest on my G.Skill RAM and still encountered errors. I reinstalled the Patriot RAMs, ran memtest for about 12 hours, and no errors appeared. Over time, the problems continued.
I investigated further by reinstalling Windows on a new disk. I was using Windows 10 at the time and switched to Windows 11 on the new drive, keeping the old one as storage. The issues persisted.
Currently, I have changed the RAM, updated all drivers (including third-party apps), performed an SFC scan, and used driver verification tools. The minidumps remain unclear, and I’m still trying to resolve the problem.
I attempted to replace my GPU with an older model (NVIDIA again). I’m still struggling to interpret the minidumps and would greatly appreciate any advice.
Thank you in advance for your help. Let me know if you need more details.
I appreciate your response. Concerning the drives, 970 was the previous drive with Win10 installed. Now it's being used for Steam games. Apacer is the latest version, running Win11. I've never run both operating systems simultaneously on different drives before. The SATA drivers have always been for storage only. RAMs: I made a mistake by checking both vendors, but neither kit appears in the QVL list for my motherboard. I plan to remove the old drive (970 EVO) from the system, but will keep using Win11 for now to test. If the issue persists, I'll reinstall Win10 on the new Apacer drive and verify. I’ll attempt to install QVL RAMs later to confirm everything works. Thank you again, and I’ll keep updating this thread if it helps someone else.
You don't require two operating systems to function simultaneously, just having multiple drives connected at once with an OS installed on each is enough. Only one drive within a system should host an operating system.
After I took out the Samsung 970 EVO, it continued to crash, this time specifically due to MEMORY_MANAGEMENT. Then, I began removing one drive at a time, followed by the other two with SATA connections. Initially, I removed the WD drive but it only failed once. The other Samsung drive was removed next. For the last 18 hours, it hasn't crashed again, so I'll keep monitoring. Right now, I'm using just one drive, the Apacer model. The three most recent dumps were created after I started removing drives.
Dumps: https://ufile.io/f/fd4nb
Yes sorry forgot to mention that:
be quiet! Straight Power 11 Platinum 850W
was bought on 10/10/2020 and it was brand new, original to build.
occasional gaming but not something demanding, no video editing or mining
So it was crashed once more, here is the latest dump. Upload files for free - 120623-6625-01.dmp from ufile.io. Download 120623-6625-01.dmp instantly for free from ufile.io without signup or popups. ufile.io. At this stage, I only have one disk left. Other options besides reinstalling Windows 10 seem limited right now.