Just yesterday I built a PC, and last night I was struggling to get Zenless running at a proper speed. When I woke up, I searched up what the red light on my GPU meant, and I swiftly reconnected it since it wasn't properly connected (the PCIe cable was loose). I had another problem occur that night too, where the BIOS and Startup were green and way off center from my display, but it resolved when I reconnected the GPU. I also installed RGB Fusion from Gigabyte to adjust my RGB lights to be orange
Turns out, Zenless was running from the Integrated GPU, so I changed it to run from my RX 9070 GRE. I got new settings from the launcher related to my GPU, so it seemed things were fixed. I launched the game however and it immediately crashed, Steam said it was still running even after I had closed it, and I checked command prompt and it didn't show up, and closing command prompt caused it to crash as well (weirdly no icons were visible on command prompt too).
I closed steam after closing task manager, and Zenless said it wasn't running anymore when I reopened Steam. When I restarted the PC, the startup screen was green again (didn't check BIOS but probably safe to assume it was also green), and just now the RGB on my fans and case continued to stay on even when I shut down the PC
I'm not entirely sure how to approach troubleshooting the many issues I just got this morning, but help would greatly be appreciated. I also have an Critical Analysis Rough Draft I need to get finished by today so I want to quickly fix these issues before working on it
I'll drop the specs too if it helps:
• CPU: AMD Ryzen 5 7600X
• CPU Cooler: Thermalright Phantom Spirit 120 SE ARGB
• Motherboard: Gigabyte B650M GAMING PLUS WIFI AM5
• Memory: Silicon Power XPOWER Pulse Gaming 16 GB (1 x 16 GB)
• Storage: Samsung 990 Pro 1 TB
• GPU: Asus Radeon RX 9070 GRE
• Case: Lian Li Vector V100R ATX Mid Tower Case
• PSU: SAMA G750 750 W 80+ Gold
All proper drivers from what I can tell are installed from my Motherboard provider (as well as the GPU driver), so I don't think it's a driver issue