| Clbull #2385 | Constant driver crashes in Bnet, D3 and Overwatch(1) | Category: Technical SupportMay-13-2016 1:09 PM PDT (9 years ago)  |
EDIT: CS support ticket submitted. Dxdiag and MSInfo files submitted as part of said ticket. Let's see what I get as a result.
Recently, I've had the following error - "Display driver stopped responding and has recovered" - appearing very consistently when using the following applications:
Battle.net - There have been times where the Battle.net client won't even boot up without triggering this error message. I have also been able to narrow down less frequent crashes in other games like WoW and World of Tanks to having the Battle.net client running in the background and neither of these games have crashed at all since limiting how Battle.net runs while a Blizzard game is launched.Diablo III: Reaper of Souls - Sometimes the game will play fine, and at other times I'll be able to play for 15 minutes before a crash occurs and forces me to reboot the game.Overwatch - On several attempts to install this to my C:\ drive, I had this error appear pretty consistently during the download and crash the client. I was however able to install the game to the D:\ drive and still experienced the error crashing the game loads while playing during the Early Access and Open beta.I haven't really tested out Heroes of the Storm much although I was able to play a game fine when Tracer came out, and as I said before, this error doesn't seem to happen with WoW, a game which I've been able to clock a lot of hours into recently.
Having looked on the Battle.net bug report forums, this seems to be an issue happening almost exclusively with people using AMD R9 270X graphics cards and Windows 10, as shown by the thread below:
http://us.battle.net/en/forum/topic/20742939744
I have done the following in an attempt to remedy the issue:
Using Windows Memory Diagnostic Tool to check for RAM errors. This is primarily because I don't have any bootable media with me at the moment to run memtest86 on. No errors detected. Considering the fact I'm using HyperX Fury RAM which I got last year, I'd actually find it pretty troubling if that was not workingUpdating to the latest AMD drivers. Twice. I have even made sure to purge any old driver versions from my computer to prevent conflicts.Scanning and repairing files in both Diablo III and Overwatch. There is sadly not that option for the Battle.net desktop client proper.Set the Battle.net client to exit completely when I launch a game, as this is a reported fix in the above linked thread. However, this hasn't worked for me, except in certain instances, i.e. WoW.Running a Chkdsk scan of both my C:\ (Solid state) and D:\ (hard disk) drives. No errors detected on either.Cleaning out my PC of dust. I really don't think graphics card overheating is the problem at all. My GPU might run at about 65 - 70 celsius on heavy load, but the R9 270 X GPU is meant to handle temperatures upwards of 90 degrees. For me to clean it out further, I'd have to disassemble my graphics card, spray the whole thing down with compressed air and put it back together, which is a much much harder job than it looks.I am more than willing to provide MSInfo and DxDiag logs if requested.
|
