[SOLVED] A Curious Conundrum

[Motornerve]

Entire system locks up when idle, some time after the screens time out (displays power off).

Sometimes it takes hours after powering on the computer, sometimes a whole day.

Never occurs when using the computer, only when away from the computer.

I have 3 identical LG 27GL650F-B Monitors, connected to the Display Ports of my Gigabyte RTX 3080

Sometimes when I have to hard shut down the computer when this lock up occurs, when I power the computer on again the windows logon screen has a RED tint to it, and it locks up at the logon screen.

Not sure the exact time the issue started, but I believe there was a Windows update. It was also around the time I switched from 4 screens to 3, and ditched two older HDMI displays for one additional Displayport display.

System has run fine through multiple Windows updates and small hardware upgrades. 14 months with no issue.

• Windows Memory Diagnostics found no errors
• Reinstalled windows
• Reset BIOS to defaults
• Bios is latest version
• Drivers are updated
• Norton is installed, has been since before the problems started, system is virus free.

Spoiler: Stack Text of Manually Initiated Memory Dump while Frozen

STACK_TEXT:
fffff8076d26dcf8 fffff80785db4170 : 00000000000000e2 0000000000000000 0000000000000000 0000000000000000 : nt!KeBugCheckEx
fffff8076d26dd00 fffff80785db3a7f : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : kbdhid!KbdHidProcessCrashDump+0x1f0
fffff8076d26dd40 fffff80785d94cad : ffff8482fa4247e0 ffff8482f8ea4dbc 0000000000000000 fffff80785d98110 : kbdhid!KbdHid_InsertCodesIntoQueue+0xbf
fffff8076d26dda0 fffff80785d94e0a : 00000000000000c6 0000000000000000 0000000000000000 0000000000000000 : HIDPARSE!HidP_KbdPutKey+0x45
fffff8076d26ddd0 fffff80785d94f88 : ffff8482f8ea4dbc 000000000000000e 0000000000000000 0000000000000000 : HIDPARSE!HidP_ModifierCode+0x9a
fffff8076d26de00 fffff80785d95083 : ffff8482f8ea4e88 ffff8482fa435050 ffff8482fa435050 fffff80785d93dca : HIDPARSE!HidP_TranslateUsage+0x8c
fffff8076d26de50 fffff80785db37af : 0000000000000000 ffff8482fa435050 ffff8482fa4247e0 0000000000000000 : HIDPARSE!HidP_TranslateUsageAndPagesToI8042ScanCodes+0xb3
fffff8076d26dec0 fffff807691549a6 : 0000000000000000 ffff848308aeb202 ffff848200000000 fffff80782cb8401 : kbdhid!KbdHid_ReadComplete+0x43f
fffff8076d26df50 fffff8076908508e : ffff8482fa435050 fffff8076d26e009 0000000000000000 ffff8482fa4355eb : nt!IopUnloadSafeCompletion+0x56
fffff8076d26df80 fffff80769084f57 : 0000000000000000 ffff8482fa2f2506 ffff8482fa7b5f30 0000000000000000 : nt!IopfCompleteRequest+0x11e
fffff8076d26e070 fffff80785d5aef5 : ffff8482fcc35ec8 ffff8482fa335202 0000000000000000 0000000000000009 : nt!IofCompleteRequest+0x17
fffff8076d26e0a0 fffff80785d5a7ed : ffff8482fa335210 ffff8482fa335202 ffff8482fa335210 0000000000000009 : HIDCLASS!HidpDistributeInterruptReport+0x3f5
fffff8076d26e1a0 fffff8076908508e : ffff8482fa5135a0 ffff8482fa5135a0 fffff8076d26e201 ffff8482fa513a1b : HIDCLASS!HidpInterruptReadComplete+0x37d
fffff8076d26e240 fffff80769084f57 : 0000000000000001 0000000000000000 ffff8482fa49b630 0000000000000002 : nt!IopfCompleteRequest+0x11e
fffff8076d26e330 fffff8076b9a811a : 0000000000000000 ffff8482f85fcba0 ffff8482fa5135a0 fffff8076d26e410 : nt!IofCompleteRequest+0x17
fffff8076d26e360 fffff8076b9a5bbf : ffff84830076ba02 ffff8482fa479050 ffff8482fa5135a0 0000000000000000 : Wdf01000!FxRequest::CompleteInternal+0x23a [minkernel\wdf\framework\shared\core\fxrequest.cpp @ 869]
fffff8076d26e3f0 fffff8078280bdbd : 00000000ffffff02 ffff84830076b8b0 ffff8482fa49ba10 ffff8482fa49ba10 : Wdf01000!imp_WdfRequestComplete+0x8f [minkernel\wdf\framework\shared\core\fxrequestapi.cpp @ 436]
fffff8076d26e450 fffff8078280bc81 : ffff84830076ba50 0000000000000008 ffff84830076bae0 fffff8076d26e668 : USBXHCI!Bulk_Transfer_CompleteCancelable+0xc9
fffff8076d26e4b0 fffff8078280ba70 : 0000000000000004 fffff8076d26e620 0000000000000000 ffff8482fa49b090 : USBXHCI!Bulk_ProcessTransferEventWithED1+0x1fd
fffff8076d26e560 fffff80782806cc1 : 0000000000000004 fffff8076d26e638 0000000000000008 fffff8076d26e640 : USBXHCI!Bulk_EP_TransferEventHandler+0x10
fffff8076d26e590 fffff807828067f5 : 0000000000000780 00007b7d07918400 ffff8482f8f6f3a0 ffff8482fa761940 : USBXHCI!Endpoint_TransferEventHandler+0xb1
fffff8076d26e5f0 fffff807828064cc : ffff8482f8f7c318 fffff80764d73180 00007b7d07918fd8 fffff8076d26e710 : USBXHCI!Interrupter_DeferredWorkProcessor+0x315
fffff8076d26e6f0 fffff8076b9a38f6 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : USBXHCI!Interrupter_WdfEvtInterruptDpc+0xc
fffff8076d26e720 fffff8076909a3be : fffff80764d76240 0000000000000000 fffff8076d26ea20 fffff80764d73180 : Wdf01000!FxInterrupt::_InterruptDpcThunk+0xa6 [minkernel\wdf\framework\shared\irphandlers\pnp\km\interruptobjectkm.cpp @ 410]
fffff8076d26e760 fffff807690996a4 : 0000000000000000 0000000000000000 0000000000140001 0000000000000000 : nt!KiExecuteAllDpcs+0x30e
fffff8076d26e8d0 fffff807691faa8e : 0000000000000000 fffff80764d73180 fffff80769b26a00 ffff8482fcdb6080 : nt!KiRetireDpcList+0x1f4
fffff8076d26eb60 0000000000000000 : fffff8076d26f000 fffff8076d268000 0000000000000000 0000000000000000 : nt!KiIdleLoop+0x9e

 

[Motornerve]

Alright, through the following testing I still don't know what it is, but I know what it ISN'T

I have a set of 3 LG 27GL650F-B monitors (the NEW monitors) and a set of 2 BenQ GL2760H monitors (the OLD monitors).
Some notable differences:
Refresh rates - NEW 144hz | OLD 60hz
Connection - NEW Display/HDMI | OLD: HDMI/DVI

I have tried all NEW DisplayPort cables with the NEW monitors - FREEZE
I have tried each NEW monitor by itself in each of the 3 display ports available in my graphics card - FREEZE
I have tried each NEW monitor with an HDMI and the other 2 with a DisplayPort connection in all of my various ports on the graphics card - FREEZE
I have tried the OLD monitors with HDMI out from the monitor to an HDMI in on the graphics card, and a DisplayPort in (with an adapter) on the graphics card, and tried all combinations of the ports - NO FREEZE

It would seem by general elimination that there is something wrong with the DisplayPort protocol or drivers? Any insight? I do not know enough about the intricacies of DisplayPort technology to troubleshoot this with the information I have.

 

[Colif]

I connected my monitor through HDMI and DP Too, DP wasn't detected at all... I went to Nvidia Control Panel - Global Settings - Image Sharpening - And from OFF, changed to ON (whatever it was in the settings window) And VOILA! The DP turned on! Now every port works fine. I hope it helps. I googled this for a few months without success. Then somehow I remembered that nvidia uses upscaling/image "improvements" and I got lucky with this one. So it's the NVIDIA driver !!!

https://www.nvidia.com/en-us/geforce/forums/geforce-graphics-cards/5/334078/display-port-not-working/

if that doesn't help I would ask on the Nvidia forums as its likely the card or drivers at this point.

 

[Motornerve]

Yeah I double checked, and the Image Sharpening is off, I will check a few more settings, but if that doesn't work, I think I will just downgrade to HDMI 2.1, and still get some screaming resolutions.

 

[Colif]

Its unusual, that is for sure.