Windows 10: BSOD CRITICAL_PROCESS_DIED w/error 0xc000000e on reboot

It is currently attached via eSATA to the subject machine. I do not have an eSATA port on any other machine. The best I can do is attached it via USB to a different machine. I will do that tomorrow and report back.

 

Good day Axe0, I have attached the docking station to my Surface Pro 3 (Win 10 Pro 64-bit) using USB. It appears to be working just fine. It is a dual-dock; I have two drives mounted, both operate normally in Windows; one of the drives is the infamous "Valiant" drive that created this thread. I need to reconnect the docking station to the original PC now--it is my main working PC.

Thanks.

Cheers!

 

The problem sounds like a faulty port/connection from your main PC.

 

It's an interesting theory and easily tested since I can swap the dock with my other eSATA drive (swap backpanel connectors) and see what that does. I can also connect the dock over USB and see what that does too. But I'm unclear on your reasoning. The system only fails to boot when that drive is not in the dock (error 0xc000000e), even though the dock is powered up and connected to the PC all the time (with or without a 2nd drive installed).

 

It was based on half of the problem, I forgot that it only happens when the drive is not in the dock.

I would like to get deeper into this part

What was/is on that HDD, an important thing would be knowing the partitioning *Arrow Disk Management - How to Post a Screenshot of - Windows 10 Forums
Another interesting thing to know would be the boot order when the dock is connected.

 

The "Valiant" drive (external) contains a backup of my C: drive prior to doing a clean install of Windows 10 some months ago. After the clean install, I used "Valiant" to recover a bunch of files. I loaded the registry hive from "Valiant" in order to dump out/reload the printer forms.** I unloaded the hive and had rebooted many times, but "Valiant" stayed in the dock for several months before I needed to pull it out to mount my project archive drives. That's when I noticed the system crashing.

I will post the partitioning scheme and boot order in the next message.

Cheers!

**I'm in the printing business and I had built up a large library of custom forms over several years that I did not want to re-key through the Print Server Properties dialog box.

 

The boot order is: CD-ROM, "Removable Device", HDD. Not sure what the "Removable Device" is (USB perhaps)? I have uploaded a screenshot of the BIOS.

I have also uploaded a screenshot of the Disk Management scheme.

Cheers!

 

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!

 

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!

 

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...)

 

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.