Share via

IRQL LESS OR NOT EQUAL BSOD, even in safe mode

Ghost Quartz 0 Reputation points
2026-02-03T09:19:24.13+00:00

I recently having a lot of bsod with various error messages. Recently a lot of "irql less or not equal"

My spec :

Asrock ab350 pro4

Ryzen 5 3600

Gtx 1060 6gb

8x2 2666 Ram

This pc is around 7 years old

Here's the minidump : https://www.mediafire.com/file/ns5f24qhy0h44i0/Mini.7z/file

Windows for home | Windows 10 | Windows update
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Alexandr S 103.7K Reputation points Independent Advisor
    2026-02-03T10:09:14.8+00:00

    Hello, Ghost Quartz.

    There are various errors in the dumps, but all are related to the failure of the nt OS kernel (ntkrnlmp.exe ). In most cases, this indicates damage/ modification of the kernel or the influence of third-party software. Please post here a screenshot of the Control Panel-Programs and Components window with a list of all installed programs. Also, take a screenshot of the task list from the Task Scheduler-Scheduler Library.

    0 comments
  2. Q&A Assist
    2026-02-03T09:19:34.3366667+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The "IRQL NOT LESS OR EQUAL" bug check (0x0000001A) typically indicates that Windows or a kernel-mode driver is trying to access paged memory at an invalid address while operating at a raised interrupt request level (IRQL). This can happen due to several reasons, including:

    1. Driver Issues: Outdated or incompatible drivers can cause this error. Ensure that all your drivers, especially for the graphics card and motherboard, are up to date.
    2. Hardware Issues: Faulty hardware, such as RAM or the motherboard, can lead to this BSOD. You might want to run hardware diagnostics to check for any issues.
    3. Memory Problems: Running the Windows Memory Diagnostics tool can help identify any memory-related issues.
    4. Overclocking: If your system is overclocked, reverting to default settings may help resolve the issue.
    5. System File Corruption: Corrupted system files can also lead to this BSOD. Running the System File Checker tool (sfc /scannow) can help repair any corrupted files.

    Since you mentioned that the issue persists even in Safe Mode, it suggests that the problem may be related to hardware or core system files rather than third-party drivers. If the problem continues, consider checking the minidump files for more specific errors related to the crash, which can provide insights into the exact cause.

    References:

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.