KBC.CLASS.SYS Gigabyte G5 MF

L

LukaBG

New member
Hi this issue has been plauging me for months and i dont know how to fix it i keep getting kbc.class.sys error while playing games it bsod me a lot. and idk how to fix it.
i use win 11
if someone could help i would be greatful.

here is the minidump.


RIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: ffffa707c7191504, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff801bb9832d2, address which referenced memory

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

*** WARNING: Unable to verify timestamp for HKKbdFltr.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 687

Key : Analysis.Elapsed.mSec
Value: 5169

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

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

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

Key : Bugcheck.Code.LegacyAPI
Value: 0xd1

Key : Bugcheck.Code.TargetModel
Value: 0xd1

Key : Failure.Bucket
Value: AV_kbdclass!memcpy

Key : Failure.Hash
Value: {dfec7698-3775-c204-13ee-4d0f5bb2791c}

Key : Hypervisor.Enlightenments.ValueHex
Value: 1417df84

Key : Hypervisor.Flags.AnyHypervisorPresent
Value: 1

Key : Hypervisor.Flags.ApicEnlightened
Value: 0

Key : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 1

Key : Hypervisor.Flags.AsyncMemoryHint
Value: 0

Key : Hypervisor.Flags.CoreSchedulerRequested
Value: 0

Key : Hypervisor.Flags.CpuManager
Value: 1

Key : Hypervisor.Flags.DeprecateAutoEoi
Value: 1

Key : Hypervisor.Flags.DynamicCpuDisabled
Value: 1

Key : Hypervisor.Flags.Epf
Value: 0

Key : Hypervisor.Flags.ExtendedProcessorMasks
Value: 1

Key : Hypervisor.Flags.HardwareMbecAvailable
Value: 1

Key : Hypervisor.Flags.MaxBankNumber
Value: 0

Key : Hypervisor.Flags.MemoryZeroingControl
Value: 0

Key : Hypervisor.Flags.NoExtendedRangeFlush
Value: 0

Key : Hypervisor.Flags.NoNonArchCoreSharing
Value: 1

Key : Hypervisor.Flags.Phase0InitDone
Value: 1

Key : Hypervisor.Flags.PowerSchedulerQos
Value: 0

Key : Hypervisor.Flags.RootScheduler
Value: 0

Key : Hypervisor.Flags.SynicAvailable
Value: 1

Key : Hypervisor.Flags.UseQpcBias
Value: 0

Key : Hypervisor.Flags.Value
Value: 21631230

Key : Hypervisor.Flags.ValueHex
Value: 14a10fe

Key : Hypervisor.Flags.VpAssistPage
Value: 1

Key : Hypervisor.Flags.VsmAvailable
Value: 1

Key : Hypervisor.RootFlags.AccessStats
Value: 1

Key : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 1

Key : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 1

Key : Hypervisor.RootFlags.DisableHyperthreading
Value: 0

Key : Hypervisor.RootFlags.HostTimelineSync
Value: 1

Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0

Key : Hypervisor.RootFlags.IsHyperV
Value: 1

Key : Hypervisor.RootFlags.LivedumpEnlightened
Value: 1

Key : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 1

Key : Hypervisor.RootFlags.MceEnlightened
Value: 1

Key : Hypervisor.RootFlags.Nested
Value: 0

Key : Hypervisor.RootFlags.StartLogicalProcessor
Value: 1

Key : Hypervisor.RootFlags.Value
Value: 1015

Key : Hypervisor.RootFlags.ValueHex
Value: 3f7

Key : WER.OS.Branch
Value: ni_release_svc_prod3

Key : WER.OS.Version
Value: 10.0.22621.2506


BUGCHECK_CODE: d1

BUGCHECK_P1: ffffa707c7191504

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff801bb9832d2

FILE_IN_CAB: 030924-17359-01.dmp

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b


READ_ADDRESS: fffff8017811c470: 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
ffffa707c7191504

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

TRAP_FRAME: fffff8017a70f030 -- (.trap 0xfffff8017a70f030)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffa70190c54b40 rbx=0000000000000000 rcx=ffffa70190c54b40
rdx=000000063653c9c4 rsi=0000000000000000 rdi=0000000000000000
rip=fffff801bb9832d2 rsp=fffff8017a70f1c8 rbp=fffff8017a70f240
r8=00000000000000c0 r9=0000000000000038 r10=ffffa7017ef2e000
r11=ffffa707c71915c4 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
kbdclass!memcpy+0x92:
fffff801`bb9832d2 0f100411 movups xmm0,xmmword ptr [rcx+rdx] ds:ffffa707`c7191504=????????????????????????????????
Resetting default scope

STACK_TEXT:
fffff801`7a70eee8 fffff801`7782c5e9 : 00000000`0000000a ffffa707`c7191504 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff801`7a70eef0 fffff801`77827b34 : ffffa701`833cc6d8 00000000`00000000 00000000`0000000b 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff801`7a70f030 fffff801`bb9832d2 : fffff801`bb985b5d 00000000`b7e24a4c fffff801`7a70f240 ffffa701`8ea99920 : nt!KiPageFault+0x474
fffff801`7a70f1c8 fffff801`bb985b5d : 00000000`b7e24a4c fffff801`7a70f240 ffffa701`8ea99920 fffff801`bb942d5c : kbdclass!memcpy+0x92
fffff801`7a70f1d0 fffff801`bb971511 : ffffa701`7eefd940 fffff801`7a70f398 ffffa701`7eefe310 fffff801`7a70f398 : kbdclass!KeyboardClassServiceCallback+0x16d
fffff801`7a70f270 ffffa701`7eefd940 : fffff801`7a70f398 ffffa701`7eefe310 fffff801`7a70f398 00000000`00000008 : HKKbdFltr+0x1511
fffff801`7a70f278 fffff801`7a70f398 : ffffa701`7eefe310 fffff801`7a70f398 00000000`00000008 fffff801`7a70f2f0 : 0xffffa701`7eefd940
fffff801`7a70f280 ffffa701`7eefe310 : fffff801`7a70f398 00000000`00000008 fffff801`7a70f2f0 ffffa701`7eefd7f0 : 0xfffff801`7a70f398
fffff801`7a70f288 fffff801`7a70f398 : 00000000`00000008 fffff801`7a70f2f0 ffffa701`7eefd7f0 fffff801`bb9713f0 : 0xffffa701`7eefe310
fffff801`7a70f290 00000000`00000008 : fffff801`7a70f2f0 ffffa701`7eefd7f0 fffff801`bb9713f0 fffff801`7328f180 : 0xfffff801`7a70f398
fffff801`7a70f298 fffff801`7a70f2f0 : ffffa701`7eefd7f0 fffff801`bb9713f0 fffff801`7328f180 fffff801`bb94b848 : 0x8
fffff801`7a70f2a0 ffffa701`7eefd7f0 : fffff801`bb9713f0 fffff801`7328f180 fffff801`bb94b848 ffffa701`7eefd940 : 0xfffff801`7a70f2f0
fffff801`7a70f2a8 fffff801`bb9713f0 : fffff801`7328f180 fffff801`bb94b848 ffffa701`7eefd940 fffff801`7a70f329 : 0xffffa701`7eefd7f0
fffff801`7a70f2b0 fffff801`7328f180 : fffff801`bb94b848 ffffa701`7eefd940 fffff801`7a70f329 ffffa701`7ee8c790 : HKKbdFltr+0x13f0
fffff801`7a70f2b8 fffff801`bb94b848 : ffffa701`7eefd940 fffff801`7a70f329 ffffa701`7ee8c790 fffff801`bb950258 : 0xfffff801`7328f180
fffff801`7a70f2c0 fffff801`7767148c : 00000000`00000000 ffff8001`00000010 00000000`00000000 ffff8001`de88d0b0 : i8042prt!I8042KeyboardIsrDpc+0x1a8
fffff801`7a70f390 fffff801`77672741 : 00000000`00000000 fffff801`7a70f9d0 00000000`00000000 00000000`00000976 : nt!KiExecuteAllDpcs+0x42c
fffff801`7a70f8d0 fffff801`7781bb5e : 00000000`00000000 fffff801`7328f180 fffff801`7814c700 ffffa701`8e5cc080 : nt!KiRetireDpcList+0x1b1
fffff801`7a70fb80 00000000`00000000 : fffff801`7a710000 fffff801`7a709000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e


SYMBOL_NAME: kbdclass!memcpy+92

MODULE_NAME: kbdclass

IMAGE_NAME: kbdclass.sys

IMAGE_VERSION: 10.0.22621.1774

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 92

FAILURE_BUCKET_ID: AV_kbdclass!memcpy

OS_VERSION: 10.0.22621.2506

BUILDLAB_STR: ni_release_svc_prod3

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {dfec7698-3775-c204-13ee-4d0f5bb2791c}

Followup: MachineOwner
---------
 
197

197

Member
ubuysa said:
Can you please post your full spec.
Click to expand...
Is there a need to look at the DMP file? I know that all files related to kbdclass.sys are created in the same way.

Rich (BB code): 
*** WARNING: Unable to verify timestamp for HKKbdFltr.sys

In the registry, you need to remove the HKKbdFltr driver in Kbdclass and mouclass values.
 
Last edited:
ubuysa

ubuysa

The BSOD Doctor
I asked for the full specs because these fora are for the support of PCS builds only and so we need to be confident that this PC is a PCS build.

Telling the OP to remove a filter driver without warning them of the potential issues and risks in doing so is a tad unwise don't you think? You do appreciate that the warning message you quoted only indicates that symbol files for the specified driver were not installed in the debugger? It doesn't indicate that the driver was necessarily the problem. If/when the user posts the full spec I may ask for the dump file to be uploaded so that I can fully analyse the dump and provide a considered and evidence based response.
 
You must log in or register to reply here.
Top