Windows 10: CRITICAL_PROCESS_DIED and cant read boot device on startup

Discus and support CRITICAL_PROCESS_DIED and cant read boot device on startup in Windows 10 BSOD Crashes and Debugging to solve the problem; Attachment 79960 Attachment 79961 Discussion in 'Windows 10 BSOD Crashes and Debugging' started by cowlicker12, May 6, 2016.

  1. CRITICAL_PROCESS_DIED and cant read boot device on startup


    Attachment 79960

    Attachment 79961
     
    cowlicker12, May 14, 2016
    #16
  2. axe0 New Member

    I assume the long generic is still going on?
     
  3. Attachment 80065

    So this failed pretty quickly...
     
    cowlicker12, May 15, 2016
    #18
  4. CRITICAL_PROCESS_DIED and cant read boot device on startup

    Just started the HD Tune, gonna leave it running overnight. Here is a screenshot of the Health tab just moments after starting the full scan.

    Attachment 80066
     
    cowlicker12, May 15, 2016
    #19
  5. axe0 New Member
    That 'failure' isn't a failure that may require a hard drive replacement, more an indication that you should check the airflow+ temperatures
     
  6. So....I walked away from my laptop after running the HD tune and came back literally like one minute later and it BSOD'd. Re-run it and hope it works or try something else?

    Details of the BSOD: Same error message and the percentage when "collecting information" never made it past 0% (like last time).
     
    cowlicker12, May 16, 2016
    #21
  7. axe0 New Member
    Seems the last time I posted SeaTools pic didn't load.
    You need to replace your hard drive a.s.ap. and backup your stuff.
     
  8. CRITICAL_PROCESS_DIED and cant read boot device on startup

    Is that possible with my Alienware model?? I don't think it is...
     
    cowlicker12, May 16, 2016
    #23
  9. axe0 New Member
    SeaTools is giving a failure with the long generic test, clearly indicative of a failing hard drive.
    If you think I'm wrong, no problem for me but you'll make it only difficult for yourself.

    Failing hardware is always possible, though within the first period of time it is called faulty. Yes it is possible with every manufacturer.

    EDIT: do you mean replacement? I'm not very healthy ATM I'm feeling a little bit sick so excuse me if I've misread your post *Redface
     
  10. Oh lol, I meant replacement! Sorry, I should have been more clear. Hope you feel better soon *Smile
     
    cowlicker12, May 16, 2016
    #25
  11. axe0 New Member
    If you have warranty, use it to replace the hard drive.
    If you have no warranty, search for a proper video to replace the hard drive (assuming you're not 100% sure about what to do) and do it yourself.
     
  12. Ok sounds good. Should I mark this as solved then or should I wait until after I test out the new hard drive?
     
    cowlicker12, May 16, 2016
    #27
  13. axe0 New Member

    CRITICAL_PROCESS_DIED and cant read boot device on startup

    I let that choice up to you *Smile
     
  14. Ok so I'm installing Windows 10 onto a brand new hard drive as we speak. Then I'm going to transfer over any files from the old hard drive to the new one (my laptop has 2 HDD slots). Question - could I simply format the broken hard drive and then reinstall Windows on it in order to keep using it?
     
    cowlicker12, May 19, 2016
    #29
  15. Another question/problem: I installed the new hard drive and used the Windows 10 Media Creation Tool to put windows 10 onto a USB drive and then installed Windows 10 on the new hard drive's primary partition.

    I finished the installation and then upon starting it asked me to choose which volume I wanted to boot on a blue screen. The options were "Windows 10 volume 7" and "Windows 10 volume 3". Remembering from the screen where I had to choose which partition I wanted to install on, I naturally picked volume 7 because partitions 1-5 were for the original hard drive and partitions 6-10 (don't remember the exact amount) were for the 2nd hard drive.

    So then it finished installing and restarted one more time and on the blue screen with the two options above, the "Windows 10 volume 7" option was now simply "Windows 10" and the other option remained the same with "Windows 10 volume 3". Naturally, I picked the default (first option).


    Here is the strange part: All of my stuff is here! My files, my desktop background, my programs, everything is here. But I think this indicates that the 2nd hard drive is not working. Also, when I put in my PIN to login to Windows, the login was very slow - almost as slow as when I was having problems with the broken hard drive.

    I thought this was pretty strange, so I restarted and went to the BIOS. From there, I selected to boot from the 2nd hard drive. It gave me this screen:

    Attachment 80684

    So I restarted and this time I didn't use the BIOS to select the BOOT, I only waited until it gave me the blue screen with the 2 "Windows 10" options. I selected the first option, "Windows 10".

    Here is what appears after getting to the desktop and opening up File Explorer:

    Attachment 80683

    OS (CCRITICAL_PROCESS_DIED and cant read boot device on startup :) has a size of 640 GB, which corresponds to the broken hard drive.
    Local Disk (FCRITICAL_PROCESS_DIED and cant read boot device on startup :) has a size of 390 GB, which corresponds to the new hard drive.

    I'm really confused as to why this is happening. Could you help me out? Or would you like me to post this in a different section of this forum instead? Your call.
     
    cowlicker12, May 19, 2016
    #30
Thema:

CRITICAL_PROCESS_DIED and cant read boot device on startup

Loading...
  1. CRITICAL_PROCESS_DIED and cant read boot device on startup - Similar Threads - CRITICAL_PROCESS_DIED cant read

  2. CRITICAL_PROCESS_DIED and SYSTEM_SERVICE_EXCEPTION blue screen on startup Need help reading...

    in Windows 10 Gaming
    CRITICAL_PROCESS_DIED and SYSTEM_SERVICE_EXCEPTION blue screen on startup Need help reading...: A little over a month ago I built a brand new pc and ever since the day I built it I've been getting blue screens. I don't think it has anything to do with windows as I've done a clean install twice and still the bsods persist. I'm pretty sure I've managed to narrow it down...
  3. CRITICAL_PROCESS_DIED and SYSTEM_SERVICE_EXCEPTION blue screen on startup Need help reading...

    in Windows 10 Software and Apps
    CRITICAL_PROCESS_DIED and SYSTEM_SERVICE_EXCEPTION blue screen on startup Need help reading...: A little over a month ago I built a brand new pc and ever since the day I built it I've been getting blue screens. I don't think it has anything to do with windows as I've done a clean install twice and still the bsods persist. I'm pretty sure I've managed to narrow it down...
  4. BSOD on boot (critical_process_died), cant boot into safe mode

    in Windows 10 Ask Insider
    BSOD on boot (critical_process_died), cant boot into safe mode: TL:DR: Can't boot (even into safe mode) after removing device 'Intel HD Graphics 4000' (and uninstalling its drivers). Getting critical_process_died BSOD. My specs: Mobo ASRock Z77 Pro4, CPU i5 3570k I had my integrated GPU (Intel HD Graphics 4000) disabled because it gave...
  5. CRITICAL_PROCESS_DIED Windows 10 Startup

    in Windows 10 Drivers and Hardware
    CRITICAL_PROCESS_DIED Windows 10 Startup: Recently I haven’t been able to get onto my PC at all. I first started getting this error message on startup: DRIVER_IQRL_NOT_LESS_OR_EQUAL But now I am getting this error message: CRITICAL_PROCESS_DIED I cannot boot in safe mode either as I get the same error...
  6. WIN10 Startup CRITICAL_PROCESS_DIED ntoskrnl.exe

    in Windows 10 BSOD Crashes and Debugging
    WIN10 Startup CRITICAL_PROCESS_DIED ntoskrnl.exe: Couple of days ago my laptop's OS stopped to loading. There is blue screen noticing CRITICAL_PROCESS_DIED. I didn't installed any soft or hardware for months - all systems worked well. Safe mode stills works. I've tried to restore system by DISM and sfc /scannow - that...
  7. BSOD Critical_process_died at startup

    in Windows 10 BSOD Crashes and Debugging
    BSOD Critical_process_died at startup: For several months now (update 1803?), I've experienced BSODs on a steady basis on my Alienware 17R3 running Windows10. At least 1 a day and up to 5 or 6, mostly during the first minutes after a restart or wake-up. Often even before I sign in. BSOD are of the...
  8. BSOD crash with CRITICAL_PROCESS_DIED cant boot or run sfc /scannow

    in Windows 10 BSOD Crashes and Debugging
    BSOD crash with CRITICAL_PROCESS_DIED cant boot or run sfc /scannow: not sure I can run dm log collector from recovery console? My desktop PC with 32-bit Windows 10 has crashed at version 10.0.17134.0. It worked fine for a few days after the upgrade to version 10.0.17134.0, and I was not using the PC at the time of the crash. It now starts up...
  9. Critical_process_died at startup

    in Windows 10 BSOD Crashes and Debugging
    Critical_process_died at startup: Several times since Windows 10 has been updated (see attached file) I have received a "Critical_process_died" notification. Sometimes at startup & at least one time during normal browsing. Have talked with a local computer shop about various problems & he suggested a clean...
  10. CRITICAL_PROCESS_DIED on boot

    in Windows 10 Support
    CRITICAL_PROCESS_DIED on boot: Hi. My mom's laptop is crashing on boot with a CRITICAL_PROCESS_DIED error. It boots in Safe Mode but most things are unresponsive: no windows menu, command prompt opens right away but admin prompt takes 10-20 minutes to open, so do task manager window, driver install...