Question Samsung S7 144Hz Monitor keeps randomly turning off while gaming ?

[Mimas175]

Hi,
I have a Samsung S7 144Hz non-curve monitor. I've had it for about 8 months now and it has worked great until about 2 months ago.

I have recently started experiencing this problem where while I am gaming, at random intervals, my monitor will turn off, then turn back on with the "Display Port" symbol showing in the top left, similar to if I unplugged and replaced in the display port cord. This happens regardless of game, time of play session or temperature.

I have swapped to a different monitor, desktop, and display port cable, and the problem only follows the Samsung monitor. I have a warranty on my desktop and had a diagnostic run, and nothing was found. I also took the monitor to UBreakIFix, and after 3 weeks they were unable to recreate the issue. The first time I sat down to play at my house, it happened.

I don't know what to do at this point, and am trying to avoid replacing the monitor. Any ideas?

If I need to provide more information, please let me know.

 

[rgd1101]

full system spec? include brand and model of the psu

 

[LinuxDevice]

Perhaps the power supply is becoming insufficient (assumes it has an internal power supply and not an external power brick). If this is the case, then you can test by running a lower refresh rate (I don't know what rates that monitor supports, but you could for example try something around 100 Hz or even go as low as 60 Hz). Run for awhile at this lower rate. If the lower rate helps, then I suspect you have an electrolytic capacitor starting to fail (again, this assumes an internal power supply). Both heat and power consumption go down at lower rates. In the case of a signal quality issue lower rates also have less of a problem compared to faster rates (which are more sensitive to things like noise and jitter).

 

[Mimas175]

full system spec? include brand and model of the psu

S

full system spec? include brand and model of the psu

Sure. Let me know if I leave something out.

Processor: Ryzen 9 7900X Raphael AM5 4.7GHz 12-Core Boxed Processor - Heatsink Not Included
Motherboard: X670E-PLUS TUF GAMING WIFI ATX Motherboard
CPU Cooler: Kraken X73 360mm CPU Water Cooling Kit
GPU: GeForce RTX 4090 TUF Gaming Overclocked Triple-Fan 24GB GDDR6X PCIe 4.0 Graphics Card
RAM: Flare X5 Series 32GB (2 x 16GB) DDR5-6000 PC5-48000 CL36 Dual Channel Desktop Memory Kit F5-6000J3636F16GX2-FX5 - Black
Power Supply: MPG A1000G PCIE5 1000 Watt 80 Plus Gold ATX Fully Modular Power Supply
Case: LANCOOL III RGB Tempered Glass ATX Mid-Tower Computer Case - Black
SSD: 980 Pro w/ Heatsink 2TB MLC V-NAND PCIe Gen 4 x4 NVMe M.2 Internal SSD
OS: Windows 10
Display: LS28AG700NNXZA 28" 4K UHD (3840 x 2160) 144Hz Gaming Monitor

I'm sorry if this is too much information. I wanted to be thorough. Let me know if you need peripherals too.

 

[Mimas175]

Perhaps the power supply is becoming insufficient (assumes it has an internal power supply and not an external power brick). If this is the case, then you can test by running a lower refresh rate (I don't know what rates that monitor supports, but you could for example try something around 100 Hz or even go as low as 60 Hz). Run for awhile at this lower rate. If the lower rate helps, then I suspect you have an electrolytic capacitor starting to fail (again, this assumes an internal power supply). Both heat and power consumption go down at lower rates. In the case of a signal quality issue lower rates also have less of a problem compared to faster rates (which are more sensitive to things like noise and jitter).

That's a good idea! Next time the issue happens. I'll drop the refresh rate and see if it continues.

 

[Mimas175]

UPDATE
I have been playing for the past week or so now. I took @LinuxDevice advice and when the problem occurred, I decreased my monitors refresh rate from 144 to 60. This did make the problem occur MUCH less often, but it still does happen.

I also removed the back panel of the monitor in case this is an overheating issue and again, this decreased the problem but did not fully resolve it.

All in all, my problem is still present, but it is much more bearable now. I'm going to keep this thread open in case someone has something else to add.