Directx function "FindClosestMatchingMode" failed
I've been getting this error whenever I try running the game ever since the latest windows update. I don't know if the update is the culprit, all I know is know I can't go murderhoboing around Thedas anymore because every time I boot the game, it freezes almost immediately (sometimes my cursor changes to the ingame one and a loading icon appears), that frelling message pops up, and then the game crashes to desktop when I click the OK.
I tried everything I could think of; running repair, installing several older GPU drivers, swearing, uninstalling/reinstalling the game, reinstalling directx, crying, searching online (my google-fu was too weak), trying to force the game to run in windowed mode (which was a solution to a similar problem in other frostbite games), but nothing has worked, so I'm hoping someone here can help me get back to being a magic murder hobo, as The Maker intended.
I wrote all this, but then decided to doublecheck over at the geforce forums, just to make sure I wasn't a liar. Turns out I was. So instead of deleting everything, saying "Problems Solved!", and wasting the minutes I spent crafting this reply, I'm leaving everything. Solution at the bottom.
mcsupersport wrote:You should try a clean boot of the system, to help weed out if it is a program interference or other issue...Tried that, nothing changedmcsupersport wrote:I also note that you have a Intel video chip listed in your Dxdiag....double, triple check that it isn't in some way being used instead of the Nvidia card. Make sure all the cables are plugged into the Nvidia card instead of main board, or make sure the Intel is disabled as much as possible through settings and such. DAI will not run or not run well at all if it somehow uses the Intel *.Checked, and that's not the problem eithermcsupersport wrote:Double check that Origin and DAI are set to run as administrator, checking at their .exe in their install locations.They both are.I'm 99.9% sure that it's the update + my nividia driver + this being a Frostbite engine game, because I found a thread with two other people that had the exact same problem as me, only with Star Wars: Battlefront and Battlefield 3 & 4, over at the geforce forum.Unfortunately, I haven't been able to find answer over there. Except I frelling did!The solution was to switch my monitor cable from dvi-d to hdmi. I never would've thought of that in a million years!
