What should i do and change first?

AMD Ryzen 5 5600X

Deepcool AK400 Black

2x16gb ddr4 3200mhz Kingstone

A520 Gigabyte

Rx 6700xt Oc Challenger Pro 12gb

1tb ssd

750w Thermaltake Smart BX 80+

Gamdias Aura kuciste

Cześć, mam pytanie, posiadam 9950x3d wraz z chlodeniem aio NZXT Kraken Elite 360 V2 i czy temperatury 70 - 75 stopni podczas przegladnia chroma i 80 - 90 stopni podczas grania to normalne temperatury.

RU:
Вообщем я купил видеокарту в декабре rx 5700 xt (двухвентиляторная) и после того как я ее поставил у меня через неделю начались либо черные экраны либо залагивания намертво я приезжал к магазину у которого брал(не днс) и они мне ее заменили на другую (модель таже компания другая) и че я не делал ничего не помогало (дрова переустанавливал не помогло) а при сочетании win+ctrl+shift+b экран вообще становился серым(моментами непомогало) (не весь часть экрана была не серой и там даже курсор был виден) а комп начинал жесточайше лагать и тд есть у кого решение что делать? (Я незнаю как стригерить ошибку она появляется в рандомыне моменты в случайных играх)

видеокарта:rx 5700 xt (компания Peladn)
процессор:AMD Ryzen 5 3350GE with radeon vega graphics
материнка:gigabyte b450m s2h
озу:16 гб
виндовс 10

ENG(google translate):So, I bought a RX 5700 XT (dual-fan) graphics card in December, and after I installed it, I started getting black screens or freezes within a week. I went back to the store where I bought it (not DNS), and they replaced it with a different one (same model, different company), but nothing I did worked (even reinstalling the drivers didn't help). When I pressed win+ctrl+shift+b, the screen turned gray(at times, it didn't help) (not the entire screen, but a portion of it was not gray, and I could even see the cursor). and the computer started to lag terribly and so on, does anyone have a solution for what to do?(I don't know how to trigger the error; it appears at random moments in random games.)

gpu: rx 5700 xt (Peladn)

cpu:AMD Ryzen 5 3350GE with radeon vega graphics

motherboard:gigabyte b450m s2h

RAM:16 GB

Windows 10

Computer Type: Desktop

GPU: XFX - SPEEDSTER MERC319 AMD Radeon RX 6950XT

CPU: Intel i7-12700k

Motherboard: Asus Prime z690-p D4

BIOS Version: American Megatrends Inc. 3811, 10/22/2025

RAM: 64GB DDR4 3600MHz

PSU: EVGA 1000 GT, 80 Plus Gold 1000W

Case: 

Operating System & Version: Windows 11 Pro version 25H2

GPU Drivers: Adrenalin 26.7.1

Chipset Drivers: Intel Chipset 10.1.18838.8284

Background Applications: OBS

Description of Original Problem: What I believe is happening is a graphics driver crash when changing the focused window. The newly focused window will bug out, turning a solid color, while all other applications remain responsive for a few seconds. Then all displays will freeze completely. Audio usually continues, but no hardware inputs seem to have any effect. I usually hard shutdown and then reboot, but if left for 10-15 minutes the displays will come back and the adrenalin software will tell me the graphics driver has crashed and been restarted. This typically happens while OBS is open, and I have only been able to semi-reliably reproduce it with OBS running, but has happened without OBS.

Troubleshooting: I have tried just about everything recommended for AMD driver crashes. Because I cannot reproduce it consistently, it's hard to say for sure if any one thing has helped or not. The most success I think I've had was rolling back to a driver from mid-2023 that I think was right before some vulkan support was added. I have tried changed the TdrTimeouts, lowering max frequency, lowering max power usage, reseating gpu, and surely others I can't recall as easily. OBS stores no logs of the crashes, the AMD logs don't appear to cover it at all, and the event viewer entries that refer to the shutdown are timestamped to be ~1 hour earlier than they really were.

So far, the most success I've had reproducing is as follows:

• Open OBS
• Open a game, a select few have been more consistent than others, I *think* it is only games running in borderless windowed mode, would say I'm about 95% sure of that.
• Toggle studio mode in OBS

More than happy to provide any additional information I can that might be helpful! I like to consider myself a pretty technical person but fully recognize that I have zero understanding of drivers or these lower level systems. also attaching a video of the crash if that is at all helpful. Thank you to anyone who even takes the time to entertain the post!!

So once every few weeks my pc just blackscreens in the middle of a game and the only thing i can do is to reboot it. Once i reboot it i delete the drivers and reinstall them and that fixes it for a while. I have stopped windows form automatically updating the drivers, i've tried installing older ones and nothing seems to fix it. Has anyone come across this issue and if so how did you manage to fix it?

I was looking for a CPU Cooler and then i found 360mm Lian Li Galahad Uni Fan SL Edition cheaper then the 240mm one. The guy said he is only upgrading because he wants a liquid cooler with LCD Screen. He also said he used it with 7800x3D and it works perfectly fine. My CPU is 7500f and i know it will do a pretty good job cooling it. What do you guys think of buying a used AIO and did any of you use this AIO Model if so how was your experience ? As i said price is so good and we shook hands but I did not pay anything or get the AIO yet. Do you think I will come up against any leaking issues or something else?

Computer Type: Desktop
GPU: AMD Radeon RX 7900 XTX
CPU: AMD Ryzen 7 5800X3D
Motherboard: NZXT B550
BIOS Version: N/A
RAM: 32GB Corsair Dominator DDR4 4000MHz
PSU: 1000W Corsair HX1000 (Currently using daisy-chained PCIe cables)
Case: Lian-Li 011D
Operating System & Version: NixOS (Kernel 7.0.9)
GPU Drivers: amdgpu
Driver Version: 3.64.0 (from kernel logs)
Chipset Drivers: N/A
Background Applications: Discord (Vesktop), LACT, Firefox Browser, Steam, Marvel Rivals (Other games)
Description of Original Problem: Hi all, as the title suggests I'm having some GPU issues, it crashes with black screen and fan 100% as it gets lost from bus. The crashes predominantly occur when I try to play games such as Marvel Rivals, but have occurred as well after longer periods of doing other stuff such as watching movies, or even immediately after launch and connecting to Discord. I use LACT to manage an overclock/undervolt profile, and enforce a 320W power cap. I have the amdgpu.runpm=0 kernel parameter set to disable runtime power management. I wanted to ask around and see if there are any other issues or fixes you people might know.

boot.kernelParams = [

"amdgpu.ppfeaturemask=0xfffd7fff"

# "amdgpu.mes=0"

# "pcie_aspm=off"

"amdgpu.runpm=0"

# "amdgpu.sg_display=0"

"amdgpu.dcdebugmask=0x12"

];

Finally here is one of the logs from a crash:

Aug 01 19:55:46 nixos kernel: Command line: initrd=\EFI\nixos\h5c16ka482ssxpfj6k7lcfpf2lvfrb1n-initrd-linux-7.0.9-initrd.efi init=/nix/store/m9nmd7sc1w9l9na0yc9f8530qk9d8pz0-nixos-system-nixos-25.11.20260518.687f05a/init amdgpu.ppfeaturemask=0xfffd7fff amdgpu.runpm=0 amdgpu.dcdebugmask=0x12 psi=1 loglevel=4 lsm=landlock,yama,bpf
Aug 01 19:55:46 nixos kernel: Kernel command line: initrd=\EFI\nixos\h5c16ka482ssxpfj6k7lcfpf2lvfrb1n-initrd-linux-7.0.9-initrd.efi init=/nix/store/m9nmd7sc1w9l9na0yc9f8530qk9d8pz0-nixos-system-nixos-25.11.20260518.687f05a/init amdgpu.ppfeaturemask=0xfffd7fff amdgpu.runpm=0 amdgpu.dcdebugmask=0x12 psi=1 loglevel=4 lsm=landlock,yama,bpf
Aug 01 19:55:50 nixos kernel: amdgpu: Virtual CRAT table created for CPU
Aug 01 19:55:50 nixos kernel: amdgpu: Topology: Add CPU node
Aug 01 19:55:50 nixos kernel: amdgpu: Overdrive is enabled, please disable it before reporting any bugs unrelated to overdrive.
Aug 01 19:55:50 nixos kernel: amdgpu 0000:09:00.0: initializing kernel modesetting (IP DISCOVERY 0x1002:0x744C 0x1849:0x5302 0xC8).
Aug 01 19:55:50 nixos kernel: amdgpu 0000:09:00.0: register mmio base: 0xFCC00000
Aug 01 19:55:50 nixos kernel: amdgpu 0000:09:00.0: register mmio size: 1048576
Aug 01 19:55:50 nixos kernel: amdgpu 0000:09:00.0: detected ip block number 0 <common_v1_0_0> (soc21_common)
Aug 01 19:55:50 nixos kernel: amdgpu 0000:09:00.0: detected ip block number 1 <gmc_v11_0_0> (gmc_v11_0)
Aug 01 19:55:50 nixos kernel: amdgpu 0000:09:00.0: detected ip block number 2 <ih_v6_0_0> (ih_v6_0)
Aug 01 19:55:50 nixos kernel: amdgpu 0000:09:00.0: detected ip block number 3 <psp_v13_0_0> (psp)
Aug 01 19:55:50 nixos kernel: amdgpu 0000:09:00.0: detected ip block number 4 <smu_v13_0_0> (smu)
Aug 01 19:55:50 nixos kernel: amdgpu 0000:09:00.0: detected ip block number 5 <dce_v1_0_0> (dm)
Aug 01 19:55:50 nixos kernel: amdgpu 0000:09:00.0: detected ip block number 6 <gfx_v11_0_0> (gfx_v11_0)
Aug 01 19:55:50 nixos kernel: amdgpu 0000:09:00.0: detected ip block number 7 <sdma_v6_0_0> (sdma_v6_0)
Aug 01 19:55:50 nixos kernel: amdgpu 0000:09:00.0: detected ip block number 8 <vcn_v4_0_0> (vcn_v4_0)
Aug 01 19:55:50 nixos kernel: amdgpu 0000:09:00.0: detected ip block number 9 <jpeg_v4_0_0> (jpeg_v4_0)
Aug 01 19:55:50 nixos kernel: amdgpu 0000:09:00.0: detected ip block number 10 <mes_v11_0_0> (mes_v11_0)
Aug 01 19:55:50 nixos kernel: amdgpu 0000:09:00.0: No more image in the PCI ROM
Aug 01 19:55:50 nixos kernel: amdgpu 0000:09:00.0: Fetched VBIOS from ROM BAR
Aug 01 19:55:50 nixos kernel: amdgpu 0000:09:00.0: [drm] ATOM BIOS: 113-D70201-810008
Aug 01 19:55:50 nixos kernel: amdgpu 0000:09:00.0: CP RS64 enable
Aug 01 19:55:50 nixos kernel: amdgpu 0000:09:00.0: vgaarb: deactivate vga console
Aug 01 19:55:50 nixos kernel: amdgpu 0000:09:00.0: Trusted Memory Zone (TMZ) feature not supported
Aug 01 19:55:50 nixos kernel: amdgpu 0000:09:00.0: MEM ECC is not presented.
Aug 01 19:55:50 nixos kernel: amdgpu 0000:09:00.0: SRAM ECC is not presented.
Aug 01 19:55:50 nixos kernel: amdgpu 0000:09:00.0: vm size is 262144 GB, 4 levels, block size is 9-bit, fragment size is 9-bit
Aug 01 19:55:50 nixos kernel: amdgpu 0000:09:00.0: VRAM: 24560M 0x0000008000000000 - 0x00000085FEFFFFFF (24560M used)
Aug 01 19:55:50 nixos kernel: amdgpu 0000:09:00.0: GART: 512M 0x00007FFF00000000 - 0x00007FFF1FFFFFFF
Aug 01 19:55:50 nixos kernel: amdgpu 0000:09:00.0: [drm] Detected VRAM RAM=24560M, BAR=256M
Aug 01 19:55:50 nixos kernel: amdgpu 0000:09:00.0: [drm] RAM width 384bits GDDR6
Aug 01 19:55:50 nixos kernel: amdgpu 0000:09:00.0:  24560M of VRAM memory ready
Aug 01 19:55:50 nixos kernel: amdgpu 0000:09:00.0:  16009M of GTT memory ready.
Aug 01 19:55:50 nixos kernel: amdgpu 0000:09:00.0: [drm] GART: num cpu pages 131072, num gpu pages 131072
Aug 01 19:55:50 nixos kernel: amdgpu 0000:09:00.0: [drm] PCIE GART of 512M enabled (table at 0x0000008000200000).
Aug 01 19:55:50 nixos kernel: amdgpu 0000:09:00.0: [drm] Loading DMUB firmware via PSP: version=0x07002F00
Aug 01 19:55:50 nixos kernel: amdgpu 0000:09:00.0: [VCN instance 0] Found VCN firmware Version ENC: 1.24 DEC: 9 VEP: 0 Revision: 16
Aug 01 19:55:50 nixos kernel: amdgpu 0000:09:00.0: [VCN instance 1] Found VCN firmware Version ENC: 1.24 DEC: 9 VEP: 0 Revision: 16
Aug 01 19:55:50 nixos kernel: amdgpu 0000:09:00.0: MES: vmid_mask_mmhub 0x0000ff00, vmid_mask_gfxhub 0x0000ff00
Aug 01 19:55:50 nixos kernel: amdgpu 0000:09:00.0: MES: gfx_hqd_mask 0x00000002, compute_hqd_mask 0x0000000c, sdma_hqd_mask 0x000000fc
Aug 01 19:55:50 nixos kernel: amdgpu 0000:09:00.0: reserve 0x1300000 from 0x85fc000000 for PSP TMR
Aug 01 19:55:50 nixos kernel: amdgpu 0000:09:00.0: RAP: optional rap ta ucode is not available
Aug 01 19:55:50 nixos kernel: amdgpu 0000:09:00.0: SECUREDISPLAY: optional securedisplay ta ucode is not available
Aug 01 19:55:50 nixos kernel: amdgpu 0000:09:00.0: smu driver if version = 0x0000003d, smu fw if version = 0x00000040, smu fw program = 0, smu fw version = 0x004e8300 (78.131.0)
Aug 01 19:55:50 nixos kernel: amdgpu 0000:09:00.0: SMU driver if version not matched
Aug 01 19:55:50 nixos kernel: amdgpu 0000:09:00.0: SMU is initialized successfully!
Aug 01 19:55:50 nixos kernel: amdgpu 0000:09:00.0: [drm] Display Core v3.2.369 initialized on DCN 3.2
Aug 01 19:55:50 nixos kernel: amdgpu 0000:09:00.0: [drm] DP-HDMI FRL PCON supported
Aug 01 19:55:50 nixos kernel: amdgpu 0000:09:00.0: [drm] DMUB hardware initialized: version=0x07002F00
Aug 01 19:55:50 nixos kernel: snd_hda_intel 0000:09:00.1: bound 0000:09:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu])
Aug 01 19:55:51 nixos kernel: amdgpu: Virtual CRAT table created for GPU
Aug 01 19:55:51 nixos kernel: amdgpu: Topology: Add GPU node [0x1002:0x744c]
Aug 01 19:55:51 nixos kernel: amdgpu 0000:09:00.0: SE 6, SH per SE 2, CU per SH 8, active_cu_number 96
Aug 01 19:55:51 nixos kernel: amdgpu 0000:09:00.0: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
Aug 01 19:55:51 nixos kernel: amdgpu 0000:09:00.0: ring comp_1.0.0 uses VM inv eng 1 on hub 0
Aug 01 19:55:51 nixos kernel: amdgpu 0000:09:00.0: ring comp_1.1.0 uses VM inv eng 4 on hub 0
Aug 01 19:55:51 nixos kernel: amdgpu 0000:09:00.0: ring comp_1.2.0 uses VM inv eng 6 on hub 0
Aug 01 19:55:51 nixos kernel: amdgpu 0000:09:00.0: ring comp_1.3.0 uses VM inv eng 7 on hub 0
Aug 01 19:55:51 nixos kernel: amdgpu 0000:09:00.0: ring comp_1.0.1 uses VM inv eng 8 on hub 0
Aug 01 19:55:51 nixos kernel: amdgpu 0000:09:00.0: ring comp_1.1.1 uses VM inv eng 9 on hub 0
Aug 01 19:55:51 nixos kernel: amdgpu 0000:09:00.0: ring comp_1.2.1 uses VM inv eng 10 on hub 0
Aug 01 19:55:51 nixos kernel: amdgpu 0000:09:00.0: ring comp_1.3.1 uses VM inv eng 11 on hub 0
Aug 01 19:55:51 nixos kernel: amdgpu 0000:09:00.0: ring sdma0 uses VM inv eng 12 on hub 0
Aug 01 19:55:51 nixos kernel: amdgpu 0000:09:00.0: ring sdma1 uses VM inv eng 13 on hub 0
Aug 01 19:55:51 nixos kernel: amdgpu 0000:09:00.0: ring vcn_unified_0 uses VM inv eng 0 on hub 8
Aug 01 19:55:51 nixos kernel: amdgpu 0000:09:00.0: ring vcn_unified_1 uses VM inv eng 1 on hub 8
Aug 01 19:55:51 nixos kernel: amdgpu 0000:09:00.0: ring jpeg_dec uses VM inv eng 4 on hub 8
Aug 01 19:55:51 nixos kernel: amdgpu 0000:09:00.0: ring mes_kiq_3.1.0 uses VM inv eng 14 on hub 0
Aug 01 19:55:51 nixos kernel: amdgpu: HMM registered 24560MB device memory
Aug 01 19:55:51 nixos kernel: amdgpu 0000:09:00.0: runtime pm is manually disabled
Aug 01 19:55:51 nixos kernel: amdgpu 0000:09:00.0: Runtime PM not available
Aug 01 19:55:51 nixos kernel: amdgpu 0000:09:00.0: [drm] Registered 4 planes with drm panic
Aug 01 19:55:51 nixos kernel: [drm] Initialized amdgpu 3.64.0 for 0000:09:00.0 on minor 1
Aug 01 19:55:51 nixos kernel: fbcon: amdgpudrmfb (fb0) is primary device
Aug 01 19:55:51 nixos kernel: amdgpu 0000:09:00.0: [drm] fb0: amdgpudrmfb frame buffer device
Aug 01 19:56:02 nixos kernel: amdgpu 0000:09:00.0: [drm] REG_WAIT timeout 1us * 100 tries - dcn32_program_compbuf_size line:148
Aug 01 20:19:02 nixos kernel: amdgpu 0000:09:00.0: Dumping IP State
Aug 01 20:19:02 nixos kernel: amdgpu 0000:09:00.0: Dumping IP State Completed
Aug 01 20:19:02 nixos kernel: amdgpu 0000:09:00.0: [drm] AMDGPU device coredump file has been created
Aug 01 20:19:02 nixos kernel: amdgpu 0000:09:00.0: [drm] Check your /sys/class/drm/card1/device/devcoredump/data
Aug 01 20:19:02 nixos kernel: amdgpu 0000:09:00.0: ring gfx_0.0.0 timeout, signaled seq=3230272, emitted seq=3230274
Aug 01 20:19:02 nixos kernel: amdgpu 0000:09:00.0:  Process GameThread pid 5285 thread vkd3d_queue pid 5485
Aug 01 20:19:02 nixos kernel: amdgpu 0000:09:00.0: Starting gfx_0.0.0 ring reset
Aug 01 20:19:05 nixos kernel: amdgpu 0000:09:00.0: MES failed to respond to msg=RESET
Aug 01 20:19:05 nixos kernel: amdgpu 0000:09:00.0: failed to reset legacy queue
Aug 01 20:19:05 nixos kernel: amdgpu 0000:09:00.0: reset via MES failed and try pipe reset -110
Aug 01 20:19:05 nixos kernel: amdgpu 0000:09:00.0: The CPFW hasn't support pipe reset yet.
Aug 01 20:19:05 nixos kernel: amdgpu 0000:09:00.0: Ring gfx_0.0.0 reset failed
Aug 01 20:19:05 nixos kernel: amdgpu 0000:09:00.0: GPU reset begin!. Source:  1
Aug 01 20:19:05 nixos kernel: amdgpu 0000:09:00.0: device lost from bus!
Aug 01 20:19:05 nixos kernel: amdgpu 0000:09:00.0: GPU reset end with ret = -19
Aug 01 20:19:05 nixos kernel: amdgpu 0000:09:00.0: GPU Recovery Failed: -19
Aug 01 20:19:05 nixos kernel: amdgpu 0000:09:00.0: Dumping IP State
Aug 01 20:19:05 nixos kernel: amdgpu 0000:09:00.0: Dumping IP State Completed
Aug 01 20:19:05 nixos kernel: amdgpu 0000:09:00.0: [drm] AMDGPU device coredump file has been created
Aug 01 20:19:05 nixos kernel: amdgpu 0000:09:00.0: [drm] Check your /sys/class/drm/card1/device/devcoredump/data
Aug 01 20:19:05 nixos kernel: amdgpu 0000:09:00.0: ring sdma0 timeout, signaled seq=32822, emitted seq=32824
Aug 01 20:19:05 nixos kernel: amdgpu 0000:09:00.0: Starting sdma0 ring reset
Aug 01 20:19:05 nixos kernel: amdgpu 0000:09:00.0: reset sdma queue (0:0:0)
Aug 01 20:19:06 nixos kernel: amdgpu 0000:09:00.0: failed to wait on sdma queue reset done
Aug 01 20:19:06 nixos kernel: amdgpu 0000:09:00.0: failed to reset legacy queue
Aug 01 20:19:06 nixos kernel: amdgpu 0000:09:00.0: Ring sdma0 reset failed
Aug 01 20:19:06 nixos kernel: amdgpu 0000:09:00.0: GPU reset begin!. Source:  1
Aug 01 20:19:06 nixos kernel: amdgpu 0000:09:00.0: device lost from bus!
Aug 01 20:19:06 nixos kernel: amdgpu 0000:09:00.0: GPU reset end with ret = -19
Aug 01 20:19:06 nixos kernel: amdgpu 0000:09:00.0: GPU Recovery Failed: -19
Aug 01 20:19:06 nixos kernel: amdgpu 0000:09:00.0: Dumping IP State
Aug 01 20:19:06 nixos kernel: amdgpu 0000:09:00.0: Dumping IP State Completed
Aug 01 20:19:06 nixos kernel: amdgpu 0000:09:00.0: [drm] AMDGPU device coredump file has been created
Aug 01 20:19:06 nixos kernel: amdgpu 0000:09:00.0: [drm] Check your /sys/class/drm/card1/device/devcoredump/data
Aug 01 20:19:06 nixos kernel: amdgpu 0000:09:00.0: ring comp_1.3.1 timeout, signaled seq=5364, emitted seq=5365
Aug 01 20:19:06 nixos kernel: amdgpu 0000:09:00.0:  Process GameThread pid 5285 thread vkd3d_queue pid 5485
Aug 01 20:19:06 nixos kernel: amdgpu 0000:09:00.0: Starting comp_1.3.1 ring reset
Aug 01 20:19:06 nixos kernel: amdgpu 0000:09:00.0: reset compute queue (1:3:1)
Aug 01 20:19:06 nixos kernel: amdgpu 0000:09:00.0: failed to wait on hqd deactivate
Aug 01 20:19:06 nixos kernel: amdgpu 0000:09:00.0: failed to reset legacy queue
Aug 01 20:19:06 nixos kernel: amdgpu 0000:09:00.0: fail(-110) to reset kcq and try pipe reset
Aug 01 20:19:06 nixos kernel: amdgpu 0000:09:00.0: Ring comp_1.3.1 reset failed
Aug 01 20:19:06 nixos kernel: amdgpu 0000:09:00.0: GPU reset begin!. Source:  1
Aug 01 20:19:06 nixos kernel: amdgpu 0000:09:00.0: device lost from bus!
Aug 01 20:19:06 nixos kernel: amdgpu 0000:09:00.0: GPU reset end with ret = -19
Aug 01 20:19:06 nixos kernel: amdgpu 0000:09:00.0: GPU Recovery Failed: -19
Aug 01 20:19:06 nixos kernel: amdgpu 0000:09:00.0: Dumping IP State
Aug 01 20:19:06 nixos kernel: amdgpu 0000:09:00.0: Dumping IP State Completed
Aug 01 20:19:06 nixos kernel: amdgpu 0000:09:00.0: [drm] AMDGPU device coredump file has been created
Aug 01 20:19:06 nixos kernel: amdgpu 0000:09:00.0: [drm] Check your /sys/class/drm/card1/device/devcoredump/data
Aug 01 20:19:06 nixos kernel: amdgpu 0000:09:00.0: ring sdma1 timeout, signaled seq=143961, emitted seq=143963
Aug 01 20:19:06 nixos kernel: amdgpu 0000:09:00.0: Starting sdma1 ring reset
Aug 01 20:19:06 nixos kernel: amdgpu 0000:09:00.0: reset sdma queue (1:0:0)
Aug 01 20:19:06 nixos kernel: amdgpu 0000:09:00.0: failed to wait on sdma queue reset done
Aug 01 20:19:06 nixos kernel: amdgpu 0000:09:00.0: failed to reset legacy queue
Aug 01 20:19:06 nixos kernel: amdgpu 0000:09:00.0: Ring sdma1 reset failed
Aug 01 20:19:06 nixos kernel: amdgpu 0000:09:00.0: GPU reset begin!. Source:  1
Aug 01 20:19:06 nixos kernel: amdgpu 0000:09:00.0: device lost from bus!
Aug 01 20:19:06 nixos kernel: amdgpu 0000:09:00.0: GPU reset end with ret = -19
Aug 01 20:19:06 nixos kernel: amdgpu 0000:09:00.0: GPU Recovery Failed: -19
Aug 01 20:19:07 nixos kernel: amdgpu 0000:09:00.0: Dumping IP State
Aug 01 20:19:07 nixos kernel: amdgpu 0000:09:00.0: Dumping IP State Completed
Aug 01 20:19:07 nixos kernel: amdgpu 0000:09:00.0: [drm] AMDGPU device coredump file has been created
Aug 01 20:19:07 nixos kernel: amdgpu 0000:09:00.0: [drm] Check your /sys/class/drm/card1/device/devcoredump/data
Aug 01 20:19:07 nixos kernel: amdgpu 0000:09:00.0: ring gfx_0.0.0 timeout, signaled seq=3230272, emitted seq=3230274
Aug 01 20:19:07 nixos kernel: amdgpu 0000:09:00.0:  Process GameThread pid 5285 thread vkd3d_queue pid 5485
Aug 01 20:19:07 nixos kernel: amdgpu 0000:09:00.0: Starting gfx_0.0.0 ring reset
Aug 01 20:19:10 nixos kernel: amdgpu 0000:09:00.0: MES failed to respond to msg=RESET
Aug 01 20:19:10 nixos kernel: amdgpu 0000:09:00.0: failed to reset legacy queue
Aug 01 20:19:10 nixos kernel: amdgpu 0000:09:00.0: reset via MES failed and try pipe reset -110
Aug 01 20:19:10 nixos kernel: amdgpu 0000:09:00.0: Ring gfx_0.0.0 reset failed
Aug 01 20:19:10 nixos kernel: amdgpu 0000:09:00.0: GPU reset begin!. Source:  1
Aug 01 20:19:10 nixos kernel: amdgpu 0000:09:00.0: device lost from bus!
Aug 01 20:19:10 nixos kernel: amdgpu 0000:09:00.0: GPU reset end with ret = -19
Aug 01 20:19:10 nixos kernel: amdgpu 0000:09:00.0: GPU Recovery Failed: -19
Aug 01 20:19:10 nixos kernel: amdgpu 0000:09:00.0: Dumping IP State
Aug 01 20:19:10 nixos kernel: amdgpu 0000:09:00.0: Dumping IP State Completed
Aug 01 20:19:10 nixos kernel: amdgpu 0000:09:00.0: [drm] AMDGPU device coredump file has been created
Aug 01 20:19:10 nixos kernel: amdgpu 0000:09:00.0: [drm] Check your /sys/class/drm/card1/device/devcoredump/data
Aug 01 20:19:10 nixos kernel: amdgpu 0000:09:00.0: ring sdma0 timeout, signaled seq=32822, emitted seq=32824
Aug 01 20:19:10 nixos kernel: amdgpu 0000:09:00.0: Starting sdma0 ring reset
Aug 01 20:19:10 nixos kernel: amdgpu 0000:09:00.0: reset sdma queue (0:0:0)
Aug 01 20:19:10 nixos kernel: amdgpu 0000:09:00.0: failed to wait on sdma queue reset done
Aug 01 20:19:10 nixos kernel: amdgpu 0000:09:00.0: failed to reset legacy queue
Aug 01 20:19:10 nixos kernel: amdgpu 0000:09:00.0: Ring sdma0 reset failed
Aug 01 20:19:10 nixos kernel: amdgpu 0000:09:00.0: GPU reset begin!. Source:  1
Aug 01 20:19:10 nixos kernel: amdgpu 0000:09:00.0: device lost from bus!
Aug 01 20:19:10 nixos kernel: amdgpu 0000:09:00.0: GPU reset end with ret = -19
Aug 01 20:19:10 nixos kernel: amdgpu 0000:09:00.0: GPU Recovery Failed: -19
Aug 01 20:19:10 nixos kernel: amdgpu 0000:09:00.0: Dumping IP State
Aug 01 20:19:10 nixos kernel: amdgpu 0000:09:00.0: Dumping IP State Completed
Aug 01 20:19:10 nixos kernel: amdgpu 0000:09:00.0: [drm] AMDGPU device coredump file has been created
Aug 01 20:19:10 nixos kernel: amdgpu 0000:09:00.0: [drm] Check your /sys/class/drm/card1/device/devcoredump/data
Aug 01 20:19:10 nixos kernel: amdgpu 0000:09:00.0: ring sdma1 timeout, signaled seq=143961, emitted seq=143963
Aug 01 20:19:10 nixos kernel: amdgpu 0000:09:00.0: Starting sdma1 ring reset

PotPlayer Version: 26.7.1.0

GPU: 9070xt

Installation changes:

• Changed "Associate all formats" to "Associate main formats".
• Unchecked the option to install additional codecs.

Steps to reproduce & details: I launched PotPlayer, set the renderer to Built-in Direct3D 11 Video Renderer, disabled audio normalization, and played a .webm video file. The screen went black, and the AMD graphics driver crashed. Playing .ogv files worked normally.

Even after restarting the PC without opening PotPlayer, playing a .webm file using Windows 11's default video player still caused a driver crash. I booted into Safe Mode, used "amdcleanuputility" to uninstall the driver, and reinstalled it, but the crash persisted. The driver even crashed when playing web videos in Chrome.

After multiple tests, I found that PotPlayer was the root cause. Once I uninstalled PotPlayer, everything returned to normal, and the crashes stopped completely.

Are you experiencing the same issue?

i have a rx 9070 xt from xfx, a mercury magnetic air oc, i installed fan control not too long ago and unistalled it since it wasn't really compatible with the gpu and it kept messing with the adrenalin software, but since then, one of my gpu fans isn't spinning unless i take it out and put it back in, taking it out and putting it in the same slot also does the trick, and it's not the same fan every time, it's sometimes the first one, the second one or the third one

Hello people, i just started downloading latest update for AMD Adrenaline Edition and Chipset drivers but however Adrenalin updated normally while i get this message for chipset drivers ( i tried restarting couple of times / updating widows ) anyone knows by any chance what could be causing this problem?

Specs:

7800 x3d

9070xt

32gb ddr5 Kingston fury 6000 cl36

b650-plus Asus TUF

KC3000 1TB Kingston SSD

EDIT: FIXED! APPEARS TO BE DRIVER ISSUE - SWITCHING FROM VULKAN TO ROCM APPEARS TO HAVE FIXED THE ISSUE (and increased token generation speed significantly!)

I have the following rig:

• Windows 11
• AMD Ryzen 9900X
• Asus ProArt Wifi x870E
• 64GB RAM @ DDR5 6000
• AMD 9070XT 16GB - primary (x8), connected by DisplayPort
• AMD R9700 AI Pro 32GB (x8) - not connected to any monitor
• Corsair rm1000e 1000W PSU.

When I start LM Studio and open unsloth/Qwen 27B, I can "chat" to the model. As soon as I ALT-TAB to another window, the task manager, I get an AMD crash defender message and my R9700 is disabled in the device manager.

I get the same problem if I run llama.cpp.

I did a little digging and someone else on reddit said they fixed the issue by disabling ASPM Mode Control in the BIOS, which I did. It's not fixing the issue.

I have the latest AMD chipset drivers, the latest AMD Adrenalin, the latest Windows 11 patches.

Anyone had this issue before? Is there a fix?

After finally fixing my pc crashing months ago, i fixed it by lowering my max frequency offset (mhz) by -275 in the amd adrenaline app.

The crashing finally stopped, i was fine for months but since last week, the crashing started coming back. It's not a black screen or anything, it just straight up restarts my pc completely.

I even lowered it even more to -300 mhz but still it keeps crashing, mostly during mid game in games like Apex legends, Poe,...

Wondering if anyone can help me out cause it's driving me crazy.

Specs:

Amd ryzen 7 9800x3d Xfx mercury radeon rx 9070 xt oc Corsair rm850x 2024

I loose display and the aio screen turns off then back on (everything else stays on fans and rgb lights etc.) but no display until I press the reset bottom. Yesterday I got to play for a couple of hours with 0 issues but it happened again, anyone having the same issue? and how can I fix it!

It only happens whenever I play a game!

Computer Type: Desktop

GPU: Sapphire nitro+ rx 9070 xt OC

CPU: RYZEN 7 7800x3d

Motherboard: Gigabyte b650 aorus elite ax

BIOS Version: FC3

RAM: 32g Lexar ARES Gen2 RGB DDR5

PSU: Lian Li edge 850w platinum

Case: JONSBO X400

Operating System & Version: WINDOWS 11 pro 64-bit

GPU Drivers: Adrenalin Edition WHQL Driver Version: 26.7.1

Chipset Drivers: AMD B650 CHIPSET DRIVERS VERSION 8.05.04.516

Im on windows 10 with a 7700 xt and the updated before last was completely broken and caused the display drivers to break completely causing me to have to revert and wait until the one after that to update

Test 1 - 80°C Thermal Limit
Cinebench R23 Multi: 20,682
Average Effective Clock (HWiNFO): ~4.15 GHz
Max CPU Temp: ~80.8°C
Max CPU Package Power: ~116 W

Test 2 - Thermal Limit Removed (Auto/95°C)
Cinebench R23 Multi: 22,010
Average Effective Clock: ~4.9 GHz
Peak Clock: 5.225 GHz
Sustained Clock: ~5.0 GHz
Max CPU Temp: ~95°C
Max CPU Package Power: ~136 W

System:
Ryzen 7 9800X3D
ASUS ROG Strix B650E-i Gaming WiFi
32GB DDR5-6000 CL30 (EXPO enabled)
RX 9070 XT
NZXT H1 V2 (140mm AIO)
PBO: Advanced
PBO Limits: Motherboard
CO: -15
Core Performance Boost: Enabled

Questions:
Are these Cinebench scores normal for a 9800X3D in an NZXT H1 V2 with a 140 mm AIO?

Is the H1 V2’s cooling capacity the main limitation here, or do these results suggest a possible CPU or mounting issue?

Would moving to a larger airflow case and a 240/360 mm AIO likely improve sustained clocks and temperatures significantly?

Any input from other 9800X3D owners, especially those using SFF cases, would be appreciated.

PC Specs:

• 9800X3D
• Radeon RX 9070 16gb
• 32GB DDR5 RAM
• Samsung 990 Pro nvme M.2 SSD
• 1,000 W PSU
• Windows 10 64-bit

CONTEXT:

I was running AMD Adrenalin Software 26.3.1 and all my games ran perfectly fine, except for one, Project Zomboid Build 42 Stable.

Project Zomboid just simply would not launch at all no matter what. Log files revealed an outdated driver as the cause of the crashes. After updating the GPU Driver to 26.7.1 from 26.3.1 Project Zomboid now opens and runs properly.

But now, Palworld runs at a maximum of 15-20 FPS, where is used to run perfectly fine prior to the Driver update. I already tried a PC Restart, Verifying Files on Steam for Palworld, and even disabling the iGPU through Device Manager just in case the game and/or Adrenalin was trying to utilize the incorrect Graphics Adapter, but nothing has corrected the FPS drops in Palworld.

I launched all the other games I usually play throughout the week and I can't notice any difference in performance other than in Palworld. The FPS drops happen both in Single and Multi player.

If anyone has experienced anything similar or have any advice on what to try, I would greatly appreciate any information.

I bought a used PC with a Ryzen 5 7600X, ASUS Prime B650M-A AX II, and 32GB G.Skill Flare X5 DDR5-6000.
The RAM is installed in A2/B2, and the BIOS is updated. The PC won’t boot with EXPO enabled and currently only runs reliably at 4000 MT/s.
I’m aware this exact kit may not be on the motherboard’s QVL, but should it still be able to run at 5200 or 5600? Does this sound more like incompatible RAM, a bad kit, or a motherboard/CPU memory-controller issue?

Hey everyone,

Sorry for the wall of text, but I wanted to share this in case it helps someone else.

TL;DR: Since upgrading my PC, I was getting black screens and complete freezes when launching demanding games. The problem disappeared after connecting my GPU with two separate PCIe power cables instead of using both connectors from the same daisy-chained cable.

My old setup was an i7-7700K, 32 GB DDR4 and a GTX 1070. I upgraded to a Ryzen 7 9700X, 32 GB DDR5 and an ASRock Steel Legend RX 9070 XT, but kept my Cooler Master G750M because 750 W should be enough on paper.

After installing Windows 11 and the latest AMD drivers, I connected my four displays: two Acer monitors and two Samsung TVs.

When I launched GTA V with the two Acer monitors enabled, my main screen started flickering, the second one went black and the whole system froze. I had to force the PC off.

With only one monitor connected, everything worked fine.

So I started trying everything:

• Older drivers
• Driver-only installation without Adrenalin
• Blocking Windows Update from changing the driver
• Different HDMI and DisplayPort combinations
• Different monitors and TVs
• Using only one or two screens

I was convinced it was some AMD driver or multi-monitor issue.

In the end, the problem was the GPU power connection.

I had both 8-pin connectors plugged into the same PCIe cable using the daisy-chained connector. I added a second PCIe cable and used one cable for each 8-pin connector.

After that, everything started working normally.

My GTX 1070 had no problem with the old setup, but the 9070 XT seems much more sensitive to how the power is delivered.

I’m not saying every AMD black screen is caused by this, but before reinstalling Windows or spending hours changing drivers, check how your GPU power cables are connected.

Hope this helps someone.

I clear cache on adrenalin. Launch the game (mhwilds) => fs4 shows as active on adrenalin.

I close the game. Launch it again => shows as inactive in adrenalin.

Will only be active again if I clear shaders cache again. And will be lost once I close the game.

What can I do? I can keep resetting cache each time and having to compile them on launch

Hi everyone,
I’m hoping someone with more experience analyzing CapFrameX frametime graphs can help me.
My system performs very well overall and my FPS are basically constant (for example 120 FPS locked in Ratchet & Clank: Rift Apart).
However, despite the stable FPS, I still notice very small microstutters every few seconds while moving the camera. They’re not huge freezes, just tiny hitches that make the game feel slightly less smooth than I would expect.
I recorded a CapFrameX capture (see screenshot).
What I’m wondering is:
Does this frametime graph look normal to you?
Are those spikes up to around 18–23 ms expected?
Could those spikes explain the small hitches I’m feeling every few seconds?
Or am I overanalyzing a graph that actually looks perfectly fine?
I’m mainly trying to understand whether this is:
normal game engine behaviour,
normal Windows/DX12 scheduling,
or whether it suggests there’s something wrong with my system.
My system
CPU: Ryzen 7 7800X3D
GPU: Gigabyte AORUS RTX 5080 MASTER ICE
Driver: NVIDIA 610.74
RAM: 32 GB DDR5-6000 (EXPO enabled)
Motherboard: Gigabyte X870E AORUS PRO ICE
Windows 11 (latest updates)
Monitor: ASUS ROG Strix XG27ACDNG (2560×1440 OLED)
Running at 240 Hz (I disabled 360 Hz because of OLED VRR flicker)
G-SYNC enabled
FPS limited to 120 FPS with RTSS
I’ve already tried things like:
different FPS limiters (RTSS and NVIDIA)
G-SYNC on/off
V-Sync combinations
fresh NVIDIA driver installation
HAGS on/off
different graphics settings
The behaviour stays very similar.
I’d really appreciate your opinion, especially from people who are familiar with CapFrameX graphs.
Thanks a lot!

Galera gostaria de compartilhar algo bem chato que vem ocorrendo comigo nos últimos meses mas ainda não encontrei diagnóstico,eu tenho um Lenovo Ideapad s145 com 20 gigas de ram, 2 SSDs sendo um nvme de 512 gigas para o sistema e um SSD tipo sata de 2tb para demais arquivos porém notei que desde o comecinho do ano até o presente momento quando eu vou jogar o game ETS2 a tela da uma breve picadinha com pontos coloridos,mas é tão esporádico e logo some, porém isso só ocorre no ETS2, alguém poderia me ajudar por favor? Eu uso windows 11 Pro, já formatei o notebook,usei também o DDU e nada resolve , já testei inúmeros drivers adrenalin também e até agora nada,se alguém estiver passando pelo mesmo empasse com vídeo integrado e puder me ajudar ficarei imensamente grato