Driver irql not less

Содержание

Name already in use
windows-driver-docs / windows-driver-docs-pr / debugger / bug-check-0xd1—driver-irql-not-less-or-equal.md
Синий экран ndis.sys в Windows 10, 8.1 и Windows 7 — как исправить
Исправление ошибки ndis.sys 0x000000d1
Дополнительные методы исправления ошибки
7 Solutions to Fix IRQL_NOT_LESS_OR_EQUAL Windows 10 [MiniTool Tips]
The Reason for IRQL_NOT_LESS_OR_EQUAL Windows 10
BSOD ВО ВРЕМЯ СТРИМА ! СИНИЙ ЭКРАН СМЕРТИ NDIS.SYS ! Ошибка Driver irql not less or equal
Seven Solutions to Fix IRQL_NOT_LESS_OR_EQUAL Windows 10
Ошибка загрузки Windows 11 с черным экраном DRIVER_IRQL_NOT_LESS_OR_EQUAL
Цикл «Сделай сам»: BSOD 0x000000d1 или driver irql not less or equal
- Solution 7: Reset This PC
Useful Suggestion
Conclusion
IRQL_NOT_LESS_OR_EQUAL Windows 10 FAQ
About The Author
- Похожие статьи

Step 5: Now you just have to wait for the computer to detect the problems. After the scanning process is completed, if there is an error, it will be displayed. And then please select the problem you want to fix.

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?

Cancel Create

windows-driver-docs / windows-driver-docs-pr / debugger / bug-check-0xd1—driver-irql-not-less-or-equal.md

Go to file T
Go to line L
Copy path
Copy permalink

This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Cannot retrieve contributors at this time
162 lines (111 sloc) 7.92 KB

Open with Desktop
View raw
Copy raw contents Copy raw contents Copy raw contents

Copy raw contents

Bug Check 0xD1 DRIVER_IRQL_NOT_LESS_OR_EQUAL

The DRIVER_IRQL_NOT_LESS_OR_EQUAL bug check has a value of 0x000000D1. This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.

Bug Check 0xD1 DRIVER_IRQL_NOT_LESS_OR_EQUAL
DRIVER_IRQL_NOT_LESS_OR_EQUAL
DRIVER_IRQL_NOT_LESS_OR_EQUAL

Bug Check 0xD1: DRIVER_IRQL_NOT_LESS_OR_EQUAL

The DRIVER_IRQL_NOT_LESS_OR_EQUAL bug check has a value of 0x000000D1. This indicates that a kernel-mode driver attempted to access pageable memory while the process IRQL that was too high.

[!IMPORTANT] This topic is for programmers. If you are a customer who has received a blue screen error code while using your computer, see Troubleshoot blue screen errors.

IRQL at time of reference.

Address that referenced memory. Use ln (list nearest symbols) on this address to see the name of the function.

To determine the cause requires the Windows debugger, programming experience and access to the source code for the faulting module.

Typically, when this error occurs, a driver has tried to access an address that is pageable (or that is completely invalid) while the interrupt request level (IRQL) was too high. This can be caused by:

Dereferencing a bad pointer (such as a NULL or freed pointer) while executing at or above DISPATCH_LEVEL.
Accessing pageable data at or above DISPATCH_LEVEL.
Executing pageable code at or above DISPATCH_LEVEL.

If a driver that is responsible for the error can be identified, its name is printed on the blue screen and stored in memory at the location (PUNICODE_STRING) KiBugCheckDriver. You can use dx (display debugger object model expression), a debugger command, to display this: dx KiBugCheckDriver.

This bug check is usually caused by drivers that have used improper memory addresses.

Possible causes for the page fault include the following events:

The function was marked as pageable and was running at an elevated IRQL (which includes obtaining a lock).
The function call was made to a function in another driver, and that driver was unloaded.
The function was called by using a function pointer that was an invalid pointer.

For more information on Windows IRQLs, see Windows Internals 7th Edition Part 1 by Pavel Yosifovich, Mark E. Russinovich, David A. Solomon and Alex Ionescu.

If the problem is caused by the driver that you are developing, make sure that the function that was executing at the time of the bug check is:

Not marked as pageable
Does not call any other inline functions that could be paged out.

The !analyze debugger extension displays information about the bug check and can be helpful in determining the root cause. The following example is output from !analyze.

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) 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 kernel debugger is available get stack backtrace. Arguments: Arg1: fffff808add27150, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, value 0 = read operation, 1 = write operation Arg4: fffff808adc386a6, address which referenced memory

If a driver that is responsible for the error can be identified, its name is printed on the blue screen and stored in memory at the location (PUNICODE_STRING) KiBugCheckDriver. You can use dx (display debugger object model expression), a debugger command, to display this: dx KiBugCheckDriver .

0: kd> dx KiBugCheckDriver KiBugCheckDriver : 0xffffc6092de892c8 : "Wdf01000.sys" [Type: _UNICODE_STRING *]

If a trap frame is available in the dump file, use the .trap command to set your context to the provided address.

In the debugger, run the !irql command to display information about the IRQL of a processor on the target computer before the debugger break. For example:

0: kd> !irql Debugger saved IRQL for processor 0x0 -- 2 (DISPATCH_LEVEL)

In the majority of cases of this type of bug check, the issue is not the IRQL level, but rather the memory that is being accessed.

Because this bug check is usually caused by drivers that have used improper memory addresses, use parameters 1, 3, and 4 to investigate further.

Use ln (list nearest symbols) with parameter 4 to see the name of the function that was called. Also examine the !analyze output to see if faulting code is identified.

Use !pool on the parameter 1 address to see whether it is paged pool. Use !address and the advanced !pte command to learn more about this area of memory.

Use the display memory commands to examine the memory referenced in command in parameter 1.

Use the u, ub, uu (unassemble) commands to look at the code in the address which referenced the memory in parameter 4.

Use the command lm t n to list modules that are loaded in the memory. Use !memusage and to examine the general state of the system memory.

Driver Verifier is a tool that runs in real time to examine the behavior of drivers. For example, Driver Verifier checks the use of memory resources, such as memory pools. If it identifies errors in the execution of driver code, it proactively creates an exception to allow that part of the driver code to be further scrutinized. Driver Verifier Manager is built into Windows and is available on all Windows PCs.

To start Driver Verifier Manager, type verifier at a command prompt. You can configure which drivers to verify. The code that verifies drivers adds overhead as it runs, so try to verify the smallest number of drivers possible. For more information, see Driver Verifier.

If you are not equipped to use the Windows debugger to work on this problem, you can use some basic troubleshooting techniques.

Check the System Log in Event Viewer for additional error messages that might help identify the device or driver that is causing this bug check.
If a driver is identified in the bug check message, disable the driver or check with the manufacturer for driver updates.
Confirm that any new hardware that is installed is compatible with the installed version of Windows. For example, you can get information about required hardware at Windows 10 Specifications.

For additional general troubleshooting information, see Blue screen data.

Синий экран ndis.sys в Windows 10, 8.1 и Windows 7 — как исправить

Исправление ошибки ndis.sys 0x000000d1

Наиболее частыми причинами синего экрана (BSoD) DRIVER_IRQL_NOT_LESS_OR_EQUAL ndis.sys являются неправильная работа драйверов сетевой карты или влияние стороннего ПО на их работу, в частности, это может быть сторонний антивирус. В списке ниже — способы исправления проблемы от более простых к более сложным:

При наличии точек восстановления системы на дату, предшествующую появлению ошибки, попробуйте использовать их, см. Точки восстановления Windows 10 (для предыдущих версий ОС всё то же самое).
Загляните в диспетчер устройств, откройте свойства используемой сетевой карты и проверьте, активна ли кнопка «Откатить» на вкладке «Драйвер». Если да — попробуйте использовать её.
Если проблема появилась после установки новой версии Windows 10 (после «большого» обновления), а на вашем компьютере находился сторонний антивирус, попробуйте полностью удалить его (лучше использовать утилиту удаления от разработчика антивируса), обязательно перезагрузить компьютер и посмотреть, возникает ли ошибка снова. Если нет — можно установить антивирус повторно, синий экран не должен появиться снова. Сбои в работе антивирусов после обновления компонентов Windows 10 — достаточно распространенная вещь.
В случае, если вы устанавливали на компьютер какие-либо программы для работы с VPN/Прокси и прочей анонимизации в сети, попробуйте отключить или удалить их и проверить, исправит ли это проблему.
Перезагрузите компьютер в безопасном режиме (см. Как зайти в безопасный режим Windows 10), откройте диспетчер устройств и удалите сетевые адаптеры. Затем в диспетчере устройств в меню выберите «Действие» — «Обновить конфигурацию оборудования» и дождитесь переустановки драйверов. Перезагрузите компьютер в обычном режиме.
Если проблема появилась после чистой установки системы на компьютер и последующей установки драйверов (особенно с помощью различных драйвер-паков), не поленитесь и скачайте драйвер сетевой карты или Wi-Fi адаптера с официального сайта производителя материнской платы (если у вас ПК) или ноутбука, именно для вашей модели. А затем вручную установите его, даже если диспетчер устройств сообщает, что драйвер не нуждается в обновлении, а на официальном сайте драйвер только для предыдущей версии ОС.
Если на вашем компьютере установлена Windows 10 и ранее она работала без ошибки, попробуйте выполнить автоматический сброс сетевых настроек.
Если недавно вы устанавливали виртуальные машины (например, VirtualBox) и соответствующие им виртуальные сетевые адаптеры, это может послужить причиной ошибки ndis.sys, попробуйте удалить виртуальный сетевой адаптер.

Обычно, один из приведенных методов позволяет избавиться от синего экрана, вызываемого ndis.sys, но не всегда.

В случае, если вышеописанные способы не помогли, попробуйте использовать дополнительные подходы, в редких случаях они помогают.

Дополнительные методы исправления ошибки

Используйте встроенное устранение неполадок сети (если еще не делали этого). Как именно описывалось в инструкции Устранение неполадок Windows 10 (способ с панелью управления работает и для предыдущих версий).
Попробуйте выполнить проверку целостности системных файлов Windows.
По некоторой информации (не могу подтвердить или опровергнуть) ошибка может быть вызвана сбоями файловой системы на диске, попробуйте выполнить проверку жесткого диска на ошибки.

А вдруг и это будет интересно:

Лучшие бесплатные программы для Windows
WinfrGUI — бесплатное восстановление данных с использованием Windows File Recovery
Как включить секунды на часах Windows 11 и Windows 10
Не удалось обнаружить правильно установленный сетевой адаптер — как исправить?
Пропал звук Windows 11 — как исправить?
Рабочий стол в OneDrive — почему и как вернуть в обычное расположение?

Windows 11
Windows 10
Android
Загрузочная флешка
Лечение вирусов
Восстановление данных
Установка с флешки
Настройка роутера
Всё про Windows
В контакте
Одноклассники

Dmitry 30.04.2019 в 09:31

7 Solutions to Fix IRQL_NOT_LESS_OR_EQUAL Windows 10 [MiniTool Tips]

A blue screen suddenly appears on the screen with IRQL_NOT_LESS_OR_EQUAL. What should you do to solve this problem when this happened? This article will provide seven ways that might make your PC run normally.

The Reason for IRQL_NOT_LESS_OR_EQUAL Windows 10

When a blue screen suddenly appears on your computer with IRQL_NOT_LESS_OR_EQUAL displayed, you may be wondering why this information appears. Below I will list some of the reasons that may cause the issue IRQL_NOT_LESS_OR_EQUAL.

BSOD ВО ВРЕМЯ СТРИМА ! СИНИЙ ЭКРАН СМЕРТИ NDIS.SYS ! Ошибка Driver irql not less or equal

Tip: If you lost data because IRQL_NOT_LESS_OR_EQUAL error, then you can try MiniTool software to recover your data.

The system file is damaged. System file corruption may be caused by a virus attack or malware infection of a Windows system file or a Windows operating system related program file.
The driver is not compatible. After installing the new hardware, its driver conflicts with the previous driver, resulting in BSOD.
The CPU is overheated. When the CPU is above a certain temperature, the computer will immediately shut down via BSOD to avoid damage to the CPU.
Windows updates or downgrades to install Windows. Windows updates or downgraded installations may cause system files to be improperly replaced, and conflicts between different versions of Windows.
There is a problem with the hardware. Such as motherboard or RAM is damaged
Corrupted registry. The recent installation or uninstallation of the software may result in registry corruption.
The software is not installed correctly.

Seven Solutions to Fix IRQL_NOT_LESS_OR_EQUAL Windows 10

After understanding what causes IRQL_NOT_LESS_OR_EQUAL Windows 10, what should be done to solve this problem? Below I will provide seven ways to fix RQL_NOT_LESS_OR_EQUAL error.

Note: Before fixing IRQL_NOT_LESS_OR_EQUAL Windows 10, I strongly recommend that you back up important data in advance to prevent data loss during the operation.

Solution 1: Uninstall Malware

If IRQL_NOT_LESS_OR_EQUAL error occurs after you install a piece of software, it is most likely because there is a virus on that software that causes the computer to have a blue screen. So you can take the method of uninstalling this software to see if it can solve this problem.

Step 1: Please click Settings from the Start menu to continue.

Step 2: Please click Apps on the Settings page to continue.

Step 3: Please click Apps & features and set sort by Install date in the right to continue.

Step 4: Please select the app and click Uninstall.

If you uninstall the recently installed software and still get IRQL_NOT_LESS_OR_EQUAL error, then you can try the following method.

Solution 2: Keep Your Computer Cool

The computer generates a lot of heat when it runs. If your computer accessories don’t remove the hot air from the computer as soon as possible, it will cause the CPU temperature to be too high, so you need to take steps to cool your computer. Below I will provide several ways to reduce the temperature of your computer.

Upgrade the CPU fan. If the CPU fan performance is not high, the heat generated by the computer cannot be eliminated in time.
Install another fan. A fan may not solve your CPU overheating problem, so installing more than one fan will work.
Install the Water Cooling Kit. If your computer is configured too much and the fan can’t solve the problem of too high CPU temperature, you can install the water cooling kit. This is a very safe accessory, and you don’t need to worry about damaging your computer.

This way doesn’t repair IRQL_NOT_LESS_OR_EQUAL error? Then you need to try next method.

Solution 3: Run Windows Memory Diagnostic Tool

The IRQL_NOT_LESS_OR_EQUAL Windows 10 error is displayed on the computer screen. There may be a problem with the RAM, so you will need to check the RAM. So how do you check if the RAM is wrong? You can run the Windows Memory Diagnostics.

Here’s the way of how to check if the RAM is wrong.

Step 1: Type Memory Diagnostic in the search box and click on Windows Memory Diagnostic to continue.

Step 2: Click Restart now and check for problems (recommended).

Note: Please pay attention to save your tasks and close all windows before rebooting.

You need to wait for the computer to find the problems for a period of time. After the search is completed, the computer will display the detected problem on the screen.

If you don’t see the problem, try the following method.

Solution 4: Update Driver

When the drive is incompatible, it is possible that a drive has not been upgraded to the latest version, causing a conflict between the drives and a blue screen. So if you want to solve IRQL_NOT_LESS_OR_EQUAL error, it is a good idea to update the driver.

Here’s how to update your driver.

Step 1: Please open File Explorer and right-click This PC to continue.

Step 2: Please choose Manage to continue.

Step 3: Please choose Device Manager under System Tools option to continue.

Step 4: Please right-click the disk device under Disk Drives, then please choose Update driver.

When the process is finished, reboot your computer to check if the error is solved. If it still occurs, try the next method.

Solution 5: Run Hardware Troubleshooter

Hardware errors can also cause IRQL_NOT_LESS_OR_EQUAL error, so you can try running the Troubleshooter to check if there is a problem with your hardware.

You can run the troubleshooter by following the steps.

Step 1: Please click Settings from the Start menu to continue.

Step 2: Please click Update & security on the Settings page to continue.

Step 3: Please click Troubleshoot and choose Hardware and Devices in the right to continue.

Step 4: Please click Run the troubleshooter to continue.

Step 5: Now you just have to wait for the computer to detect the problems. After the scanning process is completed, if there is an error, it will be displayed. And then please select the problem you want to fix.

If the computer does not detect any problems, then it may not be a hardware problem, you may need to try the following method.

Solution 6: Run Driver Verifier

When the IRQL_NOT_LESS_OR_EQUAL error occurs, it can also be solved by running Driver Verifier, but this method is more suitable for professionals to operate.

Below I will show you how to run Driver Verifier.

Warning: Create a system restore point before running this tool to avoid unrecoverable operations.

Step 1: Please enter cmd in the search box and choose the best matched one. Then right-click it to choose Run as administrator to continue.

Step 2: Please enter verifier in the Command Prompt window and press Enter to continue.

Step 3: Please choose Create standard settings and click Next to continue.

Ошибка загрузки Windows 11 с черным экраном DRIVER_IRQL_NOT_LESS_OR_EQUAL

Tip: If you are code developers, you can choose Create custom settings (for code developers).

Step 4: Please select what drivers to verify and then click Next to continue.

Note: I suggest you check Select driver names from a list to view all the drivers installed on your computer.

Step 5: Please select drivers to verify at first and then click Finish.

Цикл «Сделай сам»: BSOD 0x000000d1 или driver irql not less or equal

After that, you have to restart your computer and then Windows will place extra stress on your drivers to help you solve the problem.

Note: If the blue screen keeps flashing, please go into safe mode to do these things.

If this method doesn’t work, then you can try the following solution.

Solution 7: Reset This PC

If you have tried the above method, and you don’t know what the cause of the error is, then you can try resetting the computer. Resetting your computer allows you to save your personal files or erase them. And it’s really convenient and efficient.

Step 1: Please click Update & Security on the Settings page to continue.

Step 2: Please click Recovery and click Get Started on the right to continue.

Step 3: Please choose whether to Keep my files or Remove everything to reset your PC.

Step 4: Please read the subsequent messages and click Reset.

This method will take some time to fix your computer, so please be patient. And if this method doesn’t work this problem out, you need to reinstall your operating system.

Useful Suggestion

In order to avoid system failures and data loss when irql_not_less_or_equal error or other errors occur, I recommend that you back up your operating system and data regularly after solving the problem.

So how to safely and easily back up the operating system? I highly recommend using professional backup software — MiniTool ShadowMaker. It can not only back up files, folders, but also backup partitions, disks and operating system. In addition, MiniTool ShadowMaker can safely sync your files to two or more locations.

So why not download MiniTool ShadowMaker and have a try?

I will show how to back up Windows 10 by MiniTool ShadowMaker.

Step 1: Download, install and launch MiniTool ShadowMaker.

Note: If you want to manage a remote computer, computers need to be on the same LAN and you also need another computer’s IP address.

Step 2. Click Keep Trial and go to the Backup page.

Step 3: MiniTool ShadowMaker backs up the Windows operating system and chooses destination by default. But if you want to change destination, you can click DESTINATION to select the destination path.

Step 4: As you can see, MiniTool ShadowMaker supports you to back up data to five different paths. Then please choose a path as the location then click OK.

If you want to back up your files regularly, please go to Options >Schedule Settings.
If you want to manage the space occupied by the backed up files by deleting the specified backup image file versions, please click Backup Scheme.
If you want to set more advanced backup parameters, please click Backup Options.

Step 5: Please click Back Up Now or Back Up Later then click Yes.

Tip: If you click Back Up Later, you need to click Back Up Now to restart the backup task on the Manage page.

You can back up Windows 10 by these steps.

In order to prevent the computer from malfunctioning, I recommend that you use MiniTool ShadowMaker to create bootable media so that you can boot the computer from the bootable media to restore the system.

Conclusion

In the process of using the computer, if you encounter a blue screen, it is really annoying. And as you can see from this article, there are many reasons for RQL_NOT_LESS_OR_EQUAL Windows 10 on the computer, but you can try the seven methods provided in this article to solve this problem.

If you find other causes that cause RQL_NOT_LESS_OR_EQUAL error and other ways to resolve it, you can leave a comment below, or send an email to [email protected] .

IRQL_NOT_LESS_OR_EQUAL Windows 10 FAQ

What is the IRQL_NOT_LESS_OR_EQUAL?

IRQL_NOT_LESS_OR_EQUAL is one of the Stop errors and often companied with blue screen. When the error occurs, then it means there is something wrong with your drivers, the Windows Service becomes bad because of antivirus software or other causes.

How do I fix IRQL_NOT_LESS_OR_EQUAL?

There are 7 methods you can take to fix the IRQL_NOT_LESS_OR_EQUAL error, which are shown below:

Uninstall malware.
Keep your computer cool.
Run Windows Memory Diagnostic tool.
Update Driver.
Run Hardware Troubleshooter.
Run Driver Verifier.
Reset this PC.

What causes IRQL_NOT_LESS_OR_EQUAL?

There are several different causes of the IRQL_NOT_LESS_OR_EQUAL error, and some of them are shown below:

Damaged system files.
Incompatible drivers.
Overheated CPU.
Corrupted registry.
Hardware issues.
Incorrect software installation.
Windows updates or a downgrade to lower version of Windows.

What causes blue screen Windows 10?

You may meet blue screen on Windows 10 when there is something wrong with your hardware or your devices’ drivers. And if you want to find some methods to fix blue screen, then you should read this post — Windows 10 Blue Screen of Death – You Can Quickly Fix It.

Facebook
Twitter
Linkedin
Reddit

About The Author

Author Sonya has been engaged in editing for a long time and likes to share useful methods to get rid of the common problems of Windows computers, such as Windows Update error. And she aims to help more people to protect their data. What’s more, she offers some useful ways to convert audio and video file formats. By the way, she likes to travel, watch movies and listen to music.