Games Crash After Awhile When Ran

Games crash no matter what, or run into this issue where they start to slow down and stutter, its been happening since the November cachyos update, I use an 6900xt and a 7600x, both are well cooled, the gpu is water cooled.

When the crash occurs my motherboard reactivates my IGPU so i have to force disable it, I’ve looked all around for months for solutions to this problem and decided that I can’t play anything that puts demand on my gpu. would really love some assistance.

[ 3.741820] [drm] amdgpu kernel modesetting enabled.
[ 3.741900] amdgpu: Virtual CRAT table created for CPU
[ 3.741907] amdgpu: Topology: Add CPU node
[ 3.741934] amdgpu: Overdrive is enabled, please disable it before reporting any bugs.
[ 3.741999] amdgpu 0000:03:00.0: enabling device (0006 → 0007)
[ 3.745356] amdgpu 0000:03:00.0: amdgpu: Fetched VBIOS from VFCT
[ 3.745358] amdgpu: ATOM BIOS: 115-D412BS2-100
[ 3.755056] amdgpu 0000:03:00.0: vgaarb: deactivate vga console
[ 3.755058] amdgpu 0000:03:00.0: amdgpu: Trusted Memory Zone (TMZ) feature disabled as experimental (default)
[ 3.755077] amdgpu 0000:03:00.0: amdgpu: MEM ECC is not presented.
[ 3.755078] amdgpu 0000:03:00.0: amdgpu: SRAM ECC is not presented.
[ 3.755120] amdgpu 0000:03:00.0: amdgpu: VRAM: 16368M 0x0000008000000000 - 0x00000083FEFFFFFF (16368M used)
[ 3.755122] amdgpu 0000:03:00.0: amdgpu: GART: 512M 0x0000000000000000 - 0x000000001FFFFFFF
[ 3.755186] [drm] amdgpu: 16368M of VRAM memory ready
[ 3.755188] [drm] amdgpu: 15863M of GTT memory ready.
[ 5.656005] amdgpu 0000:03:00.0: amdgpu: STB initialized to 2048 entries
[ 5.722102] amdgpu 0000:03:00.0: amdgpu: reserve 0xa00000 from 0x83fd000000 for PSP TMR
[ 5.869006] amdgpu 0000:03:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
[ 5.869023] amdgpu 0000:03:00.0: amdgpu: smu driver if version = 0x00000040, smu fw if version = 0x00000041, smu fw program = 0, version = 0x003a5a00 (58.90.0)
[ 5.869025] amdgpu 0000:03:00.0: amdgpu: SMU driver if version not matched
[ 5.869053] amdgpu 0000:03:00.0: amdgpu: use vbios provided pptable
[ 5.944563] amdgpu 0000:03:00.0: amdgpu: SMU is initialized successfully!
[ 6.232666] amdgpu: HMM registered 16368MB device memory
[ 6.234027] kfd kfd: amdgpu: Allocated 3969056 bytes on gart
[ 6.234036] kfd kfd: amdgpu: Total number of KFD nodes to be created: 1
[ 6.234169] amdgpu: Virtual CRAT table created for GPU
[ 6.234374] amdgpu: Topology: Add dGPU node [0x73bf:0x1002]
[ 6.234376] kfd kfd: amdgpu: added device 1002:73bf
[ 6.234400] amdgpu 0000:03:00.0: amdgpu: SE 4, SH per SE 2, CU per SH 10, active_cu_number 80
[ 6.234403] amdgpu 0000:03:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
[ 6.234405] amdgpu 0000:03:00.0: amdgpu: ring gfx_0.1.0 uses VM inv eng 1 on hub 0
[ 6.234406] amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 4 on hub 0
[ 6.234407] amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 5 on hub 0
[ 6.234408] amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0
[ 6.234409] amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0
[ 6.234410] amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0
[ 6.234411] amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0
[ 6.234411] amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0
[ 6.234413] amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0
[ 6.234413] amdgpu 0000:03:00.0: amdgpu: ring kiq_0.2.1.0 uses VM inv eng 12 on hub 0
[ 6.234414] amdgpu 0000:03:00.0: amdgpu: ring sdma0 uses VM inv eng 13 on hub 0
[ 6.234415] amdgpu 0000:03:00.0: amdgpu: ring sdma1 uses VM inv eng 14 on hub 0
[ 6.234416] amdgpu 0000:03:00.0: amdgpu: ring sdma2 uses VM inv eng 15 on hub 0
[ 6.234417] amdgpu 0000:03:00.0: amdgpu: ring sdma3 uses VM inv eng 16 on hub 0
[ 6.234418] amdgpu 0000:03:00.0: amdgpu: ring vcn_dec_0 uses VM inv eng 0 on hub 8
[ 6.234419] amdgpu 0000:03:00.0: amdgpu: ring vcn_enc_0.0 uses VM inv eng 1 on hub 8
[ 6.234420] amdgpu 0000:03:00.0: amdgpu: ring vcn_enc_0.1 uses VM inv eng 4 on hub 8
[ 6.234421] amdgpu 0000:03:00.0: amdgpu: ring vcn_dec_1 uses VM inv eng 5 on hub 8
[ 6.234422] amdgpu 0000:03:00.0: amdgpu: ring vcn_enc_1.0 uses VM inv eng 6 on hub 8
[ 6.234423] amdgpu 0000:03:00.0: amdgpu: ring vcn_enc_1.1 uses VM inv eng 7 on hub 8
[ 6.234424] amdgpu 0000:03:00.0: amdgpu: ring jpeg_dec uses VM inv eng 8 on hub 8
[ 6.235551] amdgpu 0000:03:00.0: amdgpu: Using BACO for runtime pm
[ 6.235862] [drm] Initialized amdgpu 3.59.0 for 0000:03:00.0 on minor 0
[ 6.245006] fbcon: amdgpudrmfb (fb0) is primary device
[ 6.390566] WARNING: CPU: 10 PID: 198 at drivers/gpu/drm/amd/amdgpu/…/display/dc/hwss/dcn30/dcn30_hwseq.c:1007 dcn30_apply_idle_power_optimizations+0x4de/0x4f0 [amdgpu]
[ 6.390974] Modules linked in: hid_generic usbhid amdgpu(+) crc16 drm_buddy drm_suballoc_helper video wmi drm_exec i2c_algo_bit gpu_sched amdxcp drm_ttm_helper ttm drm_display_helper cec
[ 6.390986] RIP: 0010:dcn30_apply_idle_power_optimizations+0x4de/0x4f0 [amdgpu]
[ 6.391178] ? dcn30_apply_idle_power_optimizations+0x4de/0x4f0 [amdgpu 05e90674e3b4fdfe924b735d6194753d93557f10]
[ 6.391359] ? __pfx_dcn30_does_plane_fit_in_mall+0x10/0x10 [amdgpu 05e90674e3b4fdfe924b735d6194753d93557f10]
[ 6.391530] ? dcn30_apply_idle_power_optimizations+0x4de/0x4f0 [amdgpu 05e90674e3b4fdfe924b735d6194753d93557f10]
[ 6.391701] dc_allow_idle_optimizations_internal+0xa0/0x100 [amdgpu 05e90674e3b4fdfe924b735d6194753d93557f10]
[ 6.391873] amdgpu_dm_atomic_commit_tail+0x74b/0x3f20 [amdgpu 05e90674e3b4fdfe924b735d6194753d93557f10]
[ 6.392045] ? dm_read_reg_func+0x61/0xd0 [amdgpu 05e90674e3b4fdfe924b735d6194753d93557f10]
[ 6.392215] ? generic_reg_get+0x21/0x40 [amdgpu 05e90674e3b4fdfe924b735d6194753d93557f10]
[ 6.392388] ? optc1_get_crtc_scanoutpos+0xec/0x120 [amdgpu 05e90674e3b4fdfe924b735d6194753d93557f10]
[ 6.392559] ? dc_stream_get_scanoutpos+0xd5/0xf0 [amdgpu 05e90674e3b4fdfe924b735d6194753d93557f10]
[ 6.392730] ? dm_crtc_get_scanoutpos+0xcd/0x120 [amdgpu 05e90674e3b4fdfe924b735d6194753d93557f10]
[ 6.392904] ? amdgpu_crtc_get_scanout_position+0x91/0x140 [amdgpu 05e90674e3b4fdfe924b735d6194753d93557f10]
[ 6.393073] ? __pfx_amdgpu_crtc_get_scanout_position+0x10/0x10 [amdgpu 05e90674e3b4fdfe924b735d6194753d93557f10]
[ 6.393294] amdgpu_pci_probe+0x61f/0x840 [amdgpu 05e90674e3b4fdfe924b735d6194753d93557f10]
[ 6.393477] ? __pfx_init_module+0x10/0x10 [amdgpu 05e90674e3b4fdfe924b735d6194753d93557f10]
[ 6.397147] amdgpu 0000:03:00.0: [drm] fb0: amdgpudrmfb frame buffer device
[ 7.457201] snd_hda_intel 0000:03:00.1: bound 0000:03:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu])

Noticed :

RIP: 0010:dcn30_apply_idle_power_optimizations+0x4de/0x4f0 [amdgpu]

applied

echo performance | tee /sys/class/drm/card0/device/power_dpm_state

as a temporary fix still testing

Is Arch’s kernel affected? Also I’ve noticed that if you have overclocking enabled so please disable that first and check again.

We live in a time where quality is no longer desired, and that’s the case with everything, including your RAM. Choosing the XMP profile and then thinking everything is OK is fatal.
Use memtest86 from passmark to first test whether your RAM is working properly.
If you get errors, that doesn’t mean that your memory is defective, but that your CPU is not able to handle it.
As soon as you use more than 32 GB of RAM with the same XMP profile, memory errors occur.
It helps to either increase the CL timing or reduce the MHz.
If passmark then runs through 4 rounds without errors, it’s time to install your system.

True, I’ll try messing with the CL, perhaps the timings are too tight, I am using something similar to XMP, but doing the Memtest is probably a good idea, and I found a 6000MHZ ECC KIT just as tight for a decent price that i wouldn’t mind worse case.

I have installed 6000 mhz cl30 but many errors occured with xmp . since i configured as 5600 with the orginal timings and the voltage from the xmp profile it works fine and the transfer rate of the ram is identical with 6000 mhz on cl40

in memtest86 from passmark you can see on the 3 or 4 page of the spd info from your ram wich cl works proberly

1 Like

I had something similar happen on another PC with 4 sticks, but i moved down to 2 thinking It’d be cool, I mostly play games so a lower clock is fine as long as its not attached to the infinity cache speed, I think its not under 5200mhz on this cpu and since i do tighter timings and lower clock is something I should dabble with too.

Tested out the Underclock on memory, no luck, still results in the same crashes, Maybe a gpu power thing, but It crashes when I run it underclocked too, with this kernel update hoping maybe some things improved.

still occurring, memtest came out with ram being okay no issues, going to try bypassing my 3x8 rgb 8 pin to see if its not some kinda issue with this cable shorting it power.

Still occurs :frowning: for the record overclocking is on because the only way i can be stable is to underclock the gpu at this point. Really wish it was an easy fix

GPU apparently needed a vbios update, managed to update it, changed the 3x8pin rgb, no more crashing!

1 Like