New
#21
I'm seeing what looks to be single bit drops in CPU registers, which is conducive of CPU failure.
If you are overclocking, stop. Reset to factory defaults, and then try again. If it's still unstable, check temps using something like HwInfo. Your best option is to log sensor readings by checking "Sensors only" at startup and starting a log, then running a game till it crashes. Two logs will be sufficient, and three would be optimal. These will provide us both voltage and temp readouts.
I do find it odd that we have it always occurring with the graphics driver involved. The driver itself isn't that old (July 27) but I still recommend you update it to whatever's available.
Do you have any spare graphics card or perhaps onboard graphics? Try switching to something else and pulling out your current graphics card to see if we're dealing with a bad graphics card. If things stabilize, then naturally the card itself is bad. There's also the potential that your PSU just isn't up to snuff and is suffering under the load of the graphics card you have currently installed. Either the PSU itself has too poor of wattage output (remember, output degrades with age!) or it has flaws in it that only seem to manifest when under higher load.
Analysts:
Code:CONTEXT: fffff880031bc820 -- (.cxr 0xfffff880031bc820) rax=0000000000000030 rbx=0000000000000ff4 rcx=fffff8800d757210 rdx=fdfff80002dff400 rsi=0000000000000000 rdi=0000000000000001 rip=fffff80002c601f8 rsp=fffff880031bd200 rbp=0000000000000005 r8=fffff80002e28400 r9=0000000000000000 r10=0000000000000000 r11=0000fffffffff000 r12=fffff880031bd2d0 r13=000000000001fe90 r14=fffff880031bd840 r15=0000000000000000 iopl=0 nv up ei ng nz na po cy cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010287 nt!ExpGetLookasideInformation+0x8c: fffff800`02c601f8 0fb742c0 movzx eax,word ptr [rdx-40h] ds:002b:fdfff800`02dff3c0=???? Resetting default scope ... 3: kd> !niemiro.rawstack dps fffff880031bc000 fffff880031bdda8 fffff880`031bc000 00000000`0000007e fffff880`031bc008 ffffffff`c0000005 fffff880`031bc010 fffff800`02c601f8 nt!ExpGetLookasideInformation+0x8c fffff880`031bc018 fffff880`031bcfc8 fffff880`031bc020 fffff880`031bc820 fffff880`031bc028 00806ffd`008070fe fffff880`031bc030 00806ffe`00806ffd fffff880`031bc038 fffff800`02fb00dd nt! ?? ::NNGAKEGL::`string'+0x227d fffff880`031bc040 007f7fff`007f7fff ... fffff880`031bcca8 fffffa80`036e9b11 fffff880`031bccb0 00000000`00060000 fffff880`031bccb8 fffff800`02cb2ab5 nt!RtlGetExtendedContextLength+0x19 fffff880`031bccc0 d4900000`1d140963 fffff880`031bccc8 fffff880`072dffa4Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for atikmdag.sys *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys atikmdag+0xb6fa4 fffff880`031bccd0 00000000`00000000 fffff880`031bccd8 00000000`00000000 fffff880`031bcce0 00000000`00000000 fffff880`031bcce8 00000000`00000000 fffff880`031bccf0 000004e8`fffffb30 fffff880`031bccf8 000004d0`fffffb30 ... 3: kd> lmvm atikmdag start end module name fffff880`07229000 fffff880`07c4a000 atikmdag T (no symbols) Loaded symbol image file: atikmdag.sys Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys Image name: atikmdag.sys Timestamp: Fri Jul 27 21:48:09 2012 (501344D9) CheckSum: 009DA146 ImageSize: 00A21000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4