Skip to content

Published: April 21, 2016 | Applies to:

This article will help you to fix DRIVER_IRQL_NOT_LESS_OR_EQUAL stop error/BSOD in Windows 10 by safely removing the faulty driver.

When a driver in Windows reaches a stage that it can no longer work properly, it causes a stop error aka Blue Screen of Death (BSOD). This will crash the machine and wherever you’re, whatever you’re doing, everything on session will be lost as the system reboots itself to recover from this stop error.

In our series of BSOD errors for Windows 10, we’re today going to discuss DRIVER_IRQL_NOT_LESS_OR_EQUAL stop error we recently came around. The moment when this error occurs, your system will display this message:

Your PC ran into a problem that it couldn’t handle, and now it needs to restart.

You can search for the error online: DRIVER_IRQL_NOT_LESS_OR_EQUAL (epfwwfp.sys)

FIX - DRIVER_IRQL_NOT_LESS_OR_EQUAL BSOD In Windows 10

Here, epfwwfp.sys term in the message is variable and actually represents the driver name, which has caused this error. This can be also treated as a hint to solve this problem because if you know the faulty driver name, you just have to remove it and the issue will get resolved.

When you see this stop error for the very first time, you should go ahead with these general troubleshooting steps and see if the problem can be suppressed with them:

In case if issue still persists after trying these suggestions, follow these steps:

FIX : DRIVER_IRQL_NOT_LESS_OR_EQUAL BSOD In Windows 10

1. Boot into System Recovery Options. Hit the Command Prompt entry at following screen:

FIX - DRIVER_IRQL_NOT_LESS_OR_EQUAL BSOD In Windows 10

2. Previous step will result in opening of Command Prompt at boot.

FIX - DRIVER_IRQL_NOT_LESS_OR_EQUAL BSOD In Windows 10

3. Select your admin account and enter your selected account password to continue.

FIX - DRIVER_IRQL_NOT_LESS_OR_EQUAL BSOD In Windows 10

4. Now in the Command Prompt window, type following command and press Enter key:

DEL /F /S /Q /A "C:\Windows\System32\drivers\<DRIVER NAME>"

*Substitute C: with your system root drive and <DRIVER NAME> with faulty driver name in you case. For example, if the driver name is epfwwfp.sys, we would run DEL /F /S /Q /A “C:\Windows\System32\drivers\epfwwfp.sys” command.

FIX - DRIVER_IRQL_NOT_LESS_OR_EQUAL BSOD In Windows 10

Close the Command Prompt and Continue to your operating system.

5. Since you’ve deleted faulty driver in previous step, you would be able to boot Windows normally. Now your next target is reinstall the updated version of same driver but you’ll need detailed information about it. For this, go to driver’s directory created by BSOD experts and Microsoft MVPs:

Click here to visit driver’s directory

6. On the directory page, search for the same driver name which was mentioned in original stop error message. You’d be able to locate its vendor (refer screenshot below) and thus you can download driver from manufacturer’s site and hence reinstall it.

FIX - DRIVER_IRQL_NOT_LESS_OR_EQUAL BSOD In Windows 10

Hope this helps!


SHARE: Facebook Google+ Twitter

2 Comments

  • If the driver name mentioned at BSOD is a system driver like ntkrnlpa, removing that using cmd would make your computer not boot at all. You would then need to repair using a repair disk.
    So in short a dangerous advice

  • Kapil Arya

    ^^ It’s Windows Update related driver, and I believe there are very less chances that it will encounter such kind of BSOD errors. Thanks for advice though.

  • Leave a Reply

    Your email address will not be published. Required fields are marked *

    What's New


    Recent Comments

    • Kapil Arya : ^^ Happy to help ☺️...

      2 hours ago

    • frozen nerd : i also tried uninstalling avast, disabling all startup progr...

      5 hours ago

    • frozen nerd : i have a win 10 home OEM from ASUS tried this and got the ...

      6 hours ago

    • Darren : Thank you, Kapil! The first two netsh commands and reboot ju...

      7 hours ago

    • Charles : I followed your steps but got stuck at step 9 since I couldn...

      13 hours ago

    • Barry : Fantastic! You solved my problem with very clear instruction...

      14 hours ago


    Windows Group Policy Troubleshooting