Yes. MSI Tomahawk, AMD 7 5700, Geforce 2070, 32GB RAM. No hint as to why it crashes. Temperatures are fine and etc. Event Logs show crash but no useful info. After crash it wont play again until I reboot my computer. No available support from Developers that I could find.

I've been trying to figure out how to fix it for a couple weeks now. I don't think there's any 1 setting you can change to fix it. It seems to be a problem buried in how it was ported from console. The best I've been able to come up with so far is to set "reflections" to low and set the frame rate to 60hz. I had been playing with all the settings on high at 1440p/144hz, but these changes seem to help while not reducing the visual quality by any noticeable amount.
5950x/3080ti

I've only had one random crash in current ~50 hour playthrough on maxed graphical settings (Acer Helios 300 laptop w/ external monitor); I can maybe remember 1 single crash between 2 other previous playthroughs in the past, so in short game has always impressed me with how stable and polished it seems to me and I can hardly think of any bugs besides a couple very rare of graphical artifacts I can count on the fingers of one hand...I guess I can count myself lucky that my hardware and the game seem to get along; sorry to hear you are having issues and really hope you can work them out because it's a gem worth experiencing without the hassle of technical issues

Also...to second poster, there's no guarantee that you guys are experiencing the same issue. Games are complex and large pieces of software where things like different hardware, operating systems, drivers, etc etc. are all interacting and just because both your games are crashing doesn't mean that it's a related issue whatsover...

Well it can always be driver problems beside the actual game bugs. We are def. not alone with these random chrashes but also under 10% of all gamers at least this is what reddit told me. I will try to change to my 3080ti and see how that goes. I will also try to fix to 60fps / 60hz and will install it on my SteamDeck with 40hz. Its wired since its totally random...

Interestingly we have the same GPU and similar specs, could be related? I've been having consistent problems as well on my PC. The best 'solution' I've found so far is what you've already mentioned sadly; Limiting the fps to 60 has helped give me better 'sessions' (20-30min or sometimes more) before crashes. I've ensured updated graphics drivers, validated steam files. I've greedily tried increasing the fps cap but that just lets me speed run crashes :/ (2-3 min instead lol)

Specs:
Intel i5-13600k
32gb RAM
AMD 7900 XTX
Win11

A few, 4-5 over now 50+ hours. None during the first 30 hours. Hardly anything to complain about. Otherwise it runs very well with all the settings maxed out on 1080p, vsync on because of old monitor so the fps is maxed at 60.
Intel i7 8700
32 gb ram
Geforce 2700 super
win10

For all I know these few crashes can be because storage-related on my windows-drive which is severely starved for space which is a problem for me (game installed on other, still files on C)

same situation

So I installed this on my SteamDeck now and had no crashes at all. I got used to it and prob. will keep playing it on my steamdeck docked to my TV until driver updates or something else will fix this. I bet its the f king AMD drivers, they suck!

the game has trouble with higher frame rates, only had 1 crash in 5 days of playing since I limited the game to only 60fps

One thing some people have said is they're noticing that the recommended 850W PSUs for RX 7900XTX GPUs are not always sufficient and migrating to a 1000W+ unit can solve issues like this, probably related to transient spikes in power usage.

Eye of Newt님이 먼저 게시:

One thing some people have said is they're noticing that the recommended 850W PSUs for RX 7900XTX GPUs are not always sufficient and migrating to a 1000W+ unit can solve issues like this, probably related to transient spikes in power usage.

Personally I'm using a new CORSAIR RM1000e with my 7900XTX, but still getting crashes.

Specs:
Intel 13600k
32GB RAM
GTX 1080
WIN10

29 hours in game, all work perfect, no crashes, lags or other weird things

Same problem here - completely random crashes.
No AMD driver related dialog pops up just the game crash dialog and a question whether I wish to send the dump to the developers.
Sometimes the game runs fine for 2 hours, other times it crashes right after 5 minutes.
For me the crashes started right after I switched from RX 6600XT to Sapphire Pulse RX 7900XT (my PSU is Seasonic Vertex 850W).

I took a peek at the generated dumps and it always fails at the same place on the same exception...
The game makes a call into D3D12Core.dll (CGraphicsCommandList::OMSetRenderTargets) which in turn calls implementation inside the AMD GPU driver library amdxc64.dll where it crashes with an exception "Access violation reading location" and the target memory address.

Given the fact that this issue is obviously not so widespread... this points to an issue inside AMD Radeon driver 🫠

VitaI님이 먼저 게시:

Same problem here - completely random crashes.
No AMD driver related dialog pops up just the game crash dialog and a question whether I wish to send the dump to the developers.
Sometimes the game runs fine for 2 hours, other times it crashes right after 5 minutes.
For me the crashes started right after I switched from RX 6600XT to Sapphire Pulse RX 7900XT (my PSU is Seasonic Vertex 850W).

I took a peek at the generated dumps and it always fails at the same place on the same exception...
The game makes a call into D3D12Core.dll (CGraphicsCommandList::OMSetRenderTargets) which in turn calls implementation inside the AMD GPU driver library amdxc64.dll where it crashes with an exception "Access violation reading location" and the target memory address.

Given the fact that this issue is obviously not so widespread... this points to an issue inside AMD Radeon driver 🫠

Have you reported this to AMD? Guerilla appears to be radio silent with HZD these days, but AMD should be able to patch out the bug that gets triggered on that call.

https://www.amd.com/en/support/kb/faq/amdbrt

VitaI님이 먼저 게시:

Given the fact that this issue is obviously not so widespread... this points to an issue inside AMD Radeon driver 🫠

Its always AMD Drivers, they are still really really bad. You could write AMD an Email!

Off Topic: I updated my drivers via the offical software adrenalin, and guess what, it destroyed windows wich didnt boot correctly afterwards anymore... Bluescreen (they fixed this but still) How can a huge company be so bad at relasing a driver for GPUs... unbeliveable