some configurations trigger shutdown when port display interacts with the system, especially during gaming.
some configurations trigger shutdown when port display interacts with the system, especially during gaming.
Hello everyone. My setup has been stable for several years until recently when my computer began shutting down unexpectedly without any BSOD or other alerts such as tearing, dead pixels, audio distortions, or visual anomalies. After conducting some minor checks, I identified that the GPU's display output is the root cause. The issue only appears when using the GPU for non-gaming tasks—other applications run perfectly. Even with heavy workloads like a 170M vertex model in Blender, everything functions smoothly. However, running games such as Banishers: Ghosts Of New Eden causes the system to crash after a few moments, and similar problems occur with other titles, including indie games on PS3. Some games complete their campaigns without issues, but others freeze or shut down entirely. I’ve switched to another GPU output, converted the problematic signal to HDMI via an active converter, and even changed cables—still no resolution. My current hardware includes: R9 3900X, 32GB RAM, Corsair CMW32GX4M4D3600C18, Radeon 7900XTX 24GB Founder’s Edition, ASUS TUF X570 WD BLACK XPG Gaming. I’m still trying to figure this out.
I’ve ruled out RAM problems, different configurations in the graphics card, and no issues with Windows updates or system settings. The only consistent symptoms are game-related crashes and rendering glitches, especially during 360-degree frames in Blender. I’ve discarded all other potential causes, including driver versions, software conflicts, and environmental factors like dust. Until now, my PC has remained stable during regular usage, except for occasional rendering hiccups.
I’m considering a switch to another GPU or further diagnostics. For now, I’m working on a solution that seems promising but requires more testing.
You're attempting firmware diagnostics, which isn't your strength. If another port resolves the issue, the problem likely lies in the hardware—like a faulty or incorrectly made component—or it's a firmware-related issue you won't have access to fix. Those responsible for PC hardware know that changing ports often works; figuring out the root cause is beyond your capabilities.
You're almost spot on, though a few external factors or user actions could cause problems that are uncommon with standard RAM modules. For instance, ECC memory includes error correction, while regular DDR4 doesn't. If you pay attention to details, cosmic radiation might harm data—this is something to consider when selecting hardware, especially for large data centers handling sensitive information. For everyday users, these issues usually go unnoticed. Similarly, future updates like NTFS replacing ReFS could address this, but right now it's a concern for specialized environments. Regarding power issues, events like city blackouts or sudden outages could trigger such failures. You're wondering if testing cables or checking for electrical faults might help prevent it. When diagnostics suggest software is the cause, only technical support can resolve code errors leading to BSODs. Users can reduce risks by avoiding risky behaviors or spotting minor hardware issues, like faulty cables. Also, reporting software bugs can aid fixes. My perspective comes from outside the U.S., so my language might sound a bit rough. I didn't mean to come across that way.
Your own tests indicate the variable refers to the port you're employing. That means the port—either the physical connection or a software-related concern—is the focus. You can either switch to the working port, replace the hardware, or switch to alternative software/firmware that doesn't encounter this problem.
After extensive investigation due to ongoing issues across all ports, I discovered an application named OCCT, designed for stress testing with overclocking capabilities. During these tests, the hot spot (HS) consistently reached temperatures exceeding 100°C, often surpassing 115°C or even 120°C. To prevent permanent damage, the system would shut down after reaching certain thresholds. In a recent video, Jay-Z Two Cents shared his experience with thermal pads causing excessive heat buildup. He explained that the pads created significant mass, forming an angle between the GPU and the metal plate, which led to overheating. In his setup, using thermal putty in the RAM ensured good contact with the vapor chamber and flat GPU, but switching to a thermal pad introduced the same issue, raising temperatures noticeably. This problem persisted even when he replaced the GPU with one that used thermal paste similar to Thermal Grizzly Kryonaut Extreme. After applying the new thermal paste and using a thermal putty, the system stabilized. The temperature difference between the hot spot and GPU dropped significantly—from around 40°C to under 15°C in an open environment, compared to 9°C or lower in closed spaces or games like Alone In The Dark 2024. Some titles, such as Dragons Dogma and Callisto Protocol, are more forgiving of high temperatures, while others like Horizon Forbidden West and PS3 graphics indie games behave differently. It seems the first GPU model reacts more sensitively to heat, possibly due to design quirks. I also came across a video from Ancient Gameplays discussing a Reddit thread about a faulty DP cable; changing it improved overall temperatures. However, this appears to be anecdotal rather than technical. I apologize if my explanation was unclear, and thank you for your patience while I tried to assist.