BSOD CRITICAL_PROCESS_DIED w/error 0xc000000e on reboot

I rebooted the original computer and confirmed the 0xc000000e error when the HD is not attached

So this crash does not only occur when the HDD is connected?

axe0 said:

So this crash does not only occur when the HDD is connected?

The crash never occurs when the HDD is connected. It only occurs when the HDD is NOT connected. The system runs normally (I use it everyday as my graphic arts workstation) as long as that HDD is attached to that docking station. As soon as I pop the HDD out of the dock, the system will crash. The usual crash error is CRITICAL_PROCESS_DIED, however today the error was KERNEL_DATA_INPAGE_ERROR. And when the system reboots without that HDD attached, I get the 0xc000000e error. I can then plug the HDD back into the dock, reboot and the system runs find again.

Could you use the dock on a different system please and see if the same problem occurs.

axe0 said:

Could you use the dock on a different system please and see if the same problem occurs.

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.

axe0 said:

Could you use the dock on a different system please and see if the same problem occurs.

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.

axe0 said:

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

I believe this relates to having loaded a registry hive from that external HD some months ago

What was/is on that HDD, an important thing would be knowing the partitioning 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.

axe0 said:

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 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!