Step 1: GPU or Monitors?

As both monitors flicker (go black) at the exact same time and come back at the exact same time, it leads me to believe this is not a monitor issue, and is instead an interruption to the video signal originating at the card.

Step 2: GPU-Z Logs

I used GPU-Z to log GPU performances as the issue happened, and found something very interesting.  When the issues occurs, you can observe:

• GPU Clock [MHz] : 1800 to 1935
• Memory Controller Load [%] : ~16 to 4 then back to ~16
• Video Engine Load [%] : ~1 to 4 then back to ~1
• Board Power Draw [W] : Going above 200W (~27W Jump)
• GPU Chip Power Draw [W] : Going above 100W (~13W Jump)
• 8-Pin #1 Power [W] : Going above 70W (~13W Jump)
• 8-Pin #2 Power [W] : Going above 60W (~14W Jump)
• Power Consumption (%) [% TDP] : Jumping from ~43 to ~52
• PerfCap Reason [] : Moving from 16 to 4 (I believe indicating a Power issue)
• GPU Voltage [V] : 0.9310 to 1.0620

This originally noticed the correlation between the GPU Clock [MHz] and Power Jumps.  This lead me to believe there was something wrong with the power supply, not being able to deliver the needed power to the card, especially because once my monitors received video signal again, the GPU Clock [MHz] went back down to 1800.
 
Files: 1-EVGA-FTW-3090-RocketLeague-Long-GPUz-Log.txt (PasteBin YvgYU9iP) | 2-EVGA-FTW-3090-RocketLeague-Short-GPUz-Log.txt (PasteBin Qnt992mz)
Note: Log "Short" is a subset of log "Long" to make it easier to find the timeframe in issue.

Step 5: GPU-Z PerfCap Reasons

It looks like the only REAL discrepancy to deal with now is "PerfCap Reason".  Below is the numbering System as found from this forum post: (techpowerup.com/forums/threads/gpu-z-perfcap-log-number-meanings.243041)
 

/*!
* Power. Indicating perf is limited by total power limit.
*/
NV_GPU_PERF_POLICY_ID_SW_POWER = 1,
/*!
* Thermal. Indicating perf is limited by temperature limit.
*/
NV_GPU_PERF_POLICY_ID_SW_THERMAL = 2,
/*!
* Reliability. Indicating perf is limited by reliability voltage.
*/
NV_GPU_PERF_POLICY_ID_SW_RELIABILITY = 4,
/*!
* Operating. Indicating perf is limited by max operating voltage.
*/
NV_GPU_PERF_POLICY_ID_SW_OPERATING = 8,
/*!
* Utilization. Indicating perf is limited by GPU utilization.
*/
NV_GPU_PERF_POLICY_ID_SW_UTILIZATION = 16,

 
In my case, the follow is what I have seen in my logs:

• 16 : NV_GPU_PERF_POLICY_ID_SW_UTILIZATION
• 4 : NV_GPU_PERF_POLICY_ID_SW_RELIABILITY
• 12 : NV_GPU_PERF_POLICY_ID_SW_OPERATING & NV_GPU_PERF_POLICY_ID_SW_RELIABILITY

Based on the information above, and looking at the logs.  the issue log went to 4 when the screens went black and benchmark logs went to 12 (8 & 4) regularly, but did not have any issues... I am at a loss.

Step 6: Reaching Out

Hence I am here... What are next steps?  Any help would be appreciated.
 
The PerfCap Reason 4 still seems to be looming in the back of my mind, but as code 4 showed up in the issue log AND in the Benchmark logs, I don't think it is that. I have also been thinking maybe it is because I am using a motherboard (ASUS PRIME-X399-A) that only supports PCIe 3.0 it could be an issue, but there have been multiple posts, videos, etc. calling out that is will reduce performance, but as the benchmarks are WAY out performing Rocket League, I don't think it is that. I also was thinking it may just be crappy coding in Rocket League, but it have also seen this happened in Code Vein... so there is that?
 
New World Disclaimer: I did play Alpha & Beta of New World, but I have only ever had a few crashes in the game, and with benchmarks being run after that time working... I am not sure if it would be that issue either.  I never received Screen Flickering in New World, and I only played the game for about 2 days on this card before getting the news I should not do that, and how mot played since.
 
Crypto Disclaimer: I have not mined anything on this card, and do not plan to.
 
If you made it this far, Thank you.  And I hope to hear from you.

MartinUK
Is there anything showing in the Windows events logs at the time this happens? Perhaps in the System log with a source of nvlddmkm

There are no nvlddmkm references in Windows System Event Logs since the 3090 was installed... BUT I just Played Rocket League to reproduce the issue, and I did see THIS in the Application Event Logs
 
Application Error

Log Name: Application
Source: Application Error
Date: 9/18/2021 11:52:08 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: DESKTOP-MRC9EFS
Description:
Faulting application name: dwm.exe, version: 10.0.19041.746, time stamp: 0x6be51595
Faulting module name: ism.dll, version: 10.0.19041.1237, time stamp: 0x68371cb1
Exception code: 0xc0000005
Fault offset: 0x0000000000088c1a
Faulting process id: 0x594
Faulting application start time: 0x01d7acb8f42e30d1
Faulting application path: C:\WINDOWS\system32\dwm.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ism.dll
Report Id: e76f744d-bb0f-4cce-84b6-4a035075d2d5
Faulting package full name: 
Faulting package-relative application ID: 
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
 <System>
 <Provider Name="Application Error" />
 <EventID Qualifiers="0">1000</EventID>
 <Version>0</Version>
 <Level>2</Level>
 <Task>100</Task>
 <Opcode>0</Opcode>
 <Keywords>0x80000000000000</Keywords>
 <TimeCreated SystemTime="2021-09-18T18:52:08.3026510Z" />
 <EventRecordID>11261</EventRecordID>
 <Correlation />
 <Execution ProcessID="0" ThreadID="0" />
 <Channel>Application</Channel>
 <Computer>DESKTOP-MRC9EFS</Computer>
 <Security />
 </System>
 <EventData>
 <Data>dwm.exe</Data>
 <Data>10.0.19041.746</Data>
 <Data>6be51595</Data>
 <Data>ism.dll</Data>
 <Data>10.0.19041.1237</Data>
 <Data>68371cb1</Data>
 <Data>c0000005</Data>
 <Data>0000000000088c1a</Data>
 <Data>594</Data>
 <Data>01d7acb8f42e30d1</Data>
 <Data>C:\WINDOWS\system32\dwm.exe</Data>
 <Data>C:\WINDOWS\SYSTEM32\ism.dll</Data>
 <Data>e76f744d-bb0f-4cce-84b6-4a035075d2d5</Data>
 <Data>
 </Data>
 <Data>
 </Data>
 </EventData>
</Event>

 
Information

Log Name: Application
Source: Windows Error Reporting
Date: 9/18/2021 11:52:09 AM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: DESKTOP-MRC9EFS
Description:
Fault bucket 1277668416890034719, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: dwm.exe
P2: 10.0.19041.746
P3: 6be51595
P4: ism.dll
P5: 10.0.19041.1237
P6: 68371cb1
P7: c0000005
P8: 0000000000088c1a
P9: 
P10:
Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2456.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2503.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2514.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2512.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2542.tmp.txt
These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_dwm.exe_d38874f9c73afebbde45e592f21b54915f1a2_c2f10bab_29fba71d-89b0-4c08-8d9e-8997acf91394
Analysis symbol: 
Rechecking for solution: 0
Report Id: e76f744d-bb0f-4cce-84b6-4a035075d2d5
Report Status: 268435456
Hashed bucket: a13cf847fc5e81bad1bb30a7e1775a1f
Cab Guid: 0
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
 <System>
 <Provider Name="Windows Error Reporting" />
 <EventID Qualifiers="0">1001</EventID>
 <Version>0</Version>
 <Level>4</Level>
 <Task>0</Task>
 <Opcode>0</Opcode>
 <Keywords>0x80000000000000</Keywords>
 <TimeCreated SystemTime="2021-09-18T18:52:09.5896790Z" />
 <EventRecordID>11262</EventRecordID>
 <Correlation />
 <Execution ProcessID="0" ThreadID="0" />
 <Channel>Application</Channel>
 <Computer>DESKTOP-MRC9EFS</Computer>
 <Security />
 </System>
 <EventData>
 <Data>1277668416890034719</Data>
 <Data>4</Data>
 <Data>APPCRASH</Data>
 <Data>Not available</Data>
 <Data>0</Data>
 <Data>dwm.exe</Data>
 <Data>10.0.19041.746</Data>
 <Data>6be51595</Data>
 <Data>ism.dll</Data>
 <Data>10.0.19041.1237</Data>
 <Data>68371cb1</Data>
 <Data>c0000005</Data>
 <Data>0000000000088c1a</Data>
 <Data>
 </Data>
 <Data>
 </Data>
 <Data>
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2456.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2503.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2514.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2512.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2542.tmp.txt</Data>
 <Data>\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_dwm.exe_d38874f9c73afebbde45e592f21b54915f1a2_c2f10bab_29fba71d-89b0-4c08-8d9e-8997acf91394</Data>
 <Data>
 </Data>
 <Data>0</Data>
 <Data>e76f744d-bb0f-4cce-84b6-4a035075d2d5</Data>
 <Data>268435456</Data>
 <Data>a13cf847fc5e81bad1bb30a7e1775a1f</Data>
 <Data>0</Data>
 </EventData>
</Event>

 
Warning

Log Name: Application
Source: Dwminit
Date: 9/18/2021 11:52:10 AM
Event ID: 0
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: DESKTOP-MRC9EFS
Description:
The Desktop Window Manager process has exited. (Process exit code: 0xc0000005, Restart count: 1, Primary display device ID: NVIDIA GeForce RTX 3090)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
 <System>
 <Provider Name="Dwminit" />
 <EventID Qualifiers="32770">0</EventID>
 <Version>0</Version>
 <Level>3</Level>
 <Task>0</Task>
 <Opcode>0</Opcode>
 <Keywords>0x80000000000000</Keywords>
 <TimeCreated SystemTime="2021-09-18T18:52:10.1584329Z" />
 <EventRecordID>11263</EventRecordID>
 <Correlation />
 <Execution ProcessID="0" ThreadID="0" />
 <Channel>Application</Channel>
 <Computer>DESKTOP-MRC9EFS</Computer>
 <Security />
 </System>
 <EventData>
 <Data>0xc0000005</Data>
 <Data>1</Data>
 <Data>NVIDIA GeForce RTX 3090</Data>
 </EventData>
</Event>

 
Information

Log Name: Application
Source: Desktop Window Manager
Date: 9/18/2021 11:52:10 AM
Event ID: 9027
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: DESKTOP-MRC9EFS
Description:
The Desktop Window Manager has registered the session port.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
 <System>
 <Provider Name="Desktop Window Manager" />
 <EventID Qualifiers="16384">9027</EventID>
 <Version>0</Version>
 <Level>4</Level>
 <Task>0</Task>
 <Opcode>0</Opcode>
 <Keywords>0x80000000000000</Keywords>
 <TimeCreated SystemTime="2021-09-18T18:52:10.2074441Z" />
 <EventRecordID>11264</EventRecordID>
 <Correlation />
 <Execution ProcessID="0" ThreadID="0" />
 <Channel>Application</Channel>
 <Computer>DESKTOP-MRC9EFS</Computer>
 <Security />
 </System>
 <EventData>
 </EventData>
</Event>

Yeah it really sounds like a driver issue of some type. I would try only one monitor and see if it still happens. Knowing that will at least help us know if it’s a dual monitor only issue.

KernelCurry

DNAJAY
Yeah it really sounds like a driver issue of some type. I would try only one monitor and see if it still happens. Knowing that will at least help us know if it’s a dual monitor only issue.

Can confirm Dual Monitors is NOT the issue.
 
Also, Since Updating the Xbox controller drivers, I have not had an issue... I will update back in if this happens again, or if the issues has been resolved in a few days.

Really? That’s an interesting culprit! Keep us posted ! I like to log things like this away in case I ever run into those issues LOL. Good luck!!

I can Confirm that Updating the Xbox controller drivers, via the Microsoft Store Xbox Accessories app., fixed the issue.  I have replicated this issue on 3 different computers at this point.  Simple fix, but annoying to debug.  Cheers, everyone.