Forum Discussion
Why does this keep happening even after a factory reset?
Why did this happen again just four hours after I turned my PC off, especially when I already factory reset it last night? I spent two weeks trying to fix it before that, and the reset didn't solve anything. I really don't want to reset again if it's just going to come back. Is there something I'm missing that could be causing this loop?
Could the cracked version of After Effects be the culprit, or is it more likely a hardware or driver issue? I built this PC about a year ago, it's been rarely used for the past 6–8 months, and the CPU sits around 31–33°C. I don't have McAfee installed. My specs are an ASRock X870 Pro RS WiFi motherboard, Ryzen 7 7700X, ASRock Steel Legend RX 9070 XT, Corsair iCUE Link Titan 360 RX LCD cooler, 32GB TeamGroup T-Force Delta RGB DDR5, Crucial P3 Plus 2TB NVMe, and a Corsair RM850x Shift PSU. Has anyone else dealt with something like this and actually fixed it for good?
1 Reply
The screenshot shows Windows recovery couldn’t repair startup. It doesn’t identify what originally broke. “Couldn’t connect to the network” refers to the recovery attempt, not necessarily the cause of the boot failure.
I wouldn’t reset it again yet. A reset won’t fix unstable RAM, a failing SSD or BIOS settings, and reinstalling the same problematic software or driver can bring the issue back.
Press Enter > Troubleshoot > Advanced options and try Startup Settings > Restart > Safe Mode, if available. If it starts, back up your files first, then remove recently installed software or drivers. The cracked After Effects installer is a possible source of malware or unwanted changes, but this screen alone cannot establish that. Don’t reinstall it, and run a Microsoft Defender Offline scan when Windows is accessible.
If Safe Mode also fails, check whether the SSD is consistently detected in BIOS and temporarily disable EXPO or any CPU/RAM overclocking. Then test the memory and SSD. A CPU temperature of 31–33°C doesn’t rule out those faults.
The useful next evidence is the “root cause” and repair-result section of SrtTrail.txt, whose path appears on your screen. Share that text rather than performing another reset; the log may help narrow the next step, though it isn’t always conclusive.
