[7,60][Crash] freezes and crashes after, during gameplay or timelines missions

[SolemnDevil]

Hello

not much to say, is crashing randomly during gameplay or during timeline missions
recently i disabled all the dlcs besides timelines because i want to add them one by one after i achieve everything in each dlc, and during the missions in the timelines the game is freezing 2 times and after immediately crashing at some point during the missions. now i am at the last mission (Flight of the Dragonfyre) and i can not pass it because of the crash.
here are the files, i seen for timelines no save files are created locally
https://drive.google.com/drive/folders/ ... drive_link

[Alan Phipps]

The Diag element of your upload is not the DxDiag format that I am far more familiar with and so I can't easily see what device drivers you have, nor your Windows Error Reports. However, I can see that you have an Intel 13th gen cpu which may suffer from the fairly common Intel 13/14th gen cpu memory access instability issue when used with a modern capable graphics card and stress loading by such as X4. The symptoms described do sound like that issue.

[SolemnDevil]

i am using Linux , that is why i have no Windows Error Report or Direct X .
i dont think is the CPU, the crash seems to happens because some errors between the Disabled DLCs and Timelines DLC, enabling all i dont have any crash during game play (open universe ), just in the last mission of Timelines still crashes. when only Timelines is enabled as a DLC and all other DLCs disabled i have crashes everywhere. so please have a second look.

here is my system:
CPU: Intel Core i5-13600K (13th Gen, 14 cores / 20 threads)
Microcode: 0x12F
Scaling Governor: intel_pstate, powersave mode
Motherboard: ASUS TUF GAMING Z790-PLUS D4
UEFI: Version 1805 (Date: 10/30/2024)
GPU: AMD Radeon RX 7900 XTX
Driver: amdgpu (Mesa 25.1.5)
Vulkan Driver: RADV (Vulkan 1.4.313)
OpenGL: 4.6 (Renderer: radeonsi navi31 LLVM 20.1.7)
Monitors:
3x Samsung LC27G5xT @ 2560x1440 @ 144Hz (DP-1, DP-2, DP-3)
Layout: Triple screen (left-center-right)
RAM: 64 GB DDR4
Drives:
Root Disk: SanDisk Ultra 3D 2TB (btrfs)
Additional SSDs and HDDs: WD SN850X (1TB), Crucial P2 (2TB), Seagate 16TB, Seagate 4TB

Software:
OS: Arch Linux (rolling release)
Kernel: 6.15.6-zen1-1-zen (Zen performance-optimized)
Wayland Compositor: Hyprland 0.49.0
Display Server: Wayland (Xwayland: 24.1.
Login Manager: SDDM
Audio:
PipeWire 1.4.6 (with WirePlumber)
Devices: Intel HDA (onboard), AMD HDMI, SPCA2281 webcam mic
Networking: Intel I226-V (Ethernet, 1 Gbps)
Mesa Version: 25.1.5-arch1.1
DRI Driver: radeonsi (for OpenGL)
Vulkan ICD: radv (RADV for AMD GPUs)
DRM Version: 3.63
Display Driver: amdgpu
EGL Version: 1.5
wap: ZRAM 4 GiB, unused
Filesystem: Btrfs
DE Tools: Waybar, hypridle, hyprlock
Steam/Proton GE / Proton Experimental
No GPU overclocking

Temps during gameplay:
CPU Temp: ~40°C
GPU Temp: ~58°C
GPU VRAM Temp: ~60°C
GPU Fan Speed: ~930 RPM

i hope this helps

and from this error :
Vulkan::Queue(0) failed with err -4 → VK_ERROR_DEVICE_LOST
VideoBaseClass::BE_ThreadedRenderStart() Queue failed!
VideoBaseClass::GetMainCB() Queue failed!

seems to be a "disconnection" of the GPU.
please have a second look!

BR

[xrogaan]

A crash is a catastrophic failure, and as such ought to give clues as to why it happened. If the game itself is to blame then a dump file should have been created and, at the very least, a trace of the failure in your system's kern.log. Anyhow you don't provide those clues, but we might not need them. The reason is that your intel CPU is part of a family with known and well documented failure state (it literally cook itself to death). As such, it's probable that you are one of the victims of that bug. Especially if you didn't apply the microcode patches in time, because any damage is permanent.

You can try to figure out if you're affected using the stress-ng utility:

Code: Select all

stress-ng --cpu 20 --cpu-method fft --timeout 30m

Warning: this will stress your CPU for 30 minutes using fast fourrier transform. During the test, monitor your hardware "vitals", that is temp and frequency.

[xrogaan]

Sorry for the double.

If it is indeed a vulkan related problem, then you need to take a look into your system logs. Nothing you provided gives a clue as to what went wrong. Maybe a driver crash. Maybe a kernel panic. Maybe Wayland decided to act up. No idea.