question

ajb617 avatar image
0 Votes"
ajb617 asked ChanceDiPietro-2385 answered

PC crash to black screen while gaming, no BSOD

For a few months by PC has been crashing at seemingly random points while playing games. Sometimes it will happen almost as soon as I open the game, sometimes I can play for 10 or 20 or 30 minutes before it happens. I don't edit images or process videos, and I don't run any CAD software so I cant say whether that sort of program would crash my PC. Games are the only resource intensive programs I run. I can reliably do normal web browsing, YouTube, schoolwork, etc. without issue, but games will crash the PC.

The event occurs as a black screen. Whatever soundbite was playing immediately before the crash will continue and wont stop until I force shut off. The fans on the case continue at the same speed but the fans on the GPU cooler throttle to maximum rpm, again, not stopping until I force the PC to shut off by holding the power button.

Research up until this point has led me to suspect my RAM and PSU. Both of which have been replaced with brand new parts but to no avail.

PC Details:

  • AMD Ryzen 7 2700X (no overclock)

  • Gigabyte Aurous Gaming 5 WiFi X470

  • G.Skill TridentZ RGB 32 GB (4 x 8 GB) (brand new, function confirmed in another PC)

  • Asus Arez AMD Radeon RX Vega 64

  • WD Black 2 TB M.2 NVMe

  • Corsair SF750 SFX PSU (brand new, function confirmed in another PC)

All crash reports are identical save for the time stamp.

Each crash is accompanied by 3 more errors:

  1. Event 28 - Kernel-EventTracing - "Error setting traits on Provider {8444a4fb-d8d3-4f38-84f8-89960a1ef12f}. Error: 0xC0000001"

  2. Event 1101 - Eventlog - "Audit events have been dropped by the transport. 0"

  3. Event 6008 - EventLog - "The previous system shutdown at 1:06:06 PM on ‎2/‎7/‎2021 was unexpected."

66047-event-properties-general.png


66051-event-properties-details.png



Crash Dump:

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19042 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff805`40000000 PsLoadedModuleList = 0xfffff805`40c2a2f0
Debug session time: Sun Feb 7 13:12:51.076 2021 (UTC - 5:00)
System Uptime: 0 days 0:46:51.826
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
For analysis of this file, run !analyze -v
4: 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: ffff828971382010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff80554ade8d0, The pointer into responsible device driver module (e.g owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 0000000000000000, Optional internal context dependent data.

Debugging Details:



Unable to load image amdkmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for amdkmdag.sys

KEY_VALUES_STRING: 1

 Key  : Analysis.CPU.Sec
 Value: 2

 Key  : Analysis.DebugAnalysisProvider.CPP
 Value: Create: 8007007e on DESKTOP-CSIF7AM

 Key  : Analysis.DebugData
 Value: CreateObject

 Key  : Analysis.DebugModel
 Value: CreateObject

 Key  : Analysis.Elapsed.Sec
 Value: 2

 Key  : Analysis.Memory.CommitPeak.Mb
 Value: 86

 Key  : Analysis.System
 Value: CreateObject


DUMP_FILE_ATTRIBUTES: 0x18
Kernel Generated Triage Dump
Live Generated Dump

BUGCHECK_CODE: 141

BUGCHECK_P1: ffff828971382010

BUGCHECK_P2: fffff80554ade8d0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

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


PROCESS_NAME: System

STACK_TEXT:
ffffaa8b`b987d4d0 fffff805`4c210ea0 : ffff8289`71382010 ffffaa8b`b987d740 00000000`00004740 ffff8289`675b0cf0 : watchdog!WdpDbgCaptureTriageDump+0x64a
ffffaa8b`b987d580 fffff805`4c0b0f19 : 00000000`00000000 00000000`00050216 00000000`00000001 ffff8289`6624b000 : watchdog!WdDbgReportRecreate+0xd0
ffffaa8b`b987d5e0 fffff805`4c0af8d8 : ffff8289`00000000 ffffc181`e4a65b60 00000000`00000000 00000000`00004740 : dxgkrnl!TdrUpdateDbgReport+0x119
ffffaa8b`b987d640 fffff805`4e3e0ef2 : ffff8289`6634d000 00000000`00000200 ffff8289`71382010 ffff8289`6634d000 : dxgkrnl!TdrCollectDbgInfoStage1+0x2d8
ffffaa8b`b987d780 fffff805`4e481db5 : ffff8289`6634d000 00000000`00000000 ffff8289`6624b000 ffff8289`6634d001 : dxgmms2!VidSchiResetEngine+0x312
ffffaa8b`b987d930 fffff805`4e45591b : ffff8289`6624b000 00000000`00000001 00000000`00000000 00000000`00000000 : dxgmms2!VidSchiResetEngines+0xb1
ffffaa8b`b987d980 fffff805`4e42d6b2 : ffffaa8b`b987da01 00000000`0002be70 00000000`00989680 00000000`00000200 : dxgmms2!VidSchiCheckHwProgress+0x2823b
ffffaa8b`b987d9f0 fffff805`4e3bb9ca : ffff8289`6f6c7730 ffff8289`6624b000 ffffaa8b`b987db19 00000000`00989680 : dxgmms2!VidSchiWaitForSchedulerEvents+0x372
ffffaa8b`b987dac0 fffff805`4e43b1a5 : ffff8289`5c771000 ffff8289`6624b000 ffff8289`5c771010 ffff8289`663d3920 : dxgmms2!VidSchiScheduleCommandToRun+0x2ca
ffffaa8b`b987db80 fffff805`4e43b15a : ffff8289`6624b400 fffff805`4e43b090 ffff8289`6624b000 ffff9980`92700100 : dxgmms2!VidSchiRun_PriorityTable+0x35
ffffaa8b`b987dbd0 fffff805`40317e25 : ffff8289`6605c140 fffff805`00000001 ffff8289`6624b000 000f8067`b4bbbdff : dxgmms2!VidSchiWorkerThread+0xca
ffffaa8b`b987dc10 fffff805`403fcdd8 : ffff9980`92700180 ffff8289`6605c140 fffff805`40317dd0 a36b5556`b7d03687 : nt!PspSystemThreadStartup+0x55
ffffaa8b`b987dc60 00000000`00000000 : ffffaa8b`b987e000 ffffaa8b`b9878000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: amdkmdag+ae8d0

MODULE_NAME: amdkmdag

IMAGE_NAME: amdkmdag.sys

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: LKD_0x141_IMAGE_amdkmdag.sys

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {48b738dd-5a92-7ff8-63d0-f075fc680fe0}

Followup: MachineOwner












windows-10-generalwindows-10-hardware-performance
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

CarlFan-MSFT avatar image
1 Vote"
CarlFan-MSFT answered

Hi,
According to the error message, it seems to be related to your video card driver.
Event ID 41 is a normal record of an abnormal shutdown and contains almost no valid information.
For the dump file, IMAGE_NAME: amdkmdag.sys. VIDEO_ENGINE_TIMEOUT_DETECTED (141). It points to your AMD video card driver. Firstly, please check the information provided by AMD support website.
https://www.amd.com/en/support/kb/faq/gpu-800
I consider that you could try to install an older video card driver version to check.
Hope this helps and please help to accept as Answer if the response is useful.
Best Regards,
Carl

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

ajb617 avatar image
0 Votes"
ajb617 answered ajb617 rolled back

According to the error message, it seems to be related to your video card driver.
Event ID 41 is a normal record of an abnormal shutdown and contains almost no valid information.
For the dump file, IMAGE_NAME: amdkmdag.sys. VIDEO_ENGINE_TIMEOUT_DETECTED (141). It points to your AMD video card driver. Firstly, please check the >information provided by AMD support website.
https://www.amd.com/en/support/kb/faq/gpu-800
I consider that you could try to install an older video card driver version to check.

@CarlFan-MSFT Thank you for the lead. Since then I've tried a few things.

The information that AMD forums gave me didn't help much. Most of the suggestions I got were to replace the PSU and run MEMTEST, which I've already done.

Recently I utilized the Display Driver Uninstaller to clean up all display software. In using this, I've tried both the drivers I know to have worked and the newest ones that are Windows certified. (not the optional ones) However, with no success.

Other things I've tried were to move my plugs to different spots on the PSU as well as switching from the split PCIe cable to using a dedicated cable for both power cables.

Still no fix yet.



5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

ChanceDiPietro-2385 avatar image
0 Votes"
ChanceDiPietro-2385 answered

Had the same problem constant random crashing happened after a windows update never had this problem before literally tried everything still happened used ddu, windows roll back ,windows reset upgraded to windows pro still nothing and not help from windows support of nvidia support but I’d did UNINSTALL ARMOURY CRATE from my asus motherboard and updated both my Alienware monitors firmware and no crashes in 3 weeks not sure which one fixed it but since you got asus mother board I’d try armoury crate uninstall there a vid on YouTube on how to do it good luck

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.