Ever since buying the expansion, and only since then, have I been getting this crash. Has never happened before but now it is happening constantly after an hr or so.
682C970E-5EEE-4157-A3C8-21680AE1CD00
Is the code it gave me and the top of the error is calling it “fenris”
I am having this happen as well, 5 times yesterday and so far 3 times today. I spent hard earned money to play this game and now I can’t do much as it just shuts off in the middle of dungeons and such.
I am having the same issue. My code is EF66F2C7-D139-46B5-9055-D4B7BA9D7F58 and I am tired of loose mats and buffs and keys my last crash I was in stage 3 of inferno horde, so I lost the key which are suppose to be rare and I got no loot from it. this is really making me want to go play something else, but I am having fun if it was not for the crashes. Blizzard Please fix.
I’ve gotten five different Fenris crashes today, I’m beyond tired of it. And when I opened a ticket, showing each line of code the window said I should show. They just marked the ticket as resolved and closed it. I’m so upset.
Same here. I got same error 4-5 times in 3 hours today. Last one was:
4B90EA42-56EA-4958-8320-E82C3A85E210
Memory: 32 GB RAM.
Graphics: AMD Radeon RX 5600 XT
The thing is every Fenris crash I get it’s a different string of code, of which I have no clue what they mean. The problem isn’t resolved. I’m still getting them and worse? I keep wasting mats to try and play this season.
And I hate how hard it is to get any real help or acknowledgment this is a problem. It’s really upsetting because I remember when their support was good.
That was my setup a few days ago before the expansion. I was trying to run the game twice on the same machine from two platforms. One from Battlenet and one from Steam.
I did end up getting them to run, but that was when I bumped the swap file from 16GB to 32GB. Even then, it was having issues, being sluggish, etc. But I was only doing it to confirm crossplay features for a question.
But that is the error it threw when I first tried and ran it out of virtual memory. But there are lines of code like this that can tell me or others what may be going on. The file also tells us what settings are used, what hardware is present, etc. So its good info to help troubleshoot.
The codes? Nadda. Can’t do anything but count the letters and go “Neat”.