Question Monitors flickering and PC freezes up and goes to sleep ?

[camo80118]

Hi all!
I've just gotten back a few days ago after traveling for a bit, went to play CS:GO with my buddy and ran into this problem where both monitors would begin flickering before going black and sending my computer into sleep mode (PC was still on but both monitors black and couldn't even wake it up). This wasn't happening before I traveled so I'm not sure what has changed or what the issue could be. The game I'm playing and the graphic intensity of it doesn't seem to have an effect on whether or not it happens. For example, it was happening on CSGO and GTA but not Forza Horizon.

A lot of the times it strikes out of nowhere while gaming, but it also has been happening when rebooting after it has occurred as well. For example, I can be playing for hours and hours on a given day with no problem at all, but then out of nowhere it'll occur and then happen over and over every few minutes after I reboot.

I'm not overheating in my CPU or GPU at all and there isn't excessive load on either. It just seems so random that this would start happening out of NOWHERE, I hadn't touched a single thing in my PC and its been working amazingly for a year and a few months now.

While checking my event viewer, I see that sometimes it gives me an error around when it crashes, but other times nothing shows at all.
Here are some of the errors/warnings:

The description for Event ID 14 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

\Device\Video3
0000(0000) 00000000 00000000

The message resource is present but the message was not found in the message table

-------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}
and APPID
{15C20B67-12E7-4BB6-92BB-7AFF07997402}
to the user DESKTOP-KPCLPR3\Cam SID (S-1-5-21-3228121379-501142402-2727261135-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

I always see a lot of these DistributedCOM warnings, event ID 10016

---------------------------------------------------
Things I've tried:
Wiping graphics drivers with DDU, reinstalling current and old ones
Updating my display drivers
Disabled/uninstalled any programs interacting with my GPU (heard that might be an issue)
Messing with my monitors wires, but haven't tried new wires yet
Using only one monitor


Attached below are specs and a video of what is happening:

Videos:
https://youtube.com/shorts/kpOckNiS4c4?feature=share (flickering)


Specs:
CPU: i7 10700k (no overclock)
GPU: GeForce RTX 3080
RAM: 16g of G.Skill
PSU: Corsair 750 watt

Let me know if you have any other questions, I'm not very tech savvy so please help me out!

 

[Darkbreeze]

What is the actual model of your Corsair power supply and how long has it been in service?

 

[camo80118]

What is the actual model of your Corsair power supply and how long has it been in service?

So I made a mistake in my original post, turns out its a 650W and not a 750W, but it is a EVGA 120-G1-0650-XR GOLD 650W Fully Modular Continuous Power Supply. The power supply could definitely be an issue, but since its not turning off my PC I'm hoping its not, I can still hear sounds when the screens go black for a little. Its been in service for a pretty long time as well, I'd say about 5 years in total, but with my current build its been around a year and a few months with no issues up until this point.

 

[Darkbreeze]

First, that PSU does not have enough capacity to power that graphics card. That card calls for a minimum of a 700w PSU and a 750-850w unit would be a REALLY good idea since we know these 3000 series cards can spike well over their normal recommended capacity.

Secondly, being five years old AND those NEX G1 units weren't particularly good either. I hate to tell you to replace a unit that should have a 10 year warranty so if you have the original invoice or some proof of purchase somewhere EVGA will likely replace it if it IS bad.

Are you using a power strip or are the monitors and power supply plugged directly into the wall socket? If you are using a power strip, try plugging the PSU directly into the wall and also try using a different power strip for the monitors if they are not plugged directly into the wall. Power strips are notorious for this kind of thing. PSU should always be plugged directly into the wall or plugged into a UPS battery backup system.

Might also try just one monitor, and then the other, to see if perhaps one of them has crapped out.

 

[camo80118]

First, that PSU does not have enough capacity to power that graphics card. That card calls for a minimum of a 700w PSU and a 750-850w unit would be a REALLY good idea since we know these 3000 series cards can spike well over their normal recommended capacity.

Secondly, being five years old AND those NEX G1 units weren't particularly good either. I hate to tell you to replace a unit that should have a 10 year warranty so if you have the original invoice or some proof of purchase somewhere EVGA will likely replace it if it IS bad.

Are you using a power strip or are the monitors and power supply plugged directly into the wall socket? If you are using a power strip, try plugging the PSU directly into the wall and also try using a different power strip for the monitors if they are not plugged directly into the wall. Power strips are notorious for this kind of thing. PSU should always be plugged directly into the wall or plugged into a UPS battery backup system.

Might also try just one monitor, and then the other, to see if perhaps one of them has crapped out.

Yeah I was worried it might be the PSU. I'll definitely try to get a higher wattage soon and see if it keeps happening. Looking at other posts similar to mine though, people with higher wattages and lower intensive GPUs than I have are still experiencing the same problem with no fixes. If this helps at all, here is my minidump:

***

• *
• Bugcheck Analysis *
• *

***

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffffcf83219df460, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8012cd21218, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.

Debugging Details:
------------------

Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nvmdig.inf_amd64_7ad37590e62d4afc\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3764

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 6979

Key : Analysis.Init.CPU.mSec
Value: 359

Key : Analysis.Init.Elapsed.mSec
Value: 5504

Key : Analysis.Memory.CommitPeak.Mb
Value: 100

Key : Bugcheck.Code.DumpHeader
Value: 0x116

Key : Bugcheck.Code.Register
Value: 0x116

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key : WER.OS.Version
Value: 10.0.19041.1


FILE_IN_CAB: 080922-6171-01.dmp

BUGCHECK_CODE: 116

BUGCHECK_P1: ffffcf83219df460

BUGCHECK_P2: fffff8012cd21218

BUGCHECK_P3: ffffffffc000009a

BUGCHECK_P4: 4

VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffffcf83219df460
Symbol dxgkrnl!_TDR_RECOVERY_CONTEXT not found.

PROCESS_OBJECT: 0000000000000004

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffff820203d07918 fffff801281c638e : 0000000000000116 ffffcf83219df460 fffff8012cd21218 ffffffffc000009a : nt!KeBugCheckEx
ffff820203d07920 fffff80128176b04 : fffff8012cd21218 ffffcf8322c15370 0000000000002000 ffffcf8322c15430 : dxgkrnl!TdrBugcheckOnTimeout+0xfe
ffff820203d07960 fffff8012816f63c : ffffcf8322c5c000 0000000001000000 0000000000000004 0000000000000004 : dxgkrnl!ADAPTER_RENDER::Reset+0x174
ffff820203d07990 fffff801281c5ab5 : 0000000000000100 ffffcf8322c5ca70 00000000176accb0 fffff8010ff25440 : dxgkrnl!DXGADAPTER::Reset+0x4dc
ffff820203d07a10 fffff801281c5c27 : fffff8010ff25440 ffffcf8330523640 0000000000000000 0000000000000100 : dxgkrnl!TdrResetFromTimeout+0x15
ffff820203d07a40 fffff8010f4e87f5 : ffffcf83312ec040 fffff801281c5c00 ffffcf83176accb0 ffffcf8300000000 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x27
ffff820203d07a70 fffff8010f54edc5 : ffffcf83312ec040 0000000000000080 ffffcf83176b2040 ffffcf8322f1ad10 : nt!ExpWorkerThread+0x105
ffff820203d07b10 fffff8010f5ffbe8 : ffffe40163e97180 ffffcf83312ec040 fffff8010f54ed70 ffffffffffb3b4c0 : nt!PspSystemThreadStartup+0x55
ffff820203d07b60 0000000000000000 : ffff820203d08000 ffff820203d01000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: nvlddmkm+e31218

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {c89bfe8c-ed39-f658-ef27-f2898997fdbd}

Followup: MachineOwner

 

[Darkbreeze]

Did you do a clean install of Windows when you built this system? Might be a good idea to at least try doing a clean install and then installing the Nvidia drivers fresh. Sometimes even a clean install of the drivers using the DDU isn't enough if there are other registry problems involved.

What motherboard do you have and what is your current BIOS version?