Windows 10: BSOD win 10

This is the first time my pc runs into BSOD, i checked event viewers. It said MMC.exe not responding and window initiate restart to bug check. I checked the maintenance window, hardware and software are all good, no action needed. Currently im doing a maintenance check.Whats the error and should i be concern?

:)

 

Win 10 BSOD after reducing number of CPUs

• Win 10 x64 running in VMware Fusion VM on MacBook Pro w/ 6 physical cores & HT.
• When VM is configured with 5+ CPUs, Windows runs fine.
• When VM is configured with 4 or fewer, BSOD INVALID SYSTEM CONFIG INFO
  • WINLOAD.EFI missing or corrupted
  • Attempt to repair using ISO image fails

OS X 10.15.4, VMware Fusion Pro 11.5.3

Win 10 Enterprise

Version 1703

Build 15063.2108

Any suggestions appreciated, as I need to move this VM to another HW config with fewer physical CPUs.

Thanks!

 

Win 10 BSOD while using

Did upgrade to Win 10 over a month ago. This morning my Lenovo T410 laptop had the BSOD with Error=0xc000000f on it (it does backups overnight). I've run diags on the hardware (mem, motherboard bus, PCI bus and HDD) all PASS. Tried using my repair disk
(built in Jan with Win7) and was unable to recover. I checked for bad sectors and found none. From CMD prompt I did DISKPART and LIST VOLUME and all volumes say HEALTHY but I see that my C: drive (primary partition) says it is RAW (instead of NTFS). My backup
media is a network attached (NAS) disk and I used Cobian 11 Backup. Not sure what my next step would be. Looking for suggestions before I have to restore to Win7 and re-upgrade, etc.

 

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.