Constant BSOD with different error codes

[Slodin]

Hi,

 

After I used my new system for about a week, this constant BSOD started happening. However, it's not the same error code every time but a few does show up more frequent than others. 

I'm running windows 10 pro. Windows update was stuck on an error code as well and not able to update. Using the update troubleshooting tool reveal the update database was corrupted probably because of the sudden BSOD during update. 

 

The error codes are (I may not remember all or very correctly):

IRQL_NOT_LESS_OR_EQUAL

SYSTEM_SERVICE_EXCEPTION

KERNEL_SECURITY_CHECK_FAILURE

Sometimes with no code at all

 

In the dump, more often than not the error shows up as win8_driver_fault but the executable is always logged as the current program I was using at crash. The crashes are pretty random to me, it could crash at boot, 5 seconds after boot, or a few minutes after boot. Safe mode also crashes (which indicates to me it shouldn't be a driver issue).

However, I noticed some dumps always points to atikmdag.sys (I was running the latest optional driver 18.9.3)

 

I thought it was either RAM or my NVME SSD being bad, so I used memtest64 to test the ram with 20 or so loops and no errors were found. Pretty much the same result as windows tools. Then I checked health with crystal disk and it does come back with no problem either. At this point I'am so mind boggled at what went wrong as the system did work with no problems for 1 week.

 

I reinstalled windows 10, but this time I didn't install AMD drivers right a way because I left for lunch. There were no crashes anymore after windows 10 automatically installed an old AMD driver from 2017. So i grabbed the AMD uninstalling tool for a clean and installed the latest stable driver(18.5.1) and so far no more crashes. Now able to update to the latest patch for win 10.

 

I'm still not sure what just happened and why I was getting these random errors if it was just a driver problem...a win10 auto driver conflict?...

I'm asking here as maybe someone has a better explanation as in I'm not confident enough to say I actually fixed the problem and it may come back at some point like previously using the machine with no problem for a week and then poof...