That, tells me the GPU entered fail-safe due to it hitting a hardware limitation and shut down to protect itself.
While playing Diablo IV might be triggering the event, the game itself is not the cause. This is underlying an issue with the hardware itself. It just so happens to be an issue that is only presenting under certain conditions, which apparently Diablo IV is somehow triggering.
What brand of laptop is this for one thing?
Another thing to keep in mind. While there have been several reports of this issue, most of us have not been experiencing these types of problems.
And as a further note, I WILL agree that the game graphics has some poor optimization; in that performance seems to be all over the place and uneven, place to place in the game, regardless of quality settings.
I have had the best luck with capping the game to 60FPS on standard HD 1080 res (which is what my Acer Predator 24" happens to be) and it plays smooth, doesn’t seem to jump around when transitioning or anything else with pretty high settings, but not maxed. Now if I try to run it at my monitor’s native 144, it can swing more and not be as smooth at times, along with working the GPU harder.
I have ran this on 4 different computers now, and all with similar results:
HP Omen laptop with a 10th gen i7, 16GB and a 2070.
Custom built MSI ITX with a 7th gen i5, 32GB and with 3 different MSI cards: 1660, 2060, and 3060 12GB.
Custom built MSI ATX with a 12th gen i9, 32GB, and currently a 2070 from Asus
MSI Laptop Thin 11th gen i5, 32GB, and a 3050Ti.
All these systems ran the game well, from closed beta, to open beta to slam. Any issues I had were mostly in the closed beta, and that was where the graphics were at their wonkiest. Plus it was that version that the ITX system went through 3 cards before it ended. I simply was changing them out to see how it affected performance, and overall there wasn’t a huge amount of difference between each, though obviously the 3060 is going to stomp on the 1660. All were MSI cards too.
None of these systems are running overclocked, either CPU or GPU.
Two are on Windows 10, the other two on Windows 11. The i9 only ran the slam, as I just built it a couple weeks ago.
Point is, if the game was actually causing these issues for the few of you having the problem, there would be a LOT more than just a few of you.
This still falls in the line of the issue being caused by a hardware problem, even if the machine is new, clean, doesn’t matter. New stuff can also be bad, right out of the box. And sometimes doesn’t show up till something pushes it hard enough or it reaches the right conditions for it to trigger.
Game on.