New
#11
I don't have another video card. It's a laptop, so it's not that easy to change cards.
I don't have another video card. It's a laptop, so it's not that easy to change cards.
I read it, and I started working through the list.
So far I've run prime95 and memtest, tested for overheating with furmark. There were no errors and no BSODs during the testing.
I've tried multiple different drivers and I've tried underclocking the GPU, but there has been no change.
The problems only show up when I'm playing certain games, most recently Far Cry 2, but I can play other games without any crashes. If it's a hardware issue, shouldn't I be having trouble with all games and/or during stress testing?
I suspect your GPU is bad.
Every 0x116 bugcheck shows this as the subcode for the error that triggered the bugcheck. It's telling that the device isn't responding to the I/O request promptly, and the driver is notifying the system, which the system is responding with the BSOD. It's time to look at replacing the GPU, which means getting the laptop replaced/serviced.Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 116, {fffffa800d8d4010, fffff88004806f94, ffffffffc00000b5, a} *** WARNING: Unable to verify timestamp for atikmpag.sys *** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2 Probably caused by : atikmpag.sys ( atikmpag+6f94 ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* VIDEO_TDR_FAILURE (116) Attempt to reset the display driver and recover from timeout failed. Arguments: Arg1: fffffa800d8d4010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT). Arg2: fffff88004806f94, The pointer into responsible device driver module (e.g. owner tag). Arg3: ffffffffc00000b5, Optional error code (NTSTATUS) of the last failed operation. Arg4: 000000000000000a, Optional internal context dependent data. Debugging Details: ------------------ TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2 FAULTING_IP: atikmpag+6f94 fffff880`04806f94 4883ec28 sub rsp,28h DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT CUSTOMER_CRASH_COUNT: 1 BUGCHECK_STR: 0x116 PROCESS_NAME: System CURRENT_IRQL: 0 STACK_TEXT: fffff880`021c2918 fffff880`04aa4000 : 00000000`00000116 fffffa80`0d8d4010 fffff880`04806f94 ffffffff`c00000b5 : nt!KeBugCheckEx fffff880`021c2920 fffff880`04aa3ddb : fffff880`04806f94 fffffa80`0d8d4010 fffffa80`0d34a310 fffffa80`0abcf410 : dxgkrnl!TdrBugcheckOnTimeout+0xec fffff880`021c2960 fffff880`04b4af07 : fffffa80`0d8d4010 00000000`c00000b5 fffffa80`0d34a310 fffffa80`0abcf410 : dxgkrnl!TdrIsRecoveryRequired+0x273 fffff880`021c2990 fffff880`04b78d5a : 00000000`ffffffff 00000000`004b103d fffff880`021c2af0 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b fffff880`021c2a70 fffff880`04b4629e : fffffa80`0abcf410 ffffffff`feced300 fffffa80`0d6aed50 00000000`00000000 : dxgmms1!VidSchWaitForCompletionEvent+0x196 fffff880`021c2ab0 fffff880`04b72e7a : 00000000`00000000 fffffa80`0d34a310 00000000`00000080 fffffa80`0abcf410 : dxgmms1!VidSchiScheduleCommandToRun+0x1b2 fffff880`021c2bc0 fffff800`03579ede : 00000000`01e954b0 fffffa80`0aa49060 fffffa80`06ff3040 fffffa80`0aa49060 : dxgmms1!VidSchiWorkerThread+0xba fffff880`021c2c00 fffff800`032cc906 : fffff880`009ea180 fffffa80`0aa49060 fffff880`009f50c0 532f6c72`506f6865 : nt!PspSystemThreadStartup+0x5a fffff880`021c2c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16 STACK_COMMAND: .bugcheck ; kb FOLLOWUP_IP: atikmpag+6f94 fffff880`04806f94 4883ec28 sub rsp,28h SYMBOL_NAME: atikmpag+6f94 FOLLOWUP_NAME: MachineOwner MODULE_NAME: atikmpag IMAGE_NAME: atikmpag.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4cc990cb FAILURE_BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys Followup: MachineOwner --------- 2: kd> !error c00000b5 Error code: (NTSTATUS) 0xc00000b5 (3221225653) - {Device Timeout} The specified I/O operation on %hs was not completed before the time-out period expired.
I havn't got a 0x116 bug check since updating the drivers. It's always 0x7e with Arg1: ffffffffc0000094. It could still be that the GPU is bad, but 0x116 isn't the problem anymore.
The new crashes you're referring too are caused by divide by zero attempts generated by the AMD drivers. However, I do believe it's just another way the GPU is manifesting its problems by sending bad data to the drivers. It may be a bug in the most recent drivers, but the thing I'm concerned about is that no amount of alteration to the GPU or graphics drivers is altering the fact that the graphics drivers always seems to pop up as the cause, and from the 0x116 bugchecks like to say, it's because the GPU is unstable.