I have the exact same problem as you.
all the issues came up when i upgraded my Radeon Driver to version 16.12.1 - I have tested the new driver twice and both times this problem occured. Some seconds after the "getdeviceremovedreason"-notification a window telling you that "Radeon Settings: Host application" doesn't work any more, opens up.
The funny thing is that if you deinstall the driver and delete all possible AMD folders it works fine.
GPU: MSI R9 380 Gaming 4G
CPU: Intel Core i5 6600k
RAM: 16 GB DDR4
Operating System: Windows 10 64-bit
Its not possible to play BF1 without drivers.
I have forgotten to say, if the game crashes i get a pop-up message from Wattman:
The settings have been set on default.
Well maybe I expressed wrongly Of course one needs a driver, that's right.
What I meant to say is, that if you deinstall that AMD app (that app where you have the wattman and other settings) it might work again.
I have deinstalled this app (Settings -> System -> Apps and Features -> find that AMD app -> deinstall it). At least for me it worked (I can play Battlefield 1 again without any problems). Of course on the long run this might not be the best solution. But if you don't want to wait for AMD to publish a fix of the latest driver in order to play Battlefield 1, this could be a temporary option.
Naturally on the long run AMD has to fix that issues with a driver/software patch.
i finally figured out what you meant.
I have a clean install with only the drivers, and battlefield 1.
i get still dx crashes.
could it something hardware related?
i never had problems with any game before i bought the rx 480.
i have now problems in the following games:
BF1: dx crash
Deus ex: dx crash
rocket league: black screen flickering while playing (no crashing)
CSGO: driver crash.
the only "heavy" game i dont have any problems with is Civilization 6...
I don't think that this is hardware related because if it was you would have had this problem even before the latest driver update. Probably you hadn't this problem before the latest driver update because by accident you posted this problem on the day when AMD released their new drivers. For me this problem first occured when I updated to driver version 16.12.1 - I never had problems with the older crimson drivers. Meanwhile there has been a patch (16.12.2) but the problem is still not fixed. In my opinion AMD has done a bad job with this new drivers .
I have done that of course