Deadlock Detected
|
I have been playing Mirage for a week now and all of a sudden it crashes doing anything
|
|
|
Same error "deadlock detected" and extreme 8GB RAM usage on a login screen without even doing anything, just afk.
Vulkan/dx11/dx12 - all the same. It started since last small update of poe, not right after league start ggg pls fix |
|
" yes the ram usage increases massively right before deadlock detected | |
|
hellooooo,
it just started today... updated everything.. wtf is going on WHO IS DEADLOCK and where can i find to beat him/her up |
|
|
Can confirm, started today, happens regardless of chosen renderer. Linux, latest stable Proton 10, standalone client. With Vulkan I don't get past the login screen; with DX12 and DX11 I get past character selection to the instance loading screen with the gears animation, and then there it stays until it issues the deadlock error after 10k msec.
*Edit:* Oh, forgot: packcheck reports all good; renaming/deleting AppData/Roaming/Path of Exile/ and/or Documents/My Games/Path of Exile/ doesn't help; clearing all Mesa caches doesn't help either. *Edit 2*: Retried with a new, pristine Wine prefix, reinstalled PoE from scratch, and went through all Proton versions provided by Steam, plus the latest GE-Proton. No dice, deadlock every single time regardless of renderer. *Edit 3*: Two days later, and the problem has disappeared for me as mysteriously as it appeared in the first place. Nothing at all changed on my end, not even my IP address, router has a few weeks uptime... I dunno. It wasn't a client hotfix either. This certainly supports the theory that the issue is in reality *server*-side (although I'd tried all gateways with no success.) Tail end of LatestClient.txt: 2026/03/11 12:59:13 506642146 38779dcb [INFO Client 204] [D3D12] Buffer Count = 3 2026/03/11 12:59:13 506642149 577e6d9c [DEBUG Client 204] [WINDOW] TriggerDeviceCreate 2026/03/11 12:59:13 506642151 577e6dfa [DEBUG Client 204] [WINDOW] TriggerDeviceReset 2026/03/11 12:59:13 506642153 665e1f88 [INFO Client 204] [STARTUP] Device in 0.29321 seconds 2026/03/11 12:59:13 506642153 665e1faf [INFO Client 204] [STARTUP] Tencent Start 2026/03/11 12:59:13 506642153 665e1f88 [INFO Client 204] [STARTUP] Tencent in 2.1e-05 seconds 2026/03/11 12:59:13 506642153 665e1faf [INFO Client 204] [STARTUP] Loading Start 2026/03/11 12:59:13 506642155 665e1f88 [INFO Client 204] [STARTUP] Loading in 0.001315 seconds 2026/03/11 12:59:13 506642155 665e1faf [INFO Client 204] [STARTUP] DebugGUI Start 2026/03/11 12:59:13 506642155 665e1f88 [INFO Client 204] [STARTUP] DebugGUI in 5.7e-05 seconds 2026/03/11 12:59:14 506642431 e001b759 [INFO Client 204] [SCENE] Set Source [(unknown)] 2026/03/11 12:59:14 506642436 2e06c607 [DEBUG Client 204] [SCENE] Height Map Texture: 800 x 800 2026/03/11 12:59:14 506643038 13cb2f92 [WARN Client 204] Failed to create effect graph node (ID: 1542221786). Node type does not exist 2026/03/11 12:59:14 506643038 5c7c661 [WARN Client 204] Failed to create effect graph node "TrailPixelRootCameraFacing" in graph "Metadata/EngineGraphs/GpuTrails/trail_camerafacing.fxgraph" 2026/03/11 12:59:14 506643041 13cb2f92 [WARN Client 204] Failed to create effect graph node (ID: 273360946). Node type does not exist 2026/03/11 12:59:14 506643041 5c7c661 [WARN Client 204] Failed to create effect graph node "TrailPixelRoot" in graph "Metadata/EngineGraphs/GpuTrails/trail_default.fxgraph" 2026/03/11 12:59:14 506643042 13cb2f92 [WARN Client 204] Failed to create effect graph node (ID: 273360946). Node type does not exist 2026/03/11 12:59:14 506643042 5c7c661 [WARN Client 204] Failed to create effect graph node "TrailPixelRoot" in graph "Metadata/EngineGraphs/GpuTrails/trail_default.fxgraph" 2026/03/11 12:59:15 506643339 13cb2f92 [WARN Client 204] Failed to create effect graph node (ID: 1428025895). Node type does not exist 2026/03/11 12:59:15 506643339 5c7c661 [WARN Client 204] Failed to create effect graph node "VertexFlipBookOffset" in graph "Metadata/Effects/Graphs/General/FlipbookOld.fxgraph" 2026/03/11 12:59:21 506649250 890d9dbc [INFO Client 204] Async connecting to ams.login.pathofexile.com:20484 2026/03/11 12:59:21 506649325 890d9d3b [INFO Client 204] Connected to ams.login.pathofexile.com in 13ms. 2026/03/11 12:59:23 506651559 e001b759 [INFO Client 204] [SCENE] Set Source [(null)] 2026/03/11 12:59:23 506651566 88a9056b [DEBUG Client 204] Got Instance Details from login server 2026/03/11 12:59:23 506651569 ca3a6b7e [INFO Client 204] Connecting to instance server at 173.233.133.185:6112 2026/03/11 12:59:23 506651631 ca3a54d5 [DEBUG Client 204] Connect time to instance server was 50ms 2026/03/11 12:59:23 506651681 11869da8 [DEBUG Client 204] Client-Safe Instance ID = 145720917 2026/03/11 12:59:23 506651682 1186a886 [DEBUG Client 204] Generating level 69 area "2_11_endgame_town" with seed 1 2026/03/11 12:59:24 506652331 f22b6a06 [INFO Client 204] Tile hash: 2815062652 2026/03/11 12:59:24 506652331 f22b6a01 [INFO Client 204] Doodad hash: 45103505 2026/03/11 12:59:24 506652341 e001b759 [INFO Client 204] [SCENE] Set Source [Karui Shores] 2026/03/11 12:59:24 506652370 2e06c607 [DEBUG Client 204] [SCENE] Height Map Texture: 810 x 540 2026/03/11 12:59:24 506652402 df74df9b [DEBUG Client 204] [SCENE] Static Walkability Texture: 621 x 414 2026/03/11 12:59:43 506672156 88f7e90f [CRIT Client 204] Deadlock detected with timeout 10000ms; running graph nodes: MsgProc Last edited by WibblerGiddyBuzz#0076 on Mar 13, 2026, 11:14:50 PM
|
|
|
NB!!!
antiboon • 3mo ago for anyone still possibly struggling try updating your drivers and if that doesnt work delete this folder C:\Users####\Documents\My Games\Path of Exile 2 I updated my drivers and was still crashing but when i deleted the folder it worked just fine no idea why but it worked ______________________________________________ Worked for me.. you will need to remake your UI/keybinds |
|
|
I recently encountered this problem. I reinstalled the game on another ssd, I'm using a filter downloaded directly from Filterblade, and I also turn off MSI Afterburner while playing. The error recurs, but infrequently and not systematically
|
|
|
I delete all my custom filter in :
C:\Users\Users\Documents\My Games\Path of Exile I wait 15sec, the pop up deadlock appear but the game loads and works. I just slide in corner the pop up. |
|
|
Same here. The popup occurs every start now for me. I slide it to the corner and just play.
|
|
|
I am getting quite a few deadlock while the game is running in the background. Playing the game doesn't cause it. But when I tab out to another window and poe is running windowed borderless then there is a chance that I get a deadlock.
It's especially worse when I tab out before a loadscreen or when my internet connection isn't very stable. I am playing on 2 different internet connections and one is less stable than the other. So I can for sure say that this is a factor for me. I haven't tried switching graphic modes or anything. I suspect it's more a netcode thing than a graphics issue. |
|




























