New
#1
BSOD atikmpag.sys 0x00000116 now and then
Please, sometimes when I open huge games it just go BSOD. I don't know what to do.HELP, please.
Please, sometimes when I open huge games it just go BSOD. I don't know what to do.HELP, please.
The BSODs are caused by the display driver, which is very old. You need to update it. Check for any possible update in Download Drivers.
Let us know the situation after updating the driver.
___________________________________________
Code:BugCheck 116, {fffffa800d5ad4e0, fffff88004aee3f8, 0, 2} *** WARNING: Unable to verify timestamp for atikmpag.sys *** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys Probably caused by : atikmpag.sys ( atikmpag+73f8 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* VIDEO_TDR_FAILURE (116) Attempt to reset the display driver and recover from timeout failed. Arguments: Arg1: fffffa800d5ad4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT). Arg2: fffff88004aee3f8, The pointer into responsible device driver module (e.g. owner tag). Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation. Arg4: 0000000000000002, Optional internal context dependent data. Debugging Details: ------------------ FAULTING_IP: atikmpag+73f8 fffff880`04aee3f8 4883ec28 sub rsp,28h DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT CUSTOMER_CRASH_COUNT: 1 BUGCHECK_STR: 0x116 PROCESS_NAME: System CURRENT_IRQL: 0 ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre STACK_TEXT: fffff880`0bd3d888 fffff880`05b55134 : 00000000`00000116 fffffa80`0d5ad4e0 fffff880`04aee3f8 00000000`00000000 : nt!KeBugCheckEx fffff880`0bd3d890 fffff880`05b54e3e : fffff880`04aee3f8 fffffa80`0d5ad4e0 fffffa80`09b8dd50 fffffa80`09e32410 : dxgkrnl!TdrBugcheckOnTimeout+0xec fffff880`0bd3d8d0 fffff880`05a0ff13 : fffffa80`0d5ad4e0 00000000`00000000 fffffa80`09b8dd50 fffffa80`09e32410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2 fffff880`0bd3d900 fffff880`05a39cf1 : 00000000`ffffffff 00000000`00057ee6 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b fffff880`0bd3d9e0 fffff880`05a38437 : 00000000`00000102 00000000`00000008 00000000`00057ee6 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71 fffff880`0bd3da10 fffff880`05a0b2d2 : ffffffff`ff676980 fffffa80`09e32410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb fffff880`0bd3dab0 fffff880`05a37ff6 : 00000000`00000000 fffffa80`13e1f840 00000000`00000080 fffffa80`09e32410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da fffff880`0bd3dbc0 fffff800`03571456 : 00000000`fffffc32 fffffa80`09b938b0 fffffa80`06c61480 fffffa80`09b938b0 : dxgmms1!VidSchiWorkerThread+0xba fffff880`0bd3dc00 fffff800`032c92c6 : fffff800`03456e80 fffffa80`09b938b0 fffff800`03464cc0 00000000`00000004 : nt!PspSystemThreadStartup+0x5a fffff880`0bd3dc40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: .bugcheck ; kb FOLLOWUP_IP: atikmpag+73f8 fffff880`04aee3f8 4883ec28 sub rsp,28h SYMBOL_NAME: atikmpag+73f8 FOLLOWUP_NAME: MachineOwner MODULE_NAME: atikmpag IMAGE_NAME: atikmpag.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4e9bc523 FAILURE_BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:x64_0x116_image_atikmpag.sys FAILURE_ID_HASH: {83e844bc-fe68-2042-4230-7f5d3e90b48a} Followup: MachineOwner --------- 0: kd> lmvm atikmpag start end module name fffff880`04ae7000 fffff880`04b36000 atikmpag T (no symbols) Loaded symbol image file: atikmpag.sys Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys Image name: atikmpag.sys Timestamp: Mon Oct 17 11:33:15 2011 (4E9BC523) CheckSum: 000544D9 ImageSize: 0004F000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4