[SOLVED] Unable to turn on my Windows Server 2016 - Stuck in BSOD

[Slasherr00]

Hello Guru's, Good day!

During recent patching I saw once server stuck in BSOD saying :



I feel like System hive might be corrupted but not sure how can I copy System hive outta it.

Any help would be appreciated

 

[ET_Explorer]

The "BAD_SYSTEM_CONFIG_INFO" error in Windows indicates a problem with the system's configuration, often due to corrupt registry files or BCD data. This can cause a blue screen of death (BSOD) and prevent your computer from booting.

Possible causes:

Damaged Boot Configuration Data (BCD)
Corrupted Registry Files
Incompatible or Outdated Drivers
Hardware Issues
Damaged System Files

 

[Slasherr00]

Thank you for that.

Any troubleshooting we can do for that to bring it back up?

 

[ET_Explorer]

You could try fixing the problem at this > Site

 

[axe0]

You could try fixing the problem at this > Site

I think everyone would appreciate if you included troubleshooting options in the post when you point things out

@Slasherr00, I'm not well-versed with Windows Servers so correct me if what I say is not correct. I know with non-server Windows editions, you'd get a troubleshooting menu after a few consecutively failed boot attempts, are you able to get to this?

 

[ubuysa]

In addition to what @axe0 has said above, I understand that Windows Server will boot to an Advanced Options menu if you force shutdown (with the power button) three times. On that Advanced Options menu select Safe Mode and see whether it will boot.

*Safe Mode boots a stripped-down copy of Windows with only critical services and drivers loaded. Many of your devices will not work properly, or at all, because their third-party drivers are not loaded. Your display will be low res because you'll be using the Windows basic display adapter for example.

 

[Slasherr00]

Little worried, what should we do next?

 

[Slasherr00]

I think everyone would appreciate if you included troubleshooting options in the post when you point things out

@Slasherr00, I'm not well-versed with Windows Servers so correct me if what I say is not correct. I know with non-server Windows editions, you'd get a troubleshooting menu after a few consecutively failed boot attempts, are you able to get to this?

Yes, I can get to command prompt window

 

[axe0]

I recommend that you attempt a startup repair first. It may not fix things, but it should give more insight on the issue. It'll record what it finds in srttrails.txt and mentions where it stores that log. In the command prompt you can copy that file to a USB drive or something similar and post it here.

 

[Slasherr00]

Hello Axe, I tried to initiate System repair but it just came back to same screen in a second:

 

[ubuysa]

Will it boot in Safe Mode then?

 

[axe0]

Those screenshots don't look like initiating a startup repair.

What options do you see in the troubleshooting menu?