The only problem with swapping to the flatpak as a test is you’re essentially using a nuke to swat a fly. Its libraries, drivers, etc. Will all be different from repo install so you can’t pinpoint the issue.
As for the skin, I haven’t heard of skins breaking a game and not others before. I’ve been using steam and steam skins for nearly 20yrs and never encountered the scrnerio either.
No, I haven’t tried using any flatpak version but to be honest, I’ve never used them before so it didn’t come to mind.
I’m not very proficcient on how to pull data from log files but I gave it a shot. I did a clean boot, then started Steam and started Fallout and loaded into a world. It crashed as usual so I jumped over to my terminal. I killed plasma then restarted the display manager and logged back in. I then pulled the following from the KDE log viewer:
If there is another way to get more useful information, please let me know so I can try to get it for you.
10/17/22 1:27 PM [drm] amdgpu kernel modesetting enabled.
10/17/22 1:27 PM amdgpu Ignoring ACPI CRAT on non-APU system
10/17/22 1:27 PM amdgpu Virtual CRAT table created for CPU
10/17/22 1:27 PM amdgpu Topology: Add CPU node
10/17/22 1:27 PM amdgpu 0000 c:00.0: vgaarb: deactivate vga console
10/17/22 1:27 PM amdgpu 0000 c:00.0: No more image in the PCI ROM
10/17/22 1:27 PM amdgpu 0000 c:00.0: amdgpu: Fetched VBIOS from ROM BAR
10/17/22 1:27 PM amdgpu ATOM BIOS: 113-EXT23640-PRI
10/17/22 1:27 PM amdgpu 0000 c:00.0: amdgpu: Trusted Memory Zone (TMZ) feature not supported
10/17/22 1:27 PM amdgpu 0000 c:00.0: amdgpu: MEM ECC is not presented.
10/17/22 1:27 PM amdgpu 0000 c:00.0: amdgpu: SRAM ECC is not presented.
10/17/22 1:27 PM amdgpu 0000 c:00.0: amdgpu: VRAM: 8176M 0x000000F400000000 - 0x000000F5FEFFFFFF (8176M used)
10/17/22 1:27 PM amdgpu 0000 c:00.0: amdgpu: GART: 512M 0x0000000000000000 - 0x000000001FFFFFFF
10/17/22 1:27 PM amdgpu 0000 c:00.0: amdgpu: AGP: 267419648M 0x000000F800000000 - 0x0000FFFFFFFFFFFF
10/17/22 1:27 PM [drm] amdgpu 8176M of VRAM memory ready
10/17/22 1:27 PM [drm] amdgpu 16010M of GTT memory ready.
10/17/22 1:27 PM amdgpu 0000 c:00.0: amdgpu: PSP runtime database doesn't exist
10/17/22 1:27 PM amdgpu 0000 c:00.0: amdgpu: PSP runtime database doesn't exist
10/17/22 1:27 PM amdgpu hwmgr_sw_init smu backed is vega10_smu
10/17/22 1:27 PM snd_hda_intel 0000 c:00.1: bound 0000:0c:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu])
10/17/22 1:27 PM kfd kfd amdgpu: Allocated 3969056 bytes on gart
10/17/22 1:27 PM amdgpu sdma_bitmap: f
10/17/22 1:27 PM amdgpu HMM registered 8176MB device memory
10/17/22 1:27 PM amdgpu SRAT table not found
10/17/22 1:27 PM amdgpu Virtual CRAT table created for GPU
10/17/22 1:27 PM amdgpu Topology: Add dGPU node [0x687f:0x1002]
10/17/22 1:27 PM kfd kfd amdgpu: added device 1002:687f
10/17/22 1:27 PM amdgpu 0000 c:00.0: amdgpu: SE 4, SH per SE 1, CU per SH 16, active_cu_number 56
10/17/22 1:27 PM amdgpu 0000 c:00.0: amdgpu: ring gfx uses VM inv eng 0 on hub 0
10/17/22 1:27 PM amdgpu 0000 c:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
10/17/22 1:27 PM amdgpu 0000 c:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
10/17/22 1:27 PM amdgpu 0000 c:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
10/17/22 1:27 PM amdgpu 0000 c:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
10/17/22 1:27 PM amdgpu 0000 c:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
10/17/22 1:27 PM amdgpu 0000 c:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
10/17/22 1:27 PM amdgpu 0000 c:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
10/17/22 1:27 PM amdgpu 0000 c:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
10/17/22 1:27 PM amdgpu 0000 c:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0
10/17/22 1:27 PM amdgpu 0000 c:00.0: amdgpu: ring sdma0 uses VM inv eng 0 on hub 1
10/17/22 1:27 PM amdgpu 0000 c:00.0: amdgpu: ring page0 uses VM inv eng 1 on hub 1
10/17/22 1:27 PM amdgpu 0000 c:00.0: amdgpu: ring sdma1 uses VM inv eng 4 on hub 1
10/17/22 1:27 PM amdgpu 0000 c:00.0: amdgpu: ring page1 uses VM inv eng 5 on hub 1
10/17/22 1:27 PM amdgpu 0000 c:00.0: amdgpu: ring uvd_0 uses VM inv eng 6 on hub 1
10/17/22 1:27 PM amdgpu 0000 c:00.0: amdgpu: ring uvd_enc_0.0 uses VM inv eng 7 on hub 1
10/17/22 1:27 PM amdgpu 0000 c:00.0: amdgpu: ring uvd_enc_0.1 uses VM inv eng 8 on hub 1
10/17/22 1:27 PM amdgpu 0000 c:00.0: amdgpu: ring vce0 uses VM inv eng 9 on hub 1
10/17/22 1:27 PM amdgpu 0000 c:00.0: amdgpu: ring vce1 uses VM inv eng 10 on hub 1
10/17/22 1:27 PM amdgpu 0000 c:00.0: amdgpu: ring vce2 uses VM inv eng 11 on hub 1
10/17/22 1:27 PM [drm] Initialized amdgpu 3.48.0 20150101 for 0000:0c:00.0 on minor 0
10/17/22 1:27 PM fbcon amdgpudrmfb (fb0) is primary device
10/17/22 1:27 PM amdgpu 0000 c:00.0: [drm] fb0: amdgpudrmfb frame buffer device
10/17/22 1:43 PM [drm mdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=64922, emitted seq=64924
10/17/22 1:43 PM [drm mdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Fallout76.exe pid 8160 thread Fallout76.exe pid 8160
10/17/22 1:43 PM amdgpu 0000 c:00.0: amdgpu: GPU reset begin!
10/17/22 1:43 PM amdgpu 0000 c:00.0: amdgpu: BACO reset
10/17/22 1:43 PM amdgpu 0000 c:00.0: amdgpu: GPU reset succeeded, trying to resume
10/17/22 1:43 PM amdgpu 0000 c:00.0: amdgpu: ring gfx uses VM inv eng 0 on hub 0
10/17/22 1:43 PM amdgpu 0000 c:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
10/17/22 1:43 PM amdgpu 0000 c:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
10/17/22 1:43 PM amdgpu 0000 c:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
10/17/22 1:43 PM amdgpu 0000 c:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
10/17/22 1:43 PM amdgpu 0000 c:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
10/17/22 1:43 PM amdgpu 0000 c:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
10/17/22 1:43 PM amdgpu 0000 c:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
10/17/22 1:43 PM amdgpu 0000 c:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
10/17/22 1:43 PM amdgpu 0000 c:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0
10/17/22 1:43 PM amdgpu 0000 c:00.0: amdgpu: ring sdma0 uses VM inv eng 0 on hub 1
10/17/22 1:43 PM amdgpu 0000 c:00.0: amdgpu: ring page0 uses VM inv eng 1 on hub 1
10/17/22 1:43 PM amdgpu 0000 c:00.0: amdgpu: ring sdma1 uses VM inv eng 4 on hub 1
10/17/22 1:43 PM amdgpu 0000 c:00.0: amdgpu: ring page1 uses VM inv eng 5 on hub 1
10/17/22 1:43 PM amdgpu 0000 c:00.0: amdgpu: ring uvd_0 uses VM inv eng 6 on hub 1
10/17/22 1:43 PM amdgpu 0000 c:00.0: amdgpu: ring uvd_enc_0.0 uses VM inv eng 7 on hub 1
10/17/22 1:43 PM amdgpu 0000 c:00.0: amdgpu: ring uvd_enc_0.1 uses VM inv eng 8 on hub 1
10/17/22 1:43 PM amdgpu 0000 c:00.0: amdgpu: ring vce0 uses VM inv eng 9 on hub 1
10/17/22 1:43 PM amdgpu 0000 c:00.0: amdgpu: ring vce1 uses VM inv eng 10 on hub 1
10/17/22 1:43 PM amdgpu 0000 c:00.0: amdgpu: ring vce2 uses VM inv eng 11 on hub 1
10/17/22 1:43 PM amdgpu 0000 c:00.0: amdgpu: recover vram bo from shadow start
10/17/22 1:43 PM amdgpu 0000 c:00.0: amdgpu: recover vram bo from shadow done
10/17/22 1:43 PM amdgpu 0000 c:00.0: amdgpu: GPU reset(2) succeeded!
10/17/22 1:43 PM Modules linked in uvcvideo videobuf2_vmalloc videobuf2_memops snd_usb_audio videobuf2_v4l2 videobuf2_common snd_usbmidi_lib snd_rawmidi videodev snd_seq_device mc joydev btrfs intel_rapl_msr blake2b_generic xor raid6_pq intel_rapl_common amdgpu libcrc32c igb snd_hda_codec_realtek dca snd_hda_codec_generic snd_hda_codec_hdmi edac_mce_amd eeepc_wmi asus_wmi snd_hda_intel kvm_amd ledtrig_audio snd_intel_dspcfg sparse_keymap snd_intel_sdw_acpi platform_profile video mousedev kvm asus_wmi_sensors rfkill wmi_bmof snd_hda_codec mxm_wmi asus_ec_sensors gpu_sched irqbypass drm_buddy snd_hda_core crct10dif_pclmul drm_ttm_helper crc32_pclmul snd_hwdep polyval_clmulni ttm polyval_generic gf128mul snd_pcm ghash_clmulni_intel aesni_intel snd_timer drm_display_helper ccp crypto_simd snd cryptd sp5100_tco cec rapl pcspkr soundcore i2c_piix4 rng_core k10temp gpio_amdpt mac_hid wmi gpio_generic acpi_cpufreq hid_logitech_hidpp vboxnetflt(OE) vboxnetadp(OE) vboxdrv(OE) pkcs8_key_parser sg
10/17/22 1:43 PM [drm mdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
10/17/22 1:45 PM [drm mdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
10/17/22 1:45 PM [drm mdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
10/17/22 1:45 PM [drm mdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
10/17/22 1:45 PM [drm mdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
10/17/22 1:45 PM [drm mdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
10/17/22 1:45 PM [drm mdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
10/17/22 1:45 PM [drm mdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
10/17/22 1:45 PM [drm mdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
10/17/22 1:45 PM [drm mdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
10/17/22 1:45 PM amdgpu 0000 c:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:221 vmid:4 pasid:32774, for process plasmashell pid 5940 thread plasmashel:cs0 pid 5973)
10/17/22 1:45 PM amdgpu 0000 c:00.0: amdgpu: in page starting at address 0x0000800000028000 from IH client 0x1b (UTCL2)
10/17/22 1:45 PM amdgpu 0000 c:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x004009BA
10/17/22 1:45 PM amdgpu 0000 c:00.0: amdgpu: Faulty UTCL2 client ID: CPF (0x4)
10/17/22 1:45 PM amdgpu 0000 c:00.0: amdgpu: MORE_FAULTS: 0x0
10/17/22 1:45 PM amdgpu 0000 c:00.0: amdgpu: WALKER_ERROR: 0x5
10/17/22 1:45 PM amdgpu 0000 c:00.0: amdgpu: PERMISSION_FAULTS: 0xb
10/17/22 1:45 PM amdgpu 0000 c:00.0: amdgpu: MAPPING_ERROR: 0x1
10/17/22 1:45 PM amdgpu 0000 c:00.0: amdgpu: RW: 0x0
10/17/22 1:45 PM [drm mdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=64926, emitted seq=64928
10/17/22 1:45 PM [drm mdgpu_job_timedout [amdgpu]] *ERROR* Process information: process plasmashell pid 5940 thread plasmashel:cs0 pid 5973
10/17/22 1:45 PM amdgpu 0000 c:00.0: amdgpu: GPU reset begin!
10/17/22 1:45 PM amdgpu 0000 c:00.0: amdgpu: BACO reset
10/17/22 1:45 PM amdgpu 0000 c:00.0: amdgpu: GPU reset succeeded, trying to resume
10/17/22 1:45 PM amdgpu 0000 c:00.0: amdgpu: ring gfx uses VM inv eng 0 on hub 0
10/17/22 1:45 PM amdgpu 0000 c:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
10/17/22 1:45 PM amdgpu 0000 c:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
10/17/22 1:45 PM amdgpu 0000 c:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
10/17/22 1:45 PM amdgpu 0000 c:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
10/17/22 1:45 PM amdgpu 0000 c:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
10/17/22 1:45 PM amdgpu 0000 c:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
10/17/22 1:45 PM amdgpu 0000 c:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
10/17/22 1:45 PM amdgpu 0000 c:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
10/17/22 1:45 PM amdgpu 0000 c:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0
10/17/22 1:45 PM amdgpu 0000 c:00.0: amdgpu: ring sdma0 uses VM inv eng 0 on hub 1
10/17/22 1:45 PM amdgpu 0000 c:00.0: amdgpu: ring page0 uses VM inv eng 1 on hub 1
10/17/22 1:45 PM amdgpu 0000 c:00.0: amdgpu: ring sdma1 uses VM inv eng 4 on hub 1
10/17/22 1:45 PM amdgpu 0000 c:00.0: amdgpu: ring page1 uses VM inv eng 5 on hub 1
10/17/22 1:45 PM amdgpu 0000 c:00.0: amdgpu: ring uvd_0 uses VM inv eng 6 on hub 1
10/17/22 1:45 PM amdgpu 0000 c:00.0: amdgpu: ring uvd_enc_0.0 uses VM inv eng 7 on hub 1
10/17/22 1:45 PM amdgpu 0000 c:00.0: amdgpu: ring uvd_enc_0.1 uses VM inv eng 8 on hub 1
10/17/22 1:45 PM amdgpu 0000 c:00.0: amdgpu: ring vce0 uses VM inv eng 9 on hub 1
10/17/22 1:45 PM amdgpu 0000 c:00.0: amdgpu: ring vce1 uses VM inv eng 10 on hub 1
10/17/22 1:45 PM amdgpu 0000 c:00.0: amdgpu: ring vce2 uses VM inv eng 11 on hub 1
10/17/22 1:45 PM amdgpu 0000 c:00.0: amdgpu: recover vram bo from shadow start
10/17/22 1:45 PM amdgpu 0000 c:00.0: amdgpu: recover vram bo from shadow done
10/17/22 1:45 PM amdgpu 0000 c:00.0: amdgpu: GPU reset(4) succeeded!
thats pretty generic error unfortunately, try rolling back to the previous mesa release and test again to see if it still occurs
you dont happen to be running plasma on wayland do you?
You are playing Fallout? Isn’t that about the 
APOCOLYPSE?!?!
Then I guess you may be winning! 
Lol… Yeah, it is the first game in a long time that sparked my interest. Started playing nightly while the wife was studying for school. It’s a lot of fun, when it runs that is…
Yes, I’m running Plasma on Wayland though the error persists on regular X11 as well.
Well, finally figured it out. Turns out I had both vulkan-radeon and amdvlk drivers installed and Fallout76 (or rather perhaps Steam) was running amdvlk. I saw the following on the AMDGPU page for Arch:
For Vulkan support, install the vulkan-radeon or amdvlk package. Optionally install the lib32-vulkan-radeon or lib32-amdvlk package for 32-bit application support. Prefer vulkan-radeon for running DirectX12 games through wine/proton, as amdvlk is broken for that purpose.
I don’t know if this is new, I don’t recall seeing it either but doesn’t mean I just didn’t miss it somehow. Anyway, the solution was to untinstall amdvlk:
sudo pacman -R amdvlk
With that driver removed, Fallout is now using the vulkan-radeon driver and it was once again rock solid. Thanks to everyone for your help.
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.