Windows 10: Random BSoD after updating motherboard BIOS

So, I updated my motherboard's BIOS recently and since then I've been getting pretty random BSoDs. It doesn't matter if I'm doing anything or not, it just happens.

It's always one of two errors:

1. Kernel Security Check Failure
2. Driver IRQL Less or Not Equal

My Specs:

• ASUS B450M Plus
• Corsair Vengeance 2666mhz 16GB
• Nvidia RTX 2080S
• AMD Ryzen 3700x

Nothing is overclocked.

I read that it could be a hardware issue or a driver issue but I don't know how to identify exactly what the problem is so I can fix it.

submitted by /u/ComeonmanPLS1
[link] [comments]

:)

 

Random BSOD after bios update

I sent PC to computer service due to RAM issue i mentioned before. They updated BIOS. I can send them PC again, but it seems illogical to me that updating BIOS can cause random BSOD.

 

Random BSOD after bios update

Dear,

After bios update I have started to experience random BSOD. Bios was updated because system was detecting only 8 gb of ram, and i have 2 x 8 gb of ram. Things i have tried till now:

1) Memtest86 it went for 15 hours, it didn't show any error

2) I tried sfc /scannow, also it was successful

3) I updated windows and all drivers, also it was successful but BSOD still continues

4) I checked my SSD and hard disk for any errors, that was successful also

I experience BSOD in random moments. And i started experience them only after bios update, before that everything was working normally.

Can you help me detect problem?

Link to minidumps: minidump.zip

Link to SystemInfo: systemInfo.zip

King Regards,

Igor Vurdelja

 

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.