Windows 10 blue screen boot error DRIVER_IRQL_NOT_LESS_OR_EQUAL(epfwwfp.sys)

[someone_24]

Hi, I encountered this erro and I found a solution here: http://answers.microsoft.com/en-us/windows/forum/windows_10-power/windows-10-blue-screen-on-boot/2715181c-edc9-498f-aa69-76263a5a1086

but when I type the command in it says that the given route cannot be found (in free translation from my language)
Why is that? When I installed windows on my pc in december I didn't change anything. It was a clean install, everything should be on the C.

Can I avoid a reinstall? I don't want to lose my programs and games.. Would it delete the programs' folders in 'Documents'?

 

[someone_24]

I can't believe it... Everything is on the D.. Why is everything on the D?! Damnit. Nevermind, problem solved. If anybody has the same problem, visit the link in the description. By the way this problem occurs with ESET Smart Security antivirus so if you use it and you're about to upgrade, delete it.

 

[johnbl]

epfwwfp.sys = ESET Personal Firewall Driver a bugcheck caused by it will require that the software be updated OR your ethernet driver is out of date and should be updated (very common problem)
http://www.eset.com/int/download/home/

 

[tiggerkat1244]

epfwwfp.sys = ESET Personal Firewall Driver a bugcheck caused by it will require that the software be updated OR your ethernet driver is out of date and should be updated (very common problem)
http://www.eset.com/int/download/home/

Thanks!

 

[Adamant IT]

I had a laptop in my reapir shop that couldn't start due to this blue screen error in win 10.

I let it boot-loop into Recovery mode, then went to advanced options and opened a command prompt.

In cmd:

"cd C:\Windows\System32\Drivers" (replace C with whatever letter your windows partition has been assigned to)
"ren epfwwfp.sys epfwwfp.sys.old"

Then reboot. Windows is now starting, so I can update drivers, and can re-install ESNET.

 

[johnbl]

use caution when using this method. Drivers in the driverstore may be put back in place by the OS and you might have to remove them from the hidden driverstore. Just a heads up:
how to remove drivers from the driverstore:https://technet.microsoft.com/en-us/library/cc771484(v=ws.10).aspx

I had a laptop in my reapir shop that couldn't start due to this blue screen error in win 10.

I let it boot-loop into Recovery mode, then went to advanced options and opened a command prompt.

In cmd:

"cd C:\Windows\System32\Drivers" (replace C with whatever letter your windows partition has been assigned to)
"ren epfwwfp.sys epfwwfp.sys.old"

Then reboot. Windows is now starting, so I can update drivers, and can re-install ESNET.

 

[RayyaDragonheart]

This error happened to me after Avast! installed a toolbar in my Firefox browser. I ran a startup repair and it looked like it had been successful, but it gave me a BSOD a few more times before I shut it down and walked away to research the topic on another computer. Came back informed, booted the computer, and it worked, booting all the way through to Windows. No explanation, other than that Windows appeared to have rolled itself back during a restart and the Avast! toolbar was no longer installed. Not sure if this error applied to epfwwfp.sys directly (never checked the error logs) but my anti-virus seems to have been the cause.

 

[Clive Lloyd-Jones]

This error happened to me after Avast! installed a toolbar in my Firefox browser. I ran a startup repair and it looked like it had been successful, but it gave me a BSOD a few more times before I shut it down and walked away to research the topic on another computer. Came back informed, booted the computer, and it worked, booting all the way through to Windows. No explanation, other than that Windows appeared to have rolled itself back during a restart and the Avast! toolbar was no longer installed. Not sure if this error applied to epfwwfp.sys directly (never checked the error logs) but my anti-virus seems to have been the cause.

Just as a heads up for anyone who hasn't got Avast or ESET installed, this will more than likely still be related to your installed AV software (I'm working on a customers pc who has the exact same problem but it's Norton that has caused it).
If you can get into safe mode, uninstall your AV and see if that fixes the issue.