Framework 16 Boot Loop

Hello all. I’ve been using my Framework 16 (win11, Ryzen 7040) for mostly work, and light gaming for… 2? years now. It’s been working great, but I just ran into a boot loop problem. Strangely, event viewer is pointing to 2 different problems.

The first, seemingly more major, appears to be a display issue. The laptop boots, then the screen goes black.
I get a series of DCOM 1084 “ShellHWDetection” and “camsvc” errors in my event viewer. Event 10005.

The second is I recently updated to the newer Intel Wi-Fi 6E AX210. It installs fine, and runs….ok? I’m also occasionally getting Nettwtw14 errors. I had used windows drivers, but then swapped to the ones from the framework site, in case there was a discrepancy. No idea why it keeps erroring.

From another post on here, I updated Keyboard firmware, bios, uninstalled display drivers with DDU, then Display drivers. It seemed to help for… 10 minutes?

Sfc scannow in Safemode finds and fixes some corrupt files, but it doesn’t actually help anything. (i’ve done this countless times, and it keeps “fixing” then repeating the problem)

Any ideas?
I previously has a non-boot issue (maybe a month ago) and it was fixed by removing the battery for a few minutes. This boots fine, then the screen goes black after 10-20 seconds.

I’ll be submitting a support ticket in a couple days, as well. I wanted to let y’all have at it first, to see if there’s something I’m missing.

Hello @Chris_Herrington1 welcome to the community. We are all end users like yourself here.

Two things come to mind about the situation.

  1. The Windows installation is corrupt and not able to repair itself. This is a real thing still but much more uncommon. The fix would be to backup important files, wipe the drive, and start with a fresh installation.
  2. The SSD is failing and even though errors may not be reported (SMART, which sadly is not that great), it is writing corrupt files to the system. If it is a defective SSD reinstalling the OS will never fix the issue. It’s days are numbered.

Download the utility for the SSD vendor and have it run a thorough test of the drive.

To help rule out a hardware issue, try creating a Linux USB and booting a live session. Either Ubuntu or Fedora will work easily. If the system is stable then it is likely tied to the Windows 11 installation. Though checking the SSD is still important to help identify a drive issue.

I should add, in safe mode it’s very stable. Likely would be with Unbuntu.

I’ll check the SSD and report back

Western Digital SN850 Scanned. Zero problems.

Another note to add: I just left it unplugged today after some troubleshooting, previous to my post. It had been being plugged in for days. (just sitting not being used for a while) When I plugged in to scan the drive (out of habit) the battery showed fully drained and charging.

It went from 100 to 0 in a couple hours, without being on? That’s not good….

If it is stable in Safe Mode as described and there were no errors found on the Western Digital tests then that is pointing to something being corrupted on the Windows 11 installation. There is a “reset” ability which is suppose to wipe everything and start new, though at this point enough time has been spent diagnosing that formatting the drive and starting over might be the better clean solution to get the laptop working like it has been previously.

So after plentiful sfc scannow’s that for some reason kept coming up with the same “corrupted files cleaned”

I did a virus scan and malware scan (both clean)

Uninstalled all graphic drivers.
Ccleaner Reg clean
Sfc Scannow
Reinstalled Framework drivers
Got it stable enough to now crash immediately.
DISM restorehealth froze at 62.3%
ran “Get-Content C:\Windows\Logs\CBS\CBS.log -tail 10 -wait” in Powershell
And restarted DISM restorehealth again and it finished. (a that line of code was a trick I found on reddit)

Cleaned more, seemingly stable?

Ran 2 benchmark tests for CPU/Mem/Gpu… remains stable.

Did some light gaming for a couple hours, seems fine.

Hooray.

Hope my struggle through this can help someone else down the line.