Graphics card crashes under moderate use.

[SkullKing]

Hy, I've been using this computer for over a year now and this has been an issue from day one. Only now have I gotten so frustrated as to seek help on the forums. 

My graphics card seems to "give out" all the time when under moderate use, without any warning. My older, weaker, laptop was able to handle similar loads on the GPU without crashing, so this computer has to be the issue.  I've tried everything I could think of over the past year. I tried reducing the maximum processing power through windows battery settings and forcing windows to take priority in keeping the chip cool over performance, but to no avail. I tried updating the drivers, even the bios at one point, I even tried to reinstall the operating system completely, sadly nothing I tried seemed to help.

I'm really at my wit's end here, If anyone could lend me some advice on how I can possibly go about rectifying this issue that would be appreciated. 

Here is one of the latest .dmp files: 

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


Loading Dump File [C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20180621-0847.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 17134 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff803`24ca0000 PsLoadedModuleList = 0xfffff803`2505a1f0
Debug session time: Thu Jun 21 08:47:13.002 2018 (UTC - 4:00)
System Uptime: 0 days 9:53:23.824
Loading Kernel Symbols
...............................................................
................................................................
.............................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 141, {ffffd70b6e4054a0, fffff8067411cc50, 0, 1870}

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+cc50 )

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

watchdog!WdDbgReportRecreate+0x10c:
fffff806`73acd66c 488b4f38        mov     rcx,qword ptr [rdi+38h] ds:002b:ffffd70b`7627fa88=????????????????
3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_ENGINE_TIMEOUT_DETECTED (141)
One of the the display engines failed to respond in timely fashion.
(This code can never be used for a real bugcheck.)
Arguments:
Arg1: ffffd70b6e4054a0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8067411cc50, The pointer into responsible device driver module (e.g owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 0000000000001870, Optional internal context dependent data.

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


KEY_VALUES_STRING: 1


STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  10.0.17134.112 (WinBuild.160101.0800)

DUMP_TYPE:  2

BUGCHECK_P1: ffffd70b6e4054a0

BUGCHECK_P2: fffff8067411cc50

BUGCHECK_P3: 0

BUGCHECK_P4: 1870

FAULTING_IP: 
atikmpag+cc50
fffff806`7411cc50 ??              ???

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_ENGINE_TIMEOUT

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


CPU_COUNT: 8

CPU_MHZ: af8

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 5e

CPU_STEPPING: 3

BUGCHECK_STR:  0x141

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  DESKTOP-D1U6I5U

ANALYSIS_SESSION_TIME:  06-21-2018 18:33:05.0631

ANALYSIS_VERSION: 10.0.17674.1000 amd64fre

STACK_TEXT:  
ffffcc03`3b27f470 fffff806`739a0ab7 : ffffd70b`6e4054a0 ffffd70b`6e4054a0 ffffcc03`3b27f610 ffffd70b`7627fa50 : watchdog!WdDbgReportRecreate+0x10c
ffffcc03`3b27f4c0 fffff806`763dc625 : ffffd70b`00000000 ffffd70b`715c9570 ffffd70b`6e4054a0 ffffd70b`725ed000 : dxgkrnl!TdrUpdateDbgReport+0xe7
ffffcc03`3b27f510 fffff806`7646c91a : ffffd70b`725ed000 00000000`00000000 00000000`00000001 ffffd70b`725b5001 : dxgmms2!VidSchiResetEngine+0x73d
ffffcc03`3b27f800 fffff806`76449efc : ffffd70b`725ed000 00000000`00000001 00000000`00000000 0000001f`81d7825f : dxgmms2!VidSchiResetEngines+0xaa
ffffcc03`3b27f850 fffff806`764269b6 : 00000000`00000002 00000000`0022c3fc 00000000`0029d7aa 00000000`00000008 : dxgmms2!VidSchiCheckHwProgress+0x2351c
ffffcc03`3b27f8c0 fffff806`763ba75a : 00000000`00000000 ffffd70b`725b5000 00000000`ffffffff 00000000`ffffffff : dxgmms2!VidSchiWaitForSchedulerEvents+0x326
ffffcc03`3b27f990 fffff806`76430da0 : ffffd70b`9bf33700 ffffd70b`725f5ac0 ffffd70b`9bf337f0 ffffd70b`725f5ac0 : dxgmms2!VidSchiScheduleCommandToRun+0x39a
ffffcc03`3b27fa80 fffff806`76430d5e : ffffd70b`725b5500 fffff806`76430cd0 ffffd70b`725b5000 00000000`00000000 : dxgmms2!VidSchiRun_PriorityTable+0x30
ffffcc03`3b27fad0 fffff803`24d84cb7 : ffffd70b`729c4700 fffff806`76430cd0 ffffa780`5c7cf180 000004ed`b59bbfff : dxgmms2!VidSchiWorkerThread+0x8e
ffffcc03`3b27fb10 fffff803`24e3f7d6 : ffffa780`5c7cf180 ffffd70b`729c4700 fffff803`24d84c70 00310063`00360066 : nt!PspSystemThreadStartup+0x47
ffffcc03`3b27fb60 00000000`00000000 : ffffcc03`3b280000 ffffcc03`3b279000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


THREAD_SHA1_HASH_MOD_FUNC:  38ff1601a490f5ffd3426ba59d83f8532ab501a0

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  6e64ea0b06e106145185132a17555bd0d9fe2c61

THREAD_SHA1_HASH_MOD:  d61bf2826c83f42798f71aa711aa4f2cb3225799

FOLLOWUP_IP: 
atikmpag+cc50
fffff806`7411cc50 ??              ???

SYMBOL_NAME:  atikmpag+cc50

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  55e4faae

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  LKD_0x141_IMAGE_atikmpag.sys

BUCKET_ID:  LKD_0x141_IMAGE_atikmpag.sys

PRIMARY_PROBLEM_CLASS:  LKD_0x141_IMAGE_atikmpag.sys

TARGET_TIME:  2018-06-21T12:47:13.000Z

OSBUILD:  17134

OSSERVICEPACK:  112

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  784

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2018-06-08 05:00:00

BUILDDATESTAMP_STR:  160101.0800

BUILDLAB_STR:  WinBuild

BUILDOSVER_STR:  10.0.17134.112

ANALYSIS_SESSION_ELAPSED_TIME:  6cd

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:lkd_0x141_image_atikmpag.sys

FAILURE_ID_HASH:  {c4561d61-ffbc-583d-5e1a-6fd6e42466ee}

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

3: kd> lmvm atikmpag
Browse full module list
start             end                 module name
fffff806`74110000 fffff806`741b9000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: atikmpag.sys
    Image name: atikmpag.sys
    Browse all global symbols  functions  data
    Timestamp:        Mon Aug 31 18:09:02 2015 (55E4FAAE)
    CheckSum:         000A7896
    ImageSize:        000A9000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:
Mini Kernel Dump does not contain unloaded driver list

[Grzwacz · Accepted solution]

Greetings SkullKing,

Welcome to the forum.

I am not an HP employee.

You have done some great troubleshooting.

You have eliminated a driver problem or Windows system corruption problems.

The hardware is faulty.

The PC was released for sale in 2015. I guess you are out of warranty.

The AMD graphics solution is soldered to the motherboard.

This means you will have to replace the motherboard.

Regards

[SkullKing]

Hm... that does appear to be the only solution, doesn't it... Ah well, I guess I'll have to do just that. Wish me luck, and thanks for pointing me in the right direction!

[Grzwacz]

Hi SkullKing,

You're very welcome.

Best wishes.

Check HP PartSurfer.

Or you may have to check Amazon, Newegg, or Ebay if HP does not stock the part.

Regards