Fatal Error: D3D device was removed due to DXGI_ERROR_DEVICE_HUNG in BPM

[DeeStee]

So here's the issue. I recently got a steam controller (woohoo!) it works great on my gaming desktop. When I travel, I use a surface Pro 3 (windows 10) to do some casual gaming and I wanted to use my steam controller with it. When I am in Big Picture Mode, when I go to a chat box and begin using the two track pads to type a message, I receive the fatal error and a windows notification saying the display driver has stopped responding and has recovered. Here is a screenshot:
http://imgur.com/o9lqrsS

So far I have tried

• uninstalling and reinstalling graphics driver (used Display Driver Uninstaller from guru3d)
• uninstalling and reinstalling steam
• checking and installing latest updates

Has anybody else seen this issue and/or may know how to address it? Any ideas welcome

I also made a reddit post on /r/steamcontroller
https://redd.it/3yd68n

[Deerain]

I wonder of the surface turns off you GPU to save power, when you type in the chat box is big picture still in the background or minimised

Edit. Just looked at your image, it could be something like that, I will have to check around online:-)

[Deerain]

Ok so it looks like your laptop can use either integrated GPU or embedded, assuming you have this one so that could be your problem.

https://www.thurrott.com/mobile/microsoft-surface/7615/surface-book-tip-manage-the-discrete-gpu

So you need to go into your graphics settings as in the link above and set steam to use the GPU all the time

Hopefully this will solve for problem

[DeeStee]

Thank you for your reply Deerain. I tried what you said, however, I do not have NVidia onboard graphics. My SP3 has intel graphics HD 4400. I noticed that unlike in the example provided, I do not have a control panel for the graphics on this device. This has something to do with the custom driver intel and microsoft made for the SP3, as I do not have the stock drivers listed on intels website.

When I use an intel driver update utility, it says that the driver I have is up to date and is manufacturer provided, and that I cannot install one using the utility.

I have found some threads that discuss installing drivers from intels website and removing the one that comes with the device:

http://answers.microsoft.com/en-us/surface/forum/surfpro-surfusingpro/surface-pro-intel-hd-control-panel-is-not/c45115d3-8eee-4673-939f-4f46a45decbf
http://www.surfaceforums.net/threads/intel-4400-driver-update.10839

so I am going to remove the driver and install one from intel's website so I can hopefully have a control panel to edit this option.

Edit: Well this is what I did, i rolled back to previous version of display driver, installed newest driver for intel hd graphics 4400 from intel website, and then tried steam in BPM and repeated what was causing the crashing before and everything seems to be better! I also changed Steam to always run as administrator but when tested before changing display drivers, it did not have an impact on the crashing. Thanks for your help Deerain, your comments helped me to try this and so far so good!

[Deerain]

Nice job, fingers crossed its fixed for good :-) glad to be able to help

[Roland]

I have this problem constantly and have for over a year now.. But I have an Nvidia GeForce GT 760, and have gone through many drivers in the time and the problem persists.

[RambleCan]

I have had this pop up too and I'm on a desktop with a GTX 970. I don't know what causes it but usually if I just restart steam and turn the controller off and back on it works fine.

[Da Doom Man]

Have any of you completley uninstalled your drivers?

If you have an Nvidia card and Geforce Experience, Geforce Experience gives you the option to do a clean install removing any old and residual files.

[Roland]

Originally posted by Da Doom Man:

Have any of you completley uninstalled your drivers?

If you have an Nvidia card and Geforce Experience, Geforce Experience gives you the option to do a clean install removing any old and residual files.

Tried that several times.

Originally posted by ExistentialEgg:

I have had this pop up too and I'm on a desktop with a GTX 970. I don't know what causes it but usually if I just restart steam and turn the controller off and back on it works fine.

You don't have to turn the controller off and back on, but yea this is what I end up doing, or rather have to do because BPM no longer starts after this happens. Eventually it happens again though and Steam needs to be restarted again.


This issue is extra annoying with games that rely heavily on Steam (like Warframe or Awesomenauts) as it causes them to crash along with Steam.

[RambleCan]

Originally posted by Da Doom Man:

Have any of you completley uninstalled your drivers?
.

Yep, did a clean install. I've only had this error pop up once or twice. It's definitely an odd one.

[Roland]

Originally posted by ExistentialEgg:

Originally posted by Da Doom Man:

Have any of you completley uninstalled your drivers?
.

Yep, did a clean install. I've only had this error pop up once or twice. It's definitely an odd one.

Damn you're lucky! I see it daily. It even crashes when I'm asleep and doing nothing.

[Roland]

Every once in a while I google this in hopes someone found a fix (though realistically, it's a Steam BPM issue, so I don't expect one since there's so many BPM issues being ignored)
Apparently it's been exactly one month since I last tried to find a solution...

[john]

I had the same problem and found a fix for me. I have a dual monitor setup, an LCD and a plasma TV where BigPicture runs. I got the error message every time I started playing. The fix was to disable the energy saving timeout for the LCD (was set to 20 minutes) or to disable the LCD completely before playing (WIN+P). Maybe that helps for you too. Starting from there, the error message makes sense for me. LCD turns off -> Device removed -> BPM problem.

[D00hickey]

I have this error every 20th time or so that I use the Steam on screen keyboard. This can be incredibly annoying due to the fact I have to walk up two stories and across the house to restart Steam on my desktop. It wouldn't be that bad if I could just use the onscreen keyboard with windows but the left click does not register in that application using the steam controller.

[Roland]

Originally posted by D00hickey:

I have this error every 20th time or so that I use the Steam on screen keyboard. This can be incredibly annoying due to the fact I have to walk up two stories and across the house to restart Steam on my desktop. It wouldn't be that bad if I could just use the onscreen keyboard with windows but the left click does not register in that application using the steam controller.

Reasons like this are exactly why I feel Valve needs to focus on fixing their client before pushing hardware that uses their client. I have a thread in several "Steam machine" discussions about the numerous bugs that need fixed and are slowly making BPM unusable. (some of the bugs have been there for over 3 years and despite several reports, Valve just keeps ignoring em)

[D00hickey]

Originally posted by Roland:

Originally posted by D00hickey:

I have this error every 20th time or so that I use the Steam on screen keyboard. This can be incredibly annoying due to the fact I have to walk up two stories and across the house to restart Steam on my desktop. It wouldn't be that bad if I could just use the onscreen keyboard with windows but the left click does not register in that application using the steam controller.

Reasons like this are exactly why I feel Valve needs to focus on fixing their client before pushing hardware that uses their client. I have a thread in several "Steam machine" discussions about the numerous bugs that need fixed and are slowly making BPM unusable. (some of the bugs have been there for over 3 years and despite several reports, Valve just keeps ignoring em)

Everyone at Valve is too busy swiming in their Scrooge McDuckian money vaults to properly suport their software. They employ some of the most talented software developers in the world and they seem to do very little.