Consistent framedrop in update #6,014

eldiaxy

New member
What the title says. Ever since update #6,014, after about 10/15 minutes I get a drop in frames from 25-55 fps in lane to 8-13 fps for 4 to 8 minutes and then with zero imput from me, it returns to 25-55 fps for few minutes. Then it decides to return to 8-13 fps.
Nothing from my PC's side does anything NOR does any other game have this issue. Drivers are up-to-date, files are verified, rendering is directx11 (on Vulkan I have a 0 out of 0 then crash issue), Windows Defender isn't running a scan while playing. The ONLY thing that I could realistically blame for this is a LENOVO BIOS update (Ideapad 3 15,6'')

Here are my specs (I know, probably they're the issue):

CPU AMD Ryzen 5 5500U with Radeon Graphics 2.10 GHz
GPU AMD Radeon Graphics
Installed RAM 8,00 GB (dostępne: 5,85 GB)
Type of OS 64-bitowy system operacyjny, procesor x64
Version Windows 11 Home
Update 23H2

I do not know if it is enough information to work with. I am just going a bit insane with this random framedrop bs that happened.
 
Update: I changed to Vulkan and disabled pre-loading maps and shaders. Also allowed the cache file to not have big issues with freezes (I am okay with them when they're about shaders getting cached)
I only played 1 game in version #6,016 and I noticed three things- I crashed twice, had a that choppiness (8-10 fps, choppy visuals, eaten imputs ect.) and those things happened at exactly same times I had a framedrops on directx11.
Match ID: 48027743
Crashes happened at ~15 minutes and ~23 minutes. I played Billy in the game
 
Update: after changing to Vulkan- there were consistent crashes at ~15 minutes and ~30 minutes in EVERY SINGLE GAME.
Match IDs:48032882, 48034727,48066314,48068663,48068663,48072005,48073774,48077651,48095823,48148320,48152979,48155365, 48157934

I want to pinpoint a single match ID:48150619. There wasn't a ~30 minute crash. Instead, at between ~27 and ~32 minutes, few of my teammates were dead and there was a giant framedrop, in which I saw their standing (respawn) model be replaced with a dead model which flopped around all at once.
 
Your problem is most likely your 8gb of ram, you need at least 2 stick of ram, i would say 32 gb minimum with windows 11... With ryzen to run in dual-channel because of how the memory controller and Infinity Fabric work. Try to set everything to minimum but i would say you need to have dual channel memory.
 
Your problem is most likely your 8gb of ram, you need at least 2 stick of ram, i would say 32 gb minimum with windows 11... With ryzen to run in dual-channel because of how the memory controller and Infinity Fabric work. Try to set everything to minimum but i would say you need to have dual channel memory.
Here's the issue with that thought process- while it is really good... I didn't have consistent framedrops OUTSIDE OF TEAMFIGHTS (cuz yeah, those chugged my frames) issues with directx11 and crashes on Vulkan pre build #6,014. I had everything on the lowest settings since Deadlock opened for the public and I never experienced issues with Vulkan or Direct X 11 rendering on the same scale as post build #6,014.

And I'd like to update to 32 gb... but no money for it atm. Plus if I had money for the RAM- I'd much raather upgrade my laptop (college, don't ask)

I do have a theory for the reason as for crashes and consistent framedrop thought. It might sound stupid, but there was a funny bug happening whenever people died in lanes. All the bodies suddenly appear on blue bridge lane. It was a consistent and funny bug that I always welcomed. Post #6,014- that bug is gone.
So, maybe, juuuuuuust maybe, it has to do with code related to dissapearing corpses of player characters?

It's just a crackpot theory. It makes the most sense to me, especially after the matchID I specified out of all of them. That was the only match where I didn't crash at ~30 minutes and when that happened- the modeles of my dead allies appeared where their a-posing bodies should stand... and those a-posing bodies dissapeared with the effect during respawn time.
 
UPDATE: after the newest update up-to-this-date (16th December 2025 UTC+1), I experienced freezes whenever I had a crash previously, BUT I got a crash at ~23 minutes. Match ID: 49037492
 
Back
Top