Jump to content

Windows 10 BSOD because of "epfwwfp.sys"


Recommended Posts

I made a clean installation of Windows 10 at my laptop. At least 1-2 times a day I get a BSOD with message "IRQL_NOT_LESS_OR_EQUAL ERROR". I contacted with Microsoft an begun this topic at their forum:

hxxp://answers.microsoft.com/en-us/windows/forum/windows_10-hardware/irqlnotlessorequal-error-windows-10/cc0db65d-513c-40ea-aad7-e239742a3e9b?page=1 

 

After i ran Driver Verifier and sent to Microsoft my minidump files, they answered me that the cause of this error is ESET Smart Security (file "epfwwfp.sys"). I deleted this file at safe mode and installed ESET Smart Security again using the installer from ESET's site. But after this I ran Drive Verifier again and before I could log to Windows I got the same error cause by file "epfwwfp.sys". Please tell me what to do to fix these irritating errors. I am using ESET Smart Security for many years and I am surprised about this problem I see many people have. 

 

Here are the minidump files:  https://www.dropbox.com/s/fbbt38le1muiurf/082515-11859-01.dmp?dl=0

 

https://www.dropbox.com/s/e0zibcnap61qlic/082915-9343-01.dmp?dl=0

 

https://www.dropbox.com/s/flps2fn8abknmr7/083015-10359-01.dmp?dl=0

 

https://www.dropbox.com/s/ywn0cvckx7lnlv8/083115-9671-01.dmp?dl=0

 

https://www.dropbox.com/s/iqh3yyktvyo11bz/083115-22906-01.dmp?dl=0

 

https://www.dropbox.com/s/bsr84r99slfljv6/090215-9734-01.dmp?dl=0

Link to comment
Share on other sites

  • Administrators

We are aware only of one cause of BSOD in connection with epfwwfp.sys. This crash occurred during upgrade to Windows 10 when the operating system returned completely invalid data to the mentioned driver which triggered BSOD. On Aug 17, we released an update of the firewall module 1278.1 which included a workaround for the Windows issue. If installed, epfwwfp.sys shouldn't trigger BSOD even if invalid data is returned by Windows.

 

I'll ask our engineers to have a look at the minidumps, however, they may not include enough data and a kernel or complete memory dump from BSOD will be needed.

 

With epfwwfp.sys renamed in safe mode, please copy the information about installed modules from the About window and paste it here.

 

Also supply me with:

1, filters.xml created after running "netsh wfp show filters verbose=on" with administrator rights

2, export of HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\BFE from the registry.

Link to comment
Share on other sites

I have been having similar problems as detailed in this thread.

 

The workaround that I found was to enable pre-release updates.

 

The pre-release Eset Personal Firewall 1283B (20150821) seems much more stable than Eset Personal Firewall 1278.1 (20150803) which crashes Windows regularly.

 

Hopefully Eset will soon add this version of the firewall to the standard (non pre-release) update stream.

Link to comment
Share on other sites

  • Administrators

The dump looks strange. It contains both some older and some current drivers. Please drop me a pm and supply me with the output of running ESET Log Collector (hxxp://support.eset.com/kb3466/).

Are you sure you haven't upgraded from ESS v8.0.308 to 8.0.319 and you installed the latest version from scratch?

Link to comment
Share on other sites

  • Administrators

None of the dumps appears to be from a crash related to ESET. We've seen only crashes caused by win32kfull.sys, dxgkrnl.sys and ZTEusbmdm6k.sys drivers. Does temporarily disabling firewall integration and rebooting the computer make the problem go away?

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...