.jpg)
A fresh Diablo IV Technical Support thread has players reporting crashes, freezes, and out-of-memory errors on machines that should be chewing through Sanctuary without breaking a sweat. We are not talking about ancient potato rigs running on dust and hope. Several posts mention high-end CPUs, modern GPUs, and 32GB or more of RAM.
Menus are becoming the boss fight
The original report says Diablo 4 starts eating memory, freezing when basic panels are opened, and eventually crashes with an insufficient memory error. The player specifically mentions the map, stash, character panel, and other interface screens causing massive freezes, sometimes lasting long enough to make the whole game feel like it has been dragged into a swamp.
That is the annoying part. Combat problems are one thing. A boss fight going sideways is at least thematically correct. But when opening the map feels like summoning a system-level demon, the vibe changes quickly.
High-end hardware is not escaping it
Multiple replies claim similar behavior on strong systems, including PCs with modern Ryzen processors, RTX 4070 Super-class hardware, RX 7900 XT cards, RTX 5070 Ti setups, and even one machine listed with 96GB of RAM. Players describe crashes after a few minutes, freezes when entering dungeons, and stutters tied to opening maps or character screens.
One player says scanning and repairing the game did not fix it. Another says lowering texture quality helped a little but did not solve the problem. Others point out that both AMD and Nvidia cards are being mentioned, which makes the usual “it’s just one driver setting” explanation feel a bit too neat.
This echoes an older Diablo 4 problem
The timing is what makes this worth watching. Diabloz recently covered a Diablo 4 UI freeze bug forcing full restarts, but this newer thread has a sharper Lord of Hatred launch-week edge. Players are not just reporting menu weirdness. They are connecting it to memory errors, crashes, and instability right as the expansion lands.
That does not mean the issue is universal. Plenty of players are getting in, leveling, testing builds, and committing the usual crimes against monster populations. But for the affected crowd, this is exactly the kind of technical mess that turns launch excitement into hardware troubleshooting theatre.
Launch day should not feel like a RAM sacrifice
Blizzard has already confirmed some Lord of Hatred known issues, including quest blockers and a missing Talisman Tab problem. This crash thread is separate, and at the time of writing it looks like player-reported technical support chatter rather than an official confirmed known issue.
Still, it is the sort of chatter worth taking seriously. When players with serious hardware say Diablo 4 is freezing after opening basic menus, crashing after a few minutes, or throwing memory errors on systems that should have room to spare, that is not just launch-day whining. That is Hell trying to install itself directly into your RAM.
