#2 x Monitor, Black Screens, Driver Crash - 5080, 14700K

1 messages · Page 1 of 1 (latest)

simple cradle
#

Hello guys,

Just wanted to share my experience -

This "may" have started after installing the Win 11 24H2 May Update KB5058411 as the first bank of errors occurred the day I installed this update.

MSI Carbon WIFI Z790 Mobo
Intel 14700K
MSI 5080 Suprim OC
CORSAIR RM1000e (2025) Fully Modular Low-Noise ATX Power Supply with 12V-2x6 Cable – ATX 3.1 & PCIe 5.1
Dell AW2725DF @ 360Hz (main display)
ASUS PG279Q @ 60Hz (portrait mode, second display)
Both screens connected via DP
GSYNC enabled for full screen (the Dell is not certified)
Nvidia Driver 576.52 (latest)

Card is connected via supplied PSU 12V-2x6 cable and properly seated. OCCT power test indicated no issues.

Symptoms -

This has occurred when playing PUBG and possibly interacting with another app on the second screen (Discord mostly). It has also occurred now twice when I was on a Teams video call and dragged a remote desktop session from my second display to my main display.

Main display goes white(!), second display goes black, audio still plays, get the Windows plugging something in sound, after 30-60 seconds both screens come back online.

Event Viewer shows (in order)

Event 153: UCodeReset TDR occurred on GPUID:100

Event 14: \Device\Video3
32248a07 00035388 00000000 206a446c 2069db3a 2069d51c 2069fc64 2069fbc2

Event 153: \Device\Video3
Error occurred on GPUID: 100

Event 153:\Device\Video3
GpuRcReset TDR occurred on GPUID:100

Event 14: \Device\Video3
GPU recovery action changed from 0x0 (None) to 0x1 (GPU Reset Required)

Event 153: \Device\Video3
GpuRcReset TDR occurred on GPUID:100

Event 153: \Device\Video3
Resetting TDR occurred on GPUID:100

Event 153: \Device\Video3
Reset TDR occurred on GPUID:100

Event 153: \Device\Video3
Restarting TDR occurred on GPUID:100

The system then seems to recover.

Today, I have implemented the following changes to test:

Set GPU to max power
Spaced DP connectors
Installed missing Intel ME driver
Applied DWM-MPO reg fix -

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Dwm]

"OverlayMinFPS"=dword:00000000

My 2080TI recently died and I bought this card a month ago so I will be REALLY REALLY irritated if this is hardware related 😄

sharp rainBOT
#

If you encounter Code 14 or Code 153 within the Device Status of your GPU in your Device Manager or if you are having crashes when your PC is on idle or on heavy load, it means that your GPU is having issues with power management especially from PCIe connections. Please try the following remedial methods:

  • Removing existing Nvidia drivers with DDU and reinstalling Nvidia drivers manually.
  • Ensure all other drivers such as Chipset/IO/ME drivers are installed through the manufacturer’s website.
  • Disabling Active-state power management (ASPM) through the BIOS. Please consult the motherboard manual for details.
  • Disabling Fast Startup. You can disable Fast Startup by going to Control Panel > Power Options (Make sure View By is set to Small Icons) > Choose what closing the lid does > Change settings that are currently not available, and untick Turn On Fast Startup. Please restart your computer after that.
  • Disabling Link State Power Management. You can disable Link State Power Management by going to going to Control Panel > Power Options (Make sure View By is set to Small Icons) > Select Change Plan Setting (The selected power plan) > Change advanced power settings > PCI Express > Link State Power Management > Set both to Off.
  • Disable Nvidia Power Management. You can go to the Nvidia Control Panel > Manage 3D settings > Power Management Mode is set to “Prefer Maximum Performance”. Please note that your GPU will use more power and your clock speeds will remain high even on idle.
  • Rollback the driver to the previous version.

If all these methods still fail to fix your GPU, you may require to RMA your GPU for a replacement.

#

Please update your drivers as soon as possible to minimize the potential of issues cropping up. Many issues were fixed with 576.52 or newer drivers.

Current driver: 576.52

Hardware conflicts

  • Blackout/instability/undetected issues- If the PCIe slot used by the GPU is set to PCIe 5.0/auto try forcing the slot to PCIe 4.0 in the motherboard BIOS. If a PCIe riser is being used, temporarily remove the PCIe riser and try the GPU directly in the PCIe slot
  • Stuck in a PCIe mode e.g. PCIe 1.1 (Poor performance/Shown in GPU-Z) - Try changing ASPM/PEG-ASPM i.e. set to L0 and/or try setting Native ASPM to OS Controlled in the motherboard BIOS.
  • Poor performance & lower than average clock speeds - Disable NVIDIA App auto-tuning. If you are using MSI Afterburner, please disable "Unlock voltage control", "Unlock voltage monitoring" and "Force constant voltage" in the settings menu, reset/reinstall MSI Afterburner and restart your computer.

Driver bugs

  • [RTX 50 series] Dragons Dogma 2 displays shadow flicker [5252205]
  • [RTX 50 series] Video playback in a web browser may show brief red/green flash corruption [5241341]
  • [RTX 50 series] Enshrouded crashes after launching game [5279848]
  • [NVIDIA App] Adding an unsupported app to NVIDIA App and enabling Smooth Motion forces it globally to other apps [5243686]
  • [RTX 50 series][Battlefield 2042] Random square artifacts may appear around lights during gameplay [5284105]
  • [NVIDIA App] Setting "DLSS Override - Model Presets" to "Latest" and "DLSS Override - Frame Generation" to "Use the 3D application setting" forces 2x Frame Generation mode regardless of in-game setting [5214136]
#

Some Intel 13th/14th gen desktop CPUs (unlocked CPUs, as well as locked i7/i9), may have stability issues due to excessive voltages, on out of date BIOS/microcode. This may show up as errors, crashes, and BSODs. In some occasions, this error may blame a different part (e.g. out of video memory) despite it being caused by a defective CPU.

Common things that may fail with a defective CPU include the following, and more:

  • Crashes during shader compilation
  • Crashes during decompression (game loading)
  • Crashes during driver installation/updates

Please go to these Intel Community threads for further information: https://community.intel.com/t5/Blogs/Tech-Innovation/Client/Intel-Core-13th-and-14th-Gen-Desktop-Instability-Root-Cause/post/1633446#M40
https://community.intel.com/t5/Processors/Intel-Core-13th-and-14th-Gen-Vmin-Shift-Instabilty-Update-New/m-p/1686948

To prevent damage to your CPU and possibly restore stability, please perform a BIOS/firmware update for your motherboard (or system, if this is a name-brand pre-build system).

  • At a minimum, to a version containing the 0x12B microcode or newer.
  • Ideally, and if offered, have the supplementary 0x12F microcode or newer.

You can check the support pages for your motherboard/system model for any BIOS updates you may need. Below are a few common motherboard manufacturers:
ASRock
Asus
Gigabyte
MSI

If your CPU is currently exhibiting instability even after performing BIOS/firmware and microcode updates, please contact Intel or your system builder for a warranty exchange (RMA), as your CPU may be permanently damaged.

ancient wing
#

make sure that all possible causes of instability are addressed

simple cradle
#

Thanks, appreciate the help! ASPM was set to OS controlled in the BIOS so have adjusted. Will test and report back in due course.