BSOD random occurrence 0x00000116

austzorro · 18 Nov 2014

Not sure why but this BSOD has occurred twice in one day and I have never seen it happen before.

I have attached the ZIP folder as required from the forum instructions.

In my event viewer I receive the following:

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000116 (0xfffffa800f0d3310, 0xfffff88005c0aebc, 0xffffffffc0000001, 0x0000000000000003). A dump was saved in: C:\windows\Minidump\111814-11840-01.dmp. Report Id: 111814-11840-01.

I tried to google it and nothing really helps me identify my problem specifically.

If anyone can help me out that would be much appreciated.

Dan

Arc · 18 Nov 2014

Hi austzorro.

Are you overclocking? As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings.

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator - The most trusted PSU Wattage Calculator
Also let us know the wattage of the PSU.

Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: Speccy - Publish Snapshot of your System Specs .

Stress test the Graphics Card using Furmark.

Video Card - Stress Test with Furmark

Take a screenshot of the furmark window before closing it. Upload the screenshot for us.

Let us know the results.
________________________________

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800f0d3310, fffff88005c0aebc, ffffffffc0000001, 3}

Unable to load image atikmpag.sys, Win32 error 0n2
*** 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+aebc )

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: fffffa800f0d3310, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88005c0aebc, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc0000001, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000003, Optional internal context dependent data.

Debugging Details:
------------------


FAULTING_IP: 
atikmpag+aebc
fffff880`05c0aebc 48895c2408      mov     qword ptr [rsp+8],rbx

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.17237 (debuggers(dbg).140716-0327) amd64fre

STACK_TEXT:  
fffff880`07fe28d8 fffff880`05ea4134 : 00000000`00000116 fffffa80`0f0d3310 fffff880`05c0aebc ffffffff`c0000001 : nt!KeBugCheckEx
fffff880`07fe28e0 fffff880`05e77569 : fffff880`05c0aebc fffffa80`0c67a000 00000000`00000000 fffffa80`0c5c8010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`07fe2920 fffff880`05ea3ee1 : fffffa80`0f0d3310 fffffa80`0f0d3310 fffffa80`0f0d3310 fffffa80`0c5c8010 : dxgkrnl!DXGADAPTER::PrepareToReset+0x109
fffff880`07fe2960 fffff880`05f4bf13 : fffffa80`0f0d3310 00000000`00000000 fffffa80`0e186010 fffffa80`0c5c8010 : dxgkrnl!TdrIsRecoveryRequired+0x245
fffff880`07fe2990 fffff880`05f79ed6 : fffffa80`ffffffff 00000000`000b66d5 fffff880`07fe2af0 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`07fe2a70 fffff880`05f472aa : fffffa80`0c5c8010 ffffffff`feced300 fffffa80`0e186010 00000000`00000000 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`07fe2ab0 fffff880`05f73ff6 : 00000000`00000000 fffffa80`0e186010 00000000`00000080 fffffa80`0c5c8010 : dxgmms1!VidSchiScheduleCommandToRun+0x1b2
fffff880`07fe2bc0 fffff800`03d1d73a : 00000000`02b3506f fffffa80`0c5c6060 fffffa80`0792ab30 fffffa80`0c5c6060 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`07fe2c00 fffff800`03a728e6 : fffff880`03565180 fffffa80`0c5c6060 fffff880`0356ffc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`07fe2c40 00000000`00000000 : fffff880`07fe3000 fffff880`07fdd000 fffff880`07fe2250 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+aebc
fffff880`05c0aebc 48895c2408      mov     qword ptr [rsp+8],rbx

SYMBOL_NAME:  atikmpag+aebc

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5417612a

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`05c00000 fffff880`05c92000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Tue Sep 16 03:29:06 2014 (5417612A)
    CheckSum:         000964D0
    ImageSize:        00092000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

austzorro · 20 Nov 2014

Hi Arc.

I may have solved this.

One thing I noticed was my monitor ended up going blank on me on some restarts. So I moved the HDMI from the AMD Radeon GFX card into the mainboard Intel HMDI port.

I noticed that there was a driver error concerning ATI/AMD driver. After a restart it never appeared again. I never got a BSOD it just froze randomly.

Anyways. I uninstalled all the Catalyst/AMD software for my GFX card and cleaned the registry out and then reinstalled the latest drivers/software. I had previously overclocked the machine and set fan speeds higher, but I never had such freezes or BSOD issues for months.

So after this new install and factory defaults for GFX settings - I havent seen any freezes/BSOD errors. Touch wood.

Thanks.

Arc · 20 Nov 2014

Well, very good news. Still monitor the temps. That might be necessary at any time.