How To Fix A Windows BSOD Reboot Loop (When all else fails)

Windows How To Fix Blue Screen Command Prompt
By See all their Tutorials
With all the Windows 10 Blue Screen Of Death (BSOD) issues that many seem to be suffering with, I thought I’d share a recent little trick I used to bring an ailing PC back to life.

The problem in question is where a previously working PC suddenly has Windows on startup constantly showing a BSOD error, and then on restart again shows the Windows Troubleshoot options. No matter which option you try from the Troubleshoot options, none of them work.

I have tried and failed many times to solve this issue for so many unfortunates. Googled the issues. Tried command prompts SFC, BOOTREC, CHKDSK etc. None worked.

Faced with yet another similar problem with a PC recently, I remembered a trick I have used on many previous Windows versions in the past, and didn’t really consider it to work on Windows 10 Pro, but it did work for me.

Basically I booted up with a Windows 10 Pro DVD and went to Troubleshooting, Command Prompt.

Seeing that the Command Prompt started at drive X:, I seen that the Windows drive is on drive D:

From there, i looked around and noticed that Windows 10 stores the registry files in “D:\WINDOWS\SYSTEM32\CONFIG”.

Below is a command prompt directory of “C:\WINDOWS\SYSTEM32\CONFIG” from a working PC:

Looking further I noticed that a previous backup of the registry files is kept in “D:\WINDOWS\SYSTEM32\CONFIG\REGBACK”.

Below is a command prompt directory of “C:\WINDOWS\SYSTEM32\CONFIG\REGBACK” from a working PC:

So from the Command Prompt, I typed:


This copies all live registry files to the same files with a “BAK” extension. I did this for the insurance that I could restore the original registry files in case my plan didn’t work.

Then also from the Command Prompt, I typed:


This copies the backup of the registry files (From REGBACK) on top of the live registry files (In CONFIG).

After this, I rebooted the computer and it started up normally.

I did this as a last resort after trying everything else I could think of. I was at the point of starting again and formatting the PC.

I don’t suggest this will work for every BSOD situation, and I definitely will not recommend this unless every other option has been tried and you are at the point of starting again and formatting your PC.

Also, I haven’t tried this when booting from the PC and going to Troubleshooting, Command Prompt. I figure the next PC I have the same problem with, I will try the same trick by this method.