protonscr

Final Fantasy VII Rebirth consistently triggers amdgpu gfxhub page fault and ring gfx_0.0.0 timeout on RX 6700 XT (Navi22)

vkd3dopen
HansKristian-Work/vkd3d-proton#3176 · opened 2026-07-27 by JuanJoseDev88 · updated 2026-08-07 · 4 comments · github
JJuanJoseDev88 2026-07-27 github

FFVII Rebirth GPU Hang on AMD RX 6700 XT (RADV/Mesa) under Linux

Summary

Final Fantasy VII Rebirth consistently triggers a GPU hang on an AMD Radeon RX 6700 XT running Linux. The crash occurs reliably during the Chocobo race selection or shortly after entering a race.

The issue results in:

  • GPU page faults
  • ring gfx_0.0.0 timeout
  • Full GPU reset
  • VRAM loss
  • Game crash

The problem persists across multiple Proton versions and configuration changes.


System Information

Component Value
GPU AMD Radeon RX 6700 XT (Navi22)
CPU AMD Ryzen 5500X
Driver RADV
Mesa 26.1.4 → 26.1.5
Vulkan 1.4
Kernel 7.1.3-pikaos
Distribution PikaOS
Launcher Heroic Games Launcher 2.22.0
Proton GE-Proton11-1
API DX12 (VKD3D-Proton)

Vulkan

GPU:
driverName = radv
driverInfo = Mesa 26.1.5
deviceName = AMD Radeon RX 6700 XT (RADV NAVI22)

The GPU supports:

  • VK_EXT_device_fault
  • VK_EXT_robustness2

PCIe

Speed: 16 GT/s
Width: x16

No PCIe down-training.


Overclock

GPU is completely stock.

SCLK
500 MHz
2594 MHz

MCLK
97 MHz
1000 MHz

Voltage offset
0 mV

Original Kernel Messages

The GPU consistently faults while executing the VKD3D queue thread.

Process ff7rebirth_.exe
thread vkd3d_queue

Page faults:

[gfxhub] page fault
Faulty client:
SQC (data)

PERMISSION_FAULTS: 0x3

Followed by:

ring gfx_0.0.0 timeout

Then:

GPU reset

Finally:

VRAM is lost due to GPU reset

dmesg excerpt

[gfxhub] page fault

Process:
ff7rebirth_.exe

thread:
vkd3d_queue

Faulty client:
SQC (data)

PERMISSION_FAULTS: 0x3

ring gfx_0.0.0 timeout

GPU reset begin

GPU reset succeeded

VRAM is lost due to GPU reset

Proton Log Symptoms

The Proton log prior to the GPU reset shows repeated VKD3D activity until the device hangs.

After the GPU reset Heroic reports the game as crashed.


Reproduction

The issue is highly reproducible.

  1. Launch FFVII Rebirth
  2. Load save
  3. Go to Chocobo races
  4. Select a race
  5. GPU hangs

Sometimes it crashes immediately on selection.

Sometimes it crashes 20–60 seconds later.


Testing Performed

Mesa

Tested:

  • Mesa 26.1.4
  • Mesa 26.1.5

No improvement.


Proton

Tested:

  • GE-Proton11-1

Behavior:

  • crashes almost immediately

RADV_DEBUG=llvm

Tested.

Result:

  • Game crashes while loading save.
  • Worse than default.

ppfeaturemask

Originally:

0xffffffff

Disabled GFXCLK DPM:

0xfff7bfff

Kernel confirms:

DPM_GFXCLK disabled

Crash still occurs.


AMDVLK

Installed.

Forced using:

VK_ICD_FILENAMES=/opt/amdgpu/share/vulkan/icd.d/amd_icd64.json

Verification:

driverName = AMD open-source driver

Result:

  • FFVII Rebirth fails before creating Vulkan instance.
  • DXVK reports:
Failed to create Vulkan instance
Failed to initialize DXVK

AMDVLK therefore could not be tested further.


Heroic Logs Collected

FF7_Rebirth_crashlog.txt

The Heroic logs collected during testing consistently showed:

  • DXVK initialization
  • VKD3D queue activity
  • Game termination after GPU reset
  • No Wine exception before the GPU hang

One crash occurred immediately after Chocobo selection.

Another occurred after several seconds inside the race.


Additional Observations

The issue appears isolated to this title.

Other Vulkan applications run normally.

GPU stress outside FFVII Rebirth has not shown instability.

The crash always involves:

vkd3d_queue

and

ring gfx_0.0.0 timeout

suggesting a graphics queue hang rather than a general hardware failure.


What Was Not Tested

  • Mesa 25.x
  • Upstream Mesa Git
  • Latest VKD3D-Proton nightly
  • Upstream Linux kernel
  • Steam Runtime instead of Heroic
  • Steam Proton Experimental (not available in Heroic)

Suspected Cause

Current evidence suggests an interaction between:

  • FFVII Rebirth
  • VKD3D-Proton
  • RADV
  • Navi22 (RX 6700 XT)

The kernel consistently reports GPU page faults originating from the vkd3d_queue thread, followed by graphics ring timeouts and GPU reset.

No evidence currently suggests:

  • unstable GPU clocks
  • PCIe issues
  • overclock instability
  • VRAM overclock
  • power limit instability

The behavior appears software-triggered rather than hardware-induced.


Relevant Log Snippets

Kernel

[gfxhub] page fault

Process ff7rebirth_.exe

thread vkd3d_queue

PERMISSION_FAULTS: 0x3

ring gfx_0.0.0 timeout

GPU reset begin

GPU reset succeeded

VRAM is lost due to GPU reset

Vulkan

driverName = radv

Mesa 26.1.5

Proton

DXVK initialized

VKD3D queue active

GPU reset occurs

Game terminates

Requested Feedback

Has anyone observed similar GPU hangs with:

  • RX 6700 XT
  • Navi22
  • RADV
  • VKD3D-Proton
  • FFVII Rebirth

particularly during the Chocobo race sequence?

Any patches, Mesa regressions, or VKD3D workarounds would be greatly appreciated.

Oooaaqq 2026-07-29 github

I am seeing a very similar GPU reset signature on an RX 6800 (NAVI_FLOUNDER) with Mesa 26.1.5 and Linux 6.18.39.

The first fault is triggered by VS Code's Wayland/Electron GPU process, followed by:

[gfxhub] page fault
Faulty UTCL2 client ID: SQC (data)
PERMISSION_FAULTS: 0x3
ring gfx_0.0.0 timeout
Ring gfx_0.0.0 reset succeeded
device wedged, but recovered through reset

The GPU is stock, PCIe Gen4 x16, with no AER/MCE errors and normal temperatures. This is a different GPU generation and workload from this report, but the kernel fault sequence appears identical.

Rrunar-work 2026-07-31 github

@JuanJoseDev88 Can you upload a save file where you can reproduce this issue?

@ooaaqq These error messages are fairly generic and look similar across different issues. Generally, if it's not from the same game, it's unlikely that it's related.

JJuanJoseDev88 2026-08-04 github

@JuanJoseDev88 Can you upload a save file where you can reproduce this issue?
@runar-work Sure here it is.

ff7rebirth001.zip

Rrunar-work 2026-08-07 github

Thanks for the save file. Unfortunately, I haven't been able to reproduce this issue on my end so far. I've mainly tested on RX 6800 with 7.1.6-arch1-1, Proton Experimental and Proton GE 11-3, Mesa 26.1.5, 26.1.6, low and high graphics presets. I'm launching the game through Steam. I also tested briefly on RX 9070 and RX 7600 before I switched just in case, but no issues there either.

Do you know if any particular graphics settings trigger this problem?

BTW, if you check the "Allow using Valve Proton builds to run games" option in Heroic's advanced settings you should be able to test Proton Experimental as well. I don't know if it'll make a difference here, but it could be useful for future testing.

Proton versions

Launch options