Boot issues on 2 year old build...Any further suggestions?

OK, Ran the powercfg command as an administrator. Went into Settings and changed to hibernate in 3 minutes. Computer hibernated after 3 min. Pressed keys to wake...nothing worked. Had to power down. Computer didn't power back up. After several tries got the Repair screen and the *,cip was corrupt. Used advanced troubleshooting from Repair screen to boot to Safe Mode. It booted to safe mode. Went to Power and restarted. Computer started fine.

Went into CiPolicies Folder. There were three folders (Active, Internal, Staged). All were empty.

Thoughts?

Tried a clean install on my spare HDD. The hibernate issue dis not reappear. The startup problem is still there. During the install I did encounter a few problems that required starting over or rebooting. Two errors that came up were a problem with NETWTW08.SYS and "Kmodule expecption not handled". Eventually I was able to fully install Windows and tried the system without loading any additional programs or drivers. Same startup issue. I then installed all necessary Windows Updates and the problem remained.

Currently running 60% complete on Pass 2 of 4. So far no errors. It has taken over an hour and half to get to this stage. Should I run the entire 4 passes?

Secure Boot was listed as "User", Platform Key was "Loaded" and OS Type was set to "Windows UEFI mode"

Set TPM to discrete and booted it several times. It started fine once or twice on the first try, once on the second try and had Repair mode once.

I looked around on the BIOS screen but didn't see an ethernet controller. The KMODE only came up once that I recall. It may have been while I was trying to boot to Safe Mode or restarting from Safe Mode.

Switched to "Other OS". Same boot up issue.

Unfortunately, made the change but no luck.

No, actually the Boot drive was a SATA (Samsung EVO 870 SSD). There is a NVME in as storage. The replacement boot drive was a SanDisk SATA SSD.

My new problem was a mistake I made today when making the new drive. I thought I had disconnected the boot drive, but had mistakenly disconnected a data drive. When I went to make the new boot drive, Windows saw two drives that had Windows on it (My Sandisk had been used for something else and I wasn't worried about losing data on it). Unfortunately, It saw the other drive, my original boot, Long story short...My original HDD had the partition changed to inactive. When I went to install it and try and boot up, it isn't recognized. I tried reading it by connecting the drive to a SATA/USB cable and then to another computer. I can see the data on the drive, but doesn't show as Active in Disk Management and I can't change it either there or through Command Prompt. There is a bunch of user configuration info on there that we don't want to lose and I would prefer not to reformat. I tried changing the partition to Active, but received a "Not a MBR disk" message.

Is there a way to recover the drive without losing data? If need be I did run a Seagate Backup Plus on the C: this morning before I started all of this.

Got the original HDD back and operational. Ended up having to reboot multiple times to get the computer to boot to Windows, but was finally able to get the computer back to it's original state before we started with the new HDD.

As for WiFi and Bluetooth. Disabled those before recovering the original HDD. No success.

While getting the original HDD up and running, I found a *.dmp file from yesterday. Maybe it did create the dump file but it went to a drive I couldn't get to at the time. Is there a way to attach a dmp file? I tried but it said it wasn't supported.

Looking at the first line, I do remember that coming up. I think it was during the creation of the test HDD. Here's a bit of a screen shot:

I'm really quite stumped at this point. The process is always the same when starting.

1. Logo Screen comes on with "Press Esc or F2 for startup..." text underneath
2. keyboard and mouse light up
3. Logo screen goes away and keyboard and mouse light also go out briefly.
4. Logo appears again with circling dots below.
5. Keyboard Lights come back on.
6. This is where we can go in two directions.
7. Logo disappears and screen is blank. If it is successful you get an indicator on the monitor and then the Windows screen starts to appear. The keyboard lights might go out briefly but will come right back on. If it is an unsuccessful boot, the Logo disappears and the screen goes dark, the keyboard and mouse lights go out and never come back on. It does sound like the fans kick into a higher gear if it doesn't boot up, but not totally sure.

Looking at the dump file, the second and fourth lines look familiar. They appear in my original list from my bootlog of things not loading. Driver issue?

I'm not going to be able to do any additional work today on the computer but hope to get back to it later tomorrow. I haven't said it yet, but the amount of help you have provided is Amazing and is Greatly Appreciated! Thanks.

Yes, I can take one out of my computer and use it. It's much more basic than the 2070. I'll use the new HDD drive you had me make. I'll be able to test that Monday, most likely.

Should I keep the Secure boot at "Other OS" and the WiFi and Bluetooth to disabled, or go back to defaults and test.