New
#1
Cannot Resolve Boot Loop with "REGISTRY ERRORS" Stopcode.
When I start up the computer, it goes through BIOS and then gives me the blue screen stopcode REGISTRY ERRORS and it is stuck in that loop.
Using a copy of Windows 10 on a USB, I tried going through Repair Your System > Troubleshoot > Advanced Options. Startup Repair, System Resore, and Uninstall Updates do not work.
From here, I tried using the Command Prompt to look at what’s going on:
- Bootrec /rebuildBcd gave me “The requested system device cannot be found.”
- diskpart > sel disk 0 > list vol shows volume 5 as F. It is an NTFS partition, 118 GB (my M2 drive). F was always the drive letter assigned to my hard drive when it was working normally, but from what I understand this “F” doesn’t necessarily correspond to the other “F?”
- F: \shows me the Windows folder and everything else.
- I thought I should try fixing the registry. I entered via cd f:\windows\system32 and then did mkdir configBak. This gave me “the media is write protected.”
- Went back and dug more into the bootrec command and realized that I might be plugging in my USB into the wrong slot. When I changed it, now I get: 0xc000000f “The Boot configuration Data for your PC is missing or contains errors).
- Back into the original slot and now can’t boot from UEFI USB startup option (what I was doing before).
- Tried chkdsk F: /f. Write protected.
- I tried clearing with list volume F > select volume F > attributes disk clear readonly > exit. Still happened.
- Deleted MiniNT folder in registry editor to get rid of HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControl so I can write. Doesn’t fix it.
- In command prompt, tried dism.exe /online /cleanup-image /restorehealth which gave me Error: 50 (DISM does not support servicing Windows PE with the /Online option).
- Tried dism.exe /image:F:/Cleanup-Image /Restorehealth and got Error: 2 (Unable to access the image). Looked around, some said it was a registry error.
- Back to registry stuff: the other day I tried running sfc /scannow so I decided to run it again on F:. Did not find any intergrity violations.
- Also tried again (as I had previously) chkdsk F: /f /r /x but cannot run because write protected.
- Also, when I look in f:\Windows\System32\config\Regback, the DEFAULT, SAM, SECURITY, SOFTWARE, and SYSTEM all list 0 which from what I can tell means I can’t repair these.
Anyways, I’m at a total loss. Anyone know what I should do? Should I do a clean install and copy over my contents to an external drive or what? I’d prefer not to lose my data on that drive (luckily, I don’t have much).