Share via

Blue screen with HIDCLASS

Anonymous
2024-09-19T14:43:52+00:00

Hi, I have been getting a lot of blue screens in the past few days and I have not changed anything on my system. I checked the minidump files and it seems the primary cause is the HIDCLASS.sys driver but I can't narrow down the cause of the blue screens. Can anyone help me to analyze my minidump to check if there is any other information I have missed out?

12: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an IRP for too long a time
Arg2: ffffa407ac67fdd0, Physical Device Object of the stack
Arg3: ffffb6089f6df810, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffa407ad4ac010, The blocked IRP

Debugging Details:
------------------

Implicit thread is now ffffa407`99d57080

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2859

    Key  : Analysis.Elapsed.mSec
    Value: 4835

    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: 375

    Key  : Analysis.Init.Elapsed.mSec
    Value: 2242

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 94

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27704.1001

    Key  : Analysis.Version.Description
    Value: 10.2408.27.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2408.27.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x9f

    Key  : Bugcheck.Code.TargetModel
    Value: 0x9f

    Key  : Dump.Attributes.AsUlong
    Value: 8

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Failure.Bucket
    Value: 0x9F_3_HIDCLASS!CancelAllPingPongIrps

    Key  : Failure.Hash
    Value: {4f75e063-21d8-788d-807c-6f8cb2bfd785}

BUGCHECK_CODE:  9f

BUGCHECK_P1: 3

BUGCHECK_P2: ffffa407ac67fdd0

BUGCHECK_P3: ffffb6089f6df810

BUGCHECK_P4: ffffa407ad4ac010

FILE_IN_CAB:  091924-11281-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffa40799d57080

DRVPOWERSTATE_SUBCODE:  3

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
ffffb608`9f617640 fffff803`79456390     : ffffe481`ffffffff 00000000`00000000 00000000`00000000 fffff803`7c442820 : nt!KiSwapContext+0x76
ffffb608`9f617780 fffff803`794558bf     : ffffe481`00000002 00000000`00000001 ffffb608`9f617940 00000000`00000000 : nt!KiSwapThread+0x500
ffffb608`9f617830 fffff803`79455163     : ffffa407`00000000 ffffa407`00000000 ffffa407`a1d21800 ffffa407`99d571c0 : nt!KiCommitThreadWait+0x14f
ffffb608`9f6178d0 fffff803`7def4ebe     : ffffa407`a9f0bc88 00000000`00000000 00000000`00000000 ffffb608`9f617a00 : nt!KeWaitForSingleObject+0x233
ffffb608`9f6179c0 fffff803`7def41c7     : ffffa407`ac8a01d0 00000000`00000002 ffffa407`ad4ac758 ffffa407`ad4ac010 : HIDCLASS!CancelAllPingPongIrps+0x1fe
ffffb608`9f617a20 fffff803`7def26c6     : ffffa407`ac8a01b0 00000000`00000000 00000000`00000016 fffff803`7959d1b6 : HIDCLASS!HidpFdoPower+0x247
ffffb608`9f617aa0 fffff803`7959cf89     : ffffb608`9f617bb0 ffffa407`99d57080 ffffa407`ad4ac010 ffffa407`00000000 : HIDCLASS!HidpMajorHandler+0x206
ffffb608`9f617b30 fffff803`795299a5     : 00000000`00000000 fffff803`7959cdb0 00000000`00000000 00000000`00000072 : nt!PopIrpWorker+0x1d9
ffffb608`9f617bd0 fffff803`79607358     : ffffe481`b1be4180 ffffa407`99d57080 fffff803`79529950 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffffb608`9f617c20 00000000`00000000     : ffffb608`9f618000 ffffb608`9f611000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28

SYMBOL_NAME:  HIDCLASS!CancelAllPingPongIrps+1fe

MODULE_NAME: HIDCLASS

IMAGE_NAME:  HIDCLASS.SYS

IMAGE_VERSION:  10.0.19041.4842

STACK_COMMAND:  .process /r /p 0xffffa40799c68040; .thread 0xffffa40799d57080 ; kb

BUCKET_ID_FUNC_OFFSET:  1fe

FAILURE_BUCKET_ID:  0x9F_3_HIDCLASS!CancelAllPingPongIrps

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {4f75e063-21d8-788d-807c-6f8cb2bfd785}

Followup:     MachineOwner
Windows for home | Windows 10 | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

4 answers

Sort by: Most helpful
  1. DaveM121 891.1K Reputation points Independent Advisor
    2024-09-19T15:44:34+00:00

    Thank you for that information, please uninstall any SteelSeries software and drivers installed on your PC, restart the PC, then donwload and install the latest version of the drivers they provide for your mouse on their website.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2024-09-19T15:40:00+00:00

    Hi Dave,

    No I don't use any Logitech or Corsair products. However, I DO have a steelseries mouse which should use a 3rd party driver?

    Was this answer helpful?

    0 comments No comments
  3. DaveM121 891.1K Reputation points Independent Advisor
    2024-09-19T15:18:40+00:00

    Hi, I am Dave, I will help you with this.

    All your minidump files except one do indicate that HID class driver as the cause of the crashes, usually that is caused by some 3rd party driver or software you may have installed for a keyboard or mouse, do you have anything like Logitech G-Hub or Corsair iCUE installed on your PC?

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2024-09-19T14:46:55+00:00

    Was this answer helpful?

    0 comments No comments