BSOD After installing graphics drivers

Hi 17hoehbr.

It is a very old branded desktop, and a stop 0x116 may occur on it due to various reasons.

First, the GPU itself. You said that it is an ATI Radeon HD 6450; but it is not active when you executed the DM Log Collector. We are getting the GPU info is ....

Code:

          Card name: Standard VGA Graphics Adapter
       Manufacturer: (Standard display types)
          Chip type: AMD ATOMBIOS

May be the GPU is corrupt itself. As a test, get any other GPU, from friends or family. Apply it and observe it it is producing the same BSOD or not. It seems that without the GPU, the computer works fine. We need to know that if it is the particular GPU, or any other GPU.

Some other info are very much needed to know, depending on the age and the build of the computer.

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

Is the computer hot? 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 .

Let us know the results.
____________________________

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa80059b0010, fffff88003a27dac, 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+bdac )

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: fffffa80059b0010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88003a27dac, 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+bdac
fffff880`03a27dac 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) amd64fre

STACK_TEXT:  
fffff880`02c509c8 fffff880`03b1bcbc : 00000000`00000116 fffffa80`059b0010 fffff880`03a27dac 00000000`00000000 : nt!KeBugCheckEx
fffff880`02c509d0 fffff880`03b1b9c6 : fffff880`03a27dac fffffa80`059b0010 fffffa80`05814d50 fffffa80`05801010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`02c50a10 fffff880`12b2df07 : fffffa80`059b0010 00000000`00000000 fffffa80`05814d50 fffffa80`05801010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`02c50a40 fffff880`12b57b75 : 00000000`ffffffff 00000000`000005cd 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`02c50b20 fffff880`12b562bb : 00000000`00000102 00000000`00000001 00000000`000005cd 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`02c50b50 fffff880`12b292c6 : ffffffff`ff676980 fffffa80`05801010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`02c50bf0 fffff880`12b55e7a : 00000000`00000000 00000000`0000000f 00000000`00000080 fffffa80`05530b58 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`02c50d00 fffff800`02b73166 : 00000000`12f9a47b fffffa80`0580a620 fffffa80`0396c9e0 fffffa80`0580a620 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`02c50d40 fffff800`028ae486 : fffff800`02a48e80 fffffa80`0580a620 fffff800`02a56c40 fffff880`0102c534 : nt!PspSystemThreadStartup+0x5a
fffff880`02c50d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+bdac
fffff880`03a27dac 4883ec28        sub     rsp,28h

SYMBOL_NAME:  atikmpag+bdac

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  534dd7b9

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`03a1c000 fffff880`03abf000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Wed Apr 16 06:37:05 2014 (534DD7B9)
    CheckSum:         000AA5A5
    ImageSize:        000A3000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4