Share via

BLUESCREEN HELP!

Anonymous
2024-04-21T12:43:52+00:00

Used WINDBG to analyze the most recent dump file, and this is the result. Please help me to analyze what happen!

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000028, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8025d142d26, address which referenced memory

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2608

    Key  : Analysis.Elapsed.mSec
    Value: 4619

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0xa

    Key  : Bugcheck.Code.TargetModel
    Value: 0xa

    Key  : Dump.Attributes.AsUlong
    Value: 8

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Failure.Bucket
    Value: AV_PECKP_x64!unknown_function

    Key  : Failure.Hash
    Value: {0942ba8f-721c-394f-7732-df8073ac01d8}

BUGCHECK_CODE:  a

BUGCHECK_P1: 28

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff8025d142d26

FILE_IN_CAB:  042124-12218-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

READ_ADDRESS: fffff8025dafb390: 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
 0000000000000028 

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

TRAP_FRAME:  ffffa68e31daf3b0 -- (.trap 0xffffa68e31daf3b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000100000018 rbx=0000000000000000 rcx=0000000000000000
rdx=ffffe3074e6f7010 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8025d142d26 rsp=ffffa68e31daf540 rbp=0000000000000000
 r8=0000000000000000  r9=0000000000000065 r10=0000000000000070
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!IoCancelIrp+0x66:
fffff802`5d142d26 488b4928        mov     rcx,qword ptr [rcx+28h] ds:00000000`00000028=????????????????
Resetting default scope

LOCK_ADDRESS:  fffff8025da44cc0 -- (!locks fffff8025da44cc0)
Cannot get _ERESOURCE Flag field
Unexpected resource format: 0
1 total locks

PNP_TRIAGE_DATA: 
Lock address  : 0xfffff8025da44cc0
Thread Count  : 0
Thread address: 0x0000000000000000
Thread wait   : 0x0

STACK_TEXT:  
ffffa68e`31daf268 fffff802`5d212269     : 00000000`0000000a 00000000`00000028 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffa68e`31daf270 fffff802`5d20dc34     : ffffe307`00000000 ffffa68e`31daf4c0 00000000`00000880 ffffe307`5d006000 : nt!KiBugCheckDispatch+0x69
ffffa68e`31daf3b0 fffff802`5d142d26     : ffffe307`4e6f7010 ffffe307`4c8f8830 ffffe307`4c8f8830 ffffe307`4c8f8830 : nt!KiPageFault+0x474
ffffa68e`31daf540 fffff802`eb6e1155     : ffffe307`55e64f50 ffffe307`4c8f8830 00000000`0000001a ffff958f`00000000 : nt!IoCancelIrp+0x66
ffffa68e`31daf580 ffffe307`55e64f50     : ffffe307`4c8f8830 00000000`0000001a ffff958f`00000000 ffffe307`59bc7060 : PECKP_x64+0x1155
ffffa68e`31daf588 ffffe307`4c8f8830     : 00000000`0000001a ffff958f`00000000 ffffe307`59bc7060 fffff802`eb6e3101 : 0xffffe307`55e64f50
ffffa68e`31daf590 00000000`0000001a     : ffff958f`00000000 ffffe307`59bc7060 fffff802`eb6e3101 fffff802`eb6e6f50 : 0xffffe307`4c8f8830
ffffa68e`31daf598 ffff958f`00000000     : ffffe307`59bc7060 fffff802`eb6e3101 fffff802`eb6e6f50 ffffe307`5d006010 : 0x1a
ffffa68e`31daf5a0 ffffe307`59bc7060     : fffff802`eb6e3101 fffff802`eb6e6f50 ffffe307`5d006010 ffffe307`4c8f8830 : 0xffff958f`00000000
ffffa68e`31daf5a8 fffff802`eb6e3101     : fffff802`eb6e6f50 ffffe307`5d006010 ffffe307`4c8f8830 ffffe307`55e64e00 : 0xffffe307`59bc7060
ffffa68e`31daf5b0 fffff802`eb6e6f50     : ffffe307`5d006010 ffffe307`4c8f8830 ffffe307`55e64e00 ffffe307`59bc7060 : PECKP_x64+0x3101
ffffa68e`31daf5b8 ffffe307`5d006010     : ffffe307`4c8f8830 ffffe307`55e64e00 ffffe307`59bc7060 fffff802`5d02d935 : PECKP_x64+0x6f50
ffffa68e`31daf5c0 ffffe307`4c8f8830     : ffffe307`55e64e00 ffffe307`59bc7060 fffff802`5d02d935 00000000`00000000 : 0xffffe307`5d006010
ffffa68e`31daf5c8 ffffe307`55e64e00     : ffffe307`59bc7060 fffff802`5d02d935 00000000`00000000 ffffe307`55e64e00 : 0xffffe307`4c8f8830
ffffa68e`31daf5d0 ffffe307`59bc7060     : fffff802`5d02d935 00000000`00000000 ffffe307`55e64e00 ffffa68e`31daf6d0 : 0xffffe307`55e64e00
ffffa68e`31daf5d8 fffff802`5d02d935     : 00000000`00000000 ffffe307`55e64e00 ffffa68e`31daf6d0 ffffe307`5d006010 : 0xffffe307`59bc7060
ffffa68e`31daf5e0 fffff802`5d46c690     : 00000000`00000000 ffffe307`55e64e00 ffffa68e`31daf6d0 ffffe307`59bc7060 : nt!IofCallDriver+0x55
ffffa68e`31daf620 fffff802`5d549898     : 00000000`00000002 ffffe307`59bc7060 ffffe307`4bb60cc0 ffffe307`59bc7060 : nt!IopSynchronousCall+0xf8
ffffa68e`31daf690 fffff802`5d16fad8     : ffff958f`a46a2d50 ffffe307`4bb60cc0 00000000`00000001 00000000`0000000a : nt!IopRemoveDevice+0x108
ffffa68e`31daf740 fffff802`5d54945a     : ffffe307`4bb60cc0 00000000`00000000 00000000`00000000 fffff802`5da44c20 : nt!PnpRemoveLockedDeviceNode+0x1ac
ffffa68e`31daf7a0 fffff802`5d54918f     : ffffe307`4bb60cc0 ffffa68e`31daf820 00000000`00000000 00000000`00000000 : nt!PnpDeleteLockedDeviceNode+0x4e
ffffa68e`31daf7e0 fffff802`5d54c7b5     : ffffe307`4f155de0 00000000`00000002 ffffe307`6d1a1a10 00000000`00000000 : nt!PnpDeleteLockedDeviceNodes+0xf7
ffffa68e`31daf860 fffff802`5d546f74     : 00000000`00000000 ffffa68e`31daf8e0 ffffe307`4f155de0 00000000`00000000 : nt!PipRemoveDevicesInRelationList+0x8d
ffffa68e`31daf8b0 fffff802`5d5474c9     : ffffe307`6d1a1a10 00000000`00000001 ffffe307`6d1a1a10 00000000`0000000a : nt!PnpDelayedRemoveWorker+0x114
ffffa68e`31daf8f0 fffff802`5d16f824     : 00000000`0000000a 00000000`00000001 00000000`00000000 ffffe307`4d56dcc0 : nt!PnpChainDereferenceComplete+0xfd
ffffa68e`31daf920 fffff802`5d54798a     : 00000000`0000000b ffffa68e`31dafa19 ffff958f`a1871530 00000000`00000001 : nt!PnpIsChainDereferenced+0xac
ffffa68e`31daf9a0 fffff802`5d53dfdb     : ffffa68e`31dafae0 ffffe307`4d56dc00 ffffa68e`31dafb00 ffff958f`0000000b : nt!PnpProcessQueryRemoveAndEject+0x28a
ffffa68e`31dafa80 fffff802`5d4aeade     : ffff958f`a46a2d50 ffff958f`c4606ad0 ffffe307`3969d200 00000000`00000000 : nt!PnpProcessTargetDeviceEvent+0xeb
ffffa68e`31dafab0 fffff802`5d0c3ea5     : ffffe307`62011040 ffffe307`62011040 ffffe307`3969d2b0 ffffe307`52385060 : nt!PnpDeviceEventWorker+0x2ce
ffffa68e`31dafb30 fffff802`5d14ef55     : ffffe307`62011040 00000000`00000080 ffffe307`39685040 fffff802`5d42e9b8 : nt!ExpWorkerThread+0x105
ffffa68e`31dafbd0 fffff802`5d206a48     : ffffad01`acce3180 ffffe307`62011040 fffff802`5d14ef00 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffffa68e`31dafc20 00000000`00000000     : ffffa68e`31db0000 ffffa68e`31da9000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28

SYMBOL_NAME:  PECKP_x64+1155

MODULE_NAME: PECKP_x64

IMAGE_NAME:  PECKP_x64.SYS

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  1155

FAILURE_BUCKET_ID:  AV_PECKP_x64!unknown_function

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {0942ba8f-721c-394f-7732-df8073ac01d8}

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 No comments

1 answer

Sort by: Most helpful
  1. DaveM121 891.1K Reputation points Independent Advisor
    2024-04-21T13:16:34+00:00

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

    Your minidump file indicates a driver usually associated to the Power Enter Keyboard Protector software is causing your PC to crash.

    Temporarily uninstall that software and wait to see if your system is stable.

    Was this answer helpful?

    0 comments No comments