Windows 10: BSOD on 2/18/2020

Last week 2/18/2020, after having our desktop off for 10 days, it suddenly shut down after being on maybe 10 minutes. We had it on maybe 30 minutes the day before to check emails with no problems. Now all we get is bsod with error code: "bad system config info.' We have tried multiple fixes cannot start in safe mode, can't reset, won't go back to previous setting, etc and cannot get it to start up. I have access to the recovery screen with fixes, but none will work. We can access a command prompt and haven't had success with any fixes. No new hardware or programs have been added.


Is an update the cause of this?

:)

 

Bsod affter 2/18/19 update

I uninstalled the 2/18/19 updates (there were two). As soon as I rebooted Win 10
re-installed them, but I am not getting the BSOD now.

As a further precaution I disabled the auto update feature.

For future reference, the method of uninstalling the updates requires getting the system running in normal mode
long enough before the BSOD kicks in to work.

I'm guessing the initial installation was "flaky".

 

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.

 

IRQ memory BSODS, device manager, memory range?

The only time I've seen that type of BSOD for myself is when I fried the PCI-e slots on my Striker 2 board... There wasn't anything that I could do, try and rma and go on.. I would suggest the steps that MilkyWay has said.. But, if you really don't know much about Bios's... I wouldn't play with Irq's... That can mess up everything on your board. USB, ethernet, ram, chip... But, that's just me on playing with irq's... To much of a hassle IMHO..