Repeated, random BSOD. Will keep restarting until working.

kiaace · 06 Jan 2014

So, I've got a ticking time bomb here...trying to get help as soon as I can.

Display driver reset and timeout failed, something like that. On occasion I can't even get to windows before the system crashes.

Tried last known good config, windows memory diagnostics, startup repair finds stuff clean. I have not made any system changes since this happened, was so sudden.

koolkat77 · 07 Jan 2014

Update your ATI Graphics drivers.: Support & Drivers

Perform a clean install of a driver following: How to Clean Left Over Driver Files with Driver Sweeper

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa80084284e0, fffff88007286408, 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+7408 )

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: fffffa80084284e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88007286408, 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:
------------------


OVERLAPPED_MODULE: Address regions for 'lltdio' and 'RtsUVStor.sy' overlap

FAULTING_IP: 
atikmpag+7408
fffff880`07286408 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`09ca2888 fffff880`0732b140 : 00000000`00000116 fffffa80`084284e0 fffff880`07286408 00000000`00000000 : nt!KeBugCheckEx
fffff880`09ca2890 fffff880`0732ae4a : fffff880`07286408 fffffa80`084284e0 fffffa80`08960420 fffffa80`080fc410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`09ca28d0 fffff880`07f4ef13 : fffffa80`084284e0 00000000`00000000 fffffa80`08960420 fffffa80`080fc410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`09ca2900 fffff880`07f78cf1 : 00000000`ffffffff 00000000`00001834 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`09ca29e0 fffff880`07f77437 : 00000000`00000102 00000000`00000000 00000000`00001834 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`09ca2a10 fffff880`07f4a2d2 : ffffffff`ff676980 fffffa80`080fc410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`09ca2ab0 fffff880`07f76ff6 : 00000000`00000000 fffffa80`08960420 00000000`00000080 fffffa80`080fc410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`09ca2bc0 fffff800`03d132ea : 00000000`fffffc32 fffffa80`04d53b50 fffffa80`03ccab30 fffffa80`04d53b50 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`09ca2c00 fffff800`03a678e6 : fffff800`03bf1e80 fffffa80`04d53b50 fffff800`03bffcc0 55566165`6d344951 : nt!PspSystemThreadStartup+0x5a
fffff880`09ca2c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+7408
fffff880`07286408 4883ec28        sub     rsp,28h

SYMBOL_NAME:  atikmpag+7408

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d783436

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

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

0: kd> lmvm atikmpag
start             end                 module name
fffff880`0727f000 fffff880`072ce000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Thu Mar 10 08:15:18 2011 (4D783436)
    CheckSum:         000597DD
    ImageSize:        0004F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

kiaace · 11 Jan 2014

Ok. Uninstalling the driver fixed the urgent crashes. I still get rather frequent crashes. Trying to update the driver for my graphics card with the autodetect utility, AMD tells me I don't have a working card from them on the laptop which is troubling. Also, some explorer.exe crashes. sfc /scannow can't fix all files, cbs log is attached to SF diagnostics rar.

koolkat77 · 11 Jan 2014

Go through this thread as its the same error code repeating over and over:

STOP 0x116: VIDEO_TDR_ERROR troubleshooting

Code:

Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\USER\Downloads\SF_11-01-2014\011114-19266-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`0425b000 PsLoadedModuleList = 0xfffff800`0449e6d0
Debug session time: Sat Jan 11 14:52:00.262 2014 (UTC + 6:00)
System Uptime: 0 days 22:32:14.323
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa80074974e0, fffff88007647408, 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+7408 )

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

7: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa80074974e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88007647408, 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+7408
fffff880`07647408 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`09e81888 fffff880`076ec140 : 00000000`00000116 fffffa80`074974e0 fffff880`07647408 00000000`00000000 : nt!KeBugCheckEx
fffff880`09e81890 fffff880`076ebe4a : fffff880`07647408 fffffa80`074974e0 fffffa80`0845ad50 fffffa80`08483410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`09e818d0 fffff880`08166f13 : fffffa80`074974e0 00000000`00000000 fffffa80`0845ad50 fffffa80`08483410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`09e81900 fffff880`08190cf1 : 00000000`ffffffff 00000000`004f5b5d 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`09e819e0 fffff880`0818f437 : 00000000`00000102 00000000`00000001 00000000`004f5b5d 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`09e81a10 fffff880`081622d2 : ffffffff`ff676980 fffffa80`08483410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`09e81ab0 fffff880`0818eff6 : 00000000`00000000 fffffa80`08484010 00000000`00000080 fffffa80`08483410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`09e81bc0 fffff800`0456d2ea : 00000000`fffffc32 fffffa80`086ea4c0 fffffa80`03ccab30 fffffa80`086ea4c0 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`09e81c00 fffff800`042c18e6 : fffff800`0444be80 fffffa80`086ea4c0 fffff800`04459cc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`09e81c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+7408
fffff880`07647408 4883ec28        sub     rsp,28h

SYMBOL_NAME:  atikmpag+7408

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d783436

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

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

7: kd> lmvm atikmpag
start             end                 module name
fffff880`07640000 fffff880`0768f000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Thu Mar 10 08:15:18 2011 (4D783436)
    CheckSum:         000597DD
    ImageSize:        0004F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Based on the bugchecks, I would recommend you follow and complete the steps given below:

1. If you are overclocking any hardware, please stop. Reset any changed values back to default and reset/clear CMOS: Clear CMOS - 3 Ways to Clear the CMOS - Reset BIOS. Uninstall any overclocking tool as these can also be a reason of blue screens.

2. Uninstall your current antivirus software. It can be a cause of BSOD very often. Please remove it with its removal tool and use Microsoft Security Essentials in its place. Malwarebytes is a great combination with it. Go through this thread for more info.

3. Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log

4. Run SFC /SCANNOW Command - System File Checker to check windows for integrity violations. Run it up to three times to fix all errors. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.

5. Make scans with Kaspersky TDSskiller and ESET Online scanner.

6. Perform a Clean Start up, this will help avoid any problematic applications from bugging the system.

7. Use Revo Uninstaller Free to uninstall stubborn software. Opt for Advanced Mode and uninstall the software, delete the leftover registry entries.

8. Use Crystal Disk Info to upload a screenshot of your Hard Drives (s). Test your Hard Drives (s) running a Hard Drive Diag.

9. Test and Diagnose RAM issues with RAM - Test with Memtest86+. Pay close attention to Part 3 of the tutorial "If you have errors" Take the test for at least 7-10 passes. It may take up to 22 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.

10. Monitor hardware temperature for overheating issues with system monitoring software like Speccy or HWMonitor. Upload a screen shot of the Summary tab as well: