Considered attempting a speed boost but feared it could damage the system's boot functionality.
Considered attempting a speed boost but feared it could damage the system's boot functionality.
On phone and in bed with stress headache, so please forgive any writing issues.
This setup includes a Ryzen 5 2600, RTX 2070 Super, 32 Gigs 3200 mhz Trident RAM, Asus Prime B450 Plus, a Samsung Sata SSD from 2016, and a formatted 1TB HDD used as system backup before formatting to fix a booting problem.
The PC runs at 650 watts with an EVGA Supernova graphics card. After recent overclocking of the CPU and GPU, I received an ND-15 for the CPU. The CPU clocked around 4.2 Ghz, while the GPU had +130 core clock and +100 memory clock. During testing of Doom, the screen went black and the system shut down completely. Compact BIOS failed to boot Windows; the monitor would spin, then go black before powering off.
It’s worth mentioning I frequently reinstalled large games like Doom, which might have damaged the SSD earlier. However, during my tinkering, the disk health checked out every time.
I’ve turned the system off and on again, re-seated all components including the CPU, set BIOS to optimized defaults, attempted Automatic Repair, and tried booting flat. The CPU has no built-in graphics; it’s unclear if NVIDIA drivers or the RTX are malfunctioning. I’ve reinstalled Windows via the install USB and used safe mode through Windows USB.
I reset the CMOS by removing and reinserting the battery briefly. Despite these efforts, I’m unsure what’s causing the issue. My tower still boots every time and recognizes my CPU and RAM. Could overclocking have damaged a pin or motherboard component related to booting? The SSD might be faulty, preventing Windows installation even though it detects everything correctly.
If this sounds familiar, please share your thoughts. Right now I’m considering replacing the CPU and motherboard, installing a new 1TB SSD, and trying recovery options for my files. It feels like something fundamental broke during overclocking, making it impossible to boot anything on that setup. Any advice from your end would be appreciated.
Even the Windows installation USB? Is it possible to recover files from a damaged Windows drive? I haven’t created a live Linux USB before, but it seems manageable. I’ll let you know if it starts working.
The Ubuntu installation on the Live Linux USB is stuck in a boot loop, repeatedly restarting after launching Ubuntu. The issue involves lines of code and the behavior similar to what Windows does when the keyboard and mouse are turned off before the screen.
I have a "Launch CSM" feature that was already activated. It offers four settings for "Boot Device Control," including Boot from Network Devices, Boot from Storage Devices, and Boot from PCIe Expansion Devices. I modified the Storage Device setting to prioritize the UEFI driver, which improved boot speed and gave me access to a command line interface on the screen.
Attempt the test using your Windows disk now; it should display a message such as "UEFI on disk (its make or model)" in the BIOS and boot sequence.
If you're referring to my boot drive, it didn't receive any additional options. The Windows install USB worked, but the black screen issue remains. Edit: I attempted to disable Launch CSM completely. The system entered a boot loop using the Windows USB key.
Are you currently very thin and used Microsoft Media Creation to create a boot USB?
I haven't but I might not need to.
Installing the SSD into the other tower resolved the boot loop and opened the "Repair windows while keeping files" option. Fingers crossed it will boot on my tower after the fix.
Edit: I am definitely backing up this time and purchasing a new SSD regardless, though. Perhaps I'll try NVME now that prices are somewhat reasonable. Still, I need to see if this works at all.