Share via

Windows11 - I need help with analyzing minidump file, related to bsods.

Anonymous
2025-03-16T02:40:45+00:00

I was getting constant BSOD errors on my pc lately, and my problem is almost exactly like in this thread ([SOLVED] Memory Management Error not fixing, PLEASE HELP). Ive also previously tried almost everything that this guy tried to fix errors including getting my pc to computer service. Nothing worked so i am now trying this. However i have no idea how to identify the correct driver or how to uninstall any driver. Here is my minidump file ive been trying to know something about. If this helps i also add analysis from WinDbg. Using windows 11.

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)

This is a very common BugCheck. Usually the exception address pinpoints

the driver/function that caused the problem. Always note this address

as well as the link date of the driver/image that contains this address.

Arguments:

Arg1: ffffffffc0000005, The exception code that was not handled

Arg2: fffff8009485e060, The address that the exception occurred at

Arg3: fffff687f0579d58, Exception Record Address

Arg4: fffff687f0579540, Context Record Address

Debugging Details:

KEY_VALUES_STRING: 1

Key  : AV.Type

Value: Read

Key  : Analysis.CPU.mSec

Value: 2328

Key  : Analysis.Elapsed.mSec

Value: 22305

Key  : Analysis.IO.Other.Mb

Value: 23

Key  : Analysis.IO.Read.Mb

Value: 1

Key  : Analysis.IO.Write.Mb

Value: 35

Key  : Analysis.Init.CPU.mSec

Value: 625

Key  : Analysis.Init.Elapsed.mSec

Value: 48417

Key  : Analysis.Memory.CommitPeak.Mb

Value: 100

Key  : Analysis.Version.DbgEng

Value: 10.0.27793.1000

Key  : Analysis.Version.Description

Value: 10.2410.02.02 amd64fre

Key  : Analysis.Version.Ext

Value: 1.2410.2.2

Key  : Bugcheck.Code.LegacyAPI

Value: 0x1000007e

Key  : Bugcheck.Code.TargetModel

Value: 0x1000007e

Key  : Dump.Attributes.AsUlong

Value: 0x21008

Key  : Dump.Attributes.DiagDataWrittenToHeader

Value: 1

Key  : Dump.Attributes.ErrorCode

Value: 0x0

Key  : Dump.Attributes.KernelGeneratedTriageDump

Value: 1

Key  : Dump.Attributes.LastLine

Value: Dump completed successfully.

Key  : Dump.Attributes.ProgressPercentage

Value: 0

Key  : Failure.Bucket

Value: AV\_HIDCLASS!HidpCallDriver

Key  : Failure.Exception.Code

Value: 0xffffffffc0000005

Key  : Failure.Exception.IP.Address

Value: 0xfffff8009485e060

Key  : Failure.Exception.IP.Module

Value: nt

Key  : Failure.Exception.IP.Offset

Value: 0x34e060

Key  : Failure.Exception.Record

Value: 0xfffff687f0579d58

Key  : Failure.Hash

Value: {09223f76-66f9-c8bc-7ce8-d669ecd11026}

BUGCHECK_CODE: 7e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8009485e060

BUGCHECK_P3: fffff687f0579d58

BUGCHECK_P4: fffff687f0579540

FILE_IN_CAB: 031625-8234-01.dmp

DUMP_FILE_ATTRIBUTES: 0x21008

Kernel Generated Triage Dump

FAULTING_THREAD: ffff80815270d040

EXCEPTION_RECORD: fffff687f0579d58 -- (.exr 0xfffff687f0579d58)

ExceptionAddress: fffff8009485e060 (nt!IopfCallDriver+0x0000000000000030)

ExceptionCode: c0000005 (Access violation)

ExceptionFlags: 00000000

NumberParameters: 2

Parameter[0]: 0000000000000000

Parameter[1]: 00000000046dc23a

Attempt to read from address 00000000046dc23a

CONTEXT: fffff687f0579540 -- (.cxr 0xfffff687f0579540)

rax=ffff808153488128 rbx=ffff808153488010 rcx=0000000000000017

rdx=ffff808153488010 rsi=00000000046dc232 rdi=0000000000000000

rip=fffff8009485e060 rsp=fffff687f0579f90 rbp=fffff8009485e0bc

r8=00000000046dc232 r9=00000000046dc232 r10=0000fffff808b032

r11=ffff82faa6a00000 r12=0000000000000000 r13=0000000000000000

r14=ffff808153488010 r15=ffff8081511d21d0

iopl=0 nv up ei pl nz na pe nc

cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050202

nt!IopfCallDriver+0x30:

fffff8009485e060 498b4008 mov rax,qword ptr [r8+8] ds:002b:00000000046dc23a=????????????????

Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

READ_ADDRESS: fffff800954d34b0: Unable to get MiVisibleState

Unable to get NonPagedPoolStart

Unable to get NonPagedPoolEnd

Unable to get PagedPoolStart

Unable to get PagedPoolEnd

unable to get nt!MmSpecialPagesInUse

00000000046dc23a

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR: c0000005

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 00000000046dc23a

EXCEPTION_STR: 0xc0000005

LOCK_ADDRESS: fffff8009549a660 -- (!locks fffff8009549a660)

Unable to get value of PsActiveProcessHead.Flink

Cannot get _ERESOURCE Flag field

Unexpected resource format: 0

1 total locks

PNP_TRIAGE_DATA: 

Lock address  : 0xfffff8009549a660

Thread Count  : 0

Thread address: 0x0000000000000000

Thread wait   : 0x0

STACK_TEXT:

fffff687f0579f90 fffff80095079ad4 : ffff8081511d2100 fffff687f057a160 0000000000000110 fffff8009479eb3a : nt!IopfCallDriver+0x30

fffff687f0579fd0 fffff8009485e49c : ffff808153488010 fffff8009506f081 0000000000000000 0000000000000000 : nt!IovCallDriver+0x44

fffff687f057a010 fffff8009485e0bc : ffffddeefe000990 ffffddeef77f0000 ffffddeef77bbf80 fffff800953477c0 : nt!IofCallDriver+0xac

fffff687f057a050 fffff80095079ad4 : fffff687f057a0d0 0000000000000000 0000000000000000 0000000000000000 : nt!IopfCallDriver+0x8c

fffff687f057a090 fffff8009485e49c : ffff808153488010 fffff808b72ee0db 0000000000000000 0000000000000000 : nt!IovCallDriver+0x44

fffff687f057a0d0 fffff8009506f081 : ffffac3e2d22e0c1 ffff808153488010 fffff808b72ee0db ffff8081529292e0 : nt!IofCallDriver+0xac

fffff687f057a110 fffff8009485e0bc : ffff808152929430 ffff808153488010 ffff8081511d21b0 fffff8009485e49c : nt!ViFilterDispatchGeneric+0xb1

fffff687f057a150 fffff80095079ad4 : fffff687f057a328 ffff8081511d23d8 ffff8081511d2060 ffff808153488010 : nt!IopfCallDriver+0x8c

fffff687f057a190 fffff8009485e49c : ffff808153488010 0000000000000017 0000000000000000 0000000000000000 : nt!IovCallDriver+0x44

fffff687f057a1d0 fffff808b72ee0db : 0026003700380064 0031003000260030 0073005c00390065 0069007300730065 : nt!IofCallDriver+0xac

fffff687f057a210 fffff808b72f4b8e : 0000000000000017 0000000000000000 ffff8081511d21d0 ffff808153488010 : HIDCLASS!HidpCallDriver+0x5b

fffff687f057a280 fffff808b731d0ee : ffff8081511d21b0 0000000000000000 0000000000000000 00000000000000ff : HIDCLASS!HidpIrpMajorDefault+0x19e

fffff687f057a300 fffff808b72e51cf : 0000000000000002 ffff8081511d21d0 ffff8081511d21b0 0000000000000000 : HIDCLASS!HidpIrpMajorSystemControl+0x8e

fffff687f057a330 fffff8009485e0bc : ffffca0216f02000 fffff80095079ad4 ffff9301000239f0 0000000000000000 : HIDCLASS!HidpMajorHandler+0x5ff

fffff687f057a400 fffff80095079ad4 : ffff808153db6d60 fffff8009485e49c ffff808153488010 fffff8009505fffd : nt!IopfCallDriver+0x8c

fffff687f057a440 fffff8009485e49c : ffff808153488010 fffff8009505fffd 00000000c00000bb 0000000000000000 : nt!IovCallDriver+0x44

fffff687f057a480 fffff8009506f081 : fffff80094789cd7 ffff808153488010 fffff8009505fffd ffff808153db6d60 : nt!IofCallDriver+0xac

fffff687f057a4c0 fffff8009485e0bc : ffff808153db6eb0 ffff808153488010 0000000000000007 0000000000000000 : nt!ViFilterDispatchGeneric+0xb1

fffff687f057a500 fffff80095079ad4 : 0000000000000005 ffff808153db6d60 0000000000000000 fffff8009506007d : nt!IopfCallDriver+0x8c

fffff687f057a540 fffff8009485e49c : ffff808153488010 ffff808153db6d60 ffff808153db6d60 0000000000000000 : nt!IovCallDriver+0x44

fffff687f057a580 fffff8009505fffd : ffff808151ea96d0 0000000000000000 ffff808151ea96d0 fffff80094721afd : nt!IofCallDriver+0xac

fffff687f057a5c0 fffff80095078164 : ffff808151ea96d0 fffff687f057a7b9 0000000000000001 fffff80094e2dd08 : nt!VfIrpSendSynchronousIrp+0x10d

fffff687f057a630 fffff800950650f4 : 0000000000000000 fffff687f057a7b9 0000000000000001 ffff808151ea96d0 : nt!VfWmiTestStartedPdoStack+0x54

fffff687f057a6d0 fffff8009498ea04 : 0000000000000000 fffff687f057a7b9 0000000000000001 0000000000000001 : nt!VfMajorTestStartedPdoStack+0x44

fffff687f057a700 fffff80094e38898 : 0000000000000000 fffff687f057a7b9 0000000000000001 fffff687f057a7b9 : nt!PpvUtilTestStartedPdoStack+0x18

fffff687f057a730 fffff80094e325e9 : ffff8081593ef7a0 0000000000000001 0000000000000000 0000000000000001 : nt!PipProcessStartPhase3+0xcc

fffff687f057a820 fffff80094f23537 : ffff80813c821c00 ffff8081599cfd90 fffff687f057a940 fffff80000000002 : nt!PipProcessDevNodeTree+0x6b1

fffff687f057a8f0 fffff800949465cd : 0000000100000003 ffff80813c821c00 ffff8081599cfd90 0000000000000000 : nt!PiProcessReenumeration+0x9f

fffff687f057a940 fffff80094827b02 : ffff80815270d040 ffff80813c7c0ca0 fffff80094945f90 ffff808100000000 : nt!PnpDeviceActionWorker+0x63d

fffff687f057aa00 fffff8009495fd8a : ffff80815270d040 ffff80815270d040 fffff80094827950 ffff80813c7c0ca0 : nt!ExpWorkerThread+0x1b2

fffff687f057abb0 fffff80094b8a024 : ffff9301f23d1180 ffff80815270d040 fffff8009495fd30 0000000000000246 : nt!PspSystemThreadStartup+0x5a

fffff687f057ac00 0000000000000000 : fffff687f057b000 fffff687f0574000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x34

SYMBOL_NAME: HIDCLASS!HidpCallDriver+5b

MODULE_NAME: HIDCLASS

IMAGE_NAME: HIDCLASS.SYS

IMAGE_VERSION: 10.0.26100.1882

STACK_COMMAND: .cxr 0xfffff687f0579540 ; kb

BUCKET_ID_FUNC_OFFSET: 5b

FAILURE_BUCKET_ID: AV_HIDCLASS!HidpCallDriver

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {09223f76-66f9-c8bc-7ce8-d669ecd11026}

Followup: MachineOwner

Windows for home | Windows 10 | Performance and system failures

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

5 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. _AW_ 67,676 Reputation points Volunteer Moderator
    2025-03-16T21:39:52+00:00

    Upload all new minidumps, including when G Hub was removed.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2025-03-16T14:48:01+00:00

    so i tried it after just uninstalling ghub and all the drivers. Ran the command and the program returned nothing. Still bsod error. I tried it after reinstalling a g hub software and again, bsod error.

    Was this answer helpful?

    0 comments
  3. _AW_ 67,676 Reputation points Volunteer Moderator
    2025-03-16T14:25:23+00:00

    If you're using G Hub see if there's any update for it.

    If not, uninstall G Hub, then check in C:\Windows\System32\Drivers for any logi_*.sys drivers,

    or

    open Windows Powershell, then run this command:

    gci C:\Windows\System32\Drivers\logi*.sys| fl FullName

    If any logi* drivers remain, run Autoruns64.exe as admin.

    Enter logi into the quick filter and uncheck the entries found, then reboot.

    https://learn.microsoft.com/en-us/sysinternals/downloads/autoruns

    Was this answer helpful?

    0 comments
  4. Anonymous
    2025-03-16T13:42:02+00:00

    logitech g213 keyboard and a logitech g502 hero mouse. Can you tell

    me how to uninstall the faulty driver?

    Was this answer helpful?

    0 comments
  5. _AW_ 67,676 Reputation points Volunteer Moderator
    2025-03-16T10:46:02+00:00

    THE BSOD points to Hidclass.sys which is a USB related driver. As that is an operating system driver it will be a third party driver that triggered the crash. Looking at the faulting thread, the only third party driver implicated is:

    Image name: logi_joy_bus_enum.sys 

Timestamp:  Sat Sep 3 06:38:46 2022 (631269D6)

    What logitech device(s) are you using?

    Was this answer helpful?

    0 comments