My computer suddenly displays a blank screen while I'm playing games; what could be the cause?
My computer suddenly displays a blank screen while I'm playing games; what could be the cause?
During demanding gameplay, particularly with titles like *Shadow of War*, my PC monitor sometimes displays a complete black screen accompanied by a shift in the monitor's indicator light from green to orange, simulating a system shutdown. Despite this issue, audio continues to play through my headphones. The problem persists and won't resolve on its own—for example, if left untouched for ten minutes, no error messages appear and the display remains unresponsive. This phenomenon is not observed with less intensive games.
A GPU-Z log can be found at: https://files.catbox.moe/2mdmb4.txt
My PC specifications are as follows:
Operating System: Windows 10 Home 64-bit
Processor: Intel Core i7 5820K @ 3.30GHz (33 °C) – Haswell-E/EP 22nm Technology
Memory: 16.0GB Unknown @ 1166MHz (14-16-16-35)
Motherboard: ASUSTeK COMPUTER INC. X99-PRO (SOCKET 2011) – 31 °C
Graphics: BenQ XL2411Z (1920x1080@144Hz), BenQ XL2410T (1920x1080@60Hz) – 4095MB NVIDIA GeForce GTX 980 (EVGA) – 62 °C
Storage: 238GB Samsung SSD 850 PRO 256GB (SATA), 1863GB Seagate ST2000DM001-1ER164 (SATA) – 28 °C
Optical Drives: None Detected
Audio: Realtek High Definition Audio
Based on my observations, the graphics card temperature tends to rise above 70 degrees Celsius when experiencing significant processing demands. However, I've noticed that the GPU fans remain largely inactive, typically operating at less than 20% speed. I would recommend using an application to manually control the GPU fan speeds, enabling them to operate at a higher speed. Without additional logs and system specifications, that’s all I can determine at this time.
To receive thorough assistance, please initially furnish your entire computer specifications.
It is crucial that complete system details are always presented alongside any inquiries regarding drivers, hardware, or performance issues. Do not submit DirectX Diagnostic (DxDiag) reports, as they frequently contain redundant information. Posting a DxDiag in place of a detailed system specification list can discourage potential members from offering helpful support. Kindly provide the following information:
(Detailed System Specifications)
-Processor manufacturer and model number (clock speed, voltage, type of cooler, and core temperature at idle and under load)
-Motherboard manufacturer and model number (include BIOS version if graphics card recognition is problematic or stability issues exist)
-Memory (amount, clock speed, model number/link to kit, configuration)
-Graphics card(s) manufacturer and model number (clock speed, voltage if modified, driver version, and GPU temperature at idle and under load)
-Power supply manufacturer, model number, and age (note whether using 110V or 220V AC input)
-Hard drive/solid state drive configuration (e.g., RAID setup, backup drive, OS drive, etc.)
-Case/chassis manufacturer and model number (fan make, model, and configuration if experiencing thermal problems)
-Operating System (If using Windows, specify the framework and service pack version)
-Monitor manufacturer, model number, and resolution (if model number is unknown, list the resolution and refresh rate)
*If the system is a “laptop” or "all-in-one," you must include the manufacturer and model number of the device. Ensure you are consistently using the OEM/manufacturer’s driver updates for your unit.
*If experiencing “crashing”:
-Describe the nature of the crash in detail, as "crash" has multiple definitions.
*If experiencing “performance” issues:
-Specify the precise moment when performance degradation occurred (e.g., after a Windows update, after a BIOS update, after a driver update, after thermal shutdown, after hardware changes/upgrades, etc.)
*For diagnostic purposes, please disable the following:
-All antivirus/anti-malware software
-All on-screen display monitoring software
-Any overclocking beyond factory specifications
After testing two distinct monitors utilizing separate cables, I believe the issue lies elsewhere.