system crash BSOD - IRQL_NOT_LESS_OR_EQUAL

Question

system crash BSOD - IRQL_NOT_LESS_OR_EQUAL

GIHeon Han 20

My machine crashes frequently with BSoD.
Can someone please help?

My machine Info

//CPU

intel i9-13900k

//MAINBOARD

ASUS PRIME Z790-P

BIOS ver. 0812 02/24/2023

//RAM

SAMSUNG DDR 5 32GB * 4 = 128GB

M323R4GA3DB0-CWMOD

DDR5-5600

//GPU

NVIDIA GeForce RTX 4070 Ti

//SDD

Samsung SSD 990 PRO 2TB

//HDD

Seagate IronWolf Pro 20TB * 4EA

ST20000NT001-3LT101

It's a program what I'm developing is to image process two large image data (16384*75000 Byte = 1.2GB).

I'm going through the process of loading images, processing images, and storing images.

BSOD occurs during repeat test for performance test.
Which hardware driver is the problem?
Windows 11 has not been reinstalled yet.
It's only been a week since I bought a PC.

I've already delivered it to another project before, but the difference is that the hardware specifications have changed a little.

Windows 10 -> Windows 11

CPU : i9 11900k -> i9 13900k

GPU : 3080 Ti -> 4090 Ti

In particular, due to the lack of space on the PCI card, the GPU slot was installed in the 4.0 slot instead of the PCI 5.0 slot.

Here is my minidump links.

https://drive.google.com/file/d/1zGf1MifdqaVS__A-K4LNt4myUJQQegwM/view?usp=drive_link

Below is detail from WinDbg of memory dump .

Microsoft (R) Windows Debugger Version 10.0.22621.1778 AMD64
Windows 10 Kernel Version 22621 MP (32 procs) Free x64
Edition build lab: 22621.1928.amd64fre.ni_release_svc_prod3.230622-0951
Kernel base = 0xfffff802`22c00000 PsLoadedModuleList = 0xfffff802`238130e0
Debug session time: Mon Aug 28 15:21:33.652 2023 (UTC + 9:00)
System Uptime: 2 days 23:21:25.020



//<<

8: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: ffff9a805f031378, 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: fffff80222e4ef6d, address which referenced memory

//>>

KEY_VALUES_STRING: 1
    Key  : Analysis.CPU.mSec
    Value: 1234
    Key  : Analysis.DebugAnalysisManager
    Value: Create
    Key  : Analysis.Elapsed.mSec
    Value: 1342
    Key  : Analysis.Init.CPU.mSec
    Value: 93
    Key  : Analysis.Init.Elapsed.mSec
    Value: 4715
    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 101
    Key  : WER.OS.Branch
    Value: ni_release_svc_prod3
    Key  : WER.OS.Timestamp
    Value: 2023-06-22T09:51:00Z
    Key  : WER.OS.Version
    Value: 10.0.22621.1928
FILE_IN_CAB:  MEMORY.DMP
DUMP_FILE_ATTRIBUTES: 0x1000
BUGCHECK_CODE:  a
BUGCHECK_P1: ffff9a805f031378
BUGCHECK_P2: 2
BUGCHECK_P3: 0
BUGCHECK_P4: fffff80222e4ef6d
READ_ADDRESS:  ffff9a805f031378 
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
PROCESS_NAME:  LineScan.exe //<< It's my application.

TRAP_FRAME:  ffff858300486e40 -- (.trap 0xffff858300486e40)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffff978000000000 rbx=0000000000000000 rcx=3fffffffffffffff
rdx=ffff84c2613097f8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80222e4ef6d rsp=ffff858300486fd0 rbp=0000000000000080
 r8=0000000000000000  r9=ffff848000000000 r10=0000007ffffffff8
r11=ffff84c2613097f8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!MiDeleteVa+0x16d:
fffff802`22e4ef6d 498b4618        mov     rax,qword ptr [r14+18h] ds:00000000`00000018=????????????????

Resetting default scope

ffff8583`00486cf8 fffff802`230468a9
ffff8583`00486d00 fffff802`23041f34
ffff8583`00486e40 fffff802`22e4ef6d
ffff8583`00486fd0 fffff802`22e55e46
ffff8583`004870c0 fffff802`22e5620a
ffff8583`00487150 fffff802`22e5620a
ffff8583`004871e0 fffff802`22e5620a
ffff8583`00487270 fffff802`22e6d5c1
ffff8583`00487300 fffff802`22e4ed62
ffff8583`00487400 fffff802`22e8cafe
ffff8583`00487710 fffff802`232df027
ffff8583`00487760 fffff802`22eb2e1f
ffff8583`00487820 fffff802`232ebe55
ffff8583`00487880 fffff802`232eba65
ffff8583`004879c0 fffff802`23045fe5
ffff8583`00487a20 00007ffc`a594f114
000000f1`b2f3f4b8 00000000`00000000
00000010`00000000 fffff802`2386bf00 ffff7249`0b84bdd4 fffff802`22e4fe75
ffff84c2`00000000 ffff9780`00000000 00000000`00000001 8100001f`abb11c66
ffffd50d`4bfa0700 ffff8481`5a7d4ff8 ffff7249`0b84be54 ffffd50d`4bfa0700
ffff8583`00000000 ffffd50d`4bfa0700 ffff84c2`00000000 ffff8583`004874f0
ffff8583`00000000 ffffd50d`4bfa0700 ffff84c2`00000000 ffff8583`00487500
ffff8583`004874a0 ffffd50d`4bfa0700 ffff84c2`00000000 ffff8583`00487510
00000000`00000000 ffffd50d`4bfa0700 00000000`00000000 ffff8583`00487520
ffff8583`004874a0 000002b5`00000001 00000000`00000002 00000000`00000000
ffffd50d`4d118080 fffff802`22e8d112 ffff8583`004877a0 ffffd50d`53968bc0
00000000`00000000 00000000`00000001 ffff8583`004877e0 ffff8583`004877e0
000002b4`e1c00000 00000000`00000000 00000000`000083fe 00000000`00000000
00000000`00000000 00000000`00000000 ffff8583`00487980 00000000`00000000
00007ff7`b9a4b290 000002b3`0bc5e2b8 00000000`00000020 ffffa824`865777ca
ffffd50d`4d118080 ffffd50d`1596c500 ffffd50d`4d118080 00000000`00000000
00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
nt!KeBugCheckEx
nt!KiBugCheckDispatch+0x69
nt!KiPageFault+0x474
nt!MiDeleteVa+0x16d
nt!MiWalkPageTablesRecursively+0x266
nt!MiWalkPageTablesRecursively+0x62a
nt!MiWalkPageTablesRecursively+0x62a
nt!MiWalkPageTablesRecursively+0x62a
nt!MiWalkPageTables+0x371
nt!MiDeletePagablePteRange+0x3c2
nt!MiDeleteVirtualAddresses+0x4e
nt!MiDeleteVad+0x1b7
nt!MiFreeVadRange+0xa3
nt!MmFreeVirtualMemory+0x3b5
nt!NtFreeVirtualMemory+0x95
nt!KiSystemServiceCopyEnd+0x25
0x00007ffc`a594f114
SYMBOL_NAME:  nt!MiDeleteVa+16d
MODULE_NAME: nt
STACK_COMMAND:  .cxr; .ecxr ; kb
IMAGE_NAME:  ntkrnlmp.exe
BUCKET_ID_FUNC_OFFSET:  16d
FAILURE_BUCKET_ID:  AV_nt!MiDeleteVa
OS_VERSION:  10.0.22621.1928
BUILDLAB_STR:  ni_release_svc_prod3
OSPLATFORM_TYPE:  x64
OSNAME:  Windows 10
FAILURE_ID_HASH:  {dd6c76c4-dc97-5db4-009b-37294656b23e}
Followup:     MachineOwner
---------
8: kd> !pool ffff9a805f031378
Pool page ffff9a805f031378 region is Unknown
ffff9a805f031000 is not a valid large pool allocation, checking large session pool...
Unable to read large session pool table (Session data is not present in mini and kernel-only dumps)
ffff9a805f031000 is not valid pool. Checking for freed (or corrupt) pool
Address ffff9a805f031000 could not be read. It may be a freed, invalid or paged out page
8: kd> !pte ffff9a805f031378
Levels not implemented for this platform
8: kd> !address ffff9a805f031378
Mapping user range ...
Mapping system range ...
Mapping non addressable range ...
Mapping page tables...
Mapping hyperspace...
Mapping HAL reserved range...
Mapping User Probe Area...
Mapping system shared page...
Mapping system cache working set...
Mapping loader mappings...
Mapping system PTEs...
Mapping system paged pool...
Mapping session space...
Mapping dynamic system space...
Mapping PFN database...
Mapping non paged pool...
Mapping VAD regions...
Mapping module regions...
Mapping process, thread, and stack regions...
Mapping system cache regions...
Usage:                  
Base Address:           ffff9780`61800000
End Address:            ffffa824`85a00000
Region Size:            000010a4`24200000
VA Type:                SystemRange

Accepted answer

1 additional answer

Your answer

Answer 1

The collected log files were in a foreign language and there was very limited ability to scan and read event viewer files.

.

The computer has a new Windows installation dated 08/18/2023.

.

There were 5 collected mini dump files with BSOD bugchecks:

A

1A

3B

1AA

.

Additional BSOD seen in the collected files were:

1E

139

.

The debugging displayed no misbehaving drivers.

.

The above findings are most often seen when there is overclocking, overheating, malfunctioning and / or incompatible hardware.

Overclocking was not seen at the time in which the V2 log collector collected data.

.

Please perform the following steps:

.

1)The BIOS: Version/Date American Megatrends Inc. 0812, 2/24/2023

Upgrade the BIOS: 0812 > 1220

https://www.asus.com/motherboards-components/motherboards/prime/prime-z790-p/helpdesk_bios/?model2Name=PRIME-Z790-P

.

"1.Recommended for vital update to mitigate the potential security vulnerabilities
2.Update the Intel ME to version 16.1.27.2176V2
3.Improve system stability

.

"Improve system’s memory compatibility.

.

"1.Improve system stability and compatibility for the next-gen processors.
2.Fix the compatibility and instability issues when configuring RAID for high-capacity storage.
3.Do update the Intel ME to version 16.1.27.2176.

.

"1. Update Intel uCode.

.

"1. Improve system performance

.

Update Intel ME version 16.1.25.2124v4
Update Intel Microcode
Improve memory compatibility

.

2)Monitor temperatures using any third party software:

Speccy

HWMonitor

Speedfan

etc.

.

3)The installed 32GB RAM Samsung modules (M323R4GA3BB0-CQKOL) were not seen on the Qualified Vendor List (QVL):

https://www.asus.com/motherboards-components/motherboards/prime/prime-z790-p/helpdesk_qvl_memory/?model2Name=PRIME-Z790-P

If you see the RAM modules on the QVL then comment into this thread.

Test RAM modules displayed on the QVL:

https://www.asus.com/motherboards-components/motherboards/prime/prime-z790-p/helpdesk_qvl_memory/?model2Name=PRIME-Z790-P

.

--please don't forget to upvote and Accept as answer if the reply is helpful--

.

GIHeon Han 20 Reputation points

2023-08-31T06:01:07.9966667+00:00

Hello, thank you for your reply. It was very helpful.

I have one more PC with the same specifications.
After your answer, I will explain the progress of the test I conducted.
After reinstalling, I installed all the latest drivers except for BIOS update (0812 version).
And I'm still running the program I wrote, and I've been keeping it for 47 hours now.

When I monitored with the HWInfo64 program,
When the temperature is checked, the entire CPU is 44 to 90 degrees Celsius
CPU power consumption is up to 125W, typically 30 to 70W.
Note: Windows Hardware Erros has a value of 2183. Could this be a problem?

https://drive.google.com/file/d/1oX83ZHDFVfhyr2wE53Ce_pHjjMGOvq8H/view?usp=sharing
I did the same for other PCs, but BSOD occurred again. I attached the log file. (By the way, even though I changed the language setting according to the guidelines, the event viewer log still remains in Korean. Logs left before language change cannot be changed.)

After BSOD, I updated the BIOS to 1220 version and am running the program.
Docs 15,846 Reputation points

2023-08-31T08:08:25.38+00:00

For a second PC please open a new thread.

The event viewer often incompletely changes language.

For complicated or challenging threads backup images can be made followed by a clean install in English.

Once troubleshooting has completed a backup image can be restored.

The second computer just had a fresh Windows installation and an option may be to clean install using English.

Answer 2

Docs 15,846

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

https://www.tenforums.com/bsod-crashes-debugging/2198-bsod-posting-instructions.html

https://www.elevenforum.com/t/bsod-posting-instructions.103/

.

--please don't forget to upvote and Accept as answer if the reply is helpful--

.

GIHeon Han 20 Reputation points

2023-08-30T00:19:24.15+00:00

Thank you for your reply. Here is the compressed file as a result of running the V2 Logger.

[https://drive.google.com/file/d/1eby9fGq9UhiMIFHjRq20VnOzb4XN7gaS/view?usp=drive_link

](https://drive.google.com/file/d/1eby9fGq9UhiMIFHjRq20VnOzb4XN7gaS/view?usp=drive_link

)

There are several dumps, and the last dump occurred after replacing the ram.

DDR5-5600 => DDR5-4800.
The reason for replacing the RAM was simply that I received a different RAM from the order sheet.

In addition, BSOD occurred in one PC of the same specification as well, but if the windows were reinstalled after replacing RAM yesterday, it has not occurred for 17 hours now.

Share via

system crash BSOD - IRQL_NOT_LESS_OR_EQUAL

1 additional answer

Your answer