BSOD CRITICAL_PROCESS_DIED w/error 0xc000000e on reboot

Page 3 of 6 FirstFirst 12345 ... LastLast

  1. Posts : 14,901
    Windows 10 Pro
       #21

    Please change the boot order so your boot drive is the first option, set the CD-ROM as second boot option.
      My Computers


  2. Posts : 32
    Windows 10 64-bit Home
    Thread Starter
       #22

    axe0 said:
    Please change the boot order so your boot drive is the first option, set the CD-ROM as second boot option.
    Good morning Axe0. I changed the boot order to 1)HDD, 2)CD-ROM, 3)[Disabled]. It didn't change anything. With the "Valiant" drive in the dock, Windows boots OK. With the Valiant drive out of the dock, or the dock turned off, Windows throws error 0xc00000e while booting. Windows doesn't even display the small cyan "Windows" logo...it goes straight from the BIOS banner screen to the BSOD.

    Switching the order of the eSATA drives on the adapter also does not change anything--it still crashes if that Valiant drive is missing and runs OK if Valiant is connected.

    NOTE: Connecting Valiant through a SATA/USB adapter doesn't work--the drive isn't recognized before Windows starts to load at which point it throws the 0xc000000e BSOD.

    There is a LOT of activity on this Valiant drive both when Windows is starting and when shutting down. There is some file on that drive that my running Windows configuration references and it is trying to be accessed by winload.exe early in the startup phase. Is there any clue in the Registry or the dumps as to what this file is?

    Is there some sort of boot logging/tracing that can be enabled?

    Thanks.

    Cheers!
      My Computer


  3. Posts : 14,901
    Windows 10 Pro
       #23

    The zips you uploaded do not contain dumps.

    Winload.exe reads the HKLM/SYSTEM hive, ntoskrnl.exe and boot device drivers into the physical memory near the start of the boot process before virtual memory paging is enabled.

    Please format the recovery partition on the Valiant drive
      My Computers


  4. Posts : 32
    Windows 10 64-bit Home
    Thread Starter
       #24

    axe0 said:
    The zips you uploaded do not contain dumps.


    Winload.exe reads the HKLM/SYSTEM hive, ntoskrnl.exe and boot device drivers into the physical memory near the start of the boot process before virtual memory paging is enabled.


    Please format the recovery partition on the Valiant drive

    OK, will do but I will need instructions for doing it as Disk Management provides no options to operate on any of the recovery partitions.

    Thanks.

    Cheers!
      My Computer


  5. Posts : 14,901
    Windows 10 Pro
       #25

    How to delete a volume:
    In an admin command prompt enter following commands
    diskpart
    list volume
    delete volume {volume number}
    Attachment 85256
      My Computers


  6. Posts : 32
    Windows 10 64-bit Home
    Thread Starter
       #26

    axe0 said:
    How to delete a volume:
    In an admin command prompt enter following commands
    diskpart
    list volume
    delete volume {volume number}
    Attachment 85256
    Hmmm, here's what I get....
    Attachment 85262

    The "delete volume 13" command throws an error. If I first say:
    select volume 13
    delete volume

    then diskpart crashes. (Diskpart has stopped working... Windows is looking for a solution...)
      My Computer


  7. Posts : 14,901
    Windows 10 Pro
       #27

    Another option is to use Windows installer, delete the partition before installing and then abort the setup.
      My Computers


  8. Posts : 32
    Windows 10 64-bit Home
    Thread Starter
       #28

    axe0 said:
    Another option is to use Windows installer, delete the partition before installing and then abort the setup.
    OK, I'll try that. Sorry for the delay--busy week.
      My Computer


  9. Posts : 32
    Windows 10 64-bit Home
    Thread Starter
       #29

    axe0 said:
    Another option is to use Windows installer, delete the partition before installing and then abort the setup.
    OK, the recovery partition on Valiant has been deleted; now it shows as unallocated space in Disk Management. Windows still throws 0xc000000e if I boot without Valiant connected.
      My Computer


  10. Posts : 14,901
    Windows 10 Pro
       #30

    Do you have this hive that you loaded in the registry?
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 02:00.
Find Us




Windows 10 Forums