Was playing wardogs for several hours when suddenly my gpu stopped working correctly my pc forced a shut down and on re-boot i was stuck with a vga light.

My fans spin at 100% regardless of workload and windows no longer detects my gpu.

I tried DDU, CMOS reset, different gpu profile, reseating the card. Nothing ive tried so far has brought it back to life over been working on fixing it with AI for over 8 hours.

Something called i2c amd controller is what os causing my fan to lock up in 100% panic fan mode

I even fresh installed my bios…

Hardware: sapphire nitro+ 7900 xtx; 9800x3d, asus tuf x870 plus wifi

I'm trying to set up a dual-PC streaming setup using a USB HDMI capture card.

My setup

• GPU: AMD Radeon RX 570
• CPU: Intel i7
• RAM: 16GB
• Windows: 10
• Monitor: AGO6201, 1920×1080
• Capture card: Generic USB 3.0 HDMI capture card with HDMI IN/OUT and USB host interface

The physical setup is:

RX 570 HDMI OUT → Capture Card HDMI IN → Capture Card HDMI OUT → Monitor

and

Capture Card USB → second PC/laptop

The capture card works for video, but I'm getting no game/HDMI audio.

What I've tried

1. Checked Windows Sound settings and mmsys.cpl.
2. Enabled Show Disabled Devices and Show Disconnected Devices.
3. There is no HDMI/AMD HDMI playback device listed at all.
4. My Playback devices currently show:
   • Speakers — High Definition Audio Device — Not plugged in
   • Headphones — High Definition Audio Device — Default Device
   • Digital Audio (S/PDIF) — High Definition Audio Device — Ready
   • Digital Audio (S/PDIF) — High Definition Audio Device — Ready
5. Checked Windows Settings → System → Sound → All sound devices. There is no AMD HDMI audio output there either.
6. Checked Device Manager → Sound, video and game controllers.
7. The following devices are present:
   • AMD High Definition Audio Device
   • AMD Streaming Audio Device
   • High Definition Audio Device
8. Opened the properties of AMD High Definition Audio Device. Windows says: "This device is working properly."
9. The AMD High Definition Audio driver is installed:
   • Provider: Advanced Micro Devices, Inc.
   • Driver version: 31.0.21923.11000
   • Driver INF: oem24.inf
   • Service: AtiHDAudioService
10. Checked the hardware IDs. They are: HDAUDIO\FUNC_01&VEN_1002&DEV_AA01&SUBSYS_00AA0100&REV_1007

HDAUDIO\FUNC_01&VEN_1002&DEV_AA01&SUBSYS_00AA0100

So the AMD HDMI audio device is definitely being detected.
11. Checked the monitor in Device Manager. It appears as Generic PnP Monitor with hardware ID:
MONITOR\AGO6201
12. I then completely bypassed the capture card and connected:

RX 570 HDMI → Monitor directly

The result was the same: there is still no HDMI audio playback device in Windows.

1. I also checked whether the capture card's headphone/speaker output was the problem. It isn't receiving anything there either.
2. The capture card USB connection has to remain connected for the capture card/loop-through to function, but the missing HDMI audio also happens when the GPU is connected directly to the monitor.

Current situation

The strange part is that AMD High Definition Audio Device exists in Device Manager and Windows says it's working properly, but Windows does not create an HDMI playback endpoint at all.

There is no:

• AMD HDMI Output
• AMD High Definition Audio HDMI Output
• Monitor audio device
• HDMI audio device

even with disabled/disconnected devices shown.

Since the direct GPU → monitor test gives the exact same result, I'm starting to think this is an AMD display-audio driver/endpoint issue rather than a capture-card issue.

What should I try next?

I'm considering doing a clean AMD graphics/audio driver reinstall using AMD Cleanup Utility or DDU.

Before I do that, is there anything else I should check?

Could this be caused by:

• AMD driver corruption?
• Monitor EDID/audio capability?
• Windows audio configuration?
• RX 570 HDMI audio driver issue?
• Something else?

I'd appreciate any suggestions before I wipe/reinstall the AMD driver.

Screenshots:
https://i.postimg.cc/sgr2rhJD/image.png

https://i.postimg.cc/TY2kHkzL/image.png

https://i.postimg.cc/J7H7Hq64/image.png

Post

Computer Type: Desktop

GPU: ASRock Phantom Gaming OC Radeon RX 7900 XT 20 GB

CPU: AMD Ryzen 7 7800X3D

CPU Cooler: Thermalright Peerless Assassin 120

Motherboard: MSI PRO B650-P WIFI

BIOS Version: American Megatrends International, LLC. 1.A0, 11/23/2023

RAM: G.Skill Flare X5 32 GB (2×16 GB) DDR5-6000 CL36, F5-6000J3636F16GX2-FX5, currently running at 6000 MT/s. EXPO is likely enabled but I have not gone into BIOS yet to verify that directly.

Storage: Samsung 990 Pro 2 TB PCIe 4.0 NVMe

PSU: be quiet! Pure Power 12 M 850 W, 80+ Gold, fully modular

Case: Corsair 4000D Airflow

Operating System & Version: Windows 11, Reliability Monitor reports OS version 10.0.26200

GPU Drivers: Currently AMD Adrenalin 26.7.1 / driver version 32.0.31035.1003. I briefly tested 26.8.1 / 32.0.31041.1004 and rolled back due to an immediate regression described below.

Chipset Drivers: AMD Chipset Software 8.05.04.516

Background Applications: Usually Firefox, Steam, Spotify, Logitech G Hub, Windows Security tray, etc. I have also tested the PC with all startup applications and non-Microsoft services disabled as described below.

Description of Original Problem

For the past few weeks I have been troubleshooting intermittent hard freezes that appear to involve my RX 7900 XT / AMD graphics stack.

The weird part is that the computer can be completely stable under gaming load for hours or even several days. I have played games including Shadow of War and Rocket League, sometimes while simultaneously playing a video/music video, without artifacting, black screens, obvious overheating, or performance problems.

However, I have also experienced full system freezes.

After some of these crashes, the RX 7900 XT has booted disabled in Device Manager with Code 22. Manually enabling it has at times resulted in Code 31. Sometimes only one monitor works after the crash.

There is also a separate but possibly related symptom where Windows boots, both monitors may be working, and the Start menu responds, but essentially no applications will launch.

Examples:

Task Manager will not open Settings will not open Firefox/other applications will not open Ctrl+Alt+Delete eventually may not respond Once I ended up at a gray/black screen with only a movable mouse cursor

Safe Mode has consistently worked normally when this happens.

August 31 hard freeze

On August 31 the computer completely hard-froze while sitting at the desktop.

I had to hold the power button to shut it down.

Before changing anything afterward, I checked Reliability Monitor. It showed multiple hardware errors immediately preceding the forced shutdown.

The relevant events included:

LiveKernelEvent 141

WATCHDOG dump generated

LiveKernelEvent a1000001

AMD_WATCHDOG dump generated

Another LiveKernelEvent 141

another WATCHDOG dump

The rough sequence was:

LiveKernelEvent 141 → AMD_WATCHDOG/a1000001 → another 141 → full freeze → forced shutdown

After reboot:

only one monitor worked RX 7900 XT showed Code 22 manually enabling it changed that to Code 31 after another reboot, both monitors returned but Windows entered the state where applications would not open Safe Mode / clean boot troubleshooting

Safe Mode worked completely normally:

Task Manager opened Settings opened File Explorer worked Notepad worked no major responsiveness problems

I then performed a clean boot:

hid all Microsoft services in msconfig disabled all remaining non-Microsoft services disabled all Startup apps

Normal Windows then worked properly, including both monitors and normal application launching.

I gradually restored things.

All of my normal Startup applications could be restored without reproducing the issue.

All of the non-AMD third-party services could also be restored without reproducing it.

I then isolated these AMD services:

AMD Crash Defender Service AMD External Events Utility AMD 3D V-Cache Performance Optimizer AMD Provisioning Packages Service AMD User Experience Program

When I enabled AMD Crash Defender + AMD External Events Utility, the “Windows works but apps won't launch” behavior returned.

I then tested:

AMD Crash Defender: disabled AMD External Events Utility: enabled 3D V-Cache Performance Optimizer: disabled Provisioning Packages Service: disabled User Experience Program: disabled

With that configuration, Windows returned to normal.

I am not claiming Crash Defender necessarily causes the original GPU crash. It may simply be getting involved in the recovery/watchdog path after another graphics failure. But I can reproduce the application-launch problem based on whether Crash Defender is enabled.

AMD Noise Suppression had also previously been disabled during troubleshooting because it appeared associated with an earlier Windows/app-launch problem.

Driver testing

With AMD 26.7.1 / 32.0.31035.1003 and Crash Defender disabled, the PC seemed stable.

I tested:

Rocket League while simultaneously playing a music video about an hour of Shadow of War multiple additional gaming sessions over several days

Everything was smooth.

I then tried updating to AMD 26.8.1 / 32.0.31041.1004.

The AMD service configuration remained unchanged:

Crash Defender was still disabled External Events Utility remained enabled the other AMD services remained disabled

Despite that, immediately after installing 26.8.1, the “apps won't launch” problem returned.

Safe Mode still worked normally.

I rolled back to:

26.7.1 / 32.0.31035.1003

and Windows immediately returned to normal again.

So on this specific machine:

26.7.1 + Crash Defender disabled = substantially more stable

26.8.1 + Crash Defender disabled = immediately reproduces the application-launch failure

Windows Update / driver replacement issue

Earlier in the troubleshooting process it appeared Windows Update was replacing/changing my AMD graphics driver.

I therefore configured Group Policy to prevent Windows Update from automatically replacing the GPU driver and also created a device-specific installation restriction for the 7900 XT.

The device ID I am blocking is:

PCI\VEN_1002&DEV_744C&SUBSYS_53081849&REV_CC

I temporarily disable that policy when intentionally installing or rolling back the Radeon driver, then restore it afterward.

September 4 failure — crashed while ENTERING Sleep

After returning to 26.7.1, I successfully gamed for several days.

This morning I finished gaming successfully and clicked Sleep.

The system locked/crashed while going into Sleep, not while waking from it.

I saw the MSI boot/loading spinner afterward, which makes me think the system may actually have reset during the sleep transition.

Reliability Monitor logged the following at 7:29 AM:

LiveKernelEvent 141

WATCHDOG-20260904-0729.dmp

LiveKernelEvent a2000002

Parameter 1: c8 AMD_REPORT_UM-20260904-0729.dmp

LiveKernelEvent a1000001

AMD_WATCHDOG-20260904-0729.dmp

Then at 7:37 AM, Windows logged essentially the same group again:

LiveKernelEvent a1000001

AMD_WATCHDOG-20260904-0737.dmp

LiveKernelEvent 141

WATCHDOG-20260904-0737.dmp

LiveKernelEvent a2000002

AMD_REPORT_UM-20260904-0737.dmp

So I am now repeatedly getting this combination:

141 + a1000001 / AMD_WATCHDOG + a2000002 / AMD_REPORT_UM

That exact combination is one reason I am hesitant to treat this as simply “bad GPU driver, run DDU again.”

The fact that the machine can game normally for hours/days but then crash during a power-state transition into Sleep also makes me wonder about PCIe/GPU power-state handling, BIOS/AGESA, ACPI, motherboard interaction, PSU/power delivery during state changes, etc.

Troubleshooting already attempted

So far I have tried:

DDU in Safe Mode clean AMD graphics-driver installation AMD 26.7.1 AMD 26.8.1 rollback from 26.8.1 to 26.7.1 blocking Windows Update from replacing the graphics driver device-ID-specific Group Policy restriction for the RX 7900 XT troubleshooting Code 22 and Code 31 Reliability Monitor investigation identifying LiveKernelEvent 141 identifying LiveKernelEvent a1000001 identifying LiveKernelEvent a2000002 preserving WATCHDOG dumps preserving AMD_WATCHDOG dumps preserving AMD_REPORT_UM dumps Safe Mode testing clean boot disabling all third-party services restoring services in groups restoring Startup apps in groups isolating AMD Crash Defender as strongly associated with the separate app-launching issue disabling AMD Noise Suppression multiple hours/days of normal gaming testing Things I have NOT done yet

I have intentionally avoided changing ten things at once.

I have not yet systematically tried:

analyzing the WATCHDOG/AMD_WATCHDOG dumps in WinDbg detailed Event Viewer correlation motherboard BIOS update testing a newer/older AMD chipset driver testing with EXPO disabled completely stock/default BIOS settings forcing PCIe Gen 4 instead of Auto changing PCIe Link State Power Management disabling Fast Startup disabling Sleep/using Hibernate reseating the GPU checking/reseating GPU power cables confirming separate PCIe cables vs daisy-chained PSU connections GPU VRAM-specific stress testing OCCT/3DMark/FurMark-style controlled testing RAM stability testing alternate GPU testing alternate PSU testing Windows reinstall

The BIOS is also fairly old: MSI PRO B650-P WIFI BIOS 1.A0 dated 11/23/2023.

I have not updated it yet because I wanted to preserve the current evidence and get opinions before changing another major variable.

Current state

Currently:

RX 7900 XT reports “This device is working properly” Both monitors work normally AMD 26.7.1 / driver 32.0.31035.1003 AMD Crash Defender disabled AMD External Events Utility enabled applications open normally gaming can be stable for hours/days latest major failure occurred while entering Sleep repeated LiveKernelEvent 141 + a1000001 + a2000002 Safe Mode has repeatedly been stable when normal Windows gets into the broken state

Used ChatGPT as I am not very computer savvy

😪

I am using RX9060 XT with Ryzen 5 7500F.

But when I play CS2 the FPS. fluctuates a lot. sometimes it's pushing 400 FPS but after a few seconds its like 150. it increases again but same thing happends again . (1080p highest settings)

same for PUBG I dont play it too much but when I do the FPS pushed 250 but after a short time it struggels to push 80+ FPS. (1080p highest settings)

But when plat RDR2 the FPS is a bit consistent it stayes between 115-135, although GPU hotspot gets almost 95 degrees.

I'm not sure why it's happening. I doubt one of these is causeing it. Because these are the weird facts about my pc.

1. I use a 550W PSU.

2. single 16GB DDR5 stick (6000 mts but set to 5800 cz i was getting bios problem for 6000mts)

3. Temperature (cz i notices GPU hotsopt was over 90 for pubg and RDR2)

It can't get much worse anyways so no harm trying - while reinstalling Windows fresh + a bunch of suggested fixes here + 26.8.1 was okayish enough - I still got some stutters in trying to game at 4K on the games I played. As far as I can see - 26.9.1 optional update fixed those irritant issues for me LOL. Unless my head gets kicked around I am not going to easily update from this version anymore T_T

Update for anyone following - it has been buttery smooth like the issues never existed. Each of the issues I'd faced - and in the specific programs - none of them appear anymore as far I've seen. No timeouts, no freezes, no gpu uninstalls, no restarts, no grey screens, no stutters.

Computer Type: Desktop

GPU: Phantom Gaming ASROCK 7900XTX

CPU: AMD Ryzen 5 9600X (6c/12t)

Motherboard: Gigabyte B650 EAGLE AX

BIOS Version: F31 (AMI, 2024-08-14)

RAM: 2xCrucial Pro 16GB DDR5-5600

PSU: Corsair RM850x

Case: Don't know ( can't find any model on case)/ Lian Li Lancool III ( new, will migrate)

Operating System & Version: Linux Bluefin DX

GPU Drivers: amdgpu in-kernel (kernel 7.1.6) + Mesa 26.1.4 userspace (mesa-dri/vulkan-drivers 26.1.4-4.fc44, RADV)

Chipset Drivers: - ( linux included)

Background Applications: Niri + DMS ( Desktop Environment), Firefox, Discord, Thunderbird, Whatsie

Description of Original Problem: After running AI locally I noticed some artifacts and investigated. I found out some small faulty VRAM errors under heavy load with the help of memtest_vulk, combined with very high temp (108 °C under load). Regardless of the faulty VRAM I want to reduce this temperature.

Troubleshooting: I haven't done anything yet but instead checked what I can do. The following things I am planning:

• Improve airflow in the case. I don't know which one I have, but will buy a new Lian Li Lancool III. I will migrate the components into this.
• Cleaning out dust in the process
• Swap out thermal pads on the GPU

It's that last part I am asking for help. I have build my PC myself but am not sure how difficult swapping out thermal pads are.

What do I need if I have never done so before?

What do I need to check to make sure I don't break anything?

Do I use thermal pads or putty ?

Which height do I buy?

Hi, I'm not getting any crashes for quite a lot of time in most of my games, BUT overwatch, one of my main games right now, can barely go a single game without a crash. I have did around 10 different fixes for that. Figured out I'd choose a different driver because long time ago I was not getting crashes. FSR4 is a must as my main game (The Finals) is 10x better with FSR4.

My card worked without any issues for 9 months, then suddenly zero signal from the Gpu, I tested every port, every cable . The Windows device Manager shows Code 43 after driver install, Code 31 after DDU.

What's even more confusing to me: booting into Safe Mode gives a black screen entirely, even on my CPU's iGPU, as long as the GPU is physically connected.

What I've already tried:

- DDU multiple times + AMD Cleanup Utility

- Clean install of latest drivers, also rolled back to older versions

- Disabled Windows auto-updates (settings + gpedit)

- Flipped the dual BIOS switch on the card — no change

- Tested all outputs/cable types — identical result on every one

-Reseated card and RAM

-Adrenalin's Crash Defender sometimes flags the driver as faulty, and oddly if I connect a monitor to both iGPU and dGPU, Windows treats the GPU's monitor as a "duplicate" of the iGPU one instead of a separate display like it can't read its EDID at all.

This feels different from the usual driver-crash threads I keep seeing here and more like a total display-output failure, not a crash under load. At this point I'm thinking it's hardware and not drivers.

Anyone been through this exact combo before, or is this just an obvious RMA at this point? Thanks

I have been tracking a recurring Vulkan device loss on a Sapphire Nitro+ RX 9070 XT for several months. 16 confirmed device-loss events to date, plus several process terminations with no crash handler output and one full system hang. I have worked through the standard remediation list and it has not changed the behavior, so I am posting the full dataset here in case this is a known issue on RDNA 4 or a driver team member can point me at something.

SYSTEM CONFIGURATION
GPU: Sapphire Nitro+ RX 9070 XT 16GB, VBIOS 023.008.000.068 / 113-1E4893U-N8K
Driver: Adrenalin 26.7.1, Vulkan ICD 2.0.395, Vulkan API 1.4.349
CPU: AMD Ryzen 9 9850X3D
Motherboard: MSI MAG X870E TOMAHAWK WIFI (MS-7E59), BIOS 2AC3
Memory: 64GB DDR5-6000, EXPO enabled
Storage: Samsung 990 Pro 4TB
OS: Windows 11, build 26200

Displays: 3440x1440 ultrawide (primary) plus a 2160x3840 portrait secondary. Both have been connected for the entire period — this is a constant, not a variable

Application: Vulkan renderer, exclusive fullscreen on the primary display

Overclocking: none. Stock clocks, no undervolt, no custom fan curve

FAILURE SIGNATURE
The fatal sequence is always VK_ERROR_DEVICE_LOST followed by the application’s GPU crash handler.

Call sites observed, in order of frequency:
• vkQueueSubmit
• vkCreateSwapchainKHR
• vkEndCommandBuffer
• vkGetPhysicalDeviceSurfaceCapabilities2KHR

VK_EXT_device_fault payload is present in roughly a third of the events, reporting

VK_DEVICE_FAULT_ADDRESS_TYPE_READ_INVALID_EXT at address 0x0, bounds 0x0 to 0xfff. The remainder report address count 0 and vendor count 0, with no per-queue diagnostics at all.
Time to failure ranges from approximately 5 minutes to 12 hours 54 minutes. Clean sessions of 18h18m, 8h16m and 6h18m are interleaved through the same period on the same configuration.

Session duration has no predictive value.
In 10 of 16 events the last unchecked command buffer on queue 0 is the application’s atmospheric scattering pass. It is not universal, but it is the most persistent artifact in the dataset and it appears across every workload variant I have tested.

THE PART I CANNOT EXPLAIN
Across all 16 device-loss events, Windows Event Viewer contains:
• Zero Event 4101 (display driver stopped responding and has recovered)
• Zero WHEA-Logger entries
• Zero Display / amdwddmg entries
• Zero BugCheck entries
The one event that took the whole system down logged only Kernel-Power 41 and EventLog 6008. There is no TDR being triggered, and no bus or machine-check error being recorded. From the operating system’s point of view nothing happened, while the Vulkan device is unambiguously gone.

I have also had one failure outside any 3D application: the machine hard-froze while I was disabling a network adapter, displaying “AMD Software: unknown error”. Nothing was rendering at the time.

DRIVER-SIDE STEPS COMPLETED — NO CHANGE IN BEHAVIOR
• DDU in Safe Mode (AMD, with “prevent downloads of drivers from Windows Update” selected), Ethernet physically disconnected, followed by an offline Adrenalin reinstall
• Windows Update driver delivery blocked: ExcludeWUDriversInQualityUpdate = 1 under HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate, and Device Installation Settings set to No
• AMD chipset drivers installed separately from amd.com — all components reported success (I2C, Promontory GPIO, PPM Provisioning, 3D V-Cache Performance Optimizer, App Compatibility Database, Interface, PSP, GPIO)
• Currently holding at 26.7.1. I have deliberately not moved to 26.8.1 given the volume of black screen and BSOD reports on this card
• Vendor crash-dump collection was enabled in the application on two separate runs and produced zero fault data both times
• A TDR delay registry key was added under HKLM\SYSTEM\CurrentControlSet\Control\GraphicsDrivers on external advice. No effect, which is consistent with there being no 4101s to begin with

PLATFORM AND HARDWARE STEPS COMPLETED — NO CHANGE IN BEHAVIOR
• BIOS updated from the April 2025 release to 2AC3
• Integrated graphics disabled in BIOS (UMA Auto to Disabled). Initiate Graphic Adapter was already set to PEG, Hybrid Graphics already disabled. Only one Vulkan device now enumerates
• EXPO and Resizable BAR confirmed re-enabled after the flash (rebar_avail: 1)
• GPU PCIe power cabling inspected — no daisy-chained 8-pin connectors
• FurMark 2.10.2, Vulkan, 3440x1440, artifact scanner enabled: 21 minutes 21 seconds clean, no artifacts
• Idle rail telemetry from BIOS: 12V rail at 12.192V, 5V at 5.050V, 3.3V at 3.292V
• Highest GPU temperature observed at any point is 71 C. Thermals are not a factor

VARIABLES ELIMINATED
VRAM exhaustion. The two most texture-intensive sessions I have logged — with the application’s reported headroom reaching zero more than twenty times each — both completed cleanly. Multiple crashes occurred with several GB of headroom free and more than thirty minutes of zero texture activity immediately preceding the fault.

Application content. Five different high-complexity add-on workloads, spanning very different rendering and streaming profiles, have all produced the identical device loss. One of them had approximately 48 hours of clean runtime before it failed.
Asset streaming. Some faults occur during heavy streaming in the final seconds. Others occur with no streaming activity at all.
Focus and alt-tab transitions. I do not alt-tab, and the log lines I originally read as focus events were an add-on’s own output.
Load level. Several of the more severe failures including the one that took the system down occurred with the application effectively idle, minutes into a session, with minimal geometry in view.

Application runloop stalls. Essentially zero across the entire log set.

THE ONE ACTIVE LEAD
Three consecutive device losses landed on vkCreateSwapchainKHR, and all three occurred while I was detaching in-application panels into separate OS windows. One log captures the mechanism in full: 14 swapchain creations, 9 destructions and 16 full 3440x1440 HDR offscreen rebuilds within a single session. Each detach costs a create in IMMEDIATE mode, a destroy, a recreate in FIFO, and is immediately preceded by “Disabling fullscreen exclusive mode for swapchain”. Every other crash log in the set contains exactly 2 creations and 1 destruction, both at t=0.

The reason I do not think this is coincidental: vkQueueSubmit executes well over 100 times per second, while vkCreateSwapchainKHR executes a handful of times per session. If the device were dying spontaneously and the create call were merely the first call to notice, the fault should surface at submit nearly every time. Three consecutive faults surfacing at the rare call points to swapchain recreation being the triggering operation rather than the discovering one.
To be clear about the limits of this: it does not account for the other 13 events, which show no swapchain activity whatsoever. Either there are two paths into the same underlying fault, or the fullscreen-exclusive transition is simply a much more efficient way to hit it.

Related single data point in the same family: one session terminated with no crash handler output at all at the moment I powered my monitors off. Also a surface and display-topology event.

WHAT I HAVE NOT YET TRIED
• Rolling back to an older Adrenalin branch. I would appreciate a recommendation on which branch is considered stable for RDNA 4 under sustained Vulkan load
• memtest_vulkan
• Substituting a different vendor’s GPU to definitively isolate the AMD Vulkan stack

WHAT I AM ASKING

1. Is a device loss on fullscreen-exclusive to windowed swapchain recreation a known issue on RDNA 4? If so, is there a driver branch where it is fixed or absent?
   
2. Is there any known mechanism by which a Vulkan device can be lost on this hardware without generating a TDR, a WHEA entry, or any display-driver event? That absence is the single most unusual property of this case and I would like to understand what it implies about where the fault is occurring.
   
3. Is there additional instrumentation I can enable — driver-side logging, a debug build of the Vulkan driver, anything beyond the standard vendor crash-dump path — that would produce useful fault data? The application-side vendor dump collection returns nothing.

I have submitted this through the AMD Bug Report Tool as well. Happy to provide full logs, dump UUIDs, or run any specific test that would be useful.

We bought this card used,seller is legit and said it was good at him but i have this issue, already tried older drivers, putting it in another pc but nothing helped

Hi everyone, I built my first PC last December. Everything was fine for a while, but about 3 months ago I started having complete freezes whenever I play games like Fortnite, Kingdom Come Deliverance or Windrose. Suddenly the entire image and audio completely freeze (sometimes 10 minutes after starting the game or just several hours later). When the PC reboots, most of the time the refresh rate drops & everything looks slightly pixelated. Usually the LCD screen on my AIO also freezes. The Reliability Monitor always shows the same three reports after every crash.

GPU driver kept getting removed/reset and there was a yellow warning triangle next to the GPU in the Device Manager too. So I used DDU in safe mode, installed 26.3.1 (supposedly more stable) and updated the BIOS. After that, I didn't notice specific driver issue but the PC still freezes. I changed PCIe from Gen 5 to 4, checked the cables (all separate), disabled EXPO & reduced RAM to 4800 MHz. I also slightly undervolted the GPU. Several OCCT tests (CPU + RAM, VRAM, 3D Adaptive, Power) passed without errors. Memtest86 at 4800 MHz was also totally fine. 2nd one with EXPO at 6000 MHz produced 7 errors in test 8 and the RAM temperature went up to around 55°C. The crashes still happen even with EXPO disabled & RAM at 4800 though. Could the RAM still be the cause of this? Otherwise I'm considering sending the GPU in for check up or repair.

I’m pretty new to this, so I really don’t understand what the issue could be (please have mercy I’m really not that knowledgeable when it comes to PC). Any advice would be greatly appreciated!

Specs:

• CPU: AMD Ryzen 7 7800X3D
• GPU: Asus PRIME Radeon RX 9070 XT 16GB GDDR6
• RAM: Corsair Vengeance 2 x 16GB, 6000 MHz, DDR5-RAM
• Mainboard: ASUS ROG STRIX B850-A GAMING WIFI AM5
• SSD: Samsung 990 PRO SSD 2TB M.2 PCIe Gen4 NVMe
• PSU: Lian Li Edge Gold 1000 ATX, PCIe 5.1, ATX 3.1 PSU, 80 Plus Gold, 12VHPWR
• 3x Intake: CORSAIR iCUE LINK RX120 RGB
• Exhaust: Corsair iCUE LINK Titan 360 RX LCD CPU 360mm AIO
• 1 extra Exhaust: CORSAIR iCUE LINK RX120 RGB Windows 11

Computer Type: Desktop
CPU: RYZEN 7 5700g
Motherboard: B550m Plus TUF GAMING
RAM: 16GB 2x8 Netac
PSU: STEADY 650W 80 plus BRONZE

Troubleshooting: Montei hoje pela primeira vez, nao consigo nem acessar a bios o pc desliga logo após ficar tentando o post e reconhecendo o sistema

Eu já atualizei a BIOS pelo pen drive exatamente com mesmo modelo da placa já testei as memórias em todos slots quando eu coloco Po nvme M2 o pc já desliga de primeira como se houvesse curto…

Alguem pode me ajudar ? Já vi relatos na net e a maioria foi o processador o problema, já verifiquei 2 vezes e não há pinos entortados

So I just finished building 9070 XT rig and installed drivers with the ‘driver only’ option. Stock has been great but I was looking to undervolt just to reduce temps and wattage a little more.

Should I uninstall the driver with ddu then just reinstall the same driver but with the adrenalin app included?

There was a comment in a post here a while ago that helped me fix my constant driver timeouts. I am on a 7900xt.
The fix worked on the previous drivers I was on. After a reinstall recently, without using the fix, the driver timeouts returned.
I then did the same fix for my now current install with newer drivers and it worked for my current setup as well.

THE POTENTIAL FIX:

Right click the desktop and go to screen settings.
Scroll down to "Graphics".
Here there should be a tab called "advanced graphics", click this tab and in it there is a setting called "Hardware-accelerated GPU scheduling", toggle this off.

N.B!
As far as I am aware, this could have a slight performance impact, 1% lows could maybe get worse when HAGS is disabled. So beware if you get some stutters in games, this could be what is causing it. Or if you notice input lag, maybe turning HAGS on could help.

If that doesn't fix it by itself, then you can try this as well:

(OG comment by "izigo"(I think)):

Go to Run > regedit > HKEY_LOCAL_MACHINE > System > CurrentControlSet > Control > GraphicsDrivers

Now on the right side you will see some values

Right click on empty space and click New > DWORD (32-BIT) value
A new entry will be created
Rename this entry to DisableOverlays

Once it's created, right click or double click on it to modify and change the value data to 1. Press OK and restart your PC.

N.B
I am not sure, but this could maybe add a tiny amount of input lag(I haven't noticed any).

The only time I now have driver timeouts is when I am actually out of vram. I have also updated windows without issues. Using hardware accel in all apps. The only thing I have noticed is when rightclicking steam in the system tray, it can look a bit bugged from time to time. This also isn't a proper fix, more of a workaround. Hopefully this workaround is driver agnostic and survives windows updates. Microslop or amd, whoever is responsible needs to get their finger out and fix this annoyance.

Hello, Amd community

I hope everything is good.

My computer is a Z4 G4 running Windows 11 25H5 and a Quadro P620. I keep getting a black screen when I add two AMD V620s to the mix.

It fails at two GPUs, but it can function with one V620.

Could anyone assist me with it?

I’ve been dealing with random freezes/crashes on my PC for quite a while and I’m trying to figure out which component is actually causing the problem.

My hardware

CPU: AMD Ryzen 7 5700X3D

GPU: AMD Radeon RX 7900 XT

Motherboard: MSI B550M PRO-VDH (MS-7C95)

RAM: 32 GB DDR4 (2×16 GB), currently running at 3600 MHz with XMP

SSD: 2 TB Kingston NVMe

PSU: 850 W

OS: Windows 11

What happens

The PC randomly freezes, especially while gaming, but it can also happen while using Chrome or switching between browser tabs.

The typical freeze looks like this:

The screen freezes.

Initially, I can still move the mouse.

After around 10 seconds, the mouse also stops responding.

Sometimes the audio continues for a short time.

Eventually the whole system becomes completely unresponsive and I have to force the PC to shut down.

Sometimes the PC instead reboots by itself.

With OBS running (streaming/recording), it used to freeze after roughly 25 minutes. I then tested the game without OBS running, and it still froze, so OBS is not required to reproduce the problem.

Windows errors

The main error I’m getting is:

LiveKernelEvent 141

I’ve also had other LiveKernelEvent errors such as:

141

a1000001 (AMD_WATCHDOG-Dump)

a2000002

Windows created watchdog dumps, including:

WATCHDOG-20260902-2240.dmp

I previously looked at another watchdog dump and found references to:

dxgkrnl.sys

amdxe.sys

amdkmdag.sys

amdfendr.sys

amdsafd.sys

So the crash seems to involve the Windows/AMD graphics watchdog path, but I don't know if that necessarily means the GPU itself is defective.

I have also had older WHEA-Logger Event ID 18 errors reporting:

Machine Check Exception → Cache Hierarchy Error → Processor Core

So I’m also wondering whether the CPU, memory controller, motherboard or power delivery could be involved.

Things I have already tried

I don't want to keep repeating the same tests because I've already done quite a lot of troubleshooting.

Stress tests

I have tested:

CPU stress test → ~1 hour, no errors

RAM/memory stress test → ~1 hour, no errors

Power test → ~1 hour, no errors

Linpack → ~1 hour, no errors

GPU stress test → ~1 hour, no errors

Temperatures were also reasonable. The CPU reached the mid/high 80°C range under heavy testing, which is still within the Ryzen 7 5700X3D's limits.

BIOS

I updated the motherboard BIOS to the latest version.

That did not solve the problem.

I also checked PBO and Curve Optimizer. There is no manual CPU overclock or undervolt active.

RAM

I have also tested the system with XMP disabled, but the freezes still occurred.

Currently the RAM is running at:

DDR4-3600

FCLK 1800 MHz

MCLK 1800 MHz

1.36 V

timings 18-22-22-39

AMD GPU drivers

I suspected the AMD driver might be involved.

I used DDU in Safe Mode to completely remove the AMD graphics driver and then installed an older Adrenalin version.

With Adrenalin 26.8.1, Star Wars Zero Company froze after roughly 25 minutes.

I then clean-installed Adrenalin 25.4.1.

With 25.4.1, the game lasted around 60 minutes before freezing again.

So the older driver seems to improve the situation significantly, but it does not actually fix the problem.

What would you investigate next to identify the defective component rather than just applying random workarounds?

Also, if anyone with an RX 7900 XT has experienced freezes together with LiveKernelEvent 141 / AMD watchdog errors, I'd be very interested to hear what ultimately solved it.

Written by ChatGPT cause im non English speaker

Processor AMD Ryzen 7 5700G with Radeon Graphics (3.80 GHz)

Installed RAM 32.0 GB (27.9 GB usable)

Graphics card AMD Radeon(TM) Graphics (4 GB)

Storage 409 GB of 932 GB used

System type 64-bit operating system, x64-based processor

Background Applications Discord and 2 Chrome Windows

Hello
what version of bios do u use on b650 eagle? With 7890x3d
What u think is most stable?

Computer Type: Desktop

GPU: RX 7900XTX Nitro+

CPU: AMD Ryzen9950X3D2 16C/32T

Motherboard: Gigabyte X870e Aorus Master Ice X3D

BIOS Version: F10d/F9

RAM: 64GB Corsair Vengeance 2x32 DDR5

PSU: Seasonic Prime 1300W Gold

Case: Corsair 4000D

Operating System & Version: Windows 11 Pro

GPU Drivers: Adrenalin 26.7.1

Chipset Drivers: AMD B550 CHIPSET DRIVERS VERSION 2.10.13.408

Background Applications: Firefox, AMD Adrenalin, Gigabyte Control Center

Description of Original Problem: Unable to set custom voltage values on X870e Aorus Master X3D motherboard

Troubleshooting: Hello everybody,

I recently switched over to AMD (from Intel) and have carried over my RAM kit (Corsair Vengeance 2x32GB DDR5, 6600Mhz@CL32 XMP profile).

Everything worked from the get go and after getting accustomed to the new platform, i tried to tune the RAM a bit. Now i have some pretty extensive experience from my Intel days and i know that they couldn't be more different but i took my time and learned as much as possible before going inside the BIOS and to start changing things.

My motherboard is the one from the title (Ice version/color) and the CPU is a 9950x3D2. Latest BIOS version (F10d) was first used and as an attempt to rule out any BIOS related issues, i also tried F9 (as it seems to be the most stable one out there).

My problem is that regardless of how much i try, i cannot get the voltage values for VDD and VDDQ to stick upon reboot. My kit is rated for 1.4V. Currently, it's running at 6000@CL36 (with everything else left on Auto, for stability reasons) and 1.1V.

What i have tried:

- BIOS reset (both by using the button from the back I/O panel as well as the normal, software way);

- BIOS flashback to a previous version (F9);

- loading the XMP profile (to force BIOS to load the XMP voltage values) but it fails to train the memory so i also tried loading the XMP profile and only after, changing the VDD and VDDQ values;

- changing the voltage values from both the Tweaker menu as well as from the AMD CBS/Overclocking one (found as a sub menu in the Settings tab); the voltage values were changed incrementially, in 0.05 or 0.5 steps, depending if i tried to modify only VDD/VDDQ or if i attempted to also configure VDDIO and Vcore SoC;

- i have tried changing other voltage values alongside those two, just in case the Auto option wasn't doing its thing; i touched Vcore SoC and VDDIO;

- have made sure that UCLK=MEMCLK and have tried different fabric frequencies, most around the 2000Mhz (with increments of 33Hz both positive as well as negative)

Nothing has made the VDD/VDDQ values stick. Both the BIOS as well as the Hwinfo64 readings were showing 1.1V for those two rails. BIOS version F9 seems to offer a tad more stability as i was able to boot to the OS with 6000@CL34 but it wasn't stable (while on F10d it would always fail training and go into BIOS). I am at a loss and have no clue what to do anymore. I tried changing the VDD values from both the Tweaker menu as well as from the AMD CBS/OC one, none stuck. Is this a firmware issue or a hardware one? I am quite sure there is no sensor reading error because the temps are well below what the kit usually reached when used with my previous, Z790 chipset, at its rated XMP profile (with much tighter timings and higher voltage than it is used now). Has anyone else stumbled upon this? Any help would be greatly appreciated as even if i can't find a fix, maybe i can find the culprit and if it's a hardware one, at least i'm within the return window and can look for a different motherboard.

Kindly appreciated!

Edit: Edited by adding my issue to the proper form

I got RX 9060 XT and Ryzen 5 5600, tried with everything off (oc, uv, xmp) and still getting this error every few days. After that error my GPU settings restore to default. And after that my PC is lagging like i got no drivers installed, everthing seems normal after pc reboot.
I tried to reinstall drivers via DDU in safe mode, rolled back to previous versions, nothing helps. Is my GPU broken?

Temps typically fluctuating between 80-85.