Windows 10: Getting constant BSODs or random freezing

Sometimes its IRQL_NOT_LESS_OR_EQUAL, sometimes its DPC_WATCHDOG_VIOLATION, other times its UNEXPECTED_KERNEL_MODE_TRAP. The error changes every time, other times my computer just freezes and I have to restart it. I have attached a dropbox link to my minidump files, if anyone is able to figure out what is wrong that would be much appreciated! It seemingly happens at random, and I can't seem to figure out what the problem is for the life of me. https://www.dropbox.com/scl/fi/oxudfsmprsmtffkeymmby/Minidump.7z?rlkey=p9qsbdd7s38we56qz053o4l98&st=po0pue5d&dl=0

:)

 

Random freezes and BSOD crashes with code MEMORY MANAGEMENT

Ok, I managed to get it working.
It performed 9 tests on the sole 8 GB RAM slot I have. 9 passes, no errors. So RAM is not faulty after all..

So, what is the next step in investigating the BSODs and random freezes?

 

Random BSOD while browsing internet


BitDefender is nothing special. mwac.sys causes BSODs anywhere.
A tiny documentation can be found here: Solved Random BSODs - Windows 10 Forums
In that very thread, the suggested action apparently worked.

The storage and network filters of any third party antivirus can cause BSODs. Neither MBAM nor BitDefender is any special. For a regular antivirus, it may be shifted to an alternative; but MBAM has no alternative. So a clean install of the said program is the most feasible first step.
As far as the first step is not failing, it is better to not think for the second step. Because the BSODs are not universal, failure at the first step is not universal; and success at the second step is also not universal.
That is why I posted that my suggestion may work, or may not. Let us see where it goes.

 

Random freezes or BSODs (In windows drivers)

Basically you need to go back to the step described in my post #121

As the freeze happens when you leave the system idle for a while it is most likely a driver associated with a background process that starts up when the system is idle for while. You might be able to search the event information logs to check which services started around the exact time of the freeze.