Windows 10: New WIn11 Installation on new hardware, repeating random BSOD issue

Good day folks!I have recently built a new system Intel 13900k, 64GB Corsair DDR5, RTX4080 and performed a fresh OEM installation of Win11 and installed all drivers and performed updates when necessary. The PC will BSOD completely randomly, sometimes even in the middle of the night when not in direct use. I am not overclocking anything. I suspect a misbehaving driver, but as the BSODs are different downstream processes each time, I am having a difficult time identifying the culprit. I have collected a series of minidumps as well as used the verifier tool and collected a minidump from tha

:)

 

Repeated BSOD on brand new Win11 System

If this is a new build and you have not installed any third party apps, or hardware, then go back to the seller, as BSOD's should not be occurring

 

fresh Win11 install having stopcode

hi, seeking help here with a new miniPC PN64 that keep getting stopcode (very random, and everytime different stopcode). Upon customer service agent suggestion, I've also reinstalled fresh Win11 pro (not upgrade, not repair) and when it boots into desktop for the very first time, BSOD stopcode. customer service agent have changed a new unit, same thing. and have changed the motherboard, same issue. In total, I've had same issue with 3 different motherboards, all PN64 motherboards, different serial numbers.

any suggestions? thanks.

 

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.