• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

4090 randomly loses signal to display

I have a black screen issue with my 4090
My Environment is Asus x670e + 7800x3d + Asus 4090 OC (running stock) + HDMI Connection to Yamaha AV receiver (projector is only display) + PC ON 24/7 + Regular use of PC as RDP host + regular update to latest NVIDA driver + Bequiet PCI3.0 power supply with 12VhPWR + Win 11 + 64GB RAM EXPO 6000 Mhz.

My Symptoms
From time to time (1 in 20) , only on initial switch on of projector...never during use. the screen is black and the only solution is reboot
The PC has not crashed, and is still providing services eg ftp..but it is not possible to get a screen image on primary display either locally or over RDP. Plugging in a 2nd monitor (DisplayPort) does show a screen on 2nd monitor.
Indeed during use the PC has never crashed in 4 months of use.

More rarely (1 in 50) the logon screen will show, but after successful authentication...black screen. (1 in 100) the screen will be blank after switch on of projector but waiting and turning av receiver/projector on/off the screen will come to life (i think accompanied by nvidia driver crash/driver restart errors in system event log). This hasn't happened often enough for me to be sure.

The previous posts suggests this can sometimes be hardware fault related but i don't think that is always the case for "4090 black screen" symptoms.
Googling "4090 black screen" suggests there may be other causes but as is often the case with internet chatter nothing specific to hold onto to.

My wild speculation makes me think this is related to a RDP WDDM display driver crash or general NVIDIA display driver crash but i cant back that up with real evidence. I dont think its likely to be a hardware failure as its so specific and reproducible when it goes wrong...(turning on local display and never goes wrong during use)

anyways following thread with interest.

EDIT But in the OPs case of randomly showing black screen then hardware failure does seem reasonable.
 
Last edited:
These are the events which make me think its driver crash related, perhaps precipiated by something amd chipset (software) power event

XML: 
Log Name:      System
Source:        Microsoft-Windows-UserModePowerService
Date:          11/03/2024 04:30:03
Event ID:      12
Task Category: (10)
Level:         Information
Keywords:     
User:          SYSTEM
Computer:      X670e
Description:
Process C:\Windows\System32\DriverStore\FileRepository\u0398290.inf_amd64_7f51193690ed6a83\B397300\atieclxx.exe (process ID:5040) reset policy scheme from {8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c} to {8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c}
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-UserModePowerService" Guid="{ce8dee0b-d539-4000-b0f8-77bed049c590}" />
    <EventID>12</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>10</Task>
    <Opcode>0</Opcode>
    <Keywords>0x4000000000000000</Keywords>
    <TimeCreated SystemTime="2024-03-11T04:30:03.8430542Z" />
    <EventRecordID>43267</EventRecordID>
    <Correlation />
    <Execution ProcessID="1328" ThreadID="23092" />
    <Channel>System</Channel>
    <Computer>X670e</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <EventData>
    <Data Name="ProcessPath">C:\Windows\System32\DriverStore\FileRepository\u0398290.inf_amd64_7f51193690ed6a83\B397300\atieclxx.exe</Data>
    <Data Name="ProcessPid">5040</Data>
    <Data Name="OldSchemeGuid">{8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c}</Data>
    <Data Name="NewSchemeGuid">{8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c}</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Display
Date:          11/03/2024 04:27:15
Event ID:      4101
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      X670e
Description:
Display driver nvlddmkm stopped responding and has successfully recovered.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Display" />
    <EventID Qualifiers="0">4101</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2024-03-11T04:27:15.4613510Z" />
    <EventRecordID>43266</EventRecordID>
    <Correlation />
    <Execution ProcessID="8272" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>X670e</Computer>
    <Security />
  </System>
  <EventData>
    <Data>nvlddmkm</Data>
    <Data>
    </Data>
  </EventData>
</Event>

Log Name:      System
Source:        nvlddmkm
Date:          11/03/2024 04:27:13
Event ID:      0
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      X670e
Description:
The description for Event ID 0 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\000001ad
Restarting TDR occurred on GPUID:100

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

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="nvlddmkm" />
    <EventID Qualifiers="0">0</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2024-03-11T04:27:13.4989741Z" />
    <EventRecordID>43265</EventRecordID>
    <Correlation />
    <Execution ProcessID="4" ThreadID="8640" />
    <Channel>System</Channel>
    <Computer>X670e</Computer>
    <Security />
  </System>
  <EventData>
    <Data>\Device\000001ad</Data>
    <Data>Restarting TDR occurred on GPUID:100</Data>
    <Binary>00000000020030000000000000000000000000000000000000000000000000000000000000000000</Binary>
  </EventData>
</Event>

Log Name:      System
Source:        nvlddmkm
Date:          11/03/2024 04:27:13
Event ID:      0
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      X670e
Description:
The description for Event ID 0 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\000001ad
Reset TDR occurred on GPUID:100

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

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="nvlddmkm" />
    <EventID Qualifiers="0">0</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2024-03-11T04:27:13.4833660Z" />
    <EventRecordID>43264</EventRecordID>
    <Correlation />
    <Execution ProcessID="4" ThreadID="8640" />
    <Channel>System</Channel>
    <Computer>X670e</Computer>
    <Security />
  </System>
  <EventData>
    <Data>\Device\000001ad</Data>
    <Data>Reset TDR occurred on GPUID:100</Data>
    <Binary>00000000020030000000000000000000000000000000000000000000000000000000000000000000</Binary>
  </EventData>
</Event>

Log Name:      System
Source:        nvlddmkm
Date:          11/03/2024 04:27:06
Event ID:      0
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      X670e
Description:
The description for Event ID 0 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\000001ad
Resetting TDR occurred on GPUID:100

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

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="nvlddmkm" />
    <EventID Qualifiers="0">0</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2024-03-11T04:27:06.7338914Z" />
    <EventRecordID>43263</EventRecordID>
    <Correlation />
    <Execution ProcessID="4" ThreadID="11496" />
    <Channel>System</Channel>
    <Computer>X670e</Computer>
    <Security />
  </System>
  <EventData>
    <Data>\Device\000001ad</Data>
    <Data>Resetting TDR occurred on GPUID:100</Data>
    <Binary>00000000020030000000000000000000000000000000000000000000000000000000000000000000</Binary>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-UserModePowerService
Date:          11/03/2024 04:26:21
Event ID:      12
Task Category: (10)
Level:         Information
Keywords:     
User:          SYSTEM
Computer:      X670e
Description:
Process C:\Windows\System32\DriverStore\FileRepository\u0398290.inf_amd64_7f51193690ed6a83\B397300\atieclxx.exe (process ID:5040) reset policy scheme from {8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c} to {8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c}
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-UserModePowerService" Guid="{ce8dee0b-d539-4000-b0f8-77bed049c590}" />
    <EventID>12</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>10</Task>
    <Opcode>0</Opcode>
    <Keywords>0x4000000000000000</Keywords>
    <TimeCreated SystemTime="2024-03-11T04:26:21.1850003Z" />
    <EventRecordID>43262</EventRecordID>
    <Correlation />
    <Execution ProcessID="1328" ThreadID="5448" />
    <Channel>System</Channel>
    <Computer>X670e</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <EventData>
    <Data Name="ProcessPath">C:\Windows\System32\DriverStore\FileRepository\u0398290.inf_amd64_7f51193690ed6a83\B397300\atieclxx.exe</Data>
    <Data Name="ProcessPid">5040</Data>
    <Data Name="OldSchemeGuid">{8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c}</Data>
    <Data Name="NewSchemeGuid">{8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c}</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-UserModePowerService
Date:          11/03/2024 04:22:04
Event ID:      12
Task Category: (10)
Level:         Information
Keywords:     
User:          SYSTEM
Computer:      X670e
Description:
Process C:\Windows\System32\DriverStore\FileRepository\u0398290.inf_amd64_7f51193690ed6a83\B397300\atieclxx.exe (process ID:5040) reset policy scheme from {8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c} to {8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c}
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-UserModePowerService" Guid="{ce8dee0b-d539-4000-b0f8-77bed049c590}" />
    <EventID>12</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>10</Task>
    <Opcode>0</Opcode>
    <Keywords>0x4000000000000000</Keywords>
    <TimeCreated SystemTime="2024-03-11T04:22:04.7886956Z" />
    <EventRecordID>43261</EventRecordID>
    <Correlation />
    <Execution ProcessID="1328" ThreadID="2964" />
    <Channel>System</Channel>
    <Computer>X670e</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <EventData>
    <Data Name="ProcessPath">C:\Windows\System32\DriverStore\FileRepository\u0398290.inf_amd64_7f51193690ed6a83\B397300\atieclxx.exe</Data>
    <Data Name="ProcessPid">5040</Data>
    <Data Name="OldSchemeGuid">{8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c}</Data>
    <Data Name="NewSchemeGuid">{8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c}</Data>
  </EventData>
</Event>
 
JonRGV250 said:
I had a very similar problem with my Cablemods piece of trash cable (black screen and 100% fan spin).
The second I binned it and fitted a Corsair cable my problems vanished.
Click to expand...
Yup. After I re-seated the CableMod 12VHPWR cable a week ago now, I have had 0 black screens. Had the PC running for many hours at a time, 14 one day and not one un-scheduled shutdown. I changed nothing else, apart from the already changed settings that didn't help. I still get the occasional green flicker but it's good to have the PC running reliably again. :D
 
JonRGV250 said:
Awesome :)
I'd contact Cablemods and they should send you a new one if you explain what'd happened.
Click to expand...
Yeah I might as well, it's been over a year but it's worth a try.

So I've still not had any black screens or unexpected shutdowns, just the screen flickering like before. Today I put the PC to sleep and when I woke it up, it started flickering like crazy. Restarted and it went way...not sure if this is caused by the cable or the OS.
 
Solved! I've been having similar issues with my 4090. Random Green/Black screen. PC restarting etc. I went through every troubleshooting forum advise I could find, including clean windows installs, BIOS changes and updates, new HDMI cables, investigating nvlddmkm errors... None worked.
Resolution: Replace the supplied GPU power adapter/cable for a single individually sleeved 16-Pin PCIe cable. The 4090 comes with that ridiculous octopus power adapter that I'm not surprised caused issues. Replacing that for an individual cable capable of providing the appropriate power resolved the issue. Plus it looks a lot better aesthetically.
The specific cable I bought was: Corsair Premium Black Individually Sleeved 16-Pin PCIe 5.0 PSU Cable 600W TDP.
 
LB001 said:
Solved! I've been having similar issues with my 4090. Random Green/Black screen. PC restarting etc. I went through every troubleshooting forum advise I could find, including clean windows installs, BIOS changes and updates, new HDMI cables, investigating nvlddmkm errors... None worked.
Resolution: Replace the supplied GPU power adapter/cable for a single individually sleeved 16-Pin PCIe cable. The 4090 comes with that ridiculous octopus power adapter that I'm not surprised caused issues. Replacing that for an individual cable capable of providing the appropriate power resolved the issue. Plus it looks a lot better aesthetically.
The specific cable I bought was: Corsair Premium Black Individually Sleeved 16-Pin PCIe 5.0 PSU Cable 600W TDP.
Click to expand...
weird that the nvidia supplied one caused issues its normally third party ones, yeah thats the cable i got too
 
You must log in or register to reply here.
Back
Top Bottom