DXGI_ERROR_DEVICE_REMOVED Crash when Unselected

@RGF_TK-Tater Thanks for the detailed post. Can I double check, if you don't tab out does it work ok?

Are you playing in fullscreen Windowed mode normally? Can you try setting the resolution scale to 1:1 and see if that makes any sort of difference?

@EA_David I am currently running in Windowed Borderless and I just checked, it still crashed when at 100% resolution scale. It has never crashed unless I open another tab. 

The most common instances are when I open a web browser or open Windows 10 Cortana to search something up. I am not saying this is the only time it happens, but it this is what I happen to be doing when I open another window. 

Thanks for responding!

I see, thanks. If you set your Virtual Desktop settings to match those listed in this screenshot, does that have any effect?

http://answers.ea.com//t5/image/serverpage/image-id/20766i12F40DB2EB5F1FFC/image-size/original?v=v2&px=-1

Screenshot credit to @Carbonic

@EA_David

Thanks for the response! I have been using those settings all along. This error appears to only occur in Windowed Borderless, but it is still a problem because I love windowed Borderless. I don't know if affects anything, but I have a second 900p monitor (and my Default 1080p one).

I know I've seen issues with differing monitor resolutions in the past, but I don't recall anything specifically linked to SWBF.

If you play on the 900p monitor in native res and with standard scaling are you still getting the crash?

Also -and sorry for not saying this earlier- can you restart with a Clean Boot before playing too?

I get that you'll want to tab out to access other programs, but removing some programs that start up by default may prove useful. 

https://help.ea.com/en/help/faq/how-to-clean-boot-your-pc/

@EA_David

My 900p monitor is just a second monitor. It is not my default display and I do not run my games on it. My default monitor is 1080p. 

I performed a clean boot (disable startup items in task manager and disabling all services in System Config except for Microsoft)

No change. 

I also want to add that I don't know when I originally downloaded this copy of the game, but its been a while. I have performed several Clean Installs of Windows (wiping drives) in the past. I would just copy and paste my "origin games" folders onto different drives. I don't think this would have an affect because I do regularly repair the game (which come back with 0 errors). I'd Also like to add that this is a fairly new error.

Also recently my Mobo broke and I got a new one. This is when I starting getting these errors. I even performed a re-intsall of Windows 10 to try to fix this new error. It let me re-update to Windows 10 without loosing any data. Its kind of like performing the update to Windows 10 if you had Windows 8, but I already had Windows 10. Its a really useful feature, and usually fixes many errors.

I'd also like to mention that my Card is not a Stock GTX 970. Its a MSI GTX 970 100me (Twin Frozr) so the speeds are a little higher by default. I am not overclocking, but the speeds are a bit higher out of the box than a stock 970. 

Moving the game across is fine, that shouldn't be a factor, especially with the repairs added in. 

My (wild) guess at this stage is some odd registry error. Perhaps running ccleaner will have an effect?
 

https://help.ea.com/en-us/help/pc/how-to-use-ccleaner-to-fix-pc-issues/

@EA_David

I did everything on that CCleaner link told me to do. (I couldn't do all of them because I didn't have the software, like MSWord)

Interestingly enough, it still crashed, but without an error message. Could this be a coincidence? Thanks. 

Could this in any possible way mean my card is dying? 

And you didn't give your input if you think my out-of-the-box OC may be causing errors.

@EA_David

Any more suggestions?

Sorry, the BF1 launch has been taking my attention, I haven't been able to spend as much time as usual looking at other products. Generally out-of-the-box OCs are fine and its manual ones that need to be looked at, but you can always try declocking.

A damaged card can always lead to some odd behaviour too, do you have access to another card that you can use to test with? It wouldn't even need to be a powerful one, as long as the game was running you try try the tab testing and see if the issue still occurs on the alternate card.