Crashed last night with different keyboard in different port. From the minidump:
DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
DISPATCH_LEVEL or above.
Arg2: 0000000000001e00, The watchdog period (in ticks).
Arg3: fffff807cedc33a0, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding the cumulative timeout
Arg4: 0000000000000000
near the bottom:
SYMBOL_NAME: ftser2k+3aa6
MODULE_NAME: ftser2k
IMAGE_NAME: ftser2k.sys
STACK_COMMAND: .process /r /p 0xffffe38f6a559040; .thread 0xffffe38f8358e040 ; kb
BUCKET_ID_FUNC_OFFSET: 3aa6
FAILURE_BUCKET_ID: 0x133_ISR_ftser2k!unknown_function
These crashes appear to happen when I have not interacted with the computer for a few hours, but can go for a week without crashing just to make things difficult.
Researching ftser2k.sys it appears to be the driver for the chip to run a COM port from USB. I found it in Device Manager under Ports - USB Serial Port (COM3). Since I don't use the serial port, thinking of Disabling it to see if that solves the problem. If so, then this is maybe a motherboard hardware issue?
Thoughts?
