Post History for Ibaraius

Hey, Zackoulis24!It looks like you may have 32-bit Windows 10 and outdated drivers. To be sure, let's collect a DXDIAG.Please collect a new DXDIAG and post it here using the Code Blocks button in the posting options. Just make sure the full DXDIAG contents are between the code tags.

Glad to hear it helped!

Hey, LOLitsKen!I noticed you haven't tried to play since your last post, but I checked the crashes for you and it is being caused by DiscordHook64.dll. This would be the Discord Overlay feature. Just make sure to disable this option in Discord and it should prevent the crashes.

HANSIt appears your crashes are caused by Discord Overlay and Raptr/Plays.tv Overlay. Make sure both of these Overlays are disabled while playing.If you are still having issue,s please make your own Topic and we will look into this further.

MARKXLIIThere is no need to submit tickets for the time being. Providing the information here helps.We are looking into this on our end. Normally just waiting 5-10 minutes before logging back in will resolve this error. But If it is taking longer there is something else that needs to be addressed.

Hey, all.We just need some clarification for the people who are having this problem. Have you waited over 10 minutes before trying to log back in? Have you made sure to completely log out of the Battle.net app and log back in?I know one poster stated that they waited over an hour and they still had the same error. We just need some information about everyone else experiencing the problem.Thanks!

Hey, everyone!This does appear to be an account specific issue. We are currently looking into the cause. If we have any information or resolutions for this, we will update this thread.Thank you for the reports!

Hey, Bolide!What is the full installation directory you are using for Diablo 3? If you install this to your Windows 10 installation drive, does the same issue happen?

Hey, ClutchDust!Please make your own thread with a DXDIAG and we can look into this for you.I am locking this thread as it is an older one.

To tag onto what Jambrix recommended:Fault bucket 116169015819, type 5Event Name: BEXResponse: Not availableCab Id: 0Problem signature:P1: AliSafeEngine.exeP2: 1.0.0.2P3: 5731a473P4: ReportEnv.dllP5: 0.0.0.0P6: 5731a4aaP7: 0002e774P8: c0000409P9: 00000005P10: I see this is constantly throwing BEX errors, which may be causing Windows to take screen priority, and possible the cause of the issue. I would recommend temporarily uninstalling this program to see if it helps.