BSOD only while playing Civ V

My custom built computer gets BSODs, seemingly only while playing Civ V. I've been trying to figure it out for months, but I've made no progress. Hoping to find some help here! Let me know if there's anything I can add to the thread to be more useful. I've got all my specs filled in I believe, and I'm using WhoCrashed to parse the crash dumps. While this isn't the only one, this does seem to be the most common:

Code:

On Sun 9/14/2014 12:33:28 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091314-17487-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x6F63) 
Bugcheck code: 0x100000EA (0xFFFFFA80088B8B50, 0x0, 0x0, 0x0)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This indicates that a thread in a device driver is endlessly spinning.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

edit: attached debug

Code:

fffff880`02bab878  fffff8a0`00000001
fffff880`02bab880  fffffa80`08712d28
fffff880`02bab888  fffff880`04c45c6cUnable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
 atikmpag+0xbc6c
fffff880`02bab890  fffffa80`078e73c0
fffff880`02bab898  00000000`00000000
fffff880`02bab8a0  00000000`00000000
fffff880`02bab8a8  fffff880`04644038 dxgkrnl!DXGADAPTER::AcquireDdiSync+0x30
fffff880`02bab8b0  fffffa80`0d2b3010
fffff880`02bab8b8  fffff880`043ad619Unable to load image \SystemRoot\system32\DRIVERS\VirtuWDDM.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for VirtuWDDM.sys
*** ERROR: Module load completed but symbols could not be loaded for VirtuWDDM.sys
 VirtuWDDM+0x8619
fffff880`02bab8c0  fffffa80`088ea000
fffff880`02bab8c8  fffffa80`08712d28

Uninstall the current ATI driver, reboot, then run Windows Update and install the ATI driver offerred under the Optional updates.

The VirtuWDDM driver appears to be corrupted. I can't find any downlaod locations for it - I recommend uninstalling this product completely for now.

Sorry, I should have been clearer : uninstall all ATI graphics drivers. When Windows reboots, it will use a generic driver, Windows Update will then offer a tested driver. Install and use that.

Lets see if the system stays stable.

Will do. The crash is notoriously difficult to recreate. In 50 hours of play I will sometimes not have the crash, and other times have it 4 times in an hour. I will let you know.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa8004aec6b0, ffff, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35084 )

Followup: MachineOwner
---------

Mmm....nothing definitive. Lets go hard-core.

Please do the following:

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
Driver Verifier - Enable and Disable

Driver Verifier will cause your computer to run very sluggishly - this is normal. What it is trying to do is force your system to BSOD and isolate the offending driver/s. When it does, reboot, disable driver verifier, reboot as normal and upload the new dmp file/s here.

I recommend creating a system restore point before turning on driver verifier:
System Restore Point - Create

If your system fails to boot to desktop once driver verifier is enabled, turn it off by booting into Safe Mode:
Safe Mode