BSOD IRQL_NOT_LESS_OR_EQUAL

Question

Hello,

Since yesterday, I’ve been experiencing occasional Blue Screen of Death (BSOD) errors and have not yet found a solution. I’m reaching out in the hope that you might be able to assist me in resolving this issue.

I’d greatly appreciate your help.

Best regards, Andi

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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: 0000008a299ff900, memory referenced
Arg2: 00000000000000ff, 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: fffff806c60f78df, address which referenced memory

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1609

    Key  : Analysis.Elapsed.mSec
    Value: 7185

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27829.1001

    Key  : Analysis.Version.Description
    Value: 10.2503.24.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2503.24.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0xa

    Key  : Bugcheck.Code.TargetModel
    Value: 0xa

    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_nt!PspInitializeThunkContext

    Key  : Failure.Exception.IP.Address
    Value: 0xfffff806c60f78df

    Key  : Failure.Exception.IP.Module
    Value: nt

    Key  : Failure.Exception.IP.Offset
    Value: 0x8f78df

    Key  : Failure.Hash
    Value: {a81ddcd7-0a6f-2aa6-f21f-61d65f0e20fa}


BUGCHECK_CODE:  a

BUGCHECK_P1: 8a299ff900

BUGCHECK_P2: ff

BUGCHECK_P3: 0

BUGCHECK_P4: fffff806c60f78df

FILE_IN_CAB:  061025-11546-01.dmp

DUMP_FILE_ATTRIBUTES: 0x21008
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffa90cb411a080

READ_ADDRESS: fffff806c67c34c0: 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
 0000008a299ff900 

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  MsMpEng.exe

STACK_TEXT:  
fffff48c`e317eaa8 fffff806`c5eb8fe9     : 00000000`0000000a 0000008a`299ff900 00000000`000000ff 00000000`00000000 : nt!KeBugCheckEx
fffff48c`e317eab0 fffff806`c5eb42a8     : 00000000`00000000 00000000`00000000 00000000`00000000 fffff48c`e317edb0 : nt!KiBugCheckDispatch+0x69
fffff48c`e317ebf0 fffff806`c60f78df     : fffff806`c6704b28 fffff806`c6704cf8 fffff806`c6704d00 00000000`00000000 : nt!KiPageFault+0x468
fffff48c`e317ed80 fffff806`c60f7cf3     : ffffa90c`b411a080 ffffa90c`ba0d66bc ffffa90c`b411d080 fffff806`56b64180 : nt!PspInitializeThunkContext+0x24f
fffff48c`e317f900 fffff806`c5ea65b8     : fffff806`56b64180 00000000`00000000 ffffa90c`b411a080 ffffa90c`ba0d66bc : nt!PspUserThreadStartup+0xb3
fffff48c`e317f960 fffff806`c5ea6520     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartUserThread+0x28
fffff48c`e317faa0 00007ffd`9533c5b0     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartUserThreadReturn
0000008a`299ffe88 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`9533c5b0


SYMBOL_NAME:  nt!PspInitializeThunkContext+24f

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.26100.4061

STACK_COMMAND: .process /r /p 0xffffa90cba0d60c0; .thread 0xffffa90cb411a080 ; kb

BUCKET_ID_FUNC_OFFSET:  24f

FAILURE_BUCKET_ID:  AV_nt!PspInitializeThunkContext

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {a81ddcd7-0a6f-2aa6-f21f-61d65f0e20fa}

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

Answer 1

I did what you said Group d had immediate BSOD as a consequence

Here the V2 link https://drive.google.com/file/d/1Akrc-ujf8oMogmaNVhoEjeIP6VIMQEqx/view?usp=sharing

Answer 2

Please restart WDV with these groups of customized tests:

.

Group a

[ ] 0x00000010 I/O verification.

[ ] 0x00000200 Force pending I/O requests.

[ ] 0x00002000 Invariant MDL checking for stack.

[ ] 0x00004000 Invariant MDL checking for driver.

[ ] 0x00000800 Miscellaneous checks.

.

Group b

[ ] 0x00000020 Deadlock detection.

[ ] 0x00000080 DMA checking.

[ ] 0x00000100 Security checks.

[ ] 0x00020000 DDI compliance checking.

[ ] 0x00080000 DDI compliance checking (additional).

.

Group c

[ ] 0x00000400 IRP logging.

[ ] 0x00008000 Power framework delay fuzzing.

[ ] 0x00010000 Port/miniport interface checking.

[ ] 0x00040000 Systematic low resources simulation.

[ ] 0x00200000 NDIS/WIFI verification.

.

Group d

[ ] 0x00800000 Kernel synchronization delay fuzzing.

[ ] 0x01000000 VM switch verification.

[ ] 0x02000000 Code integrity checks.

[ ] 0x00000001 Special pool.

[ ] 0x00000002 Force IRQL checking.

[ ] 0x00000008 Pool tracking.

.

.

For each group:

a) Test all non-Microsoft drivers

b) Test no Microsoft drivers

.

If there is no immediate BSOD then open administrative command prompt and copy and paste:

verifier /querysettings

Post a share link.

.

For any BSOD post a new V2 share link into the newest post.

.

Answer 3

Tuneup plus results were excellent.

.

.

1)Please run Windows Driver Verifier (WDV) to find misbehaving drivers:

https://www.tenforums.com/tutorials/5470-enable-disable-driver-verifier-windows-10-a.html

.

.

2)Create a new restore point:

https://www.elevenforum.com/t/create-system-restore-point-in-windows-11.3602/

.

.

3)Learn the methods to recover from BSOD caused by WDV by booting into safe mode and running one or more of these commands:

verifier /reset

verifier /bootmode resetonbootfail

.

(option nine and seven)

https://www.elevenforum.com/t/boot-to-advanced-startup-winre-in-windows-11.425/

.

.

4)Plan to run the tool with various customized test settings.

a) Test all non-Microsoft drivers

b) Test no Microsoft drivers

c) For the first run of WDV select the 3 customized tests displayed in the TF tutorial

.

.

5)Whenever the WDV tool is started if there is no immediate BSOD then open administrative command prompt and copy and paste:

verifier /querysettings

Post a share link.

.

Customized tests will then be posted for the next run of WDV.

.

.

WDV can run continuously during the testing.

.

For any BSOD post a new V2 share link into the newest post. .

.

Answer 4

Hi Andi,

.

.

1)The logs were in a foreign language and could not be scanned.

Please temporarily use English as the default language so that files can be scanned and read.

.

.

https://www.tenforums.com/tutorials/3813-language-add-remove-change-windows-10-a.html

https://www.tenforums.com/tutorials/136792-change-display-language-windows-10-a.html#option1

Post a new V2 share link into the newest post.

.

.

2)Run Tuneup plus > post a share link

https://www.tenforums.com/attachmen...-files-use-bsod-debugging-tuneup_plus_log.bat

Batch files for use in BSOD debugging - Page 2 - Windows 10 Forums

Batch files for use in BSOD debugging - Windows 10 Forums

.

.

3)Turn off Windows fast startup:

https://www.elevenforum.com/t/turn-on-or-off-fast-startup-in-windows-11.1212/

.

.

4)Download Memory integrity system readiness scan tool from Official Microsoft Download Center

https://www.microsoft.com/en-us/download/details.aspx?id=105437

AMD

hvciscan_amd64.exe

.

.

5)Open administrative command prompt and copy and paste:

cd /users /Andreas Jurchen /downloads

hvciscan_amd64.exe

dism /online /get-drivers /format:table >c:\drivers.txt

Post share links.

.

.

.

.

Windows-Fehler beim Schnellstart mit Fehlerstatus "0xC00000D4".

.

.

Der Computer wurde nach einem schwerwiegenden Fehler neu gestartet. Der Fehlercode war: 0x000000d1 (0x0000000000000002, 0x000000000000000f, 0x0000000000000000, 0x0000000000000000). Ein volles Abbild wurde gespeichert in: C:\WINDOWS\Minidump\061025-11859-01.dmp. Berichts-ID: 24dadbd0-83bb-43f1-b4e2-58000148e4ef.

Answer 5

Please run the V2 log collector and post a share link into this thread using drop box, or google drive

BSOD - Posting Instructions | Windows 11 Forum (elevenforum.com)

For share links please use drop box or google drive.

Make sure that links are available without sign in.

https://support.google.com/drive/answer/2424384?hl=en&co=GENIE.Platform%3DDesktop