I'm having the same problem! DA:I worked fine for me through the shift to Windows 10, but I didn't play for a while, and then had to replace the video card. I can only assume that in some way contributed to it not working now.
I, too, am getting "GetDeviceRemovedReason" errors. They're happening between when I select the initial character options for a new game and when the game itself loads, so I'm not able to save, name the character, or design it.
I've tried the latest drivers and DirectX.
I've tried rolling back the video driver.
I've tried installing the DirectX End-User Runtimes (June 2010) as recommended on several sites.
I've tried putting the game and the Origins client in Compatibility mode for Win 7.
I haven't tried editing the registry yet, because I'm very wary of doing that in Win 10, though I've seen advice that gives instructions for changing Windows 8 settings that might help...
Here's my DxDiag, for what it's worth. I'm currently on the rolled back drivers, but this was recorded before I tried compatibility mode.
https://hastebin.com/ubexozajiw.tex
I'm rapidly becoming convinced that there isn't actually a current solution. I gather it's a problem with the combination of Windows 10, DirectX 12, and games of a certain age, which happens to include DA:I. ☹️
I don't suppose anyone has news?
-E-
You may want to look into running a video stress test, as the problem may be hardware related instead of software. You have tried the latest drivers, old drivers, I assume you have done a clean uninstall and reinstall to get there...but the one thing that has remained constant is the hardware in all this. It is unusual to hear of a video card being replaced in a laptop computer, usually when one of them dies, the whole thing is scrap...because usually the video card is either built onto the main board or is integrated into the main chip, thus there isn't a way to really replace it without rebuilding the whole thing, which means scrapping it and getting a new one.
So what I am wondering is IF the video element was replaced, did it get installed correctly, is the cooling system installed correctly, and was the issue partly power related to begin with and or is a power supply issue cropping up now. DAI was a fairly taxing game when it came out, and can even now stress mid range computers to the point of showing up weak components. You may want to see about running a furmark or other video stress test and see how your system preforms, keeping a close eye on heat and such as you do, using either afterburner, speedfan or some other monitoring program.
Also if you haven't already done so, I would move the saves folder out of its default location, which will make the game recreate it, and if you do this while Origin is NOT backing up to cloud, it will return all settings to default and help eliminate a corrupted save or setting for the game.
Oh, and I noticed an Wacom tablet also in your DxDiag, I would uninstall that and all software from that as well, as it is a know issue with frostbite games.
I'm not sure what gave you the impression that I'm using a laptop? This is my desktop computer.
Huh, the tablet is an issue? I had been using it before. I'll try uninstalling and reinstalling it. I need it, so I can't just not have it on the machine, but I can use a regular mouse to play the game at least, if that would help...
I can try running a video stress test, but I'm not sure why that would make much difference. The new video card is one step *better* than the previous one that worked just fine.
Since I was trying to run a new game anyway, removing the local version of my old saves is definitely something I can try. Again, not sure why that might help, but it can't hurt!
I was bummed to discover that one of the common fixes - running a system check to restore any broken Windows .dll files - found no problems and thus fixed nothing. :/
It really seems like a compatibility problem somewhere between DirectX 12, Windows 10, and DA:I, since most of the folks having this problem *didn't* just install a new video card, and no one brand of card seems responsible.
The most credible answer I've seen so far has to do with some kind of refresh rate in post-Vista Windows that didn't apply before and is potentially editable, but I haven't seen instructions geared towards Win 10 for it yet.
I will try replacing the old saves and un/re installing the Tablet next, thank you.
-E-
I forgot to mention that the *first* thing I did was use the Origin option to repair the game itself.
Removed the Wacom tablet entirely for the moment. That didn't help.
Tried to run a benchmark in the game and got the same error as I've been getting when I try to start a new game.
So now I'm downloading the FurMark stress test installer. We'll see what that tells us, I suppose.
*sigh*
[Edit] No problems with the FurMark stress test or benchmark test.
Maybe I should look into that reg edit option... mrrr...
-E-
Okay, I tried both regedit options. No dice. *sigh*
I did a full clean reinstall of the game, just in case the prior repair of the game was insufficient.
I'm really bummed about this. I have no idea what the real problem is, but none of the solutions that have worked for other people seem to be working for me. Perhaps it requires a precise combination I haven't accidentally hit upon in the process of trying each thing individually. Argh.
It seems clear that no one piece is malfunctioning. The operating system seems to be fine. The drivers are fine. The game is properly installed. The card runs fine and can handle the FurMark testing. Every piece is fine, yet somehow they aren't fine together. ☹️
-E-
I got the impression that you are on a laptop because in the DxDiag the video card is listed as a
AMD Radeon HD 7670M and when it lists a M after the numbers generally means mobile version which most times is a reduced or hybrid version of the video card. Most times that I have ever heard, you never get a mobility card listed in a desktop.....
Which MAY be part of the issue, as if it is a full HD 7670 and for some reason the driver thinks it is the mobile version then issues can occur....
Aha! That's good to know, thank you. I haven't a clue what to do about that, and it doesn't seem to be affecting anything else, but I'll see if it's fixable!
