Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › Crash Analysis and Debugging › Windows 8.1 Won't boot - CRITICAL_PROCESS_DIED - 0x000000ef
New Posts  All Forums:Forum Nav:

Windows 8.1 Won't boot - CRITICAL_PROCESS_DIED - 0x000000ef

post #1 of 9
Thread Starter 
Well, as if I wasn't fuming enough already, I just had my lovely phone erase the book of a post I typed.... So here we go again with a viable typing medium.

I have been running Windows 8.1 on my sigrig (minus the 7950) for about a week now. Everything has been running great, except for today's banner experience.

I went to go take a shower, and before going I put my computer to sleep. When I came back, my power light wasn't blinking, so I assumed my computer somehow lost power while I was gone.

I turned on my computer, and the UEFI was spamming text about it cleaning up an improper shut down, then it proceeded to display something along the lines of "Loading startup repair".

Once it got past this, it said it was repairing disk errors, then it rebooted. Now every time I turn my computer on, I get the CRITICAL_PROCESS_DIED blue screen. If I boot into safe mode, I get the same error. I can't even use the "Refresh my PC" option.

I basically can't do anything with it, so I installed windows on my ssd so I could view my bad install drive. I scanned the drive, and no errors were reported. I then deleted the pagefile, hyberfile, and swapfile, figuring that Windows corrupted them doing some weird hybrid sleep.

No dice, still get the blue screen and can't boot into Windows, or safe mode. I also reset my bios of course, and that did nothing.

I have the MEMORY.DMP file (Which I can't seem to view with bsod viewer, not compatible with 8?) And there are logs somewhere, didn't catch the location. Also, from what I've read, this bsod is more common when coming out of sleep, not at every boot *attempt*

Some help would really be appreciated, Thanks!
My Pride and Joy
(22 items)
 
  
CPUMotherboardGraphicsGraphics
[Intel] i7-3770k @ 4.8 GHz (Delid) [ASUS] P8Z77 WS [Sapphire] R9 290 Vapor-X [Sapphire] R9 290 Vapor-X 
RAMHard DriveHard DriveHard Drive
[Team Group] 16GB @ 2133 [Samsung] 850 Pro 256 GB [Samsung] 840 Evo 120 GB [Western Digital] Caviar Blue 1TB 
Hard DriveHard DriveHard DriveHard Drive
[Seagate] Barracuda 1TB [Seagate] Barracuda 500GB [Toshiba] 2TB [Kingston] SSDnow V300 60gb 
Optical DriveCoolingOSMonitor
Asus drive Custom Loop ;D [Microsoft] Windows 8.1 Pro x64 BenQ BL3200PT 
MonitorKeyboardPowerCase
Acer H276HL Logitech G19 [Corsair] HX 850 [NZXT] Phantom 630 
MouseAudio
Logitech G502 Sony MHci99 
  hide details  
Reply
My Pride and Joy
(22 items)
 
  
CPUMotherboardGraphicsGraphics
[Intel] i7-3770k @ 4.8 GHz (Delid) [ASUS] P8Z77 WS [Sapphire] R9 290 Vapor-X [Sapphire] R9 290 Vapor-X 
RAMHard DriveHard DriveHard Drive
[Team Group] 16GB @ 2133 [Samsung] 850 Pro 256 GB [Samsung] 840 Evo 120 GB [Western Digital] Caviar Blue 1TB 
Hard DriveHard DriveHard DriveHard Drive
[Seagate] Barracuda 1TB [Seagate] Barracuda 500GB [Toshiba] 2TB [Kingston] SSDnow V300 60gb 
Optical DriveCoolingOSMonitor
Asus drive Custom Loop ;D [Microsoft] Windows 8.1 Pro x64 BenQ BL3200PT 
MonitorKeyboardPowerCase
Acer H276HL Logitech G19 [Corsair] HX 850 [NZXT] Phantom 630 
MouseAudio
Logitech G502 Sony MHci99 
  hide details  
Reply
post #2 of 9
CRITICAL_PROCESS_DIED can occur at any time during Windows operation, all the way from Session Manager initialization (a bit later in the boot process), up until the system is shutdown.

It might be useful to know what critical process is actually exiting unexpectedly. Did the system collect minidumps or just the full MEMORY.DMP? If there are minidumps (C:\Windows\Minidump), please upload those here, rather than the entire MEMORY.DMP, and I'll take a peek!
Ol' Sandy
(28 items)
 
"Zeus"
(12 items)
 
Elite Preview
(6 items)
 
CPUMotherboardGraphicsRAM
Intel Xeon E3-1230v3 Gigabyte GA-Z97X-UD5H-BK MSI Gaming GTX 980 Kingston 32GB (4x8) 
Hard DriveHard DriveHard DriveHard Drive
Plextor PX-256M5S 256GB Samsung EVO 1TB Hitachi HDS721010CLA332 Hitachi HDS723020BLA642 
Hard DriveHard DriveHard DriveOptical Drive
Hitachi HDS723020BLA642 Hitachi HUA722010CLA330 WDC WD10EARS-00Z5B1 TSSTcorp CDDVDW SH-S223B 
CoolingCoolingOSMonitor
Phanteks PH-TC14PE with TY-140's Lamptron FCv5 (x2) Windows 8 Pro 64-bit Dell U2412M 
MonitorMonitorMonitorKeyboard
Dell U2412M Dell U2212HM Dell U2713HM Topre Realforce 87UB | Ducky DK9087 G2 Pro 
PowerCaseMouseMouse Pad
Corsair AX-750 Corsair Obsidian 650D Logitech G700 XTRAC Ripper XXL 
AudioAudioAudioAudio
Beyerdynamic DT-770 Pro 250ohm Schiit Bifrost DAC Schiit Asgard 2 HiVi Swan M50W 2.1 
CPUMotherboardRAMHard Drive
Intel Xeon E5-2620 Super Micro X9SRL-F-B 128GB 1333MHz LSI 9271-8i 
OSPowerCase
VMware ESXi 5.5 SeaSonic SS-400FL2 Fractal Define R3 
CPUMotherboardGraphicsRAM
Intel Core i5-3437U HP EliteBook Folio 9470m  Intel HD Graphics 4000  16GB DDR3 SDRAM 
Hard DriveOS
256GB SSD Windows 10 Insider Preview 
  hide details  
Reply
Ol' Sandy
(28 items)
 
"Zeus"
(12 items)
 
Elite Preview
(6 items)
 
CPUMotherboardGraphicsRAM
Intel Xeon E3-1230v3 Gigabyte GA-Z97X-UD5H-BK MSI Gaming GTX 980 Kingston 32GB (4x8) 
Hard DriveHard DriveHard DriveHard Drive
Plextor PX-256M5S 256GB Samsung EVO 1TB Hitachi HDS721010CLA332 Hitachi HDS723020BLA642 
Hard DriveHard DriveHard DriveOptical Drive
Hitachi HDS723020BLA642 Hitachi HUA722010CLA330 WDC WD10EARS-00Z5B1 TSSTcorp CDDVDW SH-S223B 
CoolingCoolingOSMonitor
Phanteks PH-TC14PE with TY-140's Lamptron FCv5 (x2) Windows 8 Pro 64-bit Dell U2412M 
MonitorMonitorMonitorKeyboard
Dell U2412M Dell U2212HM Dell U2713HM Topre Realforce 87UB | Ducky DK9087 G2 Pro 
PowerCaseMouseMouse Pad
Corsair AX-750 Corsair Obsidian 650D Logitech G700 XTRAC Ripper XXL 
AudioAudioAudioAudio
Beyerdynamic DT-770 Pro 250ohm Schiit Bifrost DAC Schiit Asgard 2 HiVi Swan M50W 2.1 
CPUMotherboardRAMHard Drive
Intel Xeon E5-2620 Super Micro X9SRL-F-B 128GB 1333MHz LSI 9271-8i 
OSPowerCase
VMware ESXi 5.5 SeaSonic SS-400FL2 Fractal Define R3 
CPUMotherboardGraphicsRAM
Intel Core i5-3437U HP EliteBook Folio 9470m  Intel HD Graphics 4000  16GB DDR3 SDRAM 
Hard DriveOS
256GB SSD Windows 10 Insider Preview 
  hide details  
Reply
post #3 of 9
Thread Starter 
Unfortunately windows didn't kick down any minidumps, however despite windbg not reading my symbols for whatever reason, I was able to pull this out of the 1 gig dump file:
Code:
STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  6.3.9600.16452

FAILURE_ID_HASH:  {70b057e8-2462-896f-28e7-ac72d4d365f8}

Followup: MachineOwner
My Pride and Joy
(22 items)
 
  
CPUMotherboardGraphicsGraphics
[Intel] i7-3770k @ 4.8 GHz (Delid) [ASUS] P8Z77 WS [Sapphire] R9 290 Vapor-X [Sapphire] R9 290 Vapor-X 
RAMHard DriveHard DriveHard Drive
[Team Group] 16GB @ 2133 [Samsung] 850 Pro 256 GB [Samsung] 840 Evo 120 GB [Western Digital] Caviar Blue 1TB 
Hard DriveHard DriveHard DriveHard Drive
[Seagate] Barracuda 1TB [Seagate] Barracuda 500GB [Toshiba] 2TB [Kingston] SSDnow V300 60gb 
Optical DriveCoolingOSMonitor
Asus drive Custom Loop ;D [Microsoft] Windows 8.1 Pro x64 BenQ BL3200PT 
MonitorKeyboardPowerCase
Acer H276HL Logitech G19 [Corsair] HX 850 [NZXT] Phantom 630 
MouseAudio
Logitech G502 Sony MHci99 
  hide details  
Reply
My Pride and Joy
(22 items)
 
  
CPUMotherboardGraphicsGraphics
[Intel] i7-3770k @ 4.8 GHz (Delid) [ASUS] P8Z77 WS [Sapphire] R9 290 Vapor-X [Sapphire] R9 290 Vapor-X 
RAMHard DriveHard DriveHard Drive
[Team Group] 16GB @ 2133 [Samsung] 850 Pro 256 GB [Samsung] 840 Evo 120 GB [Western Digital] Caviar Blue 1TB 
Hard DriveHard DriveHard DriveHard Drive
[Seagate] Barracuda 1TB [Seagate] Barracuda 500GB [Toshiba] 2TB [Kingston] SSDnow V300 60gb 
Optical DriveCoolingOSMonitor
Asus drive Custom Loop ;D [Microsoft] Windows 8.1 Pro x64 BenQ BL3200PT 
MonitorKeyboardPowerCase
Acer H276HL Logitech G19 [Corsair] HX 850 [NZXT] Phantom 630 
MouseAudio
Logitech G502 Sony MHci99 
  hide details  
Reply
post #4 of 9
Thread Starter 
Woot, I'm moving up! I finally was able to see the other BSOD message that only briefly flashed, and not as often as the process died one.

It looked like it said INASSCESSIBLE_BOOT_DEVICE. Also, now I get this at boot lol



EDIT: That's taken care of, I forgot to set my SATA controller back to RAID. Ooops.. lol

So now I'm back at the critical process stuff at boot, and I was able to grab the log file this time

The log location was: C:\Windows\System32\LogFiles\Srt\SrtTrail.txt
Warning: Spoiler! (Click to show)
Startup Repair diagnosis and repair log
Last successful boot time: ‎1/‎6/‎2014 5:18:07 AM (GMT)
Number of repair attempts: 15

Session details
System Disk = \Device\Harddisk0
Windows directory = C:\Windows
AutoChk Run = 0
Number of root causes = 1

Test Performed:
Name: Check for updates
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
Name: System disk test
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
Name: Disk failure diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 31 ms

Test Performed:
Name: Disk metadata test
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
Name: Target OS test
Result: Completed successfully. Error code = 0x0
Time taken = 312 ms

Test Performed:
Name: Volume content check
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
Name: Boot manager diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 47 ms

Test Performed:
Name: System boot log diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
Name: Event log diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
Name: Internal state check
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
Name: Boot status test
Result: Completed successfully. Error code = 0x0
Time taken = 31 ms

Test Performed:
Name: Setup state check
Result: Completed successfully. Error code = 0x0
Time taken = 94 ms

Test Performed:
Name: Registry hives test
Result: Completed successfully. Error code = 0x0
Time taken = 656 ms

Test Performed:
Name: Windows boot log diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
Name: Bugcheck analysis
Result: Completed successfully. Error code = 0x0
Time taken = 125 ms

Test Performed:
Name: Access control test
Result: Completed successfully. Error code = 0x0
Time taken = 3204 ms

Test Performed:
Name: File system test (chkdsk)
Result: Completed successfully. Error code = 0x0
Time taken = 30484 ms

Test Performed:
Name: Software installation log diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Root cause found:
A recent driver installation or upgrade may be preventing the system from starting.

Repair action: System files integrity check and repair
Result: Failed. Error code = 0x4005
Time taken = 1593 ms



Session details
System Disk = \Device\Harddisk0
Windows directory = C:\Windows
AutoChk Run = 0
Number of root causes = 1

Test Performed:
Name: Check for updates
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
Name: System disk test
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
Name: Disk failure diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 32 ms

Test Performed:
Name: Disk metadata test
Result: Completed successfully. Error code = 0x0
Time taken = 31 ms

Test Performed:
Name: Target OS test
Result: Completed successfully. Error code = 0x0
Time taken = 281 ms

Test Performed:
Name: Volume content check
Result: Completed successfully. Error code = 0x0
Time taken = 313 ms

Test Performed:
Name: Boot manager diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
Name: System boot log diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
Name: Event log diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 31 ms

Test Performed:
Name: Internal state check
Result: Completed successfully. Error code = 0x0
Time taken = 31 ms

Root cause found:
Startup Repair has tried several times but still cannot determine the cause of the problem.


Session details
System Disk = \Device\Harddisk0
Windows directory = C:\Windows
AutoChk Run = 0
Number of root causes = 1

Test Performed:
Name: Check for updates
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
Name: System disk test
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
Name: Disk failure diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 32 ms

Test Performed:
Name: Disk metadata test
Result: Completed successfully. Error code = 0x0
Time taken = 31 ms

Test Performed:
Name: Target OS test
Result: Completed successfully. Error code = 0x0
Time taken = 281 ms

Test Performed:
Name: Volume content check
Result: Completed successfully. Error code = 0x0
Time taken = 297 ms

Test Performed:
Name: Boot manager diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
Name: System boot log diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 16 ms

Test Performed:
Name: Event log diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 31 ms

Test Performed:
Name: Internal state check
Result: Completed successfully. Error code = 0x0
Time taken = 31 ms

Root cause found:
Startup Repair has tried several times but still cannot determine the cause of the problem.



Didn't install any drivers recently, so...
Edited by Bl00dyMurd3r - 1/6/14 at 2:07pm
My Pride and Joy
(22 items)
 
  
CPUMotherboardGraphicsGraphics
[Intel] i7-3770k @ 4.8 GHz (Delid) [ASUS] P8Z77 WS [Sapphire] R9 290 Vapor-X [Sapphire] R9 290 Vapor-X 
RAMHard DriveHard DriveHard Drive
[Team Group] 16GB @ 2133 [Samsung] 850 Pro 256 GB [Samsung] 840 Evo 120 GB [Western Digital] Caviar Blue 1TB 
Hard DriveHard DriveHard DriveHard Drive
[Seagate] Barracuda 1TB [Seagate] Barracuda 500GB [Toshiba] 2TB [Kingston] SSDnow V300 60gb 
Optical DriveCoolingOSMonitor
Asus drive Custom Loop ;D [Microsoft] Windows 8.1 Pro x64 BenQ BL3200PT 
MonitorKeyboardPowerCase
Acer H276HL Logitech G19 [Corsair] HX 850 [NZXT] Phantom 630 
MouseAudio
Logitech G502 Sony MHci99 
  hide details  
Reply
My Pride and Joy
(22 items)
 
  
CPUMotherboardGraphicsGraphics
[Intel] i7-3770k @ 4.8 GHz (Delid) [ASUS] P8Z77 WS [Sapphire] R9 290 Vapor-X [Sapphire] R9 290 Vapor-X 
RAMHard DriveHard DriveHard Drive
[Team Group] 16GB @ 2133 [Samsung] 850 Pro 256 GB [Samsung] 840 Evo 120 GB [Western Digital] Caviar Blue 1TB 
Hard DriveHard DriveHard DriveHard Drive
[Seagate] Barracuda 1TB [Seagate] Barracuda 500GB [Toshiba] 2TB [Kingston] SSDnow V300 60gb 
Optical DriveCoolingOSMonitor
Asus drive Custom Loop ;D [Microsoft] Windows 8.1 Pro x64 BenQ BL3200PT 
MonitorKeyboardPowerCase
Acer H276HL Logitech G19 [Corsair] HX 850 [NZXT] Phantom 630 
MouseAudio
Logitech G502 Sony MHci99 
  hide details  
Reply
post #5 of 9
Thread Starter 
Alrighty, so after playing with a bunch of bootsect and bootrec commands, critical process died is gone, and now windows boots to a brief INACCESSIBLE_BOOT_DEVICE blue screen, followed by this:



Remind me to never sleep Windows 8.1 again....
My Pride and Joy
(22 items)
 
  
CPUMotherboardGraphicsGraphics
[Intel] i7-3770k @ 4.8 GHz (Delid) [ASUS] P8Z77 WS [Sapphire] R9 290 Vapor-X [Sapphire] R9 290 Vapor-X 
RAMHard DriveHard DriveHard Drive
[Team Group] 16GB @ 2133 [Samsung] 850 Pro 256 GB [Samsung] 840 Evo 120 GB [Western Digital] Caviar Blue 1TB 
Hard DriveHard DriveHard DriveHard Drive
[Seagate] Barracuda 1TB [Seagate] Barracuda 500GB [Toshiba] 2TB [Kingston] SSDnow V300 60gb 
Optical DriveCoolingOSMonitor
Asus drive Custom Loop ;D [Microsoft] Windows 8.1 Pro x64 BenQ BL3200PT 
MonitorKeyboardPowerCase
Acer H276HL Logitech G19 [Corsair] HX 850 [NZXT] Phantom 630 
MouseAudio
Logitech G502 Sony MHci99 
  hide details  
Reply
My Pride and Joy
(22 items)
 
  
CPUMotherboardGraphicsGraphics
[Intel] i7-3770k @ 4.8 GHz (Delid) [ASUS] P8Z77 WS [Sapphire] R9 290 Vapor-X [Sapphire] R9 290 Vapor-X 
RAMHard DriveHard DriveHard Drive
[Team Group] 16GB @ 2133 [Samsung] 850 Pro 256 GB [Samsung] 840 Evo 120 GB [Western Digital] Caviar Blue 1TB 
Hard DriveHard DriveHard DriveHard Drive
[Seagate] Barracuda 1TB [Seagate] Barracuda 500GB [Toshiba] 2TB [Kingston] SSDnow V300 60gb 
Optical DriveCoolingOSMonitor
Asus drive Custom Loop ;D [Microsoft] Windows 8.1 Pro x64 BenQ BL3200PT 
MonitorKeyboardPowerCase
Acer H276HL Logitech G19 [Corsair] HX 850 [NZXT] Phantom 630 
MouseAudio
Logitech G502 Sony MHci99 
  hide details  
Reply
post #6 of 9

Moved to the Crash Analysis and Debugging section.

post #7 of 9
how was the solution..been a few months... what did you do? switch back to win 7 or reinstalled win 8.1?

I have the problem on two notebooks after a MS update... so I feel MS is hijaacking our hardware to stop them from boot up...non of the options in the recovery process(via auto repair to using a usb recovery stick) didn't work for me... so i am going back win 7.. I think more and more win8.1 users will run into this... I don't know if its just x86 related because x64 didn't have that problem ever.
post #8 of 9
Thread Starter 
Quote:
Originally Posted by cmiuc View Post

how was the solution..been a few months... what did you do? switch back to win 7 or reinstalled win 8.1?

I have the problem on two notebooks after a MS update... so I feel MS is hijaacking our hardware to stop them from boot up...non of the options in the recovery process(via auto repair to using a usb recovery stick) didn't work for me... so i am going back win 7.. I think more and more win8.1 users will run into this... I don't know if its just x86 related because x64 didn't have that problem ever.

I never ended up figuring it out.. One boot failure lead to a new one, so I ended up reinstalling WIndows
My Pride and Joy
(22 items)
 
  
CPUMotherboardGraphicsGraphics
[Intel] i7-3770k @ 4.8 GHz (Delid) [ASUS] P8Z77 WS [Sapphire] R9 290 Vapor-X [Sapphire] R9 290 Vapor-X 
RAMHard DriveHard DriveHard Drive
[Team Group] 16GB @ 2133 [Samsung] 850 Pro 256 GB [Samsung] 840 Evo 120 GB [Western Digital] Caviar Blue 1TB 
Hard DriveHard DriveHard DriveHard Drive
[Seagate] Barracuda 1TB [Seagate] Barracuda 500GB [Toshiba] 2TB [Kingston] SSDnow V300 60gb 
Optical DriveCoolingOSMonitor
Asus drive Custom Loop ;D [Microsoft] Windows 8.1 Pro x64 BenQ BL3200PT 
MonitorKeyboardPowerCase
Acer H276HL Logitech G19 [Corsair] HX 850 [NZXT] Phantom 630 
MouseAudio
Logitech G502 Sony MHci99 
  hide details  
Reply
My Pride and Joy
(22 items)
 
  
CPUMotherboardGraphicsGraphics
[Intel] i7-3770k @ 4.8 GHz (Delid) [ASUS] P8Z77 WS [Sapphire] R9 290 Vapor-X [Sapphire] R9 290 Vapor-X 
RAMHard DriveHard DriveHard Drive
[Team Group] 16GB @ 2133 [Samsung] 850 Pro 256 GB [Samsung] 840 Evo 120 GB [Western Digital] Caviar Blue 1TB 
Hard DriveHard DriveHard DriveHard Drive
[Seagate] Barracuda 1TB [Seagate] Barracuda 500GB [Toshiba] 2TB [Kingston] SSDnow V300 60gb 
Optical DriveCoolingOSMonitor
Asus drive Custom Loop ;D [Microsoft] Windows 8.1 Pro x64 BenQ BL3200PT 
MonitorKeyboardPowerCase
Acer H276HL Logitech G19 [Corsair] HX 850 [NZXT] Phantom 630 
MouseAudio
Logitech G502 Sony MHci99 
  hide details  
Reply
post #9 of 9
thank you for the update... I think it has other implications as to why having this problem.. i am sure someone will tell us soon... I also did the same thing..but did the smart choice reverted back to win7

Thanks Bud.. have a great day!
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Crash Analysis and Debugging
Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › Crash Analysis and Debugging › Windows 8.1 Won't boot - CRITICAL_PROCESS_DIED - 0x000000ef