Ubisoft Titles Causing BSOD 1D error

PraiseTheSun

Distinguished
Feb 7, 2014
37
0
18,560
Hey all,
I've searched through a lot of threads and have yet to figure this one out.

Storytime:
Yesterday evening I downloaded Far Cry 5, it ran at 1 FPS. I googled it and found people recommended I updated my AMD GPU drivers to version 18.4.1 (latest). I did this and since then launching Far Cry 5, Far Cry 4 or Assassins Creed Black Flag causes my machine to Bluescreen with Stop code 1D as well as the word "atikmdag" after searching I found this could be related to the drivers.

Things I have tried:
Downgrading to driver version 18.2.x
Disabled all non-essential startup programmes & Services
Reinstalled Driver 18.4.1 (Clean install)
No outstanding Windows Updates
Tried SFC/Scannow
Forcing the game to start in Window mode
^All the above changed nothing.

Specs:
CPU: AMD FX-8320 (running around 35c idle)
RAM: 16gb DDR3
Mobo: MSI 970
GPU: ATi AMD Radeon R9 200 series (It lists it 2ce as two cards running 4GB, but it's just one card running at 8GB)
Dual Monitor set up
Approx 2TB of HDD storage with an extra 500GB SSD storage

Other info: Far Cry 3 runs perfectly! The only differences I can imagine are either an older engine or that it is running through Steam & Uplay, the rest are all Uplay only as I purchased them through Uplay and not steam,

I do not know what version of driver I was on before upgrading, but downgrading to 18.2 made no difference.

If I can give any more information please let me know, it is very frustrating. I am going away for a couple of weeks on Thursday but can still apply suggestions via TeamViewer from my Macbook.

Thanks for your time

UPDATES
Ok, so I found the BSOD also states, Driver Irql less or not equal which again leads me to believe its something to do with the driver.

I flashed my BIOS to the most up to date version (no change)
I installed AMD Catalyst Control Center (No change)

Update 2:
After uninstalling all GPU related drivers and then reinstalling them, I got the error code 1603 when installing, followed by the software telling me most of it was installed. They recommenced I follow this guide

https://support.amd.com/en-us/kb-articles/Pages/KB1603.aspx?DID=67B9%7C67B9%7C%7C&VID=1002%7C1002%7C%7C&CPU=AMD%20FX(tm)-8320%20Eight-Core%20Processor%20%20%20%20%20%20%20%20%20%20%20&OS=Windows7&OSBIT=64&OSLANG=en_US&utm_campaign=rserror&utm_medium=application&utm_source=driver-installer&utm_content=error1603%7CIM_GENERAL_ERROR_INSTALL/

When running the DISM.EXE command I get an error that reads "Error: 87"

Now attempting the SURT tool.

SURT & Safe mode also make no difference

My OS is win 7 SP1 x64

Update 3: I have no restore points.
 
Solution
Unfortunately it looks like possible system file corruption. This I feel because you couldn't run DISM.EXE. A satisfactory sfc /scannow scan, especially in W7 and prior OSes, is not a guarantee of good files.

OK, so no restore points ( I really don't trust Sys Restore anyway). Do you at least have the OS itself on it's own partition? If so I would just format the OS. If not, and you end up formatting anyway, at least do yourself a favor this time and make a partition for just the OS. It makes formatting much faster and easier.

And btw, in case you're not aware, one of the things that can cause system file corruption is exceeding the HDD free space recommendation and leaving your OS drive severely fragmented, especially if you delete...
Unfortunately it looks like possible system file corruption. This I feel because you couldn't run DISM.EXE. A satisfactory sfc /scannow scan, especially in W7 and prior OSes, is not a guarantee of good files.

OK, so no restore points ( I really don't trust Sys Restore anyway). Do you at least have the OS itself on it's own partition? If so I would just format the OS. If not, and you end up formatting anyway, at least do yourself a favor this time and make a partition for just the OS. It makes formatting much faster and easier.

And btw, in case you're not aware, one of the things that can cause system file corruption is exceeding the HDD free space recommendation and leaving your OS drive severely fragmented, especially if you delete the small partition MS makes to store system files like MBR on when installing your OS.
 
Solution