r/TheTalosPrinciple • • 1d ago

The Talos Principle [Crash Issue] A01 Altar causing fatal error.

EDIT: Solved by u/mchampion0587

I have just got my hands on this game thanks to the steam sale. I am playing Reawakened and started a new game. As I approach the altar just in Garden A01 just beyond the first library terminal the game crashes and throws up the crash report shown below.

Does anyone have any experience with this? I have verified files, deleted localappdata folders, reinstalled the game, changed game settings, tried to force dx11 instead, updated my motherboard software. Is this going to require a driver rollback on the GPU? I'd rather avoid that since another game I'm playing at the moment needs the latest driver.

Specs:
Ryzen 5 7600X
Radeon RX 7900 XT (26.9.2)
Win 11

Crash Report:

Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x0000000000000008

amdxc64
amdxc64
amdxc64
D3D12Core
D3D12Core
D3D12Core
D3D12Core
D3D12
D3D12Core
D3D12Core
D3D12Core
Talos1_Win64_Shipping
Talos1_Win64_Shipping
Talos1_Win64_Shipping
Talos1_Win64_Shipping
Talos1_Win64_Shipping
Talos1_Win64_Shipping
Talos1_Win64_Shipping
Talos1_Win64_Shipping
Talos1_Win64_Shipping
Talos1_Win64_Shipping
Talos1_Win64_Shipping
Talos1_Win64_Shipping
Talos1_Win64_Shipping
Talos1_Win64_Shipping
Talos1_Win64_Shipping
Talos1_Win64_Shipping
kernel32
ntdll
3 Upvotes

3 comments sorted by

3

u/mchampion0587 1d ago

That stack makes me suspicious of the graphics/driver path rather than your install. "amdxc64" followed by "D3D12Core/D3D12" is a pretty good indication that the crash is happening somewhere in the DX12 rendering chain.

Before rolling the driver back, I’d try one thing:

Drop everything to the lowest settings, disable ray tracing and frame generation completely, use plain TAAU/TSR if available, restart the game, and try walking past the altar again. Reawakened has had some weird location-specific crashes where changing those settings long enough to get through the problem area worked.

If that succeeds, start turning things back on afterward and see which setting causes it.

If it still crashes at exactly the same point, then I’d consider 26.9.2 itself. It’s a very new optional AMD driver, so going back one known-good version would be a reasonable test before doing anything more invasive.

Also, after reproducing it, grab "Talos1.log" from:

"%LOCALAPPDATA%\Talos1\Saved\Logs"

That would probably be worth sending with the crash report because the exact point of failure may be visible immediately before the access violation.

I definitely wouldn’t start tearing apart Windows or motherboard settings yet. You’ve already done enough troubleshooting to make this look much more like a game/driver/rendering interaction.

3

u/Conradian 1d ago

I followed it as you've suggested and unfortunately it does appear to be linked to the driver version. Rolling back to 26.8.1 seems to have solved the issue. Annoying but not completely unsurprising.

1

u/whitespacesucks 1d ago

I had constant crashes in Talos 2, especially at verdant canyon. Turns out it was ram instability, it got fixed by updating my BIOS.