F5F Stay Refreshed Hardware Desktop Windows experiencing crashes when waking up, potentially linked to Intel iGPU problems?

Windows experiencing crashes when waking up, potentially linked to Intel iGPU problems?

Windows experiencing crashes when waking up, potentially linked to Intel iGPU problems?

T
TehStratosHD
Senior Member
492
01-18-2023, 10:37 PM
#1
Hi all,
I'm running an Intel NUC 13 Extreme with an Nvidia RTX 4060 TI GPU. I use both the Intel iGPU and the 4060, allowing me to connect five displays. The system works well but has been experiencing crashes or reboots during sleep or when waking up. I haven't tried troubleshooting recently, so I've just tolerated it until now. After a fresh OS installation from scratch, the problem persists. I've examined the dump file and it points to a GPU issue. I disabled the Intel iGPU before leaving, and this time the PC remained operational. It's been this way for about seven months, and I keep my drivers updated, so it doesn't seem to be caused by the latest drivers. Any advice or possible solutions would be appreciated?
T
TehStratosHD
01-18-2023, 10:37 PM #1

Hi all,
I'm running an Intel NUC 13 Extreme with an Nvidia RTX 4060 TI GPU. I use both the Intel iGPU and the 4060, allowing me to connect five displays. The system works well but has been experiencing crashes or reboots during sleep or when waking up. I haven't tried troubleshooting recently, so I've just tolerated it until now. After a fresh OS installation from scratch, the problem persists. I've examined the dump file and it points to a GPU issue. I disabled the Intel iGPU before leaving, and this time the PC remained operational. It's been this way for about seven months, and I keep my drivers updated, so it doesn't seem to be caused by the latest drivers. Any advice or possible solutions would be appreciated?

M
mineuout482
Posting Freak
812
01-18-2023, 11:08 PM
#2
Update your post with complete hardware details and operating system specifics. Provide PSU information such as make, model, wattage, age, and condition (original, build, refurbished, used). List disk drive specifications including make, model, and capacity, noting their current usage level. Check for any error codes in the Reliability History or Event Viewer. Clarify whether you are downloading, installing, and configuring drivers yourself versus using a third-party tool or installer.
M
mineuout482
01-18-2023, 11:08 PM #2

Update your post with complete hardware details and operating system specifics. Provide PSU information such as make, model, wattage, age, and condition (original, build, refurbished, used). List disk drive specifications including make, model, and capacity, noting their current usage level. Check for any error codes in the Reliability History or Event Viewer. Clarify whether you are downloading, installing, and configuring drivers yourself versus using a third-party tool or installer.

I
Ion23
Member
170
01-20-2023, 01:17 AM
#3
The system has been running for over six months. The hardware specifications are as follows: an Intel NUC 13 Extreme (Intel Core i9-13900K), a standard PSU FSP750-27SCB delivering 750W, a Gigabyte GeForce RTX 4060 Ti OC 8G4, a Samsung 990 Pro M2 1TB. I have tested both RAM options to eliminate any memory-related problems: two units of Silicon Power 32GB SP032GBSVU480F02 at 4800MHz CL40 DDR5 SODIMM and two units of Crucial 32GB CT32G48C40S5 at 4800MHz SODIMM DDR5. Despite these efforts, I have endured crashes for the past six months and have only recently focused on proper troubleshooting. The current setup was built from scratch using a freshly created Windows 11 installation USB drive. For most of the incidents, the system reports the error code 19c, indicating a reboot triggered by a bugcheck. A dump was saved at C:\Windows\MEMORY.DMP with Report ID 43c05fb3-eca0-4114-91a7-8106dfc6fd51. Additionally, I have observed similar issues occurring twice in the past two to three days: another bugcheck reboot with Report ID 42f02b20-afde-445b-a4a4-0f7d6963b50f and a corresponding dump at C:\Windows\MEMORY.DMP. I manually download and install drivers, attempted removal of both Intel and nVidia drivers using DDU, and reinstalled them. Recently, I disabled the Intel GPU and found that the system remained stable during sleep or wake cycles—except during the 9f bugcheck events.
I
Ion23
01-20-2023, 01:17 AM #3

The system has been running for over six months. The hardware specifications are as follows: an Intel NUC 13 Extreme (Intel Core i9-13900K), a standard PSU FSP750-27SCB delivering 750W, a Gigabyte GeForce RTX 4060 Ti OC 8G4, a Samsung 990 Pro M2 1TB. I have tested both RAM options to eliminate any memory-related problems: two units of Silicon Power 32GB SP032GBSVU480F02 at 4800MHz CL40 DDR5 SODIMM and two units of Crucial 32GB CT32G48C40S5 at 4800MHz SODIMM DDR5. Despite these efforts, I have endured crashes for the past six months and have only recently focused on proper troubleshooting. The current setup was built from scratch using a freshly created Windows 11 installation USB drive. For most of the incidents, the system reports the error code 19c, indicating a reboot triggered by a bugcheck. A dump was saved at C:\Windows\MEMORY.DMP with Report ID 43c05fb3-eca0-4114-91a7-8106dfc6fd51. Additionally, I have observed similar issues occurring twice in the past two to three days: another bugcheck reboot with Report ID 42f02b20-afde-445b-a4a4-0f7d6963b50f and a corresponding dump at C:\Windows\MEMORY.DMP. I manually download and install drivers, attempted removal of both Intel and nVidia drivers using DDU, and reinstalled them. Recently, I disabled the Intel GPU and found that the system remained stable during sleep or wake cycles—except during the 9f bugcheck events.

U
UberSean
Member
64
01-20-2023, 04:32 AM
#4
The system crashed this morning around the time when I woke it up.
Here's the message from reliability history:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000019c (0x0000000000000050, 0xffff9d8d2d11c080, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: ac3ace32-cba4-4769-a760-8353df687140.
Hee's the logs from Memory Dump:
4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
WIN32K_POWER_WATCHDOG_TIMEOUT (19c)
Win32k did not turn the monitor on in a timely manner.
Arguments:
Arg1: 0000000000000050, Calling monitor driver to power on.
Arg2: ffff9d8d2d11c080, Pointer to the power request worker thread.
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
------------------
Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_dispsig.inf_amd64_1b8f9115c198ff0c\nvlddmkm.sys, Win32 error 0n2
Page 180402 not present in the dump file. Type ".hh dbgerr004" for details
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 1546
Key : Analysis.Elapsed.mSec
Value: 4802
Key : Analysis.IO.Other.Mb
Value: 0
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 0
Key : Analysis.Init.CPU.mSec
Value: 265
Key : Analysis.Init.Elapsed.mSec
Value: 3817
Key : Analysis.Memory.CommitPeak.Mb
Value: 128
Key : Bugcheck.Code.KiBugCheckData
Value: 0x19c
Key : Bugcheck.Code.LegacyAPI
Value: 0x19c
Key : Dump.Attributes.AsUlong
Value: 1800
Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1
Key : Dump.Attributes.ErrorCode
Value: 0
Key : Dump.Attributes.LastLine
Value: Dump completed successfully.
Key : Dump.Attributes.ProgressPercentage
Value: 100
Key : Failure.Bucket
Value: 0x19C_DRVSETMONITORPOWERSTATE_HANG_nvlddmkm!unknown_function
Key : Failure.Hash
Value: {830d81bf-fada-74e3-80d9-75aa3363ba13}
Key : Hypervisor.Enlightenments.ValueHex
Value: 1417df84
Key : Hypervisor.Flags.AnyHypervisorPresent
Value: 1
Key : Hypervisor.Flags.ApicEnlightened
Value: 0
Key : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 1
Key : Hypervisor.Flags.AsyncMemoryHint
Value: 0
Key : Hypervisor.Flags.CoreSchedulerRequested
Value: 0
Key : Hypervisor.Flags.CpuManager
Value: 1
Key : Hypervisor.Flags.DeprecateAutoEoi
Value: 1
Key : Hypervisor.Flags.DynamicCpuDisabled
Value: 1
Key : Hypervisor.Flags.Epf
Value: 0
Key : Hypervisor.Flags.ExtendedProcessorMasks
Value: 1
Key : Hypervisor.Flags.HardwareMbecAvailable
Value: 1
Key : Hypervisor.Flags.MaxBankNumber
Value: 0
Key : Hypervisor.Flags.MemoryZeroingControl
Value: 0
Key : Hypervisor.Flags.NoExtendedRangeFlush
Value: 0
Key : Hypervisor.Flags.NoNonArchCoreSharing
Value: 1
Key : Hypervisor.Flags.Phase0InitDone
Value: 1
Key : Hypervisor.Flags.PowerSchedulerQos
Value: 0
Key : Hypervisor.Flags.RootScheduler
Value: 0
Key : Hypervisor.Flags.SynicAvailable
Value: 1
Key : Hypervisor.Flags.UseQpcBias
Value: 0
Key : Hypervisor.Flags.Value
Value: 21631230
Key : Hypervisor.Flags.ValueHex
Value: 14a10fe
Key : Hypervisor.Flags.VpAssistPage
Value: 1
Key : Hypervisor.Flags.VsmAvailable
Value: 1
Key : Hypervisor.RootFlags.AccessStats
Value: 1
Key : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 1
Key : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 1
Key : Hypervisor.RootFlags.DisableHyperthreading
Value: 0
Key : Hypervisor.RootFlags.HostTimelineSync
Value: 1
Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0
Key : Hypervisor.RootFlags.IsHyperV
Value: 1
Key : Hypervisor.RootFlags.LivedumpEnlightened
Value: 1
Key : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 1
Key : Hypervisor.RootFlags.MceEnlightened
Value: 1
Key : Hypervisor.RootFlags.Nested
Value: 0
Key : Hypervisor.RootFlags.StartLogicalProcessor
Value: 1
Key : Hypervisor.RootFlags.Value
Value: 1015
Key : Hypervisor.RootFlags.ValueHex
Value: 3f7
Key : SecureKernel.HalpHvciEnabled
Value: 1
Key : WER.OS.Branch
Value: ni_release
Key : WER.OS.Version
Value: 10.0.22621.1
BUGCHECK_CODE: 19c
BUGCHECK_P1: 50
BUGCHECK_P2: ffff9d8d2d11c080
BUGCHECK_P3: 0
BUGCHECK_P4: 0
FILE_IN_CAB: MEMORY.DMP
TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b
DUMP_FILE_ATTRIBUTES: 0x1800
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
PROCESS_NAME: csrss.exe
FAULTING_THREAD: ffff9d8d2d11c080
STACK_TEXT:
fffffa8f`f1655eb0 fffff806`54a0eda7 : 00000000`00000000 ffffffff`fed1355a fffffa8f`f1656118 00000000`00000000 : nt!HalpTimerStallExecutionProcessor+0xf8
fffffa8f`f1655f50 fffff806`8ba594a3 : 00000000`00000000 00000000`00000000 ffff9d8d`2a50fa40 fffffa8f`f16560e8 : nt!KeStallExecutionProcessor+0x27
fffffa8f`f1655f80 fffff806`8c081b2d : 00000000`00000064 00000000`00000000 fffffa8f`f1656100 ffff9d8d`2a502000 : nvlddmkm+0xb694a3
fffffa8f`f1656060 fffff806`8c052b78 : ffff9d8d`2a502000 00000000`04010040 ffff9d8d`2a502000 ffff9d8d`2a502000 : nvlddmkm+0x1191b2d
fffffa8f`f1656180 fffff806`8c0cf7f5 : 00000000`00000001 ffffd108`ed407ae0 00000000`00000000 ffffd108`f566280a : nvlddmkm+0x1162b78
fffffa8f`f16561c0 fffff806`8c0d4f6b : 00000000`00000001 ffff9d8d`25ecb001 00000000`00000001 00000000`00000002 : nvlddmkm+0x11df7f5
fffffa8f`f1656240 fffff806`8c0d893f : fffffa8f`f1656478 00000018`00000000 00000000`00000800 00000000`00000800 : nvlddmkm+0x11e4f6b
fffffa8f`f16563e0 fffff806`8c0d8a7b : 00000000`00000003 ffffd108`f3da97f4 00001b00`00000003 00000000`00644403 : nvlddmkm+0x11e893f
fffffa8f`f1656460 fffff806`8c0af867 : 00000000`00000004 fffffa8f`f16565c0 00000000`00000004 ffff9d8d`25ecb000 : nvlddmkm+0x11e8a7b
fffffa8f`f16564c0 fffff806`8c0b0676 : 00000000`00000000 ffffd108`f3da95e0 fffffa8f`f1656b48 00000000`00000003 : nvlddmkm+0x11bf867
fffffa8f`f1656620 fffff806`8c26f22f : ffff9d8d`25ea6000 fffffa8f`f1656889 ffff9d8d`25ea6000 fffff806`00000000 : nvlddmkm+0x11c0676
fffffa8f`f1656820 fffff806`767e2d98 : fffff806`8c26f0d3 ffff9d8d`3324c820 00000000`00000000 fffffa8f`f1656b48 : nvlddmkm+0x137f22f
fffffa8f`f16568f0 fffff806`767a5ef2 : ffffd108`ac3c6320 fffffa8f`f1656b30 ffffd108`ac3c6320 00000000`00000000 : dxgkrnl!ADAPTER_DISPLAY:
😀
diSetTimingsFromVidPn+0x100
fffffa8f`f1656a30 fffff806`767ebee4 : ffffd108`ac3c6320 00000000`00000001 00000000`00000001 ffff9d8d`27ec1920 : dxgkrnl!VIDPN_MGR::SetTimingsFromVidPn+0x38e
fffffa8f`f1656c90 fffff806`767f0571 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff806`7662aeb2 : dxgkrnl!VIDPN_MGR:
😛
owerOnOffVidPnTarget+0x1a0
fffffa8f`f1656e60 fffff806`767f09f6 : 00000000`00000002 fffffa8f`f1656fa9 ffff9d8d`23897cd8 ffffd108`ac34adb0 : dxgkrnl!VIDPN_MGR::_MonitorEventHandler+0x3f1
fffffa8f`f1656ed0 fffff806`767ee419 : 00000000`ffffffff 00000000`00000000 00000000`00000000 00000000`00000000 : dxgkrnl!MONITOR_MGR::_IssueMonitorEvent+0x316
fffffa8f`f1657000 fffff806`767df1ec : ffff9d8d`23897ca0 00000000`00000009 fffffa8f`f16570f0 ffff9d8d`23897ca0 : dxgkrnl!MONITOR_MGR::_EnableDisableMonitorInternal+0x259
fffffa8f`f1657080 fffff806`767ea69f : 00000000`00000000 ffff9d8d`276b8000 00000000`00000000 fffff806`54a6a2ec : dxgkrnl!MONITOR_MGR::_EnableDisableMonitor+0x3e0
fffffa8f`f1657120 fffff806`767ea345 : ffff9d8d`255b4100 fffffa8f`00000001 fffffa8f`f16573a0 ffff9d8d`255b4f01 : dxgkrnl!MonitorEnableDisableMonitor+0xfb
fffffa8f`f16571c0 fffff806`767a83b8 : fffffa8f`f1657370 fffff806`76610f0c 00000000`0000ffff 00000000`000000ff : dxgkrnl!DxgkPowerOnOffMonitor+0x439
fffffa8f`f16572f0 fffff806`767d7d10 : ffff9d8d`ffffffff ffff9d8d`45fde110 ffff9d8d`2aa32e80 ffff9d8d`2aa32d30 : dxgkrnl!DpiGdoDispatchInternalIoctl+0x578
fffffa8f`f16573a0 fffff806`8c37b2e0 : 00000000`c0000002 ffff9d8d`45fde1e0 00000000`00000000 00000000`c0000225 : dxgkrnl!DpiDispatchInternalIoctl+0x100
fffffa8f`f16574d0 fffff806`54aec0a5 : 00000000`c0000002 00000000`00000000 ffff9d8d`2aa32d30 fffffa8f`f16575b0 : nvlddmkm+0x148b2e0
fffffa8f`f1657510 ffff89b7`b9827b6b : 00000000`00000002 00000000`00000000 ffffd108`e2609f20 ffff89b7`b981ed9a : nt!IofCallDriver+0x55
fffffa8f`f1657550 ffff89b7`b98cf0b3 : ffffd108`e2609f20 fffffa8f`f16576f0 00000000`00000002 ffff9d8d`211893f0 : win32kbase!GreDeviceIoControlImpl+0xfb
fffffa8f`f16575f0 ffff89b7`b98cee3f : fffffa8f`f1657870 00000000`706d7447 00000000`00000001 00000000`00000000 : win32kbase!DrvSetWddmDeviceMonitorPowerState+0x253
fffffa8f`f1657740 ffff89b7`b981d0cb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32kbase!DrvSetMonitorPowerState+0x2f
fffffa8f`f1657770 ffff89b7`b981c206 : 00000000`00000000 fffffa8f`f1657889 00000000`0000000c 00000000`00000001 : win32kbase!PowerOnMonitor+0x21b
fffffa8f`f16577e0 ffff89b7`b981bdc4 : ffff9d8d`46e0c8c0 ffff9d8d`46e0c8c0 00000000`00000001 00000000`00000001 : win32kbase!xxxUserPowerEventCalloutWorker+0x33e
fffffa8f`f16578f0 ffff89b7`b9c252fd : ffff9d8d`2d11c080 00000000`00000000 00000000`00000020 fffff806`54f3f5de : win32kbase!xxxUserPowerCalloutWorker+0x264
fffffa8f`f16579c0 ffff89b7`ba1d6ed6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32kfull!NtUserUserPowerCalloutWorker+0x1d
fffffa8f`f16579f0 fffff806`54c2bbe5 : fffffa8f`f1657aa0 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!NtUserUserPowerCalloutWorker+0x16
fffffa8f`f1657a20 00007ffe`d963c8f4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
00000099`03cbfda8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`d963c8f4
SYMBOL_NAME: nvlddmkm+b694a3
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
STACK_COMMAND: .process /r /p 0xffff9d8d2cd9e140; .thread 0xffff9d8d2d11c080 ; kb
BUCKET_ID_FUNC_OFFSET: b694a3
FAILURE_BUCKET_ID: 0x19C_DRVSETMONITORPOWERSTATE_HANG_nvlddmkm!unknown_function
OS_VERSION: 10.0.22621.1
BUILDLAB_STR: ni_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {830d81bf-fada-74e3-80d9-75aa3363ba13}
Followup: MachineOwner
---------
Any suggestions on a possible cause / fix?
I have collected the logs using V2 log collector and can post it up if that helps.
U
UberSean
01-20-2023, 04:32 AM #4

The system crashed this morning around the time when I woke it up.
Here's the message from reliability history:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000019c (0x0000000000000050, 0xffff9d8d2d11c080, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: ac3ace32-cba4-4769-a760-8353df687140.
Hee's the logs from Memory Dump:
4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
WIN32K_POWER_WATCHDOG_TIMEOUT (19c)
Win32k did not turn the monitor on in a timely manner.
Arguments:
Arg1: 0000000000000050, Calling monitor driver to power on.
Arg2: ffff9d8d2d11c080, Pointer to the power request worker thread.
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
------------------
Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_dispsig.inf_amd64_1b8f9115c198ff0c\nvlddmkm.sys, Win32 error 0n2
Page 180402 not present in the dump file. Type ".hh dbgerr004" for details
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 1546
Key : Analysis.Elapsed.mSec
Value: 4802
Key : Analysis.IO.Other.Mb
Value: 0
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 0
Key : Analysis.Init.CPU.mSec
Value: 265
Key : Analysis.Init.Elapsed.mSec
Value: 3817
Key : Analysis.Memory.CommitPeak.Mb
Value: 128
Key : Bugcheck.Code.KiBugCheckData
Value: 0x19c
Key : Bugcheck.Code.LegacyAPI
Value: 0x19c
Key : Dump.Attributes.AsUlong
Value: 1800
Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1
Key : Dump.Attributes.ErrorCode
Value: 0
Key : Dump.Attributes.LastLine
Value: Dump completed successfully.
Key : Dump.Attributes.ProgressPercentage
Value: 100
Key : Failure.Bucket
Value: 0x19C_DRVSETMONITORPOWERSTATE_HANG_nvlddmkm!unknown_function
Key : Failure.Hash
Value: {830d81bf-fada-74e3-80d9-75aa3363ba13}
Key : Hypervisor.Enlightenments.ValueHex
Value: 1417df84
Key : Hypervisor.Flags.AnyHypervisorPresent
Value: 1
Key : Hypervisor.Flags.ApicEnlightened
Value: 0
Key : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 1
Key : Hypervisor.Flags.AsyncMemoryHint
Value: 0
Key : Hypervisor.Flags.CoreSchedulerRequested
Value: 0
Key : Hypervisor.Flags.CpuManager
Value: 1
Key : Hypervisor.Flags.DeprecateAutoEoi
Value: 1
Key : Hypervisor.Flags.DynamicCpuDisabled
Value: 1
Key : Hypervisor.Flags.Epf
Value: 0
Key : Hypervisor.Flags.ExtendedProcessorMasks
Value: 1
Key : Hypervisor.Flags.HardwareMbecAvailable
Value: 1
Key : Hypervisor.Flags.MaxBankNumber
Value: 0
Key : Hypervisor.Flags.MemoryZeroingControl
Value: 0
Key : Hypervisor.Flags.NoExtendedRangeFlush
Value: 0
Key : Hypervisor.Flags.NoNonArchCoreSharing
Value: 1
Key : Hypervisor.Flags.Phase0InitDone
Value: 1
Key : Hypervisor.Flags.PowerSchedulerQos
Value: 0
Key : Hypervisor.Flags.RootScheduler
Value: 0
Key : Hypervisor.Flags.SynicAvailable
Value: 1
Key : Hypervisor.Flags.UseQpcBias
Value: 0
Key : Hypervisor.Flags.Value
Value: 21631230
Key : Hypervisor.Flags.ValueHex
Value: 14a10fe
Key : Hypervisor.Flags.VpAssistPage
Value: 1
Key : Hypervisor.Flags.VsmAvailable
Value: 1
Key : Hypervisor.RootFlags.AccessStats
Value: 1
Key : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 1
Key : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 1
Key : Hypervisor.RootFlags.DisableHyperthreading
Value: 0
Key : Hypervisor.RootFlags.HostTimelineSync
Value: 1
Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0
Key : Hypervisor.RootFlags.IsHyperV
Value: 1
Key : Hypervisor.RootFlags.LivedumpEnlightened
Value: 1
Key : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 1
Key : Hypervisor.RootFlags.MceEnlightened
Value: 1
Key : Hypervisor.RootFlags.Nested
Value: 0
Key : Hypervisor.RootFlags.StartLogicalProcessor
Value: 1
Key : Hypervisor.RootFlags.Value
Value: 1015
Key : Hypervisor.RootFlags.ValueHex
Value: 3f7
Key : SecureKernel.HalpHvciEnabled
Value: 1
Key : WER.OS.Branch
Value: ni_release
Key : WER.OS.Version
Value: 10.0.22621.1
BUGCHECK_CODE: 19c
BUGCHECK_P1: 50
BUGCHECK_P2: ffff9d8d2d11c080
BUGCHECK_P3: 0
BUGCHECK_P4: 0
FILE_IN_CAB: MEMORY.DMP
TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b
DUMP_FILE_ATTRIBUTES: 0x1800
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
PROCESS_NAME: csrss.exe
FAULTING_THREAD: ffff9d8d2d11c080
STACK_TEXT:
fffffa8f`f1655eb0 fffff806`54a0eda7 : 00000000`00000000 ffffffff`fed1355a fffffa8f`f1656118 00000000`00000000 : nt!HalpTimerStallExecutionProcessor+0xf8
fffffa8f`f1655f50 fffff806`8ba594a3 : 00000000`00000000 00000000`00000000 ffff9d8d`2a50fa40 fffffa8f`f16560e8 : nt!KeStallExecutionProcessor+0x27
fffffa8f`f1655f80 fffff806`8c081b2d : 00000000`00000064 00000000`00000000 fffffa8f`f1656100 ffff9d8d`2a502000 : nvlddmkm+0xb694a3
fffffa8f`f1656060 fffff806`8c052b78 : ffff9d8d`2a502000 00000000`04010040 ffff9d8d`2a502000 ffff9d8d`2a502000 : nvlddmkm+0x1191b2d
fffffa8f`f1656180 fffff806`8c0cf7f5 : 00000000`00000001 ffffd108`ed407ae0 00000000`00000000 ffffd108`f566280a : nvlddmkm+0x1162b78
fffffa8f`f16561c0 fffff806`8c0d4f6b : 00000000`00000001 ffff9d8d`25ecb001 00000000`00000001 00000000`00000002 : nvlddmkm+0x11df7f5
fffffa8f`f1656240 fffff806`8c0d893f : fffffa8f`f1656478 00000018`00000000 00000000`00000800 00000000`00000800 : nvlddmkm+0x11e4f6b
fffffa8f`f16563e0 fffff806`8c0d8a7b : 00000000`00000003 ffffd108`f3da97f4 00001b00`00000003 00000000`00644403 : nvlddmkm+0x11e893f
fffffa8f`f1656460 fffff806`8c0af867 : 00000000`00000004 fffffa8f`f16565c0 00000000`00000004 ffff9d8d`25ecb000 : nvlddmkm+0x11e8a7b
fffffa8f`f16564c0 fffff806`8c0b0676 : 00000000`00000000 ffffd108`f3da95e0 fffffa8f`f1656b48 00000000`00000003 : nvlddmkm+0x11bf867
fffffa8f`f1656620 fffff806`8c26f22f : ffff9d8d`25ea6000 fffffa8f`f1656889 ffff9d8d`25ea6000 fffff806`00000000 : nvlddmkm+0x11c0676
fffffa8f`f1656820 fffff806`767e2d98 : fffff806`8c26f0d3 ffff9d8d`3324c820 00000000`00000000 fffffa8f`f1656b48 : nvlddmkm+0x137f22f
fffffa8f`f16568f0 fffff806`767a5ef2 : ffffd108`ac3c6320 fffffa8f`f1656b30 ffffd108`ac3c6320 00000000`00000000 : dxgkrnl!ADAPTER_DISPLAY:
😀
diSetTimingsFromVidPn+0x100
fffffa8f`f1656a30 fffff806`767ebee4 : ffffd108`ac3c6320 00000000`00000001 00000000`00000001 ffff9d8d`27ec1920 : dxgkrnl!VIDPN_MGR::SetTimingsFromVidPn+0x38e
fffffa8f`f1656c90 fffff806`767f0571 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff806`7662aeb2 : dxgkrnl!VIDPN_MGR:
😛
owerOnOffVidPnTarget+0x1a0
fffffa8f`f1656e60 fffff806`767f09f6 : 00000000`00000002 fffffa8f`f1656fa9 ffff9d8d`23897cd8 ffffd108`ac34adb0 : dxgkrnl!VIDPN_MGR::_MonitorEventHandler+0x3f1
fffffa8f`f1656ed0 fffff806`767ee419 : 00000000`ffffffff 00000000`00000000 00000000`00000000 00000000`00000000 : dxgkrnl!MONITOR_MGR::_IssueMonitorEvent+0x316
fffffa8f`f1657000 fffff806`767df1ec : ffff9d8d`23897ca0 00000000`00000009 fffffa8f`f16570f0 ffff9d8d`23897ca0 : dxgkrnl!MONITOR_MGR::_EnableDisableMonitorInternal+0x259
fffffa8f`f1657080 fffff806`767ea69f : 00000000`00000000 ffff9d8d`276b8000 00000000`00000000 fffff806`54a6a2ec : dxgkrnl!MONITOR_MGR::_EnableDisableMonitor+0x3e0
fffffa8f`f1657120 fffff806`767ea345 : ffff9d8d`255b4100 fffffa8f`00000001 fffffa8f`f16573a0 ffff9d8d`255b4f01 : dxgkrnl!MonitorEnableDisableMonitor+0xfb
fffffa8f`f16571c0 fffff806`767a83b8 : fffffa8f`f1657370 fffff806`76610f0c 00000000`0000ffff 00000000`000000ff : dxgkrnl!DxgkPowerOnOffMonitor+0x439
fffffa8f`f16572f0 fffff806`767d7d10 : ffff9d8d`ffffffff ffff9d8d`45fde110 ffff9d8d`2aa32e80 ffff9d8d`2aa32d30 : dxgkrnl!DpiGdoDispatchInternalIoctl+0x578
fffffa8f`f16573a0 fffff806`8c37b2e0 : 00000000`c0000002 ffff9d8d`45fde1e0 00000000`00000000 00000000`c0000225 : dxgkrnl!DpiDispatchInternalIoctl+0x100
fffffa8f`f16574d0 fffff806`54aec0a5 : 00000000`c0000002 00000000`00000000 ffff9d8d`2aa32d30 fffffa8f`f16575b0 : nvlddmkm+0x148b2e0
fffffa8f`f1657510 ffff89b7`b9827b6b : 00000000`00000002 00000000`00000000 ffffd108`e2609f20 ffff89b7`b981ed9a : nt!IofCallDriver+0x55
fffffa8f`f1657550 ffff89b7`b98cf0b3 : ffffd108`e2609f20 fffffa8f`f16576f0 00000000`00000002 ffff9d8d`211893f0 : win32kbase!GreDeviceIoControlImpl+0xfb
fffffa8f`f16575f0 ffff89b7`b98cee3f : fffffa8f`f1657870 00000000`706d7447 00000000`00000001 00000000`00000000 : win32kbase!DrvSetWddmDeviceMonitorPowerState+0x253
fffffa8f`f1657740 ffff89b7`b981d0cb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32kbase!DrvSetMonitorPowerState+0x2f
fffffa8f`f1657770 ffff89b7`b981c206 : 00000000`00000000 fffffa8f`f1657889 00000000`0000000c 00000000`00000001 : win32kbase!PowerOnMonitor+0x21b
fffffa8f`f16577e0 ffff89b7`b981bdc4 : ffff9d8d`46e0c8c0 ffff9d8d`46e0c8c0 00000000`00000001 00000000`00000001 : win32kbase!xxxUserPowerEventCalloutWorker+0x33e
fffffa8f`f16578f0 ffff89b7`b9c252fd : ffff9d8d`2d11c080 00000000`00000000 00000000`00000020 fffff806`54f3f5de : win32kbase!xxxUserPowerCalloutWorker+0x264
fffffa8f`f16579c0 ffff89b7`ba1d6ed6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32kfull!NtUserUserPowerCalloutWorker+0x1d
fffffa8f`f16579f0 fffff806`54c2bbe5 : fffffa8f`f1657aa0 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!NtUserUserPowerCalloutWorker+0x16
fffffa8f`f1657a20 00007ffe`d963c8f4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
00000099`03cbfda8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`d963c8f4
SYMBOL_NAME: nvlddmkm+b694a3
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
STACK_COMMAND: .process /r /p 0xffff9d8d2cd9e140; .thread 0xffff9d8d2d11c080 ; kb
BUCKET_ID_FUNC_OFFSET: b694a3
FAILURE_BUCKET_ID: 0x19C_DRVSETMONITORPOWERSTATE_HANG_nvlddmkm!unknown_function
OS_VERSION: 10.0.22621.1
BUILDLAB_STR: ni_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {830d81bf-fada-74e3-80d9-75aa3363ba13}
Followup: MachineOwner
---------
Any suggestions on a possible cause / fix?
I have collected the logs using V2 log collector and can post it up if that helps.