I'm not doing a file system/table repair. There are no bad sectors. I am not dealing with a 10 year old drive. Read the thread. Moreover the disk does not blindly overwrite data, they have spare sectors specifically for that problem and they certainly don't overwrite data already indexed in the file table.
I don't know what you qualify as modules but again, I had a bootable system. SFC+CheckSURT were run without error (after feeding it necessary manifests) and as far as I'm aware that's how you tell your Windows integrity is good.
This BSoD didn't occur after cloning the bad disk. It occurred after running troubleshooting steps in the originally linked thread.
Yes, even Safe Mode with Command Prompt. I see it load the Windows Files and then the same BSoD shows up.
Still not certain what I would be pointing to with "reg load"
The Microsoft documentation seems to suggest that you can point to a "computer name", but I don't believe that applies when merely accessing a different drive within the same computer. The drive itself has no computer name, rather it's the Windows installation that would and I don't feel Windows would search for that in all the drives connected to it. This isn't remote access; it's offline access.
If you think manually restoring the registry backup is the easiest/best first option I can definitely do that much.
