Display driver problems (Witcher 3)

[Benergy]

I'm using an MSI 270x HAWK in Windows 10 Pro 64 bit and am having driver problems.

If relevant, it's running a 4690k (not overclocked) in an AsRock Z97M-ITX board with 2x4GB 1866MHz Kingston RAM.  

 

Until now I had been using an older ~15.6 version of GPU drivers, which worked but had some strange quirks with really bad light flickering and texture flickering in modern games. In Fallout 4 I fixed this by turning the lighting detail level down, but in Witcher 3 nothing had any effect. Thus, I uninstalled this driver using DDU and updated to Crimson 15.12 drivers.

 

This is where the real fun began, every time I open the Crimson settings panel, it freezes after about ~2 seconds and goes transparent, with a Windows 'display driver stopped working (amdkmpap)' message coming up, thus barring me from using overdrive etc. Various games are working fine (Fallout 4, Witcher 2) but as soon as I get into the game proper in Witcher 3 after loading a save, it immediately freezes with the same windows message as above (sometimes while still loading).

 

Since then, I've used DDU to cleanly uninstall in safe mode, and then install many different versions of driver, Crimson and non-Crimson, but each one is having the same problem (14.12 actually caused blue screens too), the old catalyst control center would open OK but I'd still have problems in Witcher 3. I've tried stress testing with Furmark, GPU is running cool and normal at stock clocks. I've updated all firmware and BIOS, but the problems persists. Windows has been updated to latest version (1511), I've done an sfc /scannow, verified Witcher game data in Steam, and also redownloaded Witcher 3.

 

My other PC running a 280x with 15.12 Crimson drivers has had zero problems at all with Witcher 3, unfortunately I don't have access to it now and I'd love to get back into Witcher 3   

 

Any ideas would be greatly appreciated   

 

Edit: GTA 5 has now stopped working entirely like Witcher 3, but Fallout 4 works flawlessly, could that possibly narrow the problem down?