Error 0X0000454 on UEFI startup

[Poroto]

So I just did a CLEAN UEFI install of Windows 10 and Im experiencing a pretty weird issue.

When I turn pc off and turn it back on I get this error: http://i.imgur.com/E64XUBd.jpg which tells me to press esc to go to uefi settings, once I press esc and my computer reboots into UEFI BIOS, I make NO CHANGES WHATSOEVER, restart and the PC boots just fine when I never even changed anything.

Any clue what this error refers to? I googled a lot and run various commands from the installation usb stick terminal but Im unable to fix it.

Thanks.

 

[Colif]

Lets try to fix that then. The problem is your Boot Config Data is not right.

from desktop, go to settings/update & security/recovery
under Advanced Startup. choose restart PC now
this loads you into a blue menu

there are two ways to fix it from here,
1.run Startup repair
choose troubleshoot
choose advanced
choose start up repair - this will scan PC and maybe fix this - will ask for logon info

or
2. manually fix BCD
choose troubleshoot
choose advanced
choose command prompt
We need to use the Bootrec.exe tool. Click on command prompt and type in the following commands, one after the other:
bootrec /fixMbr
bootrec /fixboot
bootrec /RebuildBcd
Exit
Now go ahead and reboot your system. In some cases you may need to run some additional commands.
bootsect /nt60 SYS or bootsect /nt60 ALL

 

[Poroto]

Lets try to fix that then. The problem is your Boot Config Data is not right.

from desktop, go to settings/update & security/recovery
under Advanced Startup. choose restart PC now
this loads you into a blue menu

there are two ways to fix it from here,
1.run Startup repair
choose troubleshoot
choose advanced
choose start up repair - this will scan PC and maybe fix this - will ask for logon info

or
2. manually fix BCD
choose troubleshoot
choose advanced
choose command prompt
We need to use the Bootrec.exe tool. Click on command prompt and type in the following commands, one after the other:
bootrec /fixMbr
bootrec /fixboot
bootrec /RebuildBcd
Exit
Now go ahead and reboot your system. In some cases you may need to run some additional commands.
bootsect /nt60 SYS or bootsect /nt60 ALL

Hey thanks for the answer and sorry for the delay in getting back to you.

I have alredy done the first method but it didnt fix it, all I got was a "Windows was unable to identify your problem".

As for method two, I had already done /fixboot and /rebuildbcd which didnt help unfortunately. I never did /fixMbr as my Windows install is not MasterBootRecord but GPT Partition table, I assume /fixMBR wont work on a GPT system, right? Feel free to correct me if i'm wrong please.

I never did bootsect /nt60 SYS or bootsect /nt60 ALL though.

Ill re run those command once I get home though, just for the heck of it.

If you come up with an other idea let me know!

Thanks!

 

[Colif]

Try the fixmbr, as far as I know it works on GPT or MBR

longer version of same process: https://www.lifewire.com/how-to-rebuild-the-bcd-in-windows-2624508

 

[Poroto]

Try the fixmbr, as far as I know it works on GPT or MBR

longer version of same process: https://www.lifewire.com/how-to-rebuild-the-bcd-in-windows-2624508

Sorry for the delay.

I tried doing the steps in the guide but unfortunately I encountered errors as per the following picture.

http://imgur.com/a/mM84n

Its starting to get annoying so I might do a fresh install and see if that helps.

 

[Colif]

hmm, can't find anything on that error.

try typing it as attrib -h -r -s c:\boot\bcd and see if it makes any changes as I found that order on another page tied to guide. It should work, as the previous backup found C after all.

you could try this otherwise: http://woshub.com/how-to-repair-uefi-bootloader-in-windows-8/

 

[Poroto]

hmm, can't find anything on that error.

try typing it as attrib -h -r -s c:\boot\bcd and see if it makes any changes as I found that order on another page tied to guide. It should work, as the previous backup found C after all.

you could try this otherwise: http://woshub.com/how-to-repair-uefi-bootloader-in-windows-8/

Did a 100% clean UEFI install and the issue remains, so after all it might be hardware related unfortunately. It's weird though since a simple restart fixes it, but the initial power on after a shut down never works.

I'll see if installing Legacy instead of UEFI fixes it? Thoughts?

 

[Colif]

See if turning fast startup off helps: https://www.tenforums.com/tutorials/4189-turn-off-fast-startup-windows-10-a.html

If it does, it could be one of your drivers doesn't like the new power modes in win 10
what are the specs of the PC?

 

[Poroto]

See if turning fast startup off helps: https://www.tenforums.com/tutorials/4189-turn-off-fast-startup-windows-10-a.html

If it does, it could be one of your drivers doesn't like the new power modes in win 10
what are the specs of the PC?

Couple of news, thought the issue remains.

*Turning fast startup did not help
*The WosHub link you sent me doesn't work either, all steps completed and the issue remains.

But I did find something weird, before having this issue I tried hackintoshing my system (running macOS on non-Apple hardware) along with Windows in dualboot, this requires a bootloader called Clover. Once I decided to fully uninstall macOS and just run Windows, I of course did a 100% clean Windows install (literally deleting every partition on my SSD and installing windows on the unallocated space left), so logic would tell me that there would be no chance on earth of anything related to macOS nor clover left in my system, right? Well, guess I was wrong. Please check the following pictures:

1)Was about to run the commands you instructed me and for whatever reason clicked "Use a device"
2)Next thing I know is I get an entry named "Clover start boot.efi at Sierra SSD". Sierra SSD was the name I assigned to my macOS Sierra partition. Weird, right?

http://i.imgur.com/5MZNbcV.jpg
http://i.imgur.com/2vYGHtY.jpg

Something tells me this has something to do with the problem, as I also had this issue back when I was dualbooting.

Any ideas as to why deleting everything on a drive didn't really delete the Clover stuff?

Thanks.

 

[Colif]

it must be stored in the bios as it would be looking at the boot loader to see what device options there are. Its only way it can survive a fresh install.

resetting BIOS to default might clear it, with only the hdd attached
many of the fixes rely on you having clover still installed - https://www.tonymacx86.com/threads/guide-remove-extra-clover-bios-boot-entries-prevent-further-problems.175274/

clearing the CMOS should remove it as well as it resets all settings in bios.

 

[Poroto]

it must be stored in the bios as it would be looking at the boot loader to see what device options there are. Its only way it can survive a fresh install.

resetting BIOS to default might clear it, with only the hdd attached
many of the fixes rely on you having clover still installed - https://www.tonymacx86.com/threads/guide-remove-extra-clover-bios-boot-entries-prevent-further-problems.175274/

clearing the CMOS should remove it as well as it resets all settings in bios.

Thanks for the fast reply.

By "resetting BIOS to default might clear it" you mean selecting the option in my BIOS which says "Load optimized defaults"? If so, I have already done that and the issue remains.

As for "many of the fixes rely on you having clover still installed". I can't boot to clover since I wiped it from my SSD, and selecting the option "Clover start boot.efi at Sierra SSD" takes me to Windows. I still have the Clover USB I used to install macOS though and that might get me to Clover and its appropiate shell to run the commands on that guide, but I don't know if it wants to me to boot Clover from the SSD (I can't since I wiped it), or from the USB stick, or if its the same.

What do you mean "with only the hdd attached"? I currently have an m.2 nvme SSD for my main Windows install and a 1TB HDD for media storage. What would I have to plug/unplug before attempting the steps in the guide?

Thanks!

 

[Colif]

Is that an Asus motherboard? What motherboard do you have?

Clear CMOS does a factory reset, in other words returns your system to factory defaults. So when you next power up your system should behave as if it was powering up for the first time. That is why you are asked to F1 to enter the bios.

F5 or reset BIOS to defaults simply sets the default bios values. Any errors or corruption in BIOS is still present.

There are different ways to clear CMOS and depending on the way or method they will do slightly different things, but the core purpose is to reset to factory defaults.

https://rog.asus.com/forum/showthread.php?27562-BIOS-resetting-methods

I wouldn't do anything with clover guide. removing the record from the bios is best option, don't want to introduce it again.

Resetting CMOS will do that. If nothing else it will remove clover as the BIOS will forget everything about it with no cmos attached to keep its memory. If you not sure how to do it, your motherboard manual should show us. And most of those are online pdf now so just need to look.

 

[Colif]

there might be another way through windows - https://www.sevenforums.com/tutorials/2288-windows-boot-manager-delete-listed-operating-system.html

can tell I don't do this very often.

 

[Poroto]

there might be another way through windows - https://www.sevenforums.com/tutorials/2288-windows-boot-manager-delete-listed-operating-system.html

can tell I don't do this very often.

So yeah, now I can finally assure I have no idea what to do next.

Followed the guide and deleted the EFI entry via the shell, that did not fix it so I cleared the CMOS by following the guide on my motherboards manual, I can assure it cleared since I got this message upon entering the BIOS http://imgur.com/a/dK9i2 .

As for the last link you posted, only detected operating system is Windows so not much I can do there.

I'm literally lost here.

 

[Colif]

That CMOS screen is to be expected, its telling you it worked and that you need to set up the defaults in the bios again by choose use optimised defaults

have you tried that Use device menu again and see if it only see Win 10 as well?

have you tried running start up repair again? now BIOS boot order shouldn't include any reference to clover
boot from installer
on screen after languages, choose repair this pc, not install.
choose troubleshoot
choose advanced
choose start up repair - this will scan PC and maybe fix this - will ask for logon info

 

[SaschaB72]

could you fix this problem?

cause I have the exact same problem right now with an ASUS ROG GL502VT!

If yes, what did you do to get rid of error code: 0x0000454?

 

[Colif]

He is still trying to figure it out, he tried to install win 10 as MBR instead and ran into exact same error so we still trying to work it out. I was wrong about him having Asus motherboard

His other thread is: http://www.tomshardware.com/forum/id-3452661/broken-bcd-wake-sleep.html#19869776

did you start your own thread?

 

[SaschaB72]

no I didn't start my own thread, I was just checking google, desperate for an answer, since I did almost everything you guys talked about myself. without luck. it is not a big deal for me, since I can use my laptop just fine. It's just annoying to see this error from time to time and not having a clue, what this is all about...

if you could update me as soon as you have a solution that would be very much appreciated!

 

[Poroto]

no I didn't start my own thread, I was just checking google, desperate for an answer, since I did almost everything you guys talked about myself. without luck. it is not a big deal for me, since I can use my laptop just fine. It's just annoying to see this error from time to time and not having a clue, what this is all about...

if you could update me as soon as you have a solution that would be very much appreciated!

Hey, no worries.

Unfortunately I did everything humanely possible and the issue remains.

I installed Windows on my normal HDD to see wether it was the drive or not and it seems it was, as I don't have any problems whatsoever on the HDD, so my guess is I somehow broke my nvme SSD, which sucks.

Are you getting the same 0X0000454 error? I tried googling but found close to nothing regarding that error, that's why I opened up a thread.

@Colif

I might be getting a Samsung 960 EVO Series - 250GB PCIe NVMe - M.2 Internal SSD , thinks this is a solid replacement for my 600p?

 

[SaschaB72]

Yes! I am getting the exact same 0X0000454 error. But not always, just from time to time, like out of the blue... I then press Crtl, Alt, Delete and let it boot again and then Win10 is starting without problems... very strange!

 

[Colif]

have you checked the health of the drive? turning off smart detection just leads me to think you need to check health of the drives out, as smart is for drive health monitoring.

Turns out Poroto's problem appears to be the M.2 slot he was using but something isn't right there as it worked fine before.

 

[Poroto]

Yes! I am getting the exact same 0X0000454 error. But not always, just from time to time, like out of the blue... I then press Crtl, Alt, Delete and let it boot again and then Win10 is starting without problems... very strange!

Yeah, exactly what I experienced. Sometimes it would work and sometimes don't. And when it didn't a simple restart would fix it. Sorry I can't help you enough, my issue was solved by chaning the m.2 slot, but I still have to find out whats the cause of all this, wether my old m.2 slot is broken, needs to be reconfigured, I don't really know. At this point I am just glad it works and wont touch ANYTHING there lol, I've waster countless hours trying to fix it and now that it works I'm scared to even open my PC case door lmao.

If there's anything I can do to help, shoot.

have you checked the health of the drive? turning off smart detection just leads me to think you need to check health of the drives out, as smart is for drive health monitoring.

Turns out Poroto's problem appears to be the M.2 slot he was using but something isn't right there as it worked fine before.

Yeah, so far it's working flawless on the new slot, I'm still sooo curious as to what actually happened with the other slot or whatever caused this, but Im also just glad I didn't waste 130 unnecesary bucks replacing something that works.

On abd btw, your support was superb, thank you so much for the fast replies!

 

[Colif]

lol. that last question was for Sascha.

I am glad I helped even if the fix wasn't something I thought of. It doesn't feel right anyway.

 

[garbkon]

Absolutely same problem with Asus GL502V, as it was on a warranty send it to Asus tech support, they changed SSD, reinstalled factory Windows and send me my Asus back, so worked fain for about 1 hr, and then Windows installed Fall Creator from version 1703 to version 1709, and the problem accrued again, which make me think its Windows update doing something with particular build of PC. I think I will give up here and try to get my money back.