Diablo 4 restarts my computer when I teleport into a dungeon, out of a dungeon or enter the game in general. It’s completely random what the trigger is, but when I want to teleport from A to B, the computer restarts. Not every time either. Sometimes after the fifth teleport, sometimes directly, sometimes not at all. But it occurs regularly.
I already had this problem about 5-6 weeks ago and shared it here. I then updated my BIOS, updated all drivers etc. and followed all the guides I could find and tried various things (there is a Blizzard guide)
Reinstalling the game helped in the short term. But even that hasn’t helped now.
From release to Ocotober i was able to play like freak no problem. Than it occured
Does anyone have the same problem?
Any other game (BG3, Sea of Stars or whatever) I can play for hours without any problems.
Just to make absolutely sure I’m not misunderstanding, it’s not just the game that crashes and you have to restart it, but your entire computer restarts when you teleport sometimes? A full reboot?
If it’s the game itself, I’ve personally had plenty of instability issues with the game where I’d noticed rubber-banding, gear, potions, etc. visually dropping and not showing up on the ground, then crashing whenever I’d try to go to another area via TP like you say. If you mean that, then I think that’s a game problem sadly, or possibly a connection issue that the game’s servers have with your internet. I’ve seen this talked about by different people and from what I can tell that’s not necessarily a problem on your end. Good to know you’re not doing anything wrong, but frustrating that there’s not really a fix for it either as far as I can tell.
If you do mean that your entire PC reboots when teleporting sometimes, that’s a much bigger issue and I wonder if any game on its own could ever do something that big to your computer. The only thing I can think of in that case is that D4 is a lot more resource intensive (CPU, GPU, RAM) than other games you have played. In that case, if your PC parts are older and/or haven’t been cleaned in a while, they can overheat. At a certain point of overheating, your computer can shut itself down to protect itself from damage.
I’m not very tech savvy myself though so someone else might have a much better answer. These are just things I’ve experienced myself before with D4 specifically for in-game crashes and my PC overheating leading to complete shutdowns in the past.
That’s a bizarre interaction in that case. If alt+tab fixes it for you, you might want to check if changing from fullscreen to borderless windowed fixes the problem completely for you. I know some other games that had trouble with alt+tab use during gameplay, although in those cases using it often could actually hurt performance or make those games crash. So who knows, maybe playing borderless windowed instead of fullscreen might fix the problem entirely in that case!
If not, you still have your personal alt+tab hotfix at least, even though I personally can’t comprehend how a single game can completely crash your entire PC in the first place…
I know of 2 people who had the same issue on highend hardware and it seemed to be power related for them. D4 randomly spiked so high in gpu and memory usage that some kernel-power-error prompted windows to reboot. both of them stopped playing the game immediately but one of them seemed to had fixed it by slighty increasing voltage limits in bios (he was able to play for hours after that, but quit the game the same evening for good as he was ‘done with it’ he said). I cant really tell what voltage limits he touched nor the exact description of the error, but he found it after looking through windows event logs. the funniest thing though is, that whenever my game stutters like crap and pc gets unresponsive, I also fix it by either alt-tabbing or hitting the windows key. I’ve done so since the first time I’ve had freezing issues as originally I wanted to see if the game froze or the entire OS froze.
just for reference: im on 5800x3D, 3080Ti, 32gigs 3600mhz, nvme, etc. the friend who managed to fix the issue is on 5950x, 4090, 64g of mem, …
