After playing for 10 to 30 minutes in certain games, the screen stops showing any display.
After playing for 10 to 30 minutes in certain games, the screen stops showing any display.
Recently, I installed a new PC and everything appears to function properly. I completed some performance tests such as Cinebench and 3D Mark, and all tasks are operating correctly. I can play Counter-Strike for six hours without any issues. However, with F1 23, my monitors stop sending signals. I can still hear the game and music, but there’s no video output, and I need to restart the computer. This also occurred with another game, and honestly, I’m puzzled about it. My GPU drivers are up to date, and I’ve even reinstalled Windows. Perhaps there’s a problem in the BIOS—this is one of the two possibilities I considered. The other option is that the GPU itself might be faulty, since I purchased it used. But as I mentioned, I stress-tested it, and it worked well; temperatures were normal. I’m unsure what’s happening. If anyone has any ideas about the cause, please share them. Thank you very much!
likely RAM issue. Possible models and quantities of installed sticks vary. XMP enabled or disabled. More probable problems come from the CPU—Intel 13th gen known for significant stability concerns. Yes, stress tests aren’t real-world usage, which is why they sometimes pass in some games but fail in others. They mainly confirm functionality, not diagnose memory controller instability during specific tasks. Similarly, RAM tests simply indicate presence or absence, not underlying controller issues.
or GPU: sure, but it's brand new. I should double-check the 13th/14th gen drop and try all fixes that could help. XMP doesn't seem to work here since 1200Mhz x2 equals 2400MT. I have a question about why the RAM shows 24GB instead of what it should say.
You own two 8GB modules at 3200 MHz each, all powered at 1.35V. About five years ago you added another 8GB stick, assuming it matched. Recently you discovered differences: the third module now operates at 1.2V, which prevents XMP support and caused crashes. When using only the first 16GB at 1.35V with XMP enabled, the problem persisted. It seems the instability emerged gradually.
Task manager also indicates it's at 30% — not sure, that seems odd