Question BSOD - - - DRIVER_IRQL_NOT_LESS_OR_EQUAL and ntoskrnl.exe ?

[Ziwer9]

A little over a year ago I built a new PC with the following components:
1) Ryzen 7 5800x
2) Gigabyte GeForce RTX 3080 Ti GAMING OC
3) Gigabyte B550M AORUS ELITE
4) Kingston FURY Beast Black [KF432C16BBK2/16] x 2
5) Thermaltake Toughpower GF1 Snow 850W
6) Air cooler for CPU

I also installed storage devices from an old PC and one was with Windows installed and working, and I continued to work on it without reinstalling (I only cleared old devices from the device manager and removed unnecessary drivers, but I'm not sure if I removed all the old drivers).

The problem is that my PC spontaneously reboots without any blue screens or saving memory dumps (very rarely dumps were saved, I have one left). It can reboot once in two weeks or four times in two days or twice in less than an hour, no matter what I do, rebooted even when idle with no programs running. The last memory dump says the following (I viewed it with BlueScreenView)
Bug Check String: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code: 0x000000d1
but in the memory dumps that I deleted there was
Bug Check String: APC_INDEX_MISMATCH
Bug Check Code: 0x00000001
and in all memory dumps
Crash address: ntoskrnl.exe

I disabled all hardware acceleration (video cards, disabled XMP profiles, reset the motherboard settings to factory defaults), removed all applications that could somehow affect the change in the PC operating parameters (except for gigabyte system information viewer, since I used it to configure fan speeds), checked the memory using the built-in Windows application, as well as using memtest86, tried to make a memory dump using Driver Verifier (the dumps simply were not created, although in the settings there was saving new ones without overwriting old dumps).

Can you please try to help solve the problem? I can also upload a last memory dump and a screenshot of the one old memory dump from BlueScreenView (

https://imgur.com/a/RmVUq42

View: https://imgur.com/a/RmVUq42
).

 

[Lutfij]

Welcome to the forums, newcomer!

I also installed storage devices from an old PC and one was with Windows installed and working, and I continued to work on it without reinstalling (I only cleared old devices from the device manager and removed unnecessary drivers, but I'm not sure if I removed all the old drivers).
+
The problem is that my PC spontaneously reboots
+
Can you please try to help solve the problem?
Your problem is that you didn't reinstall the OS after migrating an older OS drive. In your current state of affairs, you should backup all mission critical data, recreate your bootable USB installer for your OS, then install the OS with only the drive you wish to install the OS onto in offline mode. You should also download necessary drivers for your platform before hand, to install them in an elevated command once you've installed the OS.

 

[Ziwer9]

Welcome to the forums, newcomer!

I also installed storage devices from an old PC and one was with Windows installed and working, and I continued to work on it without reinstalling (I only cleared old devices from the device manager and removed unnecessary drivers, but I'm not sure if I removed all the old drivers).
+
The problem is that my PC spontaneously reboots
+
Can you please try to help solve the problem?
Your problem is that you didn't reinstall the OS after migrating an older OS drive. In your current state of affairs, you should backup all mission critical data, recreate your bootable USB installer for your OS, then install the OS with only the drive you wish to install the OS onto in offline mode. You should also download necessary drivers for your platform before hand, to install them in an elevated command once you've installed the OS.

Ok, thank you very much for the advice.
When I was looking for a solution from people who had the same error, all people wrote that reinstalling the OS did not help them.
I hope this will help me. Thanks again!

Could there be other sources of this problem or should I only look for them after reinstalling the OS and if reboots persist?

 

[ubuysa]

As above. When WIndows installs it configures itself for the hardware platform it's being installed on. You've now booted a Windows system that was configured for a different platform.

You can't diagnose your problem by referring to other people's experiences because the systems are not identical. You really have to bite the bullet and clean install from bootable media (ie. NOT a Windows Reset) so that you get a completely clean Windows system configured for this platform. Only then can anyone start to troubleshoot it.

 

[Ziwer9]

Reinstalling windows didn't help, reboots continued and memory dumps are not created. I have automatic memory dump creation, disabled overwriting old dumps and disabled deleting dumps if there is not enough memory. Is there any way to keep memory dumps after reboot so that you can track down what the problem is?

 

[johnbl]

Reinstalling windows didn't help, reboots continued and memory dumps are not created. I have automatic memory dump creation, disabled overwriting old dumps and disabled deleting dumps if there is not enough memory. Is there any way to keep memory dumps after reboot so that you can track down what the problem is?

make sure you have space on your drive, make sure there is a pagefile.sys. google how to force a memory dump using a keyboard. make the registry change and then force a memory dump on a working system to make sure the file is created.

update the bios and cpu chipset drivers.
write down the bugcheck code if it only is on the screen.
if you have a sata drive see if you have a option in bios to enable hotswap for the drive sata port. if the drive disconnects then it will be able to reconnect,

scan your drive for *.dmp files sometimes they get moved by windows live error reporting.
generally, would be looking for a power or overheating problem.
make sure your bios is updated and motherboard vendors updated drivers are installed. Do not install the utilities. some drivers need to match the running service version and the bios version. old bios with updated drivers and service can produce a bugcheck.
https://www.gigabyte.com/Motherboard/B550M-AORUS-ELITE-rev-13/support#support-dl-bios

looks like bios update is sept 2024
chipset driver update jan 2024
amd raid driver Jan 17, 2025

if you use a utility to install the bios, you should uninstall the utility after you do the update.

 

[ubuysa]

Reinstalling windows didn't help, reboots continued and memory dumps are not created. I have automatic memory dump creation, disabled overwriting old dumps and disabled deleting dumps if there is not enough memory. Is there any way to keep memory dumps after reboot so that you can track down what the problem is?

No, those settings are not right. For dumps to be written all of the following must be true...

• The page file must be on the same drive as your operating system
• Set page file size to "system managed"
• Set system crash/recovery options to "Automatic memory dump"
• The "Overwrite any existing file" box must be checked
• The "Write an event to the system log" must be checked
• The dump file location must be %SystemRoot%\MEMORY.DMP
• Windows Error Reporting (WER) system service must be set to MANUAL
• User account control must be running

In addition, the following can also prevent you seeing dumps...

• SSD drives with older firmware may not create dumps (update the drive firmware)
• Cleaner applications like Ccleaner delete dump files, so don't run them until you are fixed
• Bad RAM may prevent the data from being saved and written to a file on reboot, so if all else fails test your RAM

 

[Ziwer9]

No, those settings are not right. For dumps to be written all of the following must be true...

• The page file must be on the same drive as your operating system
• Set page file size to "system managed"
• Set system crash/recovery options to "Automatic memory dump"
• The "Overwrite any existing file" box must be checked
• The "Write an event to the system log" must be checked
• The dump file location must be %SystemRoot%\MEMORY.DMP
• Windows Error Reporting (WER) system service must be set to MANUAL
• User account control must be running

In addition, the following can also prevent you seeing dumps...

• SSD drives with older firmware may not create dumps (update the drive firmware)
• Cleaner applications like Ccleaner delete dump files, so don't run them until you are fixed
• Bad RAM may prevent the data from being saved and written to a file on reboot, so if all else fails test your RAM

Thanks for the advice. I did everything and the memory dumps started to be saved.
But a new problem appeared:
after reinstalling Windows twice (after the first reinstallation there was a reboot, but I did not save the dump, and then I turned on the raid mode for the SSD on which the OS is located and this broke everything and I had to reinstall Windows again) for 4 days everything worked stably, but when the following Windows updates arrived:
1) KB5051974
2) KB5050188
3) KB5027937
then after turning off the PC with the installation of these updates I get a blue screen with the following error line "WHEA UNCORRECTABLE ERROR" and after an automatic reboot the PC gets stuck on an endless installation of updates or constantly reboots with this error. I got rid of this error by starting the PC in safe mode and the installation of these updates was canceled and I could start the PC normally until the next shutdown (the error appears even if I turn off the PC without installing updates).
I also got a message that said there were problems installing updates and the error code (0x80070057).
I also attach a link to the latest memory dump https://drive.google.com/file/d/1xvmdvax5MPOPKSNoomoYLdYk93hW68w9/view
Can you please help with this problem?

 

[ubuysa]

If the problem persists after a clean reinstall (or two) then it's a hardware issue. The WHEA bugcheck also supports that - WHEA is the Windows Hardware Error Architecture.

The dump suggests that the problem might be RAM. In the call stack leading up to the BSOD (which you read from the bottom up) we see a memory function call, followed by a machine check exception - that's the beginning of the BSOD...

15: kd> k
 # Child-SP          RetAddr               Call Site
00 ffff9000`53967948 fffff800`138ba79a     nt!KeBugCheckEx
01 ffff9000`53967950 fffff800`0f2a15b0     nt!HalBugCheckSystem+0xca
02 ffff9000`53967990 fffff800`139bcaed     PSHED!PshedBugCheckSystem+0x10
03 ffff9000`539679c0 fffff800`138bc0c1     nt!WheaReportHwError+0x3dd
04 ffff9000`53967a90 fffff800`138bc433     nt!HalpMcaReportError+0xb1
05 ffff9000`53967c00 fffff800`138bc310     nt!HalpMceHandlerCore+0xef
06 ffff9000`53967c50 fffff800`138bb855     nt!HalpMceHandler+0xe0
07 ffff9000`53967c90 fffff800`138be015     nt!HalpHandleMachineCheck+0xe9
08 ffff9000`53967cc0 fffff800`13913bd9     nt!HalHandleMcheck+0x35
09 ffff9000`53967cf0 fffff800`1380f97a     nt!KiHandleMcheck+0x9
0a ffff9000`53967d20 fffff800`1380f637     nt!KxMcheckAbort+0x7a
0b ffff9000`53967e60 fffff800`138036d0     nt!KiMcheckAbort+0x277     <--- And here is the failure
0c ffffc98c`71ebeac8 00000000`00000000     nt!KeCopyPage+0x50       <--- Here is the problem

If we take a look at that failing CopyPage function we see the problem...

15: kd> .frame /r c
0c ffffc98c`71ebeac8 00000000`00000000     nt!KeCopyPage+0x50
rax=fffffffffffffe80 rbx=ffffd108fe400000 rcx=ffffeccec112d000
rdx=ffffd108fed38800 rsi=ffff810018221be0 rdi=ffffb70e959379c0
rip=fffff800138036d0 rsp=ffffc98c71ebeac8 rbp=0000000000000004
 r8=0000007ffffffff8  r9=0000000000000000 r10=ffff840000005170
r11=ffffc98c71ebea60 r12=000000000080df17 r13=0000000000938800
r14=0000000000937800 r15=ffffeccec112c000
iopl=0         nv up ei pl nz ac po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00000216
nt!KeCopyPage+0x50:
fffff800`138036d0 0f280402        movaps  xmm0,xmmword ptr [rdx+rax] ds:002b:ffffd108`fed38680=????????????????????????????????

This MOVAPS instruction (an aligned move instruction) uses the RDX and RAX registers as memory pointers but the resulting memory address is invalid. The contents of the RDX and RAX registers look reasonable, as does the resulting address, but the ? characters show that it is invalid (not allocated, paged-out, not aligned, or bad). Since this is a Windows function we can discount all but bad RAM.
I would now suggest a RAM test with Memtest86....

1. Download Memtest86 (free), use the imageUSB.exe tool extracted from the download to make a bootable USB drive containing Memtest86 (1GB is plenty big enough). Do this on a different PC if you can, because you can't fully trust yours at the moment.
2. Then boot that USB drive on your PC, Memtest86 will start running as soon as it boots.
3. If no errors have been found after the four iterations of the 13 different tests that the free version does, then restart Memtest86 and do another four iterations. Even a single bit error is a failure.