Seemingly Random BSOD

koolkat77 · 03 Aug 2014

Was there an update on the firmware for the SSD?

Hellsrage · 03 Aug 2014

There was but the update would have wiped the drive of all data and since it holds my OS I was trying to avoid going through the process of setting everything up again.

koolkat77 · 03 Aug 2014

Well that could be the problem.

Hellsrage · 16 Aug 2014

Alright, got my drive back from Adata today. Installed Windows 7 again, still got a few things to do before everything is back to the way I like it but at least my computer is up and running again. :)

koolkat77 · 17 Aug 2014

Thanks for the update.

Hellsrage · 06 Sep 2014

Well, looks like I just can't get away from what ever is causing this. I'm thinking this might be hardware related at this point.... We can rule out my crap MOBO as I have yet to apply my previous CPU OC, nice to see that even though Gigabyte failed massively with this board

I still haven't tested the RAM but tomorrow I'll swap RAM with my old PC and run Memtest but I do think the problem may be my GPU. It's always been a bit wonky, and I know for a fact the Vram on it either is of low quality or is failing/has been failing. I had to have my first one replaced and when the replacement(referb) came it had the exact same Vram issues, I guess I know why Sapphire released a newer version of it....

Hellsrage · 11 Jan 2015

Well, I'm getting BSOD's again but this time it's different, right before the BSOD my display drivers crash. I'm not sure if it's a bad install of my AMD drivers or a hardware problem.

Hellsrage · 13 Jan 2015

Anyone?

koolkat77 · 14 Jan 2015

Code:


Microsoft (R) Windows Debugger Version 6.3.9600.16384 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\YUSRA\Downloads\Compressed\SF_11-01-2015\SF_11-01-2015\011115-9812-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*c:\symbols*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.18526.amd64fre.win7sp1_gdr.140706-1506
Machine Name:
Kernel base = 0xfffff800`0220b000 PsLoadedModuleList = 0xfffff800`0244e890
Debug session time: Mon Jan 12 01:37:26.033 2015 (UTC + 6:00)
System Uptime: 0 days 1:58:09.678
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8011cc0010, fffff88002c9431c, 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+b31c )

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: fffffa8011cc0010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88002c9431c, 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+b31c
fffff880`02c9431c 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.16384 (debuggers(dbg).130821-1623) x86fre

STACK_TEXT:  
fffff880`085d8928 fffff880`06341134 : 00000000`00000116 fffffa80`11cc0010 fffff880`02c9431c 00000000`00000000 : nt!KeBugCheckEx
fffff880`085d8930 fffff880`06340e3e : fffff880`02c9431c fffffa80`11cc0010 fffffa80`1118ed50 fffffa80`0e331410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`085d8970 fffff880`0520ff13 : fffffa80`11cc0010 00000000`00000000 fffffa80`1118ed50 fffffa80`0e331410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`085d89a0 fffff880`05239cf1 : fffffa80`ffffffff 00000000`0006ee8f 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`085d8a80 fffff880`0520b2e1 : fffffa80`0e331410 fffffa80`00000008 00000000`0006ee8f 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`085d8ab0 fffff880`05237ff6 : 00000000`00000000 fffffa80`102632a0 00000000`00000080 fffffa80`0e331410 : dxgmms1!VidSchiScheduleCommandToRun+0x1e9
fffff880`085d8bc0 fffff800`0251c73a : 00000000`fffffc32 fffffa80`0e35a610 fffffa80`0cd63040 fffffa80`0e35a610 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`085d8c00 fffff800`022718e6 : fffff800`023fbe80 fffffa80`0e35a610 fffff800`02409cc0 6164335f`656e6f6e : nt!PspSystemThreadStartup+0x5a
fffff880`085d8c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+b31c
fffff880`02c9431c 4883ec28        sub     rsp,28h

SYMBOL_NAME:  atikmpag+b31c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  546a3644

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
---------

7: kd> lmvm atikmpag
start             end                 module name
fffff880`02c89000 fffff880`02d1c000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Mon Nov 17 23:54:12 2014 (546A3644)
    CheckSum:         00090738
    ImageSize:        00093000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

follow steps on this thread

STOP 0x116: VIDEO_TDR_ERROR troubleshooting

Hellsrage · 21 Jan 2015

koolkat77 said:

follow steps on this thread

STOP 0x116: VIDEO_TDR_ERROR troubleshooting

Thanks for the link, I ended up having a different problem though.

It turns out the AMD Gaming Evolved App was behind all of my 0X0116 BSOD's, if you're getting this error and are using the App, try disabling the Replay feature or just uninstalling the app all together. The problem has been reported by users before so hopefully they can fix this very annoying issue.

Hopefully this will help others having the same problem I did.