I just spent about 5 hours or so troubleshooting why my PC was stuck in a boot loop with the very unhelpful error message 'CRITICAL_PROCESS_DIED'(because there's like 50 different things that can cause this).
This is the second time this has happened within a year. The first time was that a hard drive had died(overheating issue due to this comp's case sucking ass because it puts the fan within inches of the hard drives so wires can get sucked in)and promptly became Jesus once I shelled out for a shiny new SSD and installed Windows on it, this second time killed the master boot record, and I spent time richarding around because the first error message it gave me (something about the windows config being corrupted) and the fact CRITICAL_PROCESS_DIED can often be a driver error pointed me to believe that I needed to chkdsk.
That didn't do anything, so then I took off the side panel of the case to check if the hard drive fan was running, and also disconnect the other drives to check if they were interfering.
And then I had to jam several different small objects into a very small port in the CD drive because Windows cannot figure out how CD drives work if they don't have CD's in them(the port tells the drive to move the motor manually rather than do it according to how the driver it has wants it done), and put an install disk in there to do a recovery with bootrec(which decided that Windows wasn't a real thing for forget if I know) and bootsec(which was completely inconsistent with which drive(between the SSD and the 'system reserved' partition) it believed was being used(hint: the actual answer is neither, i'm running off the disc godammit) despite using the /force flag which shouldn't care if there's a drive in use to begin with.
This all happened because of a single bluescreen from a wifi dongle crashing because my router was kicked offline because god knows why.
tl;dr - windows is an unstable, whiny bitch and it's recovery options suck richard
