Win 10 Boot Manager / Loader Help

[damnfinecoffee]

Hi guys, I really need your help!

In an attempt to fix a BSOD issue I think I’ve screwed something up.

 

I have two M.2’s one is my OS (500gb) the other a scratch disk (1TB). I can’t boot into the OS (Win 10 Pro) due to a continuous cycle of BSOD’s, but I have a feeling it’s trying to boot from the wrong location.
 

Can anyone take a look at this and tell me if I’m right in thinking that ‘device’ under both Boot Manager and Boot Loader should be set to ‘partition=D:’ and if so do you know how to change it?

 

When I list volumes my OS is showing as D and my scratch as C (Even though they are C and S in Windows).

 

thanks in advance!

[Jimkirk363]

Reinstall windows over the top of current installation and see what happens?

[C2dan88]

Or delete the existing efi boot partition and create a new one

https://www.tenforums.com/installation-upgrade/52837-moving-recreating-efi-partition.html#post698505

[damnfinecoffee]

47 minutes ago, C2dan88 said:

Or delete the existing efi boot partition and create a new one

https://www.tenforums.com/installation-upgrade/52837-moving-recreating-efi-partition.html#post698505

Thanks, I did stumble across this one but to be honest I was a little confused by it.
 

Based on my disk setup attached do you know what the commands to delete the existing EFI partition and create a new would be exactly? 
 

[C2dan88]

I would guess Volume3 is the efi partition. You may find volume3 is actually on disk0, not disk1

 

To confirm run

select disk 0
list partition

If that shows a 100MB partition, then it is on your scratch disk. You can delete that partition. Now just follow the guide I linked to create a new 100mb efi partition on your OS drive (disk1).

[damnfinecoffee]

1 hour ago, C2dan88 said:

I would guess Volume3 is the efi partition. You may find volume3 is actually on disk0, not disk1

 

To confirm run

select disk 0
list partition

If that shows a 100MB partition, then it is on your scratch disk. You can delete that partition. Now just follow the guide I linked to create a new 100mb efi partition on your OS drive (disk1).

Thank you, much appreciated.

 

 

[damnfinecoffee]

1 hour ago, C2dan88 said:

I would guess Volume3 is the efi partition. You may find volume3 is actually on disk0, not disk1

 

To confirm run

select disk 0
list partition

If that shows a 100MB partition, then it is on your scratch disk. You can delete that partition. Now just follow the guide I linked to create a new 100mb efi partition on your OS drive (disk1).

And I can confirm your suspicion was correct:

 

so this is where I got up to:

 

I then exited and double checked in the BIOS that the correct drive was listed as boot. All looked OK!

 

Then I booted as normal. 
BSOD with CRITICAL_PROCESS_DIED

It then rebooted and it gave me this screen:

 

I hit F1 to be then shown this screen:

 

I then booted from the Win 10 DVD and ran startup recovery, which resulted in this:

 

so.. I’m kinda back where I started and not sure what to try now. Any advice would be massively appreciated here.

 

I did try this but some posts seem to suggest this is no longer relevant!?:

 

I also tried this method of assigning a letter to the boot partition and attempting fixboot there but this resulted in the same access denied error. Let me know if I’m being led down the wrong path here..

 

[damnfinecoffee]

Not sure if this is helpful but I assigned R to the EFI partition and had a look inside, it appears to be empty. Would this suggest the needed boot files are not present?

 

 

[damnfinecoffee]

I also noticed that the ‘required’ status is set to ‘No’ ..from what I’ve read elsewhere this should say yes. Any advice guys?

 

 

[C2dan88]

Trying to list/view contents of system protect partitions will always result in 0 files being listed, noway around this while in the windows recovery enviroment

11 minutes ago, damnfinecoffee said:

I also noticed that the ‘required’ status is set to ‘No’ ..from what I’ve read elsewhere this should say yes. Any advice guys?

Mine is set to no and my system boots fine.

 

Not sure whats going on. Recreating the efi boot partition should help resolve it.

 

Only thing I can suggest is to delete the efi partition again with only your c drive connected and recreate the efi boot partition

select disk 0
select partition 3 <--- verify this is the efi partition first!!!!
delete partition
create partition efi size=100
format quick fs=fat32
assign letter=s
bcdboot C:\Windows /s S:

 

 

[damnfinecoffee]

17 minutes ago, C2dan88 said:

Trying to list/view contents of system protect partitions will always result in 0 files being listed, noway around this while in the windows recovery enviroment

Mine is set to no and my system boots fine.

 

Not sure whats going on. Recreating the efi boot partition should help resolve it.

 

Only thing I can suggest is to delete the efi partition again with only your c drive connected and recreate the efi boot partition

select disk 0
select partition 3 <--- verify this is the efi partition first!!!!
delete partition
create partition efi size=100
format quick fs=fat32
assign letter=s
bcdboot C:\Windows /s S:

 

 

Thanks Dan, really appreciate the prompt responses.

 

I’ll try this now.

[damnfinecoffee]

21 minutes ago, C2dan88 said:

Trying to list/view contents of system protect partitions will always result in 0 files being listed, noway around this while in the windows recovery enviroment

Mine is set to no and my system boots fine.

 

Not sure whats going on. Recreating the efi boot partition should help resolve it.

 

Only thing I can suggest is to delete the efi partition again with only your c drive connected and recreate the efi boot partition

select disk 0
select partition 3 <--- verify this is the efi partition first!!!!
delete partition
create partition efi size=100
format quick fs=fat32
assign letter=s
bcdboot C:\Windows /s S:

 

 

Should I change C:\Windows to D:\Windows as it seems to be assigned D here? Although it is C:\ when actually booted into win..

[C2dan88]

Yes, use d if that is what diskpart shows

[damnfinecoffee]

2 minutes ago, C2dan88 said:

Yes, use d if that is what diskpart shows

Seemed to go ok until that last command:

 

 

[damnfinecoffee]

My bad, didn’t exit diskpart.

 

so now I’ve got ‘boot files successfully created’

 

what should I check now?

[C2dan88]

That it, restart and see Windows will boot.

[damnfinecoffee]

2 minutes ago, C2dan88 said:

That it, restart and see Windows will boot.

BSOD with CRITICAL_PROCESS_DIED

 

I checked in my BIOS and my 1st boot is set to ‘Windows Boot Manager (M1: Samsung SSD 500GB) which is correct!

secure boot state: enabled

OS Type: Windows UEFI mode

 

I booted into recovery via the DVD and ran diskpart again, if you wouldn’t mind just checking this looks correct to you (again really appreciate you helping me out here, this is my work PC and I’m in trouble if I can’t get back into windows by Monday)

 

I checked disk 1 and it appears the 100MB system partition is there, I double checked disk 0 and it is no longer there.

 

is there anything else I can check here? I’m positive I’m just doing something wrong at this point..

 

 

[damnfinecoffee]

I did the whole process again with just my os ssd connected. No joy, same BSOD. 
 

Should this volume be labelled or marked as EFI somewhere?

 

 

[Jimkirk363]

I still think u should just do a reinstall over the top of the installation u have, this should fix the issues ur having.

[damnfinecoffee]

1 hour ago, Jimkirk363 said:

I still think u should just do a reinstall over the top of the installation u have, this should fix the issues ur having.

Hi,

Stupid question but when you say over the top of it do you mean effectively a clean install? Or is there a way to do this whilst preserving existing applications and files?

thanks

[Jimkirk363]

@damnfinecoffee It will save existing files but i'm unsure whether existing applications will run.

[damnfinecoffee]

20 minutes ago, Jimkirk363 said:

@damnfinecoffee It will save existing files but i'm unsure whether existing applications will run.

Ah ok, so how would I go about doing this?

[Jimkirk363]

@damnfinecoffee Rerun the windows setup as if ur installing a fresh version of windows and just install to a different folder for example "Windowsnew" instead of the default windows folder.

[damnfinecoffee]

43 minutes ago, Jimkirk363 said:

@damnfinecoffee Rerun the windows setup as if ur installing a fresh version of windows and just install to a different folder for example "Windowsnew" instead of the default windows folder.

Ah ok so it would be an additional install of windows in a different folder? I didn’t know you could specify that during windows install.. or do you mean to a separate partition?

[Jimkirk363]

@damnfinecoffeeU can do it to a different Partition or the same drive, just rename the folder your installing windows to.