General Discussions

[Cyberfyber]

Hi and sorry if I posted to the wrong group.

Got my new Gaming PC several days ago (second one in this household with similar issues and exact same build).

Been getting 3-4 black screens / reboots / semi reboots each day now. Sometimes not sure if it's actually rebooted or not or in some weird limbo state. Can't tell with the darn screen black.
 
Usually though, I'll have to hold down the power button for a full reboot. Most often I'll end up with a black screen and the keyboard still lit as well as the RGB lights in the pc still going on.

I guess they amount to Kernel Errors (41, 10001)? Been having the Event Viewer on at all times as a constant reminder. 

Soooo, I searched and finally stumbled upon you fine folk. Originally thought it to be an HDMI issue between my smart tv and the graphics card. Experimented lots there (using old monitors as well as the DVI connection).

Also noticed mention of the PBO and changing it to disabled (from other posts here at the forum). 

Now I've connected the pc to my Smart TV again, using a DVI to HDMI converter (testing things out) with PBO disabled.

Too early for me to judge since it could take hours for anything to happen.

Any suggestions?

btw, I found it so very odd how sometimes it'd appear to happen at the mere whiff of the air my body would produce when walking by my PC (which is on the ground nearby).  Yet, it's nothing I could ever assuredly reproduce intentionally. 'and maybe it's just coincidental.

Thanks in advance for any input. 

[Cyberfyber]

Speaking of the devil.

Just now happened again but this time with a BSOD.

With mention of AMD kmdag fail.

So much for my DVI and PBO route. 

[goodplay]

Please read and supply https://community.amd.com/t5/knowledge-base/information-required-when-posting-a-discussion/ta-p/4227... and someone may be able to offer suggestions.

[Cyberfyber]

Thanks for the correction.

Couldn't find a way to remove my post so's I can get the info then repost.

Alas, it'd have to wait till morn. Sorry bout that and again, thanks.

[Cyberfyber]

Forgive me for not sharing this the first time around. Below is an update.

Windows 10 // Ryzen 5 3600 // Corsair - Vengeance RGB Pro - 16GB DDR4 3200 (2 modules) // RX 580 // EVGA 600W Gold PSU // Western Digital Drives: SSD 240 GB + 2 TB HD // B350M Gigabyte Motherboard

Using two USB extension cords (one for MS Bluetooth Mouse - one for wired Logitech Keyboard)

Today:

• Reinstalled windows (Crashed even during installation)
• Had to use a Windows Installation via USB to get back in past the Reboot loop
• Crashed not too long after full installation
• Removed the AMD Driver 
• Installed AMD 20.11.2 through Radeon Software

Finally figured out how to read the Memory Dump File which I’ll share below in case anyone’s willing to help me make sense of it. 

Oddest thing. What I mentioned in my OP has become more apparent. Movement. Could be the extension cables? Or maybe static electricity? I’m like a walking lightning rod in my home with static electricity. BUT, does that fall in line with what shows up in the Dump File?

[Cyberfyber]

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff804`67000000 PsLoadedModuleList = 0xfffff804`67c2a3b0
Debug session time: Fri Mar 5 13:24:54.787 2021 (UTC - 5:00)
System Uptime: 0 days 0:46:10.411
Loading Kernel Symbols
...............................................................
....Page 802cbd not present in the dump file. Type ".hh dbgerr004" for details
............................................................
..........................................................
Loading User Symbols

Loading unloaded module list
......
For analysis of this file, run !analyze -v
5: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffffe7870df52460, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff80482cd0a40, 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:
------------------

KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 2

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

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 3

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

Key : Analysis.System
Value: CreateObject

BUGCHECK_CODE: 116

BUGCHECK_P1: ffffe7870df52460

BUGCHECK_P2: fffff80482cd0a40

BUGCHECK_P3: ffffffffc0000001

BUGCHECK_P4: 3

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXWINLOGON: 1

PROCESS_NAME: System

STACK_TEXT:
ffff858c`db8219f8 fffff804`764b145e : 00000000`00000116 ffffe787`0df52460 fffff804`82cd0a40 ffffffff`c0000001 : nt!KeBugCheckEx
ffff858c`db821a00 fffff804`7645981b : fffff804`82cd0a40 ffffe787`093a3000 ffffe787`093a30f0 00000000`00000000 : dxgkrnl!TdrBugcheckOnTimeout+0xfe
ffff858c`db821a40 fffff804`7645a5ee : ffffe787`00000101 00000000`00002000 ffffe787`093a3000 00000000`01000000 : dxgkrnl!DXGADAPTER::PrepareToReset+0x1a3
ffff858c`db821a90 fffff804`764b0b85 : 00000000`00000100 ffffe787`093a3a58 00000000`010a3cf0 fffff804`67229bec : dxgkrnl!DXGADAPTER::Reset+0x28e
ffff858c`db821b10 fffff804`764b0cf7 : fffff804`67d25440 00000000`00000000 00000000`00000000 00000000`00000a00 : dxgkrnl!TdrResetFromTimeout+0x15
ffff858c`db821b40 fffff804`673034b5 : ffffe787`0b523080 fffff804`764b0cd0 ffffe787`010a3cf0 ffffe787`00000000 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x27
ffff858c`db821b70 fffff804`672a29a5 : ffffe787`0b523080 00000000`00000080 ffffe787`0108f040 000f8067`b4bbbdff : nt!ExpWorkerThread+0x105
ffff858c`db821c10 fffff804`673fc868 : ffff9681`51d5c180 ffffe787`0b523080 fffff804`672a2950 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffff858c`db821c60 00000000`00000000 : ffff858c`db822000 ffff858c`db81c000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28

SYMBOL_NAME: amdkmdag+b0a40

MODULE_NAME: amdkmdag

IMAGE_NAME: amdkmdag.sys

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x116_IMAGE_amdkmdag.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {1c94a7e8-453f-c7b9-1484-0a0454a0ee36}

Followup: MachineOwner

[TKKG-Trummy]

und wie sieht das jetzt aus ... ? 

[Cyberfyber]

Your Question:
"and what does it look like now? ‎... ? "

I'm convinced now it's static electricity. Thing is, it'll happen without me even touching the case. 

Sooooo, it's my first new desktop in over a decade. Is this even normal? My old desktop, kept in the same spot has no troubles whatsoever.