Share via

How to get around DRIVER_IRQL_NOT_LESS_OR_EQUAL crashes?

Jan Schröer 25 Reputation points
2025-11-09T15:21:47.9433333+00:00

Since a few days I've been havng issues with random crashes / BSODs once or twice a day for no apparent reason. The Bug Check String is DRIVER_IRQL_NOT_LESS_OR_EQUAL and BlueScreenView says its caused by the driver tcpip.sys. ntoskrnl.exe is also marked red in BlueScreenView. Furthermore, when I check the windows events, I see that at any given time when the PC may crash, I get this warning:

"A provider, IntelMEProv, has been registered in the Windows Management Instrumentation namespace root\Intel_ME to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests."

I already tried updating all my drivers and even tried updating IntelMEProv as provided by Intel on their website, this did not resolve the Issue.

Here are the associated minidump files: https://1drv.ms/u/c/5757c152a8dd0bd2/EZjtPfjvquxJgLd0ZV5B9W4BZq1vBO4T4j38aZKxvpVgcQ?e=HqgA5a

PC Specs:

Radeon RX7800

Intel i5 14600K 14

2x16 GB G.Skill Flare X5 DDR5-6000

MSI Gaming Plus WIFI Intel B760 So.1700 DDR5 ATX Retail

2TB KIOXIA Exceria Plus G3 M.2 2280 PCIe 4.0 NVMe 1.4 3D-NAND TLC

.Dmp File says this:

==================================================

Dump File : 110525-10296-01.dmp

Crash Time : 05.11.2025 21:23:48

Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL

Bug Check Code : 0x000000d1

Parameter 1 : 00000000`00000028

Parameter 2 : 00000000`00000002

Parameter 3 : 00000000`00000000

Parameter 4 : fffff807`5d7f2ad1

Caused By Driver : tcpip.sys

Caused By Address : tcpip.sys+142ad1

File Description : TCP/IP-Treiber

Product Name : Betriebssystem Microsoft® Windows®

Company : Microsoft Corporation

File Version : 10.0.26100.6713 (WinBuild.160101.0800)

Processor : x64

Crash Address : ntoskrnl.exe+4f6430

Stack Address 1 :

Stack Address 2 :

Stack Address 3 :

Computer Name :

Full Path : C:\WINDOWS\Minidump\110525-10296-01.dmp

Processors Count : 20

Major Version : 15

Minor Version : 26100

Dump File Size : 7.728.422

Dump File Time : 05.11.2025 21:24:11

==================================================

Windows for home | Windows 11 | Performance and system failures
0 comments
Answer accepted by question author
  1. DaveM121 869.3K Reputation points Independent Advisor
    2025-11-09T15:58:32.8366667+00:00

    Your minidump files all indicate it is the Realtek Ethernet drivers causing your PC to crash.

    Go to the support page for your motherboard on the MSI website, then form there, download and re-install (not update) the version of Realtek Ethernet (LAN) drivers they provide.

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Q&A Assist
    2025-11-09T15:22:05.7133333+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The DRIVER_IRQL_NOT_LESS_OR_EQUAL error, with the bug check code 0x000000D1, typically indicates that a driver is trying to access a memory address that it should not. In your case, the crash is related to the tcpip.sys driver, which is responsible for TCP/IP networking in Windows.

    Here are some steps you can take to troubleshoot and potentially resolve the issue:

    1. Update Network Drivers: Ensure that all network drivers are up to date. Since you mentioned updating drivers, double-check that you have the latest version for your network adapter from the manufacturer’s website.
    2. Check for Windows Updates: Make sure your Windows operating system is fully updated. Sometimes, Microsoft releases patches that can fix underlying issues with drivers.
    3. Run Network Troubleshooter: Use the built-in Windows Network Troubleshooter to diagnose and fix network-related issues. You can find this in Settings > Update & Security > Troubleshoot > Additional troubleshooters > Network Adapter.
    4. Disable Third-Party Security Software: Temporarily disable any third-party antivirus or firewall software to see if it resolves the issue. Sometimes, these programs can interfere with network drivers.
    5. Check for Hardware Issues: Run hardware diagnostics to ensure there are no issues with your RAM or other components. Faulty hardware can sometimes cause driver-related crashes.
    6. Analyze Minidump Files: Since you have minidump files, you can analyze them using tools like WinDbg to get more insights into what might be causing the crash. Look for patterns or specific drivers that are mentioned in the dump files.
    7. Reinstall TCP/IP Stack: You can try resetting the TCP/IP stack using the command prompt. Run the following commands:
      • netsh int ip reset
      • netsh winsock reset
      • Restart your computer after running these commands.
    8. Check Event Viewer: Continue monitoring the Event Viewer for any additional warnings or errors that occur around the time of the crashes. This can provide more context on what might be causing the issue.

    If the problem persists after trying these steps, consider reaching out to Microsoft support or the community for further assistance.

    References:

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.