0.4.0 "Deadlock Detected"

BUMP

Guys, I did something that worked for me!

When you open the game, it will ask you to click 'play' with your character. Just hold Alt (the same thing you do to create a new instance).

This will take you back to your base or the map.

I hope it works for you too!

I'm completely unable to run my temple. I have a 70 room temple, when I've completed around 30 rooms, the performance gets terrible, with stutters, freezes, deadlock crashes and disconnects. For me to complete a temple, I need on average to restart the game four times and pc one time. I also notice fps drops, stutters and sometimes crashes while maping.

Not sure what to do now. I didn't have any issues in 0.1, 0.2 and 0.3. I'm pretty sure this has something to do with the cpu. I can see the cpu bar spike high on the graph, and quick google on 'deadlock detected' also suggests cpu. And after reading this thread, this issue seems to be more common on X3D-cpu's.
Any suggestions?


RTX3080
AMD7800X3D
32GB DDR5
WIN11
DX12

When I changed the Texture Filtering option to just "4x", this error gone, everything fine is for multiple days already.

Update: I started to play a twink and encountered this error 2 more times:
- On the Microtransactions shop menu lauch
- On the Atlas menu launch

I agree that the most rational idea is to stop play this League. No feedback from developers about this error, no fixes.

Still no staff posts. What's going on?

Same. Deadlocks killing the game from time to time since 0.4.0

Yeah, agreed. The weird part isn't even the deadlock - it's that this thread has been sitting here for about two months like a forgotten houseplant. No staff reply, no "we're looking into it", not even a token "have you tried turning it off and on again".

So what's the deal? Is this getting ignored, or is the plan to pretend it doesn't exist until it evolves into a feature?

In solo it's already annoying, but at least you can usually limp along. In group play it's straight-up party poison. You disconnect, get kicked, lose momentum, and everyone's sitting there waiting like you're running the world's worst "brb" simulator. A bug this widespread shouldn't be nuking party sessions with zero acknowledgment.

Interestingly enough after struggling with the deadlock detected issue and constant freeze then gears turning followed by disconnect from the server for the last few weeks, after the little update that seems to not really contain anything the game is not doing it anymore.

I'm not sure if they silently released something that addressed the bug or if the millions of things I have done over the last few weeks all came together to start working now.

The last thing I did was use the startup tags in steam:
--nologo --no-nv --24h2-mt --test-disable-transfer-queue --test-std-alloc --test-disable-frame-move-jobs --test-disable-frame-render-jobs --no-device-recovery --disable-assert-box

I've also reinstalled my graphics drivers using DDU uninstall first, tried a few different version, upgraded my BIOS firmware, updated all my drivers, tried with or without sound, disabled cache in Steam, deleted cache, changed cache directory to another drive, restarted router, changed DNS servers, used TCP/IP optimizer, trimmed all M.2 SSD's, factory reset GPU, deleted POE2 settings and started anew, tried various settings in POE, tried with or without triple buffering and dynamic culling as well as dynamic resolution, tried with or without multi threading, tried using process lasso and and not using Core 0, tried with or without game mode, tried using game booster from iobit to disable all non critical services before the game starts...

I mean I've tried EVERYTHING, I'm an IT person and if I get an unsolvable problem I will continue until I find a solution.

Every single fix I tried I still crashed frequently and in a similar fashion. I believe it has to do with shader cache and it has slightly improved after rebuilding it and disabling it in Steam, but I still go frequent crashes.

This last update that was silently pushed through made me crash only once in 15 maps or more and before that I was crashing maybe 3 times per map at least.

Oh and I have a 7800 XT GPU and a 7800X3D CPU. From what I have read it's not related to GPU issues as both Nvidia and AMD users are complaining about it. There does seem to be a slight correlation with AMD X3D CPU's perhaps