[SOLVED] A Curious Conundrum

Motornerve

Commendable
May 8, 2019
21
0
1,520
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.
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
 
Last edited:
Solution
freezes aren't windows style. If you not getting BSOD its unlikely to be software.

I would do the restricted build as suggested above and see if you can get a stable build and work up from there.

what type of logging? did you try HWINFO? its records shouldn't corrupt, they will just sort of end but might show something.

Ralston18

Titan
Moderator
As requested earlier: full system hardware specs and OS information.

= = = =

Look in Reliability History and Event Viewer for error codes, warnings, or even informational events that correspond with the lockups.

Look in Windows Update History for any problem updates/installs.

Temporarily disable all power and/or screen savers to determine if the lockups stop.

If not, then run "sfc /scannow" and "dism" via the Command Prompt.

References:

https://www.lifewire.com/how-to-use-sfc-scannow-to-repair-windows-system-files-2626161

Fix Windows Update errors via DISM or System Update Readiness tool - Windows Server | Microsoft Docs
 

Motornerve

Commendable
May 8, 2019
21
0
1,520
As requested earlier: full system hardware specs and OS information.

= = = =

Look in Reliability History and Event Viewer for error codes, warnings, or even informational events that correspond with the lockups.

Look in Windows Update History for any problem updates/installs.

Temporarily disable all power and/or screen savers to determine if the lockups stop.

If not, then run "sfc /scannow" and "dism" via the Command Prompt.

References:

https://www.lifewire.com/how-to-use-sfc-scannow-to-repair-windows-system-files-2626161

Fix Windows Update errors via DISM or System Update Readiness tool - Windows Server | Microsoft Docs
Full system hardware and specs, as requested, are in the DxDiag link above.
 

Motornerve

Commendable
May 8, 2019
21
0
1,520
As requested earlier: full system hardware specs and OS information.

= = = =

Look in Reliability History and Event Viewer for error codes, warnings, or even informational events that correspond with the lockups.

Look in Windows Update History for any problem updates/installs.

Temporarily disable all power and/or screen savers to determine if the lockups stop.

If not, then run "sfc /scannow" and "dism" via the Command Prompt.

References:

https://www.lifewire.com/how-to-use-sfc-scannow-to-repair-windows-system-files-2626161

Fix Windows Update errors via DISM or System Update Readiness tool - Windows Server | Microsoft Docs
sfc found no errors, and I am not sure what command line arguments I should use with DISM. I tried clicking on the reference link that starts "Fix Windows Update..." but the link is broken.
 

Motornerve

Commendable
May 8, 2019
21
0
1,520
No, they're not. Some are. You're not going to find PSU information in that file. Or the exact model of RAM.
Oh snap, my bad.

Thermaltake Toughpower iRGB Plus 1050W 80+ Platinum Digital RGB LED Smart Zero Fan SLI/Crossfire Ready ATX12V v2.4 / SSI EPS v2.92 Power Supply

Corsair Vengeance RGB Pro 64GB (4x16GB) DDR4 3200 (PC4-25600) C16 Desktop Memory - Black
 

Motornerve

Commendable
May 8, 2019
21
0
1,520
As requested earlier: full system hardware specs and OS information.

= = = =

Look in Reliability History and Event Viewer for error codes, warnings, or even informational events that correspond with the lockups.

Look in Windows Update History for any problem updates/installs.

Temporarily disable all power and/or screen savers to determine if the lockups stop.

If not, then run "sfc /scannow" and "dism" via the Command Prompt.

References:

https://www.lifewire.com/how-to-use-sfc-scannow-to-repair-windows-system-files-2626161

Fix Windows Update errors via DISM or System Update Readiness tool - Windows Server | Microsoft Docs
Also, there hasn't been any events that I could find that correlate to the lockups, other than the "Error: you hard reset your pc and we are grumpy about it" error. Also why I posted my logs here, because I am not entirely sure what I am looking for.

No trouble in the windows update history, although I did just perform a clean install, formatting the windows drive in the process.
 

Colif

Win 11 Master
Moderator
USBXHCI = USB Extemsible Host Controller
HIDCLASS! = Human Interface Device CLass... mostly used for Keybaord/Mouse/USB type devices
HIDPARSE - Hid Parsing Library files (new one to me)

those are mentioned in the dump text while PC was frozen so could be mouse/keyboard is cause?

although if you forced the error it might just be showing actions that would occur after forcing error. I don't see many forced dumps

if say it doesn't just show those actions, Apart from a Yeti X microphone, what USB do you have?
 
Last edited:

DSzymborski

Titan
Moderator
Oh snap, my bad.

Thermaltake Toughpower iRGB Plus 1050W 80+ Platinum Digital RGB LED Smart Zero Fan SLI/Crossfire Ready ATX12V v2.4 / SSI EPS v2.92 Power Supply

Corsair Vengeance RGB Pro 64GB (4x16GB) DDR4 3200 (PC4-25600) C16 Desktop Memory - Black

Thanks! Unfortunately, no obvious problems there.

I'd simplify the build, if possible, to do troubleshooting. Remove GPU and use integrated graphics. One stick of RAM. One monitor. Force the PC to go into idle and see if there is any behavior change.
 

Motornerve

Commendable
May 8, 2019
21
0
1,520
USBXHCI = USB Extemsible Host Controller
HIDCLASS! = Human Interface Device CLass... mostly used for Keybaord/Mouse/USB type devices
HIDPARSE - Hid Parsing Library files (new one to me)

those are mentioned in the dump text while PC was frozen so could be mouse/keyboard is cause?

although if you forced the error it might just be showing actions that would occur after forcing error. I don't see many forced dumps
Yeah that was my thought, since the forced dump was initiated from my USB keyboard, I think that is the case. Having a lot of trouble finding monitoring software that can do logging that doesn't get corrupted if the system locks up.
 

Colif

Win 11 Master
Moderator
freezes aren't windows style. If you not getting BSOD its unlikely to be software.

I would do the restricted build as suggested above and see if you can get a stable build and work up from there.

what type of logging? did you try HWINFO? its records shouldn't corrupt, they will just sort of end but might show something.
 
Solution

Motornerve

Commendable
May 8, 2019
21
0
1,520
freezes aren't windows style. If you not getting BSOD its unlikely to be software.

I would do the restricted build as suggested above and see if you can get a stable build and work up from there.

what type of logging? did you try HWINFO? its records shouldn't corrupt, they will just sort of end but might show something.
Alright, I have HWINFO up and logging enabled, I have a busy day today away from the computer, so I will leave it logging and see what happens. Thanks for the suggestion!
 

Motornerve

Commendable
May 8, 2019
21
0
1,520
So I have discovered that the keyboard is responsive during these freezes (as it allows me to do a manual crash dump and restart the computer). Are there any other keyboard commands other than Ctrl+Alt+Del (not working) that can do some background windows mojo and unstuck the computer?
 

Motornerve

Commendable
May 8, 2019
21
0
1,520
This time it crashed WITHOUT freezing! I don't know if this new info will be helpful.


On Sun 8/29/2021 12:07:40 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\082921-6984-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x3AD0)
Bugcheck code: 0x119 (0x2, 0xFFFFFFFFC000000D, 0xFFFFFB009725F860, 0xFFFF9A081EFDC590)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
file path: C:\WINDOWS\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video scheduler has detected a fatal violation.
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
 

Motornerve

Commendable
May 8, 2019
21
0
1,520
This time it crashed WITHOUT freezing! I don't know if this new info will be helpful.


On Sun 8/29/2021 12:07:40 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\082921-6984-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x3AD0)
Bugcheck code: 0x119 (0x2, 0xFFFFFFFFC000000D, 0xFFFFFB009725F860, 0xFFFF9A081EFDC590)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
file path: C:\WINDOWS\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video scheduler has detected a fatal violation.
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
dxgmms2.sys dxgmms2.sys+1ab0b fffff80721940000 fffff80721a21000 0x000e1000 0x6d8411e5 3/22/2028 2:04:37 PM Microsoft® Windows® Operating System DirectX Graphics MMS 10.0.19041.1151 (WinBuild.160101.0800) Microsoft Corporation C:\Windows\system32\drivers\dxgmms2.sys
watchdog.sys watchdog.sys+3ad0 fffff80720bb0000 fffff80720bc8000 0x00018000 0xf13839ab 3/29/2098 9:57:15 PM Microsoft® Windows® Operating System Watchdog Driver 10.0.19041.868 (WinBuild.160101.0800) Microsoft Corporation C:\Windows\system32\drivers\watchdog.sys
 

Colif

Win 11 Master
Moderator
watchdog.sys is also part of Nvidia drivers.

the error itself makes it obvious what cause was, GPU or drivers.

Have you run ddu in safe mode and reinstalled drivers?

I'd simplify the build, if possible, to do troubleshooting. Remove GPU and use integrated graphics. One stick of RAM. One monitor. Force the PC to go into idle and see if there is any behavior change.
you could do this, at least check if problem is GPU
 

Motornerve

Commendable
May 8, 2019
21
0
1,520
Update, I recently moved, and I switched from 3 Display port monitors to an HDMI and a HDMI out to Display Port in (using my wife's monitors as mine are not unpacked) and the freeze has not occurred in almost 5 days. Is it possible that display port cables or the display ports on my card could be bad?
 

Colif

Win 11 Master
Moderator
i don't think the brands matter, it could have just been a bad cable or connection.

only asked about GPU as older cards could get a DP update to firmware but I believe the 3k series has it built in.
slaps self as you said name of GPU in opening post.
 

Motornerve

Commendable
May 8, 2019
21
0
1,520
I will make sure that I check the cables when I set up the triple monitor set up in the new office, and I will mark that trophy for you if it turns out to be just the cables. THIS WAS DRIVING ME NUTS! Took moving to a different house and sheer coincidence to fix!