Windows 10: BSOD on Boot 0xc0000034

My first thought is that you do not have set your internal hard drive (with the installed OS) as the first boot device on the BIOS after the repair but your USB is still set as first boot.

 

Thank you for your prompt reply and help!
I have the problem whether the USB stick or the main hard drive (it's a Samsung SSD) is earlier than the other in the BIOS's Boot list, so I don't think that's it. Rather, I'm suspecting the problem is that my drive list in Disk Management does not show any drive whose Status is "Healthy (EFI System Partition)". I don't understand what that means, but I see my other computers have one. Here is a screen capture of my Disk Management screen:

 

Maybe you can use this tutorial to restore/repair your missing EFI system partition. Restore/Repair Deleted EFI Boot Partition in Windows 10/8/7 – EaseUS

 

Thank you lifetec, yes I am up for that!

However (because I've never done something like this and don't want to screw up),
I an unclear on this point: is my goal to convert that last drive list on my screen capture to go from being "Healthy (Recovery Partition)" to "Healthy (EFI System Partition)"? ...or is my goal to add another partition that will end up named "Healthy (EFI System Partition)"? Or something else?
And if I am creating another partition: does it matter where in the partition order it is? And where will the space needed for it come from (i.e. do I have to first make another partition smaller in order so that there is some space to give to the new partition)?

Thank you very much!

 

If you have a GPT partitioning, the goal is to have at least the following partitions
Healthy (Recovery Partition)
Healthy (EFI System Partition)
C:

If you have a MBR partitioning, the goal is to have at least the following partitions
Healthy (recovery)
C: (System, Active, Primary partition)

C: is the partition on which Windows is installed, the lettter may vary depending on what partition someone chooses to install, but this is the standard letter.

If you don't see the EFI system partition, it usually means that you have MBR partitioning. But since the picture of your disk management is gone I can't confirm this, because there are many situations where the partitioning is just messed up.

 

Thank you very much, Axe0. Your words are helping clarify this for me.

I'm somewhat confident I had an EFI partition before things went wrong, but I am not sure. How can I determine if I am GPT or MBR?

Here is the screen capture again of my Disk Management:

 

I still can't see it, try to directly upload it if possible How to upload files

 

Certainly... I have attached a screen capture, inline:


Attachment 121974

 

It looks like you have a MBR partitioning, so you don't have to worry about the EFI partition.

 

Thank you. I am still skeptical about it being MBR, because we have an identical machine with identical hardware and OS and it has a EFI Partition on its SSD. Is there a test I can do to confirm I am MBR vs EFI?

Also, I an unclear on this point: is my goal to convert that last drive list on my screen capture to go from being "Healthy (Recovery Partition)" to "Healthy (EFI System Partition)" (or the MBR equivalent)? ...or is my goal to add another partition that will end up named "Healthy (EFI System Partition)" (or the MBR equivalent)?

And if I am creating another partition: does it matter where in the partition order it is? And where will the space needed for it come from (i.e. do I have to first make one of the existing partitions smaller in order so that there is some space to give to the new partition)?

 

This is my partitioning, with GPT
Attachment 122127


For the goal, see my previous post, I edited the post a little to correct a few things with MBR partitioning. The recovery partition is an optional partition that I believe is created when the OS is being reinstalled (or upgraded).


I believe the order doesn't really matter. As an example, a few days ago I reinstalled my system completely because I found out that the EFI partition was installed on Disk 1 between the 2nd and the 3rd partition (Disk 1 was at the time Disk 0 because I accidentally switched the connections). The partitioning of Disk 1 was a chaos due to a previous Windows installation that I used for testing.

To create a new partition, you have to shrink a partition.

 

Hi axe0.
Thank you.
So, I used Disk Management to Shrink a partition to get a spare 1GB.
Then I tried to create a new EFI partition using diskpart's "create partition efi size=260" command.
But sadly this resulted in a long error message: "No usable free extent could be found..." even though I have 1GB available.
Is there a limit to how many partitions I am allowed to have?

 

Open an admin command prompt and enter following commands
Code: diskpart list disk[/quote] If you see a * below GPT, it means EFI partition should normally be present, then we'll go from there.

See below image for an example
Attachment 122325

 

Thank you.
Here is what I see when I do that:

==========
Microsoft DiskPart version 10.0.14393.0
Copyright (C) 1999-2013 Microsoft Corporation.
On computer: DAVIDMAIN
DISKPART> list disk
Disk ### Status Size Free Dyn Gpt
-------- ------------- ------- ------- --- ---
Disk 0 Online 931 GB 700 MB
Disk 1 Online 14 GB 0 B
Disk 2 Online 14 GB 7240 MB
Disk 3 Online 239 GB 0 B

================
... as you can see, there are no asterisks in the Gpt column.

Disk 0 is the drive that is my drive C:, that used to happily boot Windows 10, but no longer does so. Disk 2 is the USB stick that I currently must use to boot Windows.

Thank you,
David

If you see a * below GPT, it means EFI partition should normally be present, then we'll go from there.

See below image for an example
Attachment 122325[/quote]

 

Download an ISO from this post, mount the ISO on a USB and boot from the USB. When booted, open Macrium and use the 'fix boot problems' option.