experiencing an issue where my PC randomly restarts or freezes with a black screen when left idle

Ahmed Amin 0 Reputation points
2026-06-09T18:10:14.0733333+00:00

I am currently experiencing an issue where my PC randomly restarts or freezes with a black screen, accompanied by a weird popping sound (pop pop pop). This exclusively occurs when the system is left idle.

My PC Specifications:

  • Motherboard: Gigabyte Z890 eagle
  • GPU: ASUS Prime Radeon RX 9070
  • RAM: Kingston FURY Beast 32g
  • Storage: WD_BLACK 2TB NVMe SSD
  • OS: Windows 11

According to the Windows Reliability Monitor, the hardware error is logged as follows:

Problem Event Name: LiveKernelEvent

Code: 193

Parameter 1: 810

Parameter 2: ffffc406b86e0000

Parameter 3: ffffc40681ca33c0

Parameter 4: 111

The associated WATCHDOG dump file points to a dxgkrnl!ProcessDeadlockThread failure and contains the following:I am currently experiencing an issue where my PC randomly restarts or freezes with a black screen, accompanied by a weird popping sound (pop pop pop). This exclusively occurs when the system is left idle.

Troubleshooting steps I have already taken:

  • I suspected the RAM, but I verified it is correctly installed in DIMM slots A2 and B2 for a dual-channel configuration.
  • I did a completely clean installation of the latest GPU drivers (with a factory reset).

According to the Windows Reliability Monitor, the hardware error is logged as follows:

Problem Event Name: LiveKernelEvent

Code: 193

Parameter 1: 810

Parameter 2: ffffc406b86e0000

Parameter 3: ffffc40681ca33c0

Parameter 4: 111

The associated WATCHDOG dump file points to a dxgkrnl!ProcessDeadlockThread failure and contains the following:

IDEO_DXGKRNL_LIVEDUMP (193)
Livedumps triggered by dxgkrnl when a problem is detected.
(This code can never be used for a real BugCheck; it is used to identify live dumps.)
Arguments:
Arg1: 0000000000000810, Reason Code.
	100 Internal
Arg2: ffffc406b86e0000, Reserved.
Arg3: ffffc40681ca33c0, Reserved.
Arg4: 0000000000000111, Reserved.

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

Mini Kernel Dump does not contain unloaded driver list
Mini Kernel Dump does not contain unloaded driver list

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 828

    Key  : Analysis.Elapsed.mSec
    Value: 2644

    Key  : Analysis.IO.Other.Mb
    Value: 24

    Key  : Analysis.IO.Read.Mb
    Value: 1

    Key  : Analysis.IO.Write.Mb
    Value: 31

    Key  : Analysis.Init.CPU.mSec
    Value: 578

    Key  : Analysis.Init.Elapsed.mSec
    Value: 35220

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.29547.1002

    Key  : Analysis.Version.Description
    Value: 10.2602.27.2 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2602.27.2

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x193

    Key  : Bugcheck.Code.TargetModel
    Value: 0x193

    Key  : Dump.Attributes.AsUlong
    Value: 0x18

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Failure.Bucket
    Value: LKD_0x193_dxgkrnl!ProcessDeadlockThread

    Key  : Failure.Hash
    Value: {cd7886fb-c389-14b9-08f5-7f88f35fd2d8}


BUGCHECK_CODE:  193

BUGCHECK_P1: 810

BUGCHECK_P2: ffffc406b86e0000

BUGCHECK_P3: ffffc40681ca33c0

BUGCHECK_P4: 111

FILE_IN_CAB:  WATCHDOG-20260609-2008.dmp

DUMP_FILE_ATTRIBUTES: 0x18
  Kernel Generated Triage Dump
  Live Generated Dump

FAULTING_THREAD:  ffffc406e6bed080

PROCESS_NAME:  System

STACK_TEXT:  
fffff987`2777f1b0 fffff800`76905ad9     : 00000000`00000810 00000000`00000000 00000000`00000000 00000000`00000000 : nt!DbgkpWerCaptureLiveTriageDump+0x8e
fffff987`2777f6e0 fffff800`76ca3d8a     : 00000000`00000000 00000000`c0000022 fffff800`76cea5f0 00000000`c0000022 : nt!DbgkpWerProcessPolicyResult+0x21
fffff987`2777f710 fffff800`76ca3b89     : ffffc406`81ca33c0 fffff987`2777f950 ffffffff`c0000022 00000000`00000000 : nt!DbgkWerCaptureLiveKernelDump2+0x1ea
fffff987`2777f770 fffff800`08203ecc     : 00000000`00000057 ffffc406`81ca33c0 ffffffff`c0000022 00000000`00000000 : nt!DbgkWerCaptureLiveKernelDump+0x69
fffff987`2777f7f0 fffff800`764ea8bb     : ffffc406`e6bed080 ffffc406`7b6eeb00 fffff987`2777fa00 ffffc406`7b6eebe0 : dxgkrnl!ProcessDeadlockThread+0xec
fffff987`2777f980 fffff800`7668173a     : ffffc406`e6bed080 ffffc406`e6bed080 fffff800`764ea400 ffffc406`7b6eebe0 : nt!ExpWorkerThread+0x4bb
fffff987`2777fb30 fffff800`768a9ff4     : fffff800`038c4180 ffffc406`e6bed080 fffff800`766816e0 00000000`00000297 : nt!PspSystemThreadStartup+0x5a
fffff987`2777fb80 00000000`00000000     : fffff987`27780000 fffff987`27779000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


SYMBOL_NAME:  dxgkrnl!ProcessDeadlockThread+ec

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

IMAGE_VERSION:  10.0.26100.8521

STACK_COMMAND: .process /r /p 0xffffc4067b6cb040; .thread /r /p 0xffffc406e6bed080 ; kb

BUCKET_ID_FUNC_OFFSET:  ec

FAILURE_BUCKET_ID:  LKD_0x193_dxgkrnl!ProcessDeadlockThread

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {cd7886fb-c389-14b9-08f5-7f88f35fd2d8}

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

1: kd> .process /r /p 0xffffc4067b6cb040; .thread /r /p 0xffffc406e6bed080 ; kb
Implicit process is now ffffc406`7b6cb040
Loading User Symbols

Implicit thread is now ffffc406`e6bed080
Implicit process is now ffffc406`7b6cb040
Loading User Symbols

  *** Stack trace for last set context - .thread/.cxr resets it
 # RetAddr               : Args to Child                                                           : Call Site
00 fffff800`76905ad9     : 00000000`00000810 00000000`00000000 00000000`00000000 00000000`00000000 : nt!DbgkpWerCaptureLiveTriageDump+0x8e
01 fffff800`76ca3d8a     : 00000000`00000000 00000000`c0000022 fffff800`76cea5f0 00000000`c0000022 : nt!DbgkpWerProcessPolicyResult+0x21
02 fffff800`76ca3b89     : ffffc406`81ca33c0 fffff987`2777f950 ffffffff`c0000022 00000000`00000000 : nt!DbgkWerCaptureLiveKernelDump2+0x1ea
03 fffff800`08203ecc     : 00000000`00000057 ffffc406`81ca33c0 ffffffff`c0000022 00000000`00000000 : nt!DbgkWerCaptureLiveKernelDump+0x69
04 fffff800`764ea8bb     : ffffc406`e6bed080 ffffc406`7b6eeb00 fffff987`2777fa00 ffffc406`7b6eebe0 : dxgkrnl!ProcessDeadlockThread+0xec
05 fffff800`7668173a     : ffffc406`e6bed080 ffffc406`e6bed080 fffff800`764ea400 ffffc406`7b6eebe0 : nt!ExpWorkerThread+0x4bb
06 fffff800`768a9ff4     : fffff800`038c4180 ffffc406`e6bed080 fffff800`766816e0 00000000`00000297 : nt!PspSystemThreadStartup+0x5a
07 00000000`00000000     : fffff987`27780000 fffff987`27779000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34

Windows for home | Windows 11 | Performance and system failures

1 answer

Sort by: Most helpful
  1. Carl-L 23,535 Reputation points Microsoft External Staff Moderator
    2026-06-10T07:11:29.41+00:00

    Hello Ahmed Amin,

    Welcome to Microsoft Q&A forum.

    The dump file indicates a stability issue of GPU driver or firmware. You said that this only happen when the screen is idle, that means this issue only appear in low power mode.

    In this case, please help try a few quick tests and fixes to see if they helps.

    1. Disable problematic power transitions.
      • Go to your BIOS.
      • Find and disable these options:
      • Global C-State Control
      • PCIe ASPM
      • CPU C-states
    2. Change Windows power settings.
      • Type "PowerShell" in the search bar and press Enter.
      • Type control powercfg.cpl and press Enter.
      • Change plan to high performance.
      • Turn off Link State Power Management.
      • Raise Minimum CPU state to 5-10% or higher.
    3. Raise GPU minimum frequency to higher in the GPU OEM application.

    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    Was this answer helpful?

    1 person found this answer helpful.

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.