AMD driver timeout during mapping which freezes whole PC

"

spant83#4321 wrote:

I tried with the new drivers (26.1.1), it’s the same issue — I crashed halfway through the first map. I switched back to Arc instead. I also tried with DX12; Vulkan still seems dead for me.

absolutely same for me ((((

Unfortunately for my last tests, the adrenalin driver 26.1.1 remains fully unstable and it is driving the PoE2 game to hard crash.

I am running the game with the following rig :

CPU : 5800x3D
Memory : 64 GB (DDR4-3600)
GPU : AMD Sapphire Nitro+ 7900XT

At the moment, the best driver that's ensure the best stability is the flavor AMD Adrenalin 25.9.2 ; so I stick on it, no choices.

All uplifted flavors as 25.10.x, 25.11.x, 25.12.x and 26.1.x, remains problematic and broke the game.

Something seems to have been reworked in these latest AMD driver versions and it has introduced a major regression for the PoE2 game.

It would be great if GGG engine team could contact AMD Graphic driver Team for signaling this issue and ask them to provide a fix for a flaw that's occuring during 4 major release of AMD Driver now.

It is an AMD issue, not a GGG issue

These latest drivers passed the whql and they are able to freeze the whole PC, it is just mind-blowing

I don’t know whether GGG or AMD is at fault, but on my end everything works perfectly fine — all my other games run without any issues. So I’m wondering what’s going on. Before patch 0.4, I had no problems at all, so I’m not sure if their optimization broke something, but it definitely used to work.

And aside from Vulkan, which I wasn’t using anyway, the only time I get driver timeouts is with Comet. The game reloads itself and I can keep playing, but if I have, say, a 5% chance to crash every time I cast Comet (just a rough estimate), I’d rather not play the skill than risk messing up my drivers. And it’s not only my own Comets that cause crashes — it has already happened with enemy Comets as well (though that’s even rarer).

What makes me think the issue comes from GGG is that Comet is really a “full package” spell:

a large projectile

impact + AoE

particles

probably a dedicated shader (ice / light / transparency)

and sometimes multiple Comets at the same time

And I’m wondering whether AMD is more strict or sensitive when it comes to borderline shaders.

On top of a shader on GGG’s side that’s already pushing the limits, this likely creates a combo that ends up crashing the driver.

I have the same issue... No answer yet from GGG?

Playing spark. Had same problem. But only with comet in cast on crit. Arc version was fine.
Rolled back to september version. 25.9. works fine. Try it.

Allso i suggest you to undervolt your radeon a bit. Im, with my asus 7900 xtx, now on 97% voltage/95% max core frequency. Much more stable and less heating.