Windows 10: BSOD - Unknown Cause

I have been running into issues with my PC for the past couple of days and the BSOD. I have tried my best to troubleshoot and even re-imaged my system from scratch and the issue is still occurring. Prior to the re image the issue would happen while I was using the PC but since then it only seems to occur when it is asleep. Been trying to troubleshoot from the event viewer but I can't seem to figure it out.

When using WhoCrashed the conclusion was "6 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you. "

Any help getting to the bottom of this would be much appreciated.

Windows 10 Pro - Version 1909 (Build 18363.720)

Diagnostic Files - Dropbox - DESKTOP-RC42K19-(2020-03-30_19-53-06).zip - Simplify your life

:)

 

Random BSODs with unknown cause

Please run driver verifier using the following settings for 48 hours.

• Special Pool
• Force IRQL checking
• Pool Tracking
• Deadlock Detection
• Security Checks
• Miscellaneous Checks
• Power framework delay fuzzing
• DDI compliance checking

Warning: driver verifier could cause boot issues and/or performance issues.

• Make sure that you have recovery media, if needed you can create it.
• Configure a restore point prior enabling driver verifier.

Resetting driver verifier options (recommended in this order)

1. In normal mode open an administrator command prompt and enter the below command
2. In safe mode open an administrator command prompt and enter the below command
3. On 3 boot failures, you'll boot automatically to the recovery options,
   • click Troubleshoot
   • go to the advanced options
   • choose command prompt
   • enter the below command
4. Boot with the recovery media, see above 4 steps in option 3.
5. Via the recovery options or recovery media, select a restore point prior enabling driver verifier

Code:

Crashed when running driver verifier

1. Reset driver verifier
2. Boot in normal mode if necessary
3. Follow Blue Screen of Death (BSOD) Posting Instructions to provide the requested logs

 

BSOD Hardware Caused???

they do weird things like that, which all seem like something else is failing.
One of the worst things to diagnose, they seem to only quit when they want to.

Memtest is a good next step, if you rule out RAM and Power Supply make sure you disconnect all unnecessary peripherals and try to start the system with as little hardware as possible, if it works then, you can narrow down the culprit by trial and error.

the follow was taken from some website:

It's very difficult to determine if a failure is caused by the CPU because many other components can cause the same symptom when they fail.

1. System fails to boot
2. System re-boots intermittently
3. General Protection Fault
4. Illegal Operation
5. Stop Error, or BSoD (Blue Screen OfDeath)

Actually, CPUs rarely fail, and about the only way to determine if the CPU is causing the failure is to swap it out with a known working CPU of the same type and speed. Since this is difficult, the best bet is to first rule out every other possibility.

Before suspecting the CPU, rule out all the possibilities listed below.

1. The Operating System
2. A peripheral port device
3. A bad memory module
4. The hard disk drive
5. The power supply
6. The motherboard

If you have ruled out out all the other possibilities, investigate the items listed below.

1. Overheating
2. A short circuit
3. ESD

 

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.