Is there a recent update causing BSOD/no boot?

[mikeroq]

I had two computers with this issue, possibly the same and a third just now.

First computer reported yesterday not booting. Goes into automatic repair.
Second computer same thing.

Looked at both this morning out of town and found one of them was blue screening with CRITICAL_PROCESS_DIED.

On both I was able to system restore and all is working fine now. Checked for updates, one installed some, other didn't have any. Rebooted them a few times and called it good for now. I almost wanted to blame an update but I couldn't be 100% sure.

Now I have a third computer in another city with a similar issue. This could be just coincidence, or could be a similar issue. The first two were HP, one 8th gen Intel, other 11th gen. This third one is an older 2nd gen Dell. Mix of Windows 10 and 11. This third one I had them try system restore and there were no restore points available. Since it's 11 years old I think we will just replace it and move on.

I just wanted to check if anyone had anything similar going on this week.

 

[Markverhyden]

Not here. Other typical problems but nothing killing booting up.

 

[frase]

No issues here, did you check event viewer; most likely a driver issue.

 

[HCHTech]

Wow, the google results on that phrase aren't exactly precise. Could be hardware, software, drivers or infection. Well, that's everything!

 

[Sky-Knight]

Patch week is NEXT week, if you've got BSOD's happening before patch rollout.... it isn't patches.

Critical Process Died is usually a bad driver or RAM in my experience.

 

[nlinecomputers]

Patch week is NEXT week, if you've got BSOD's happening before patch rollout.... it isn't patches.

Critical Process Died is usually a bad driver or RAM in my experience.

This. Make and model on all these PCs would help. Could be they’re all from the same manufacturer. Or it could just be your magnetic personality and it is just a coincidence.