Error code: 0xc000000d BCD BSOD after Power Outage during booting up

samplenhold · 11 Sep 2018

I received the error 0xc000000d when trying to enter windows after my boot sequence was interrupted by a power outage. Searching this error lead me to this forum.

I tried to use a Windows 10 USB created with the Media Creation Tool to do a Startup Repair, but that was unsuccessful.

I tried to use your dm log collector, but got the message that it is not compatible with my version of windows. Then tried to use the beta, but was not successful in getting the link to work. Had loaded those to a USB and tried running them in the cmd window.

Using the Windows 10 USB, I can get a cmd window up. I tried running bootrec /fixboot, bootrec /fixmbr, and bootrec /rebuildbcd but did not help.

This is a machine I built a few years ago and has Windows 10 upgraded from a Windows 7 install, so I do not have a Windows 10 key.

The C-drive is an SSD - Samsung 840 PRO 256GB that is used for the OS and apps mostly. I have two WD 2 TB drives in raid for data.

If you can help me repair this, that would be great. Otherwise I suspect I will have to purchase a new Win 10 Pro to do a restore and also loose all of my apps, correct?

Thanks
Bob

dalchina · 11 Sep 2018

Otherwise I suspect I will have to purchase a new Win 10 Pro to do a restore

Hi, welcome to tenforums. This question has been asked many times- once Win 10 has been activated on a PC you can clean install as many times as you wish and even change your disk. Your activation is tied to one form of your hardware id and registered on MS's activation servers.

For interest e.g.
Windows 10 activations may be tied to your Microsoft Account, to validate Windows after a clean install
Windows 10 | Digital License can now be tied to your Microsoft Account | IT Pro

I'd suggest you first check your disk integrity after such an event- as you can't boot, you could use a live boot disk such as Kyhi's available from the top of the Software and Apps section here.

HD Tune is available on that- Health (SMART params) and Error Scan tabs.

Then run chkdsk on your system disk to check for and repair any inconsistencies.

Then you can try running Macrium reflect (also available on that disk), and use its Fixboot utility.

samplenhold · 11 Sep 2018

HD Tune found no issues.
chkdsk found no issues.

Macrium Reflect Fix Boot did not work. It seems that my SSD now has 3 partitions, C, L, and M. Selecting C as the partition it should boot from ran, but I never get a check next to 'Updating Master Boot Record'. Yet all of the other steps show a check mark and the app completes and requests a restart.

Upon restart I now get a black screen of death with error code 0xc000000f and it boot loops.

Another interesting note is that on POST, my SSD now shows status of 'Unconfigured', yet I can see it fine once I go back into the Win 10 rescue USB.

Please help.

Bob

dalchina · 12 Sep 2018

Hi, can you post a screenshot or similar of Minitool Partition Wizard (on Kyhi's disk) showing your SSD partitions, expanding columns as necessary to show all text?

It seems you were not expecting so many partitions- if you examine their content, what do they seem to be?

Post any screenshots of interest.

Have you been using disk images? Do you have one you could restore? (Routine disk imaging is often and strongly recommended here).

The unconfigured status is significant- hopefully someone here who's experienced this will comment. There are some unclear refs. on the internet.

It seems your SSD was not part of your RAID configuration, but perhaps somehow is now confused with it as the 'unconfigured' designation seems to apply to RAID. However, this is just my impression from looking around.

Perhaps that is also linked to the appearance of additional (data?) partitions on it.

Caledon Ken · 12 Sep 2018

If you are using RAID the unconfigured designation just means it is not part of a Raid.

Your data drives are the raid, likely Raid 1.

My Windows 7 machine boots I see my raid drives as configured and all other drives as unconfigured.

dalchina's request for SSD Disk Management shot is next piece to puzzle.

samplenhold · 12 Sep 2018

Thank you Ken.
Dalchina:
Attached as requested MiniTool.jpg.
Some additional background:
This happened Saturday (BSOD.jpg). After searching the web, came across a post that got me to make a Windows 10 USB created with the Media Creation Tool to do a Startup Repair. That failed stating it "...could not repair your PC". Learned that I could open up notepad from the cmd window. Found the Setup Repair logs. The only part that was interesting was the final entry in the SrtTrail.txt file (Startup Repair.jpg).

Finally found this forum and have been trying to work it out, thank you.

Answers to other questions:

No, I was not expecting 3 partitions on the SSD. I originally configured it as the "C" drive. I have only used this for the OS and apps. Very little data, if any, except what Windows places under Users/ID, like docs and such. I noticed these two extra partitions after trying the Startup Repair. As far as content, I have included pics C-drive.jpg, L-drive.jpg and M-drive.jpg.

No disk images. My bad. Will now do in the future though.

The SSD was not part of a RAID.

As I really had no experience in this process, I tried the FixBoot on the L drive, C drive, and M drive in that order (the L drive was checked when I opened up the app). After trying the FixBoot and then attempting to boot normally is when I got the Black screen of death (Black-SOD.jpg). I have included two pics to show how those were run (Fixboot1.jpg and Fixboot2.jpg)

Bob

PS see there is max of 5 attachments. Will ad the others in a separate post.

samplenhold · 12 Sep 2018

Additional attachments as requested.
My first reply is waiting for a moderator. Not sure why this one went straight to the thread.

dalchina · 12 Sep 2018

Hi, first, your configuration is seems to be MBR, not UEFI from the partitions present. Please confirm that's what you expected. (Legacy BIOS).

BIOS/MBR-based hard drive partitions | Microsoft Docs

There are 3 partitions, the first being the System partition, the second, Windows, the third, perhaps Recovery.
The first and third should not have drive letters.
These contain EFI folders, which surprises me.

My personal approach would be to create a disk image of your Windows partition (saved to external storage), wipe your SSD, clean install Win 10, making sure the Windows partition is large enough, make sure that boots ok, then restore the image of your existing Windows partition in its place.

Reboot, and either automatic repair will sort that out, or you can run startup repair.

Others may well have other approaches.

Note that the act of imaging your Windows partition also helps to verify its integrity.

HD Tune: the significant tabs are Health (SMART params) and Error Scan, rather than Info.

Do you know the approximate build of your Win 10?
(You can find that from the properties, details of any system file such as explorer.exe)

samplenhold · 12 Sep 2018

I really do appreciate your time and how quickly you have responded. Thank you.

I was not expecting MBR. My BIOS seems to be UEFI (see Bios1.jpg, Bios2.jpg) as per the BIOS interface. Also it is called UEFI in the system information window generated by msinfo32.exe (Sys Info.jpg). Accourding to that window, the OS version is 10.0.17134 build 17134. Hmm, I ran msinfo32.exe that I found on my C-drive, but now I wonder if it is reporting the version that is running from the USB recovery from Kyhi? I have found some dll's on the C-drive in Windows folders with File Version and Product Version of 4.13.17134.228 so maybe that OS version is correct.

I had run the HD Error and the HD Health and include here (HD Error Scan.jpg and HD Health.jpg).

So when you say to "...create a disk image of your Windows partition (saved to external storage)" is that just doing a simple copy command to a USB, or is there an app that creates a disk image on the USB?

Then the "restore the image" part, again a simple copy to replace or is this an app that does this? Will that preserve the apps I have purchased and downloaded?

Thanks again for your help.
Bob

dalchina · 12 Sep 2018

Hi, Good your disk looks ok.

UEFI would normally (by default) have 4 partitions.

However I also note an EFI folder in your windows partition - which I don't have in mine (which is UEFI).

Further, note:

Drive Partition Rules

When you deploy Windows to a UEFI-based device, you must format the hard drive that includes the Windows partition by using a GUID partition table (GPT) file system. Additional drives may use either the GPT or the master boot record (MBR) file format.

UEFI/GPT-based hard drive partitions | Microsoft Docs

Your partitions are NTFS, not GPT format.

Notes on BIOS and UEFI /CSM for interest:
Boot to UEFI Mode or Legacy BIOS mode | Microsoft Docs
Windows Setup: Installing using the MBR or GPT partition style | Microsoft Docs

1. Disk imaging: the first step - and highly recommended before undertaking any fix actions:
a. Boot from Kyhi's boot disk
b. Plug in a large USB disk - say 60% of the size of your Windows partition absolute min.
c. Run Macrium Reflect on Kyhi's disk.
d. Use that to create a disk image of your Windows partition, written to your USB disk.
You can choose to verify the image as well.

2. Do you have a Win 10 1803 build bootable installation medium?
If not you will need one to clean install Win 10. This should be the same base language, just in case that causes a a problem. You can create one on another PC using the Microsoft Media Creation Tool.

3. Clean install Windows using that. This will mean deleting the existing partitions.
Make sure your SSD is configured to use AHCI rather than IDE.
Clean Install Windows 10 | Windows 10 Tutorials

Now note your present file system is NTFS, so you will need to choose that. It's possible to convert from NTFS to GPT but this adds a stage of complexity I've not been through.

If you can get your PC running using MBR/NTFS, you could then consider converting to UEFI/GPT if you wished.

4. Check that boots ok.

5. Boot from Kyhi's disk

6. Run Macrium R and restore the disk image you created earlier.