Solved Black (not blue) screen, Fatal Error

Windows 11 Home 24H2 OS build 26100.7623, I have not installed 25H2 as it is optional.

Used HP PC in afternoon with no indication of a problem. Later in the evening at log in had a black screen with various messages, as best as I remember - Fatal error, Enter repair environment, Your device couldn’t be repaired, Enter Windows which I did and was able to do a restart.
I have done:
i) CMD run SFC (found corrupt files and repaired), then run DISM.exe /Online /Cleanup-Image /AnalyzeComponentStore followed by DISM.exe /Online /Cleanup-Image /StartComponentCleanup.
ii) Checked Device Manager – no exclamation marks
iii) Checked Event Viewer > windows logs for evening log in:
Application: Warning WMI x3, x3
Security: Nothing flagged
Set Up: Nothing flagged
System: Warning Distributed Com x3, x1
Warning Kernel PnP
Error Distributed Com
Error TPM-WMI x2
Warning Distributed Com x4
Warning Kernel-PnP x2
Critical Kernal power
Error Event log
PC seems to be working OK, but I have no idea what the System log entries mean, apart from not good. Is there something else I should be doing?

Hope you can help, thanks.

Should run restore health before running sfc.

Dism /Online /Cleanup-Image /RestoreHealth

KevTech said:

Should run restore health before running sfc
Dism /Online /Cleanup-Image /RestoreHealth

Click to expand...

I usually run SFC first. If SFC completes successfully, either with no errors or errors it can correct, then there is no need to restore health.

Only if SFC says it found errors it cannot correct then the component store is probably corrupt and needs fixing with the DISM restore health command.

Please run the V2 log collector > post a share link into the newest post

Bree said:

I usually run SFC first. If SFC completes successfully, either with no errors or errors it can correct, then there is no need to restore health.

Click to expand...

But that is doing it in the incorrect order.

If the component store itself is corrupt then SFC can not find files that are not corrupt to repair with or will use corrupt files to repair with.

Restore health is what repairs the component store files.

Microsoft details the correct order.

Many thanks for the replies, seems to have been resolved without using BSOD, which was beyond me. Ran the DISM and SFC again in correct order and also found an optional HP BIOS update which I installed. I didn’t think to do a check after each, so it could have been one or other, or both!

All Microsoft is trying to do is make sure you have a healthy image before running SFC.

There is another way you can make sure you are working with a healthy image and then may not have to even need to run restorehealth before running SFC.

That is checkhealth and scanhealth.

Checkhealth is a fast check that looks at the Windows Update logs for corruption flags.
Scanhealth is a more thorough scan of the component store (WinSxS) for corruption.

These will report if the image is repairable, non-repairable, or healthy.
If either of them reports that the image is repairable then you should run restorehealth before running SFC.
If checkhealth and/or scanhealth come back "No component store corruption detected" then you can skip restorehealth as you now know that SFC has a "healthy" image to work with and can do it's job correctly.

I have worked on hundreds of systems where SFC reported "Windows Resource Protection did not find any integrity violations." but then checkhealth and/or scanhealth report the image needs to be repaired or cannot be repaired. So now I have learned to just check or scan the health before running SFC.

Also, before creating Macrium or other backup images, I now run checkhealth and/or scanhealth then only if needed restorehealth before running SFC to make sure the image I am backing up is "healthy".

For reference:



Only if needed as reported by check or scan health:


Then run SFC:

Thanks KevTech, copied and pasted notes to my computer info.