New
#11
Even though it's a new driver the asmthub3 is still being called out as the problem. You may have to consider removing or replacing the device if that is possible.
Code:0: kd> !irp fffffa8010d29700 Irp is active with 8 stacks 6 is current (= 0xfffffa8010d29938) No Mdl: No System Buffer: Thread 00000000: Irp stack trace. cmd flg cl Device File Completion-Context [N/A(0), N/A(0)] 0 0 00000000 00000000 00000000-00000000 Args: 00000000 00000000 00000000 00000000 [N/A(0), N/A(0)] 0 0 00000000 00000000 00000000-00000000 Args: 00000000 00000000 00000000 00000000 [N/A(0), N/A(0)] 0 0 00000000 00000000 00000000-00000000 Args: 00000000 00000000 00000000 00000000 [N/A(0), N/A(0)] 0 0 00000000 00000000 00000000-00000000 Args: 00000000 00000000 00000000 00000000 [N/A(0), N/A(0)] 0 0 00000000 00000000 00000000-00000000 Args: 00000000 00000000 00000000 00000000 >[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)] 0 e1 fffffa800e7d8c70 00000000 fffff88004bd1b70-00000000 Success Error Cancel pending \Driver\asmthub3 serenum!Serenum_FDOPowerComplete Args: 00014400 00000001 00000000 00000002 [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)] 0 e1 fffffa80105b8d60 00000000 00000000-00000000 pending \Driver\Serenum Args: 00014400 00000001 00000000 00000002 [N/A(0), N/A(0)] 0 0 00000000 00000000 00000000-fffffa8010d87160 Args: 00000000 00000000 00000000 00000000