Share via

My Windows Crash and Stop Responding 0x000000d1

Anonymous
2024-05-12T22:13:27+00:00

Recently while i am playing valorant the windows in my laptop just crash and stop responding , and force me to force shutdown by long press power button

my laptop Gigabyte A5k1
CPU : Ryzen 5 5600H

GPU : RTX 3060

RAM 16

when i check windows reliability history i get always this error

The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000d1 (0xffffcb86e794d600, 0x0000000000000002, 0x0000000000000000, 0xfffff801782532d2)

and when i analysed the dumbfile in winDebug this is the output
0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * *******************************************************************************

DRIVER_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: ffffcb86e794d600, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, value 0 = read operation, 1 = write operation Arg4: fffff801782532d2, address which referenced memory

Debugging Details:

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec
Value: 1906

Key  : Analysis.Elapsed.mSec
Value: 5983

Key  : Analysis.IO.Other.Mb
Value: 32

Key  : Analysis.IO.Read.Mb
Value: 0

Key  : Analysis.IO.Write.Mb
Value: 39

Key  : Analysis.Init.CPU.mSec
Value: 343

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

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

Key  : Bugcheck.Code.LegacyAPI
Value: 0xd1

Key  : Bugcheck.Code.TargetModel
Value: 0xd1

Key  : Dump.Attributes.AsUlong
Value: 1808

Key  : Dump.Attributes.DiagDataWrittenToHeader
Value: 1

Key  : Dump.Attributes.ErrorCode
Value: 0

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\_kbdclass!memcpy

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

Key  : Hypervisor.Enlightenments.ValueHex
Value: 1497cf94

Key  : Hypervisor.Flags.AnyHypervisorPresent
Value: 1

Key  : Hypervisor.Flags.ApicEnlightened
Value: 1

Key  : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 0

Key  : Hypervisor.Flags.AsyncMemoryHint
Value: 0

Key  : Hypervisor.Flags.CoreSchedulerRequested
Value: 0

Key  : Hypervisor.Flags.CpuManager
Value: 1

Key  : Hypervisor.Flags.DeprecateAutoEoi
Value: 0

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

Key  : Hypervisor.Flags.ValueHex
Value: 4a10ef

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

BUGCHECK_CODE: d1

BUGCHECK_P1: ffffcb86e794d600

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff801782532d2

FILE_IN_CAB: 051224-21828-01.dmp

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

DUMP_FILE_ATTRIBUTES: 0x1808 Kernel Generated Triage Dump

READ_ADDRESS: fffff80135b1c4a8: 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 ffffcb86e794d600

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: dwm.exe

DPC_STACK_BASE: FFFFF801332AFFB0

TRAP_FRAME: fffff801332af460 -- (.trap 0xfffff801332af460) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=ffffcb81fe194dc0 rbx=0000000000000000 rcx=ffffcb81fe194dc0 rdx=00000004e97b8840 rsi=0000000000000000 rdi=0000000000000000 rip=fffff801782532d2 rsp=fffff801332af5f8 rbp=fffff801332af670 r8=00000000000000c0 r9=0000000000000038 r10=ffffcb81ff892000 r11=ffffcb86e794d6c0 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na pe nc kbdclass!memcpy+0x92: fffff801782532d2 0f100411 movups xmm0,xmmword ptr [rcx+rdx] ds:ffffcb86e794d600=???????????????????????????????? Resetting default scope

STACK_TEXT:
fffff801332af318 fffff8013522de69 : 000000000000000a ffffcb86e794d600 0000000000000002 0000000000000000 : nt!KeBugCheckEx fffff801332af320 fffff80135229305 : 0000000000000000 ffffcb820c0233a0 0000000000000246 fffff8013503722b : nt!KiBugCheckDispatch+0x69 fffff801332af460 fffff801782532d2 : fffff80178255b5d 000000001ed02ec0 fffff801332af670 ffffcb8218f20010 : nt!KiPageFault+0x485 fffff801332af5f8 fffff80178255b5d : 000000001ed02ec0 fffff801332af670 ffffcb8218f20010 fffff80178212d5c : kbdclass!memcpy+0x92 fffff801332af600 fffff80178241511 : ffffcb81fae15190 fffff801332af7c8 ffffcb81ff5d3310 fffff801332af7c8 : kbdclass!KeyboardClassServiceCallback+0x16d fffff801332af6a0 ffffcb81fae15190 : fffff801332af7c8 ffffcb81ff5d3310 fffff801332af7c8 0000000000000008 : HKKbdFltr+0x1511 fffff801332af6a8 fffff801332af7c8 : ffffcb81ff5d3310 fffff801332af7c8 0000000000000008 fffff801332af720 : 0xffffcb81fae15190 fffff801332af6b0 ffffcb81ff5d3310 : fffff801332af7c8 0000000000000008 fffff801332af720 ffffcb81fae15040 : 0xfffff801332af7c8 fffff801332af6b8 fffff801332af7c8 : 0000000000000008 fffff801332af720 ffffcb81fae15040 fffff801782413f0 : 0xffffcb81ff5d3310 fffff801332af6c0 0000000000000008 : fffff801332af720 ffffcb81fae15040 fffff801782413f0 fffff80131445180 : 0xfffff801332af7c8 fffff801332af6c8 fffff801332af720 : ffffcb81fae15040 fffff801782413f0 fffff80131445180 fffff8017821b847 : 0x8 fffff801332af6d0 ffffcb81fae15040 : fffff801782413f0 fffff80131445180 fffff8017821b847 ffffcb81fae15190 : 0xfffff801332af720 fffff801332af6d8 fffff801782413f0 : fffff80131445180 fffff8017821b847 ffffcb81fae15190 fffff801332af759 : 0xffffcb81fae15040 fffff801332af6e0 fffff80131445180 : fffff8017821b847 ffffcb81fae15190 fffff801332af759 ffffcb81fec75970 : HKKbdFltr+0x13f0 fffff801332af6e8 fffff8017821b847 : ffffcb81fae15190 fffff801332af759 ffffcb81fec75970 fffff80178220258 : 0xfffff80131445180 fffff801332af6f0 fffff8013503f4bc : 0000000000000000 ffffa88000000010 0000000000000000 ffffa880ee64fe70 : i8042prt!I8042KeyboardIsrDpc+0x1a7 fffff801332af7c0 fffff80135040771 : 0000000000000020 fffff801332afe00 ffffcb82259dd990 000000000000018c : nt!KiExecuteAllDpcs+0x42c fffff801332afd00 fffff801352218a5 : 0000000000000000 0000000000000000 fffff80131445180 ffffdc0412be3ac0 : nt!KiRetireDpcList+0x1b1 fffff801332affb0 fffff8013522184f : fffffc080babea19 fffff80135044235 fffffc080babe9d8 0000000000000000 : nt!KxSwapStacksAndRetireDpcList+0x5 fffffc080babe980 fffff80135044235 : fffffc080babe9d8 0000000000000000 0000000000000091 0000000000000001 : nt!KiPlatformSwapStacksAndCallReturn fffffc080babe990 fffff80135220fdb : fffffc080babec40 fffff80136451269 0000000000000000 ffffdc0412be3ac0 : nt!KiDispatchInterrupt+0xd5 fffffc080babea80 fffff8013521a311 : fffffc080babeb30 0000000000000000 ffffdc0412be3a90 000003d3ffffffea : nt!KiDpcInterruptBypass+0x1b fffffc080babeab0 fffff1e2fa830816 : 000003d300000000 000003d3ffffffea 000003d3ffffffea 0000000000000000 : nt!KiInterruptDispatch+0xb1 fffffc080babec40 fffff1e2fa83076a : 000003d3ffffffea fffffc080babed00 fffff1e2faa8afa0 0000000000000000 : win32kbase!CCursorClip::BoundPointToRegions+0x76 fffffc080babeca0 fffff1e2fa8306ad : fffffc080babee81 000003d3ffffffea 000003d3ffffffea 00000000ffffffea : win32kbase!CCursorClip::ApplySystemClips+0x7a fffffc080babed10 fffff1e2f9b34d5f : 0000000000000001 000003d3ffffffea ffffdc040aaed678 0000000000000001 : win32kbase!CCursorClip::BoundPoint+0x7d fffffc080babedc0 fffff1e2f9bac369 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : win32kfull!xxxMoveEventAbsolute+0x38b fffffc080babeed0 fffff1e2faa2a3ff : 0000000000000000 fffffc080babf0a8 fffffc080babf618 0000000000000000 : win32kfull!EditionCommitMousePosAndMove+0x99 fffffc080babef40 fffff1e2fa9f5ad5 : 0000000000000001 0000000000000000 000000000000003f fffffc080babf100 : win32kbase!EditionCommitMousePosAndMove+0x83 fffffc080babefb0 fffff1e2fa8b5684 : 0000000000000001 fffffc080babf0b9 0000000000000000 0000000000000000 : win32kbase!ApiSetEditionCommitMousePosAndMove+0x125 fffffc080babf040 fffff1e2fa8d9263 : 000003ca00000000 fffffc080babf220 fffffc080babf600 0000000000000000 : win32kbase!CMouseProcessor::CommitMousePosAndMoveCursor+0x17a fffffc080babf120 fffff1e2fa8b5fbd : 000003d3ffffffea 000003ca00000000 0000000000000000 0000000000000001 : win32kbase!CMouseProcessor::ProcessMouseInputData+0xb8077 fffffc080babf480 fffff1e2fa8b4b2a : ffffdc0411204700 fffff1e2fa8b4bad ffffdc0411204d60 ffffdc04112047e0 : win32kbase!CMouseProcessor::ProcessInput+0x61b fffffc080babf6b0 fffff1e2fa8b4d63 : ffffdc04112047e0 000001a1510b98e6 ffffdc0411204d60 ffffcb8214d6b668 : win32kbase!CMouseSensor::FlushMouseReports+0x42 fffffc080babf6f0 fffff1e2fa8b4c94 : ffffdc0404eca220 0000000000000018 ffffdc0411204700 ffffdc04112047e0 : win32kbase!CMouseSensor::ProcessInputWithRateLimitingIfEnabled+0xb3 fffffc080babf740 fffff1e2fa7c2e3c : 0000000000000000 fffff1e2faa39a01 ffffdc04112047e0 fffffc080babf9d9 : win32kbase!CMouseSensor::ProcessInput+0x54 fffffc080babf780 fffff1e2fa821461 : 0000000000000002 0000000000000002 0000000000000000 0000000000000000 : win32kbase!CBaseInput::OnReadNotification+0xbc fffffc080babf800 fffff1e2fa821382 : 0000000000000001 0000000000000001 0000000000000000 0000000000040282 : win32kbase!CBaseInput::OnDispatcherObjectSignaled+0xd1 fffffc080babf870 fffff1e2fa828ead : 0000000000000001 0000000000000001 ffffdc03f2968050 ffffdc03f2968050 : win32kbase!CBaseInput::\_OnDispatcherObjectSignaled+0x12 fffffc080babf8a0 fffff1e2fa828e15 : 0000000000000000 0000000000000000 0000000000000000 0000000000040286 : win32kbase!IOCPDispatcher::HandleSensorDispatcherSignal+0x75 fffffc080babf900 fffff1e2fa828bb8 : 0000000000000001 0000000000000001 0000000000000000 fffff80135030132 : win32kbase!IOCPDispatcher::Dispatch+0x15 fffffc080babf960 fffff1e2fa8922d1 : 0000000000000000 0000018c45e5f190 0000000000000020 0000000000000002 : win32kbase!UserKSTWait+0x130 fffffc080babfa40 fffff1e2f9880ae9 : 0000000000000000 fffff8013522d407 0000000000000010 0000000000050246 : win32kbase!NtKSTWait+0x21 fffffc080babfa70 fffff8013522d538 : ffffcb820000032f 0000000000000300 0000000000000000 0000000000000001 : win32k!NtKSTWait+0x15 fffffc080babfaa0 00007ff87e8d7ab4 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x28 000000096597fa58 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ff87e8d7ab4

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

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

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

Followup: MachineOwner

Windows for home | Windows 11 | 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

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-05-13T05:48:17+00:00

    Hello Elguessab Abderrafie,

    Welcome to the Microsoft Community!

    I’m sorry to hear that you’re encountering a DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) error on your Windows 11 system. This error is often associated with the kbdclass.sys driver, which is a keyboard class driver. Let’s collaborate to troubleshoot and resolve this issue.

    This error typically suggests that a driver has attempted to access a pageable or completely invalid address at an interrupt request level (IRQL) that is too high. Here are some steps you can take to address this issue:

    1. Update Drivers: Ensure that all device drivers, including the keyboard driver (kbdclass.sys), are up-to-date. Outdated or incompatible drivers can often lead to such errors. You can manually update the drivers through the Device Manager. If the Device Manager doesn’t find any driver updates, consider visiting the hardware manufacturer’s official website to download the latest suitable drivers.
    2. Check Memory: Memory issues can also contribute to system crashes and BSOD errors. Use the Windows Memory Diagnostic tool to check your system’s RAM for any problems. To run the Windows Memory Diagnostic, search for it in the Start menu and follow the on-screen instructions. If the tool doesn’t detect a fault, consider testing with Memtest86, which is known to be more robust in certain aspects of detection according to users.
    3. Scan for Malware: Conduct a comprehensive scan of your system for malware or viruses. Malicious software can sometimes interfere with system processes and drivers, leading to errors like the one you’re experiencing. Use a reputable antivirus or antimalware program to scan your system and remove any threats found.
    4. Check Hardware: If the issue persists after updating drivers and scanning for malware, there might be a hardware problem causing the error. Inspect your keyboard and other hardware components for any signs of damage or malfunction. You might also want to try using a different keyboard to see if the issue persists.

    If you continue to encounter the DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) error after trying these steps, please provide additional details, such as any recent changes or updates to your system, so we can further assist you in resolving the issue.

    Best Regards,

    Martin | Microsoft Community Support Specialist

    Was this answer helpful?

    0 comments