Problem encountered; system fails to load any operating system.
Problem encountered; system fails to load any operating system.
i'm still unsure what else i can attempt, so i'm starting over. the system runs a gigabyte b650 gaming x ax v2 rev 1.1 bios with an amd ryzen 7 7800x3d cpu, a sapphire pulse radeon rx 7900 xt 20gb ram, g skill ddr5 flare x5 2x16 gb, an msi mag a850gl pcie5 motherboard, and windows 10. it's been running for just over a year now. there was a ram stick failure a few months ago, but after replacing it, the pc has been stable. i've used the pc for 3 to 5 hours at a time. when i tried to launch the game, it didn't load properly initially, but after checking a steam file, it worked. i played for under 30 minutes during a discord call, then the pc blue-screened and shut down repeatedly. after the first blue screen, it kept restarting or freezing. i noticed audio problems with 8-bit sounds and delayed volume changes. using windbg logs revealed a critical process error (faillog: 0xEF_svchost.exe). it seems the issue might have started during troubleshooting, and the system froze at the gigabyte logo screen. i've updated the bios from 31 to 34, tried removing the graphics card and using integrated graphics, but nothing works. i'm unable to access the motherboard lights for issues, can enter bios, performed a cmos reset, but still hit the gigabyte logo and rebooted. i've tried removing all system drives and using a usb with linux mint and later fedora, but both attempts didn't help. the compatibility modes in linux showed some errors with job ldconfig.service and rcu_preempt, possibly pointing to a deeper problem. i'm exhausted from trying various fixes and need fresh suggestions to identify the root cause.
You handled the troubleshooting very well. Those are exactly the steps I would have followed. Have you checked the debug lights on the motherboard while trying to boot? That might provide useful information. I’d also suggest re-seating the CPU. I had a similar machine with these problems and it resolved them. Best of luck!
This might indicate a CPU problem (possibly memory controller or internal cache/crossbar error) or a Motherboard issue (voltage regulation or firmware failure). I recommend checking the motherboard firmware or reinstalling the latest updates to determine if the issues continue.
Just reacting to catch attention. Turns out I didn’t take off the plastic from the cooler, and it’s still functioning after a year. The tech who took it out was surprised how simple it was. With the right cooking, it can seep into windows and get past the boot screen, but it still causes a blue screen. Ultimately, CPU problems that weren’t obvious or noticeable during the last year but eventually damaged a CPU.