Windows 10: KB 5000802 caused repeated BSOD and

The KB5000802 update caused repeated BSOD crashes at printing, and after a third of fourth one the computer became unusable, cycling BSOD "critical process died". No recovery options worked so far. In only have the option of "Advanced Options" of the Windows RE environment or booting from a thumbdrive, but SFC /scannow results in windows resource protection could not perform the requested operation, DISM results in error 2. CHKDSK discovers no problems on the disc.

:)

 

Repeated Crashes and Boot Errors Apparently Caused by Driver Updates

Steps 1-5:
Microsoft Windows [Version 10.0.15063](c) 2017 Microsoft Corporation. All rights reserved.C:\WINDOWS\system32>sfc/scannowBeginning system scan. This process will take some time.Beginning verification phase of system scan.Verification 100% complete.Windows Resource Protection did not find any integrity violations.C:\WINDOWS\system32>dism /online /cleanup-image /restorehealthDeployment Image Servicing and Management toolVersion: 10.0.15063.0Image Version: 10.0.15063.0[==========================100.0%==========================] The restore operation completed successfully.The operation completed successfully.C:\WINDOWS\system32>chkdsk /scanThe type of the file system is NTFS.Volume label is OS.Stage 1: Examining basic file system structure ... 641024 file records processed.File verification completed. 38938 large file records processed. 0 bad file records processed.Stage 2: Examining file name linkage ... 752848 index entries processed.Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found.Stage 3: Examining security descriptors ...Security descriptor verification completed. 55913 data files processed.CHKDSK is verifying Usn Journal... 37708720 USN bytes processed.Usn Journal verification completed.Windows has scanned the file system and found no problems.No further action is required. 975633897 KB total disk space. 657134732 KB in 395186 files. 231620 KB in 55914 indexes. 0 KB in bad sectors. 806393 KB in use by the system. 65536 KB occupied by the log file. 317461152 KB available on disk. 4096 bytes in each allocation unit. 243908474 total allocation units on disk. 79365288 allocation units available on disk.C:\WINDOWS\system32>

Steps 7-9:

 

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.