#A fatal error occurred

1 messages · Page 1 of 1 (latest)

toxic obsidian
#

A warning message appeared on the screen and then the game closed.

Intel Core i5-7300HQ
NVIDIA GeForce GTX 1050 Ti
8 GB RAM
Windows 11 (64bit)

Details: The game crashed while I was in combat. I was using Barbarian Blade with Burning Rage as the 2nd effect. Goblet has Nasty Aftermath and heart has Blood Rapture.

This crash occurred in the shroom dungeon close to the entrance to the boss chamber and shortcut. Screenshot of the location included.

Actions just before the crash and speculations about things that might have occurred just before or at the moment of crash:

I was in the middle of a crowd, used vortex to throw Barbarian Blade and immediately followed it with a kick. Rage and Burning Rage weren't in effect, but at the moment of crash one or both of them could have reached 100% due to vortex raking up many hits.

Drivers might not be entirely up to date, but it hasn't been long since I last updated. The game has running fairly smoothly for the most part and this is the first time the game has crashed for me. There were a few browser tabs in the background and discord open, but those haven't caused any problems to me in last 25 hours of gameplay.

#

A detail I forgot to mention, the exact moment of crash is a brief moment after using kick. Not right away but either when the hit connected with something or right after. Happened too fast to know for sure

peak quail
#

Hey, thank you for the incredible amount of detail and the files you’ve shared!

That said, your drivers appear to be somewhat outdated (about 6 months old), and updating to the latest version can make a huge difference when it comes to game crashes.

Could you please try updating to the latest driver version (566.36) from NVIDIA’s official site and let us know if the crashes persist?

Rest assured, we’ll continue looking deeper into your report in the meantime!

toxic obsidian
#

I'll do that. But I doubt it's going to repeat any time soon even without updating. Been playing about 30 hours, not counting any time spent idle in the lobby and this is the first time any crash occurred at all.

#

Additional detail: Hags were nearby at the time and almost certainly close enough to summon mobs, if it's related to that known error.

peak quail
#

Noted, and thank you for all the details provided! Lightning

toxic obsidian
#

Happened while Vortex was spinning, again. But I have a sneaking suspicion that it's related to dragonhead + ablaze since that is bound to trigger those meteors a lot. Or maybe it only makes it worse since for the very first crash those 2 weren't involved... unless Burning Rage started the moment of crash