Deadlock detected

Hello, after the latest update, I started getting the "Deadlock detected" error in "Heist." The game freezes, and after about 5 seconds, the error appears. After about 10-15 seconds, the game unfreezes and disconnect from server. If I click OK or close the error window, the game closes too. I haven't been able to find a cause or pattern for this issue, but I only encounter it in "Heist"—sometimes right at the beginning, sometimes when opening a large chest using a skill, and sometimes just for no reason. This can happen multiple times during a single contract. I might open one chest, start opening a second, and get a crash on it, then re-enter, open the second chest, and get a crash on opening the third, for example. I've tried almost every tip on the forum and done almost every basic thing I could think of to fix the problem (updating my graphics card drivers, verifying file integrity, reinstalling the game and deleting all files, deleting DXCache, trying moving the error window to a second monitor and continuing to play, changing the renderer, disabling MTX, etc.), but nothing has helped. Sometimes, after a crash, some effects would "brick" (Cyclone would only render 1m from the character, Shockwave would lose some effects) and would take a long time to load—a minute or two. The performance graph doesn't show anything abnormal during gameplay, before the crash, or at the time of the crash. My PC doesn't freeze; I can easily minimize it at the time of the crash and use the browser or file explorer. I'm attaching a link to Google.Drive archive, which contains the client log, DxDiag, screenshots, and a video of the error. I'm ready to provide all the necessary information and conduct additional tests if necessary. Please help me solve this problem.

The new patch didn't fix the issue for me. I completed three contracts without the error, but on the fourth I got deadlock detected again on every chest and at the end of the heist while opening the door to escape. RIP my loot.
The logs still show the same line: 2026/04/20 23:19:09 303113625 88f7e90f [CRIT Client 20248] Deadlock detected with timeout 10000ms; running graph nodes: Simulation

It's been almost three weeks since I contacted via email and forum.I've been unable to play the game for over a month now. I initially hoped the issue would be resolved quickly, given the number of people affected. I was wrong. I see no sign of any work being done on the problem. The only response I received was to review the forum materials and, if all else fails, create a thread and provide as much information as possible to resolve the issue. I created a thread and waited, bumping the thread every day, checking other threads with this issue, trying various other solutions, but nothing changed.
I ask for your help once again in resolving this issue. I will burn my contracts daily and create bug reports until the issue is resolved.
Bug Report ID: #2 240 433 924 - Deadlock Detected. During the contract, at the very end, when i broke the display case containing the main target and pick it up, a crash occurred after a few seconds.
Bug Report ID: #1,531,650,924
Bug Report ID: #1,176,586,543
Bug Report ID: #1,996,939,608
Bug Report ID: #2,747,152,809
Bug Report ID: #2,473,556,587
These five crashes were received in the next contract. The first four crashes occurred while opening the reward chests, and the fifth, like in the previous contract, occurred at the very end.

Today I get only 1 crush and ever managed to get the loot out, lucky me
Bug Report ID: #2 157 119 030
Deadlock detected during lockpicking second reward chest in heist (Jewelry)
Still have the same line in logs - 2026/04/30 23:40:03 100859578 88f7e90f [CRIT Client 13744] Deadlock detected with timeout 10000ms; running graph nodes: Simulation
Full log file: https://pastebin.com/wxzQpTiP

Bug Report ID: #3 205 482 796
Same situation, as was yesterday, 1 crush at start, during opening reward chest
2026/05/01 22:20:40 182495187 88f7e90f [CRIT Client 21344] Deadlock detected with timeout 10000ms; running graph nodes: Simulation
Full log file: https://pastebin.com/zqv4wfUJ

Bug Report ID: #2 819 512 678
Bug Report ID: #3 818 212 042
Crush two times, this time i pick trap disarmament contract. First crush was on opening second reward chest, second during escape faze after picking up main target
2026/05/02 23:59:24 274816375 88f7e90f [CRIT Client 13992] Deadlock detected with timeout 10000ms; running graph nodes: Simulation
2026/05/03 00:02:32 275004046 88f7e90f [CRIT Client 25216] Deadlock detected with timeout 10000ms; running graph nodes: Simulation
Full logs file - https://pastebin.com/s52nZuPM

Bug Report ID: #2 401 264 858
Today, I almost believed that the problem was gone because I completed three contracts without any errors. But I have a bug report, which means I've get deadlock again. It happened on the fourth contract while opening the reward chest
Still same line - 2026/05/04 02:14:50 369340984 88f7e90f [CRIT Client 15664] Deadlock detected with timeout 10000ms; running graph nodes: Simulation
Full logs file - https://pastebin.com/naDsMLye

Bug Report ID: #668 375 347
Bug Report ID: #488 251 599
Another day, another bug report , sadly for me.
First one i get during opening reward chest, second after picking up main target
Logs lines still the same:
2026/05/05 02:58:46 458375406 88f7e90f [CRIT Client 14376] Deadlock detected with timeout 10000ms; running graph nodes: Simulation
2026/05/05 03:03:05 458634140 88f7e90f [CRIT Client 9772] Deadlock detected with timeout 10000ms; running graph nodes: Simulation
Full logs file - https://pastebin.com/scbSTaD7

Bug Report ID: #3 584 285 858
Today, I ran about 10+- contracts. I did it on the second character on the same league, just out of curiosity. I started with 68-level contracts because this character was too weak to complete 83-level contracts, but after finishing a few low-level contracts without any errors, I decided to try higher-level contracts again out of curiosity. I didn't get a single deadlock during that time, but when i login to my main character and run a contract, i was immediately get a deadlock detected. I still don't know why it's happening, and why it happens only to one character.
Log file is a mess right now, i guess it's because the sands of time and trigger bot interaction
Full log file - https://drive.google.com/file/d/1SwNLlcTHKDhk0f2_hzMNph3g2qB9R_oA/view?usp=drive_link