Windows 10: BSOD on Windows Startup after Power Failure - Cannot boot, cannot SFC, cannot DISM -...

I had a power failure the other day while using the computer and I cannot boot past the Windows logo and progress ring without encountering a BSOD for Critical Process Died. Examining the drive via the WinRE command line or another working Windows drive, it appears that everything is fine, so the problem is probably some corrupted system files. I just can't figure out which.I had restore points, but WinRE can't find them. I have run CHKDSK multiple times and it finds no problems. SFC always yields "Windows resource protection could not perform the requested operation" and I haven't found any

:)

 

Can't get SFC and DISM to work anymore on Win10

Ok, can someone help me out because this crap is starting to piss me off. There was once a time when you could simply run SFC and DISM to check Windows files integrity and if there were any problems found with the local files, Windows repaired it automatically. The reason why I want to run this is because I'm getting stupendously huge amount of errors and warnings in Event Viewer, but I don't want to run refresh because it'll mess up tons of apps.

Commands I used:
sfc /scannow
Dism /Online /Cleanup-Image /RestoreHealth

Fast forward few years and we now have glorious Windows 10. Trying to run the same tools, they find errors but stubbornly refuse to fix ANYTHING. What's the god damn point of it then?

Sfc finds issues but can't repair them and DISM constantly bitches how it can't find the source. All this used to work directly in Windows 7, but in Win 10, nothing. This was one of the best features to get OS back in good state and they go and ruin it. Because Microsoft!

I've checked this thread:
https://social.technet.microsoft.co...sfc-failed-to-repair?forum=win10itprohardware

Nothing worked. And they keep mentioning install.wim where my Windows image downloaded from Microsoft itself! only carries install.esd which I can't seem to use with anything.

I've also tried this tool:
CodePlex Archive

Which again wants .wim file and refuses to work with esd.

 

Driver Power State Failure (ntoskrnl.exe+22092e ) BSOD

Hi Ayan,

I suggest you to follow the steps given in the link below and check if it helps you.

Shutdown BSOD: Driver Power State Failure (Windows 8.1 Pro 64-bit)

Let us know the status of the issue.

 

Driver Power State Failure (.dmp file)

Thank you for the reply,

I ran both SFC and DISM both returned no errors

I ran a CHKDSK on the HD and it returned no errors

I ran the HD checking utility from WD and it returned no errors

I also tried disabling the HD in questions as it is not the HD I boot from and still received a Driver Power State Failure about a 30 - 45 seconds after startup.

any suggestions?