Driver irq not less than or equal and ntoskrnl.exe?
Driver irq not less than or equal and ntoskrnl.exe?
Not long ago, I assembled a new PC using these parts:
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) CPU cooler
I also added storage drives from a previous system, one of which ran Windows and was fully functional. I kept working on it without reinstalling, just clearing old devices in the device manager and removing unused drivers—though I’m not certain all old drivers were removed.
The issue is that my PC would restart unexpectedly, without blue screens or memory dumps (only a few were saved). It could reboot every two weeks, four times in two days, or twice within less than an hour, regardless of actions taken. Even when idle with no programs running, it would restart. The most recent dump showed:
Bug Check String: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code: 0x000000d1
Memory dumps from deleted files contained:
Bug Check String: APC_INDEX_MISMATCH
Bug Check Code: 0x00000001
Crash address: ntoskrnl.exe
I turned off all hardware acceleration (video cards, disabled XMP profiles), reset the motherboard to factory settings, removed any apps that might influence system behavior (except the Gigabyte System Info viewer for fan tuning), checked memory with Windows tools, and used memtest86. I also tried creating a dump with Driver Verifier, but no dumps were produced, even though the settings suggested saving new ones without overwriting old ones.
Could you assist in resolving this? I’m ready to share the latest memory dump and a screenshot of the BlueScreenView image (link provided).
Welcome to the forums, newcomer!
I also added storage devices from a previous PC and one had Windows already running and functioning. I kept working on it without reinstalling—just cleared old entries in the device manager and removed unused drivers, though I’m not entirely sure if all old drivers were gone.
The issue is that my PC suddenly restarts.
Can you assist in resolving this?
Your situation is that you didn’t reinstall the operating system after moving an older drive. Right now, you should back up all essential data, create a bootable USB for your OS, and install it offline using only the drive you want to use. Also, download any required drivers ahead of time so you can install them via an elevated command once the OS is set up.
It seems you're seeking guidance on troubleshooting a recurring issue. It might be useful to explore additional sources beyond reinstalling the OS, especially if reboots continue to occur.
As previously mentioned, when Windows installs it it sets itself up for the hardware it's being installed on. You've now started a Windows system that was tailored for another platform.
You cannot solve your issue by looking at other people's experiences since the systems aren't the same. You really need to proceed with a clean installation from bootable media (not a Windows Reset) so you obtain a fresh Windows system suited for this platform. Only then will anyone be able to troubleshoot it effectively.
Reinstalling windows didn't resolve the issue, reboots persisted and no memory dumps were generated. Automatic memory dump creation remains enabled, but overwriting old dumps and deleting dumps when memory is insufficient are disabled. Is there a method to ensure memory dumps continue after a reboot so you can identify the problem?
Check if there’s enough space on your drive and ensure *pagefile.sys* is present. Research methods to force a memory dump via keyboard input. Modify the registry settings and then initiate a memory dump on a functional system to verify creation of the file. Update the BIOS and CPU chipset drivers accordingly. Record the bugcheck code if it appears only on the screen. For SATA drives, check if the BIOS offers an option to enable hot-swap for the drive port; reconnecting should resolve disconnection issues. Periodically scan drives for *.dmp files, as Windows Live error reporting can relocate them. Typically, investigate power or overheating concerns. Confirm your BIOS is current and that motherboard vendors have updated drivers installed. Avoid installing third-party utilities—ensure compatibility between service and BIOS versions. Updated BIOS with new drivers can trigger a bugcheck.
Here’s your message rewritten:
Thank you for your guidance. I completed all the steps and memory dumps began to be saved. However, a new issue emerged:
after reinstalling Windows twice (the first install caused a reboot, but I didn’t save the dump; later I enabled RAID on the SSD where the OS is stored, which caused everything to fail and required another Windows reinstall), for four days everything functioned smoothly. But once the subsequent updates arrived:
1) KB5051974
2) KB5050188
3) KB5027937
after turning off the PC with these updates installed, I encountered a blue screen displaying the error "WHEA UNCORRECTABLE ERROR." After an automatic restart, the PC became stuck in an endless update process or repeatedly rebooted due to this issue. I resolved it by booting in safe mode, which stopped the update installation and allowed me to continue until the next shutdown (the error still appears even when I turn off the PC without updates).
I also received a notification stating there were problems installing the updates, with error code 0x80070057.
Please find the latest memory dump here:
https://drive.google.com/file/d/1xvmdvax...W68w9/view
If the issue continues even after a fresh installation (or two), it likely points to a hardware fault. The WHEA bugcheck confirms this by identifying WHEA as the Windows Hardware Error Architecture.
The dump indicates a possible RAM problem. In the call stack preceding the BSOD (read from bottom to top), we observe a memory function call, followed by a machine exception check—this marks the start of the BSOD...
Rich (BB code):
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
Examining the failing CopyPage function reveals the issue...
Rich (BB code):
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 instruction (aligned move) relies on RDX and RAX as pointers, yet the memory location is invalid. Although the data appears valid and the address seems correct, the '?' indicates it's not properly allocated or is misaligned—making RAM failure likely.
Given this, I recommend running a RAM test using Memtest86...
Download
Memtest86 (free)
Use the extracted imageUSB.exe tool on a USB drive to create a bootable installation of Memtest86 (1GB should suffice).
Perform this on another machine if possible, as your current system is unreliable.
After rebooting with the USB, Memtest86 will begin scanning immediately.
If no issues appear after completing the 13 tests in the free version, restart Memtest86 and repeat four more times.
Even a single bit error will trigger a failure.
Thanks for the advice
I conducted a memory test for my two memory kits
1) 4x8GB, as described at the start
2) 2x16GB, which I purchased about six months after setting up the PC, following recommendations and hoping it would assist. I also used this kit before reinstalling Windows and after reinstalling before checking the memory.
Both kits successfully passed 4 times 4 iterations with no errors detected. I even acquired another 4x16GB kit from ADATA and experienced a reboot after a few hours of use while playing. No memory dump was generated, although I did not alter any settings.
Could the issue lie with the SSD where the system is installed? The SSD is relatively new, around 2-3 years old.
Could the problem stem from the power supply? I tested it using OSCT for an hour and found no errors or reboots, though perhaps the test was insufficient.
Could this error be related to recent system updates or other software, or is it purely a hardware concern?