Jump to content

Black screen on both monitors during gameplay - monitors go into sleep mode like they are not getting a signal from GPU

Sorry in advance for the long post but I've tried my best to summarize my troubleshooting so far. I've been having an issue for the past 4-5 weeks or so which has prevented me from being able to play GTA V, Apex Legends, Scavengers (early access), etc. but still allows me to play non-GPU intensive games such as League of Legends, Rocket League, etc. without issue. 

 

Mid 2020 I took my existing computer (seen here; https://pcpartpicker.com/b/cVtgXL) and I traded the GPU with a local guy for a EVGA XC Ultra 2080 ti because I needed a GPU that would fit the water block in EK's O11D water cooling kit. Now that I had a GPU that would fit I converted the components into this build; https://pcpartpicker.com/b/mRq323  *NOTE THAT THIS IS MY CURRENT BUILD
 
I've been gaming and working on this new water-cooled PC configuration for about a year now but in the last 5-6 weeks I have been experiencing issues when I try to play more GPU heavy games both my monitors will randomly black screen when the GPU is under heavy load; tested Ultra settings in Heaven Benchmark and it crashed a few minutes in once the GPU hit 71*C. The interesting thing is that the PC still runs and I get audio from the games and discord but I have to force restart the PC in order to restore the GPU signal to the monitors. I'm using a display port main gaming monitor (https://pcpartpicker.com/product/BcTrxr/dell-monitor-s2716dg) and an HDMI for my 56" Samsung TV (read as "secondary monitor"). I've tried unplugging and re-plugging in the HDMI cable and DP cables into the GPU/monitors to no avail, I've tried to redownload the latest GeForce drivers (released yesterday 5/18/21; 466.27) to no avail, and I have checked my fan and pump curves in my BIOS and everything there is fine. 
 
Interestingly enough this issue began occurring right about when the temperatures in my region began to climb into the 80s but also coincided with the latest NVIDIA GeForce driver update version 466.27 released on 4/29/21. Just an FYI; I have an AC unit in my room that keeps ambient temps at around 70-72*F so definitely not a thermal throttling issue.

 

I tried swapping out the GPU power cord with a different one to see if it was a power supply issue or a bad GPU power cable but that did not seem to solve the issue.

 

After some thinking I force rebooted my system, started streaming my main PC screen for a friend of mine and launched Apex Legends to see if he could see any error messages when I black screened. When I black screened a few min into a match he could see the following error on my screen; "0x887A0007 - DXGI_ERROR_DEVICE_RESET The device failed due to a badly informed command. This is a run time issue; The application should destroy and recreate the device".  

 

I did quite a bit of research on this issue and tried several solutions to no avail.

 

1) I tried this; https://www.youtube.com/watch?v=Mw6FRWbQhjA

2) and this; https://docs.substance3d.com/spdoc/gpu-drivers-crash-with-long-computations-128745489.html

3) and this; I tried reverting to the previous NVIDIA driver 466.11 from 4/12/21 since my system worked well with that driver but I still got the black screen when playing GPU intensive titles.

 

As of today I started digging in the event viewer and found that there were errors from several ASUS services such as "AsusCertService" and "AsusFanControlService" as well as from Armoury Crate. These were remnants from the previous ASUS ROG Strix 2080ti that I traded away for a EVGA XC Ultra 2080ti to fit the water cooled GPU block in the new build. I downloaded the Armoury Crate Uninstaller, ran the uninstall process, "shift+deleted" all of the remaining ASUS files located at "C:\Program Files (x86)\ASUS", and then I ran command prompt in admin mode and used the SC DELETE "enterservicenamehere" command to delete all the remaining ASUS services.

 

After that I tried to update the NVIDIA drivers again to version 466.27, deleted the DWORD entries I made in solution attempts 1 & 2 above, and tested some games. However, I still got black screened.
 

Another Evernt Log item I see pretty often is;

"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 USERNAME-RYZE\User Name SID (blah blah blah) 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."

Not sure if that has anything to do with this issue either but after some prelim research it looks like it does not.

 

I just stumbled on this post and may try this later today; https://www.reddit.com/r/apexlegends/comments/etslil/psa_i_solved_dxgi_error_device_reset_crashes_on/


Please let me know if you know of any potential solutions for this issue or know of any way to better track down what the root cause of the issue may be. I'm really at a loss as to what this could be and there's no way I'm getting my hands on another 2080 ti right now. Any assistance would be appreciated.
Thank you.

BIOS Version.JPG

Link to comment
Share on other sites

Link to post
Share on other sites

I also forgot to mention that I tried installing MSI afterburner, limited the GPU power limit to 90% and slightly lowered the core clock speed (-6). This seemed to work for Scavengers (early access) as I was finally able to get through the entire tutorial mission without a hitch but this solution did not work for Apex Legends.

Link to comment
Share on other sites

Link to post
Share on other sites

I'm not an expert, but this might be an older driver conflicting with the newer driver and causing weird problems. I would maybe try running the ddu app and removing old drivers and trying to reinstall the latest driver release, but again. I'm no expert. Hopefully someone else has ideas too.

Link to comment
Share on other sites

Link to post
Share on other sites

I M-flash updated the BIOS and made sure that Windows 10 was up to date as well. Still getting crashes mainly in Apex Legends in the first few min of a match and even during character selection. After a deeper dive into Event Viewer it appears that dwm.exe, the Desktop Windows Manager, is crashing repeatedly causing the black SOD. Comments below have the error/event info;

 

 

Link to comment
Share on other sites

Link to post
Share on other sites

Faulting application name: dwm.exe, version: 10.0.19041.746, time stamp: 0x6be51595
Faulting module name: KERNELBASE.dll, version: 10.0.19041.964, time stamp: 0x812662a7
Exception code: 0xc00001ad
Fault offset: 0x000000000010b39c
Faulting process id: 0x568
Faulting application start time: 0x01d74d09848d473f
Faulting application path: C:\WINDOWS\system32\dwm.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 992b1dbc-f8af-4545-8ac2-adf09838bcf4
Faulting package full name: 
Faulting package-relative application ID: 

Link to comment
Share on other sites

Link to post
Share on other sites

The Desktop Window Manager has registered the session port.

Link to comment
Share on other sites

Link to post
Share on other sites

Fault bucket 1516579030178783116, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: dwm.exe
P2: 10.0.19041.746
P3: 6be51595
P4: KERNELBASE.dll
P5: 10.0.19041.964
P6: 812662a7
P7: c00001ad
P8: 000000000010b39c
P9: 
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREE35.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREED3.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREEF3.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREEF1.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREF21.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_dwm.exe_6ab5e5b7d243fc29324376885dc86f679bb51_c2f10bab_99ee2767-f434-4582-89e2-e3728676f639

Analysis symbol: 
Rechecking for solution: 0
Report Id: 992b1dbc-f8af-4545-8ac2-adf09838bcf4
Report Status: 268566528
Hashed bucket: 75ce059f846090e3c50bf897bf9cdf8c
Cab Guid: 0

Link to comment
Share on other sites

Link to post
Share on other sites

Faulting application name: dwm.exe, version: 10.0.19041.746, time stamp: 0x6be51595
Faulting module name: KERNELBASE.dll, version: 10.0.19041.964, time stamp: 0x812662a7
Exception code: 0xe0464645
Fault offset: 0x000000000010b39c
Faulting process id: 0x584c
Faulting application start time: 0x01d74d0c2ddc6c17
Faulting application path: C:\WINDOWS\system32\dwm.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 3911cce0-1662-4bc9-a6b8-7ba5e42bda3a
Faulting package full name: 
Faulting package-relative application ID: 

Link to comment
Share on other sites

Link to post
Share on other sites

Fault bucket 1999354782626927910, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: dwm.exe
P2: 10.0.19041.746
P3: 6be51595
P4: KERNELBASE.dll
P5: 10.0.19041.964
P6: 812662a7
P7: e0464645
P8: 000000000010b39c
P9: 
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF692.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF720.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF730.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF740.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF760.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_dwm.exe_875763f0ca168253cd30c87c5b4a87525df22b8_c2f10bab_b2470098-0933-4374-a0ff-3deb57fe1ce6

Analysis symbol: 
Rechecking for solution: 0
Report Id: 3911cce0-1662-4bc9-a6b8-7ba5e42bda3a
Report Status: 268435456
Hashed bucket: bd608f8387e3d6d4bbbf2294ee74d526
Cab Guid: 0

Link to comment
Share on other sites

Link to post
Share on other sites

The Desktop Window Manager process has exited. (Process exit code: 0xe0464645, Restart count: 1, Primary display device ID: NVIDIA GeForce RTX 2080 Ti)

Link to comment
Share on other sites

Link to post
Share on other sites

The Desktop Window Manager has registered the session port.

Link to comment
Share on other sites

Link to post
Share on other sites

Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

Problem signature:
P1: 141
P2: ffffca072a2cf010
P3: fffff8041a556f64
P4: 0
P5: 17f0
P6: 10_0_19042
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20210519-1707.dmp
\\?\C:\WINDOWS\TEMP\WER-1174687-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8D2.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8E2.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8F5.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER915.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_141_5e66171ce3dcfaca32e6f4ea65beeff3b0ae6b_00000000_f1fc4eb3-1cc3-44d4-a1e4-0f24c7072810

Analysis symbol: 
Rechecking for solution: 0
Report Id: f1fc4eb3-1cc3-44d4-a1e4-0f24c7072810
Report Status: 4
Hashed bucket: 
Cab Guid: 0

Link to comment
Share on other sites

Link to post
Share on other sites

Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

Problem signature:
P1: 141
P2: ffffca072a2cf010
P3: fffff8041a556f64
P4: 0
P5: 17f0
P6: 10_0_19042
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20210519-1707.dmp
\\?\C:\WINDOWS\TEMP\WER-1174687-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8D2.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8E2.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8F5.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER915.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_5e66171ce3dcfaca32e6f4ea65beeff3b0ae6b_00000000_cab_f1fc4eb3-1cc3-44d4-a1e4-0f24c7072810

Analysis symbol: 
Rechecking for solution: 0
Report Id: f1fc4eb3-1cc3-44d4-a1e4-0f24c7072810
Report Status: 2049
Hashed bucket: 
Cab Guid: 0

Link to comment
Share on other sites

Link to post
Share on other sites

This basically repeats until; 

The Desktop Window Manager process has exited. (Process exit code: 0x000000ff, Restart count: 1, Primary display device ID: NVIDIA GeForce RTX 2080 Ti)

 

The Desktop Window Manager has registered the session port.

 

Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: dwm.exe
P2: 10.0.19041.746
P3: 6be51595
P4: KERNELBASE.dll
P5: 10.0.19041.964
P6: 812662a7
P7: e0464645
P8: 000000000010b39c
P9: 
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFC5A.tmp.WERInternalMetadata.xml

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_dwm.exe_875763f0ca168253cd30c87c5b4a87525df22b8_c2f10bab_f3337dc3-096d-4b9e-9a98-989e044b9bcd

Analysis symbol: 
Rechecking for solution: 0
Report Id: a7243485-d394-43d5-a723-fa0ced714e82
Report Status: 100
Hashed bucket: 
Cab Guid: 0

 

Then black screened

Link to comment
Share on other sites

Link to post
Share on other sites

I just ran the sfc scan now repair. Going to see if that fixed it.

 

image.png.7acdfc512d39a86ecf7281df90de3805.png

Link to comment
Share on other sites

Link to post
Share on other sites

Here's the reliability logs from all of todays troubleshooting. Please help me 😛

Log 1.JPG

Log 2.JPG

Link to comment
Share on other sites

Link to post
Share on other sites

  • 1 month later...

@engrdandid you manage to solve it? I found https://appuals.com/how-to-fix-the-application-specific-permission-settings-do-not-grant-local-activation-permission-for-the-com-server-application-error/ that I will try myself.

 

I've been having this issue for 3 weeks now, had a RTX 3080 for a few months without issues. Only when gaming but can even happen in the lobby in Apex 5 minutes after i booted the pc - or i can have Apex in firing range, Destiny 2 in the Tower, a Benchmark running --- all at the same time for more then an hour without any issues. So it's not the power draw or heat of the GPU.

 

Switched monitor, switched dp-cable. 

Updated BIOS

DDU and fresh driver install (3 times)

I found so many threads with this kind of issue and format haven't worked for many ppl, otherwise its my last remaining resort before switching to a new PSU and if that doesnt work RMA the 3080.

 

When I get the no input signal. I get the following logs: 

 

Windows Logs - System

 

Time: 23:54:16
Level: Warning
Source: Display
General:

 

Display driver nvlddmkm stopped responding and has successfully recovered.


 

Time: 23:54:17 (twice)
Level: Warning
Source: DistributedCOM
General:

 

The programspecifik permission settings do not grant Lokal Aktivering permission for the COM Server application with CLSID

{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}

 and APPID

{15C20B67-12E7-4BB6-92BB-7AFF07997402}

 to the user RYZEN3700X\timot SID (S-1-5-21-1759053338-2426172462-174786528-1001) from address LocalHost (med LRPC) running in the application container Inte tillgänglig SID (Inte tillgänglig). This security permission can be modified using the Component Services administrative tool.

 

 

Windows Logs - Application

 

Time: 23:54:17 (and ownward every second 8 seconds forward for all following events)


Level: Error
Source: Application Error
General:

 

Faulting application name: dwm.exe, version: 10.0.19041.746, time stamp: 0x6be51595

Faulting module name: KERNELBASE.dll, version: 10.0.19041.1081, time stamp: 0xde3fc775

Exception code: 0xe0464645

Fault offset: 0x000000000010bd3e

Faulting process id: 0x1fbc

Faulting application start time: 0x01d76dfa78655f84

Faulting application path: C:\WINDOWS\system32\dwm.exe

Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll

Report Id: fc3c2419-1ad4-439f-bb8a-96037b9d5b5a

Faulting package full name:

Faulting package-relative application ID:

 

Level: Warning
Source: Dwminit
General:

 

The Desktop Window Manager process has exited. (Process exit code: 0xe0464645, Restart count: 1, Primary display device ID: NVIDIA GeForce RTX 3080)

 

Link to comment
Share on other sites

Link to post
Share on other sites

  • 1 month later...

did any of you manage to fix the problem? i'm having the same problem as @risby with the dwm.exe errors with the same exception code and dwm.exe version, but a different (later?) kernelbase.dll version. it happens much sooner for me though, like 3-5 mins after loading into windows and with no load applied at all.

 

also tried 2 different monitors, 2 different hdmi cables, 2 different DP cables, DDU (no difference between both updated and base versions of nvidia drivers). Been using my 3080 (zotac trinity non-OC) stock with no problems at all for almost a year and since the problem first started midway thru a game of warhammer battlesector this morning its been happening every single time i boot up and my PC's virtually unusable now.

Link to comment
Share on other sites

Link to post
Share on other sites

Any luck folks? I've scoured the entire internet without a real solution to this issue...

Link to comment
Share on other sites

Link to post
Share on other sites

Had the exact same issues with a brand new Gigabyte AORUS RTX 3080 Extreme (Rev 2.0). Only sometimes after crashing like this and rebooting I couldn't even get back into windows only getting vertical artifacts. The same PC runs a RTX 2070 Super rocksolid. 

Beside using a different PCIe Slot (not possible due to the size of that card) and a full reinstall of windows I tried everything.

I RMA'd the card right now, cause I'm not willing to put any more effort into getting it to run stable.


It's just so strange that this seems to happen for so many RTX 20 / RTX 30 cards of all brands without any real solution.

Link to comment
Share on other sites

Link to post
Share on other sites

  • 4 months later...

Any luck with this issue? I'm having the exact same issue with the errors for few days now and I couldn't be able to find a solution for the same 

Link to comment
Share on other sites

Link to post
Share on other sites

  • 6 months later...

I am in the same issue, last time this happened I RMA'd the card and it solved it.

 

Happened again 9 months later, I read taking the card out and reseating the card solved the issue. Crossing my fingers, only other option is to:
DDU Uninstaller

Reinstall drivers

Link to comment
Share on other sites

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×