So my brother came to me with his computer which isn't working right, and it's gotten me stumped a bit...
So when he first gave it to me, it was BSODing a lot with the error CRITICAL_PROCESS_DIED I think. I tried running sfc /scannow and a couple different DISM commands, but none were able to finish before a BSOD.
Currently, I've booted into a repair environment on a USB drive and tried running sfc /scannow again. It gave an error about Windows Resource Protection not being able to perform the requested operation.
Because of what I found pertaining to that error, I next tried to run chkdsk C: /R. It's still in the middle of running that, but in sateg 4 (Looking for bad clusters in user file data), it gives me this error: "A disk read error occurredc0000185". After a little bit more time it said "The disk does not have enough space to replace bad clusters". A little more time and then "detected in file 2556 of name . " The same thing has appeared twice now, the second time with file 2559.
It appears that the command is still running, with and ETA of about 4 and a half hours. Does anyone have any suggestions on what I should be doing?
UPDATE: It just finished running the command, and it left me with this: "An unspecified error occurred (6e74667363686b2e af0). Failed to transfer logged messages to the event log with status 50."
Edited by sasschary, 19 February 2017 - 11:29 PM.