Jump to content

Archived

This topic is now archived and is closed to further replies.

viper37

Unexpected kernel mode trap: Epfwwfp.sys

Recommended Posts

Hello,

When trying to access one of my network drive, I always get a blue screen of death with the following message:
Stop code: Unexpected kernel mode trap
What failed: epfwwfp.sys

Sometimes I can't access any of my mapped network drives, but it is usually always the same one containing simple Acess database files.

Sometimes, the file isn't mentionned, only the bluescreen.

I uninstalled Eset Endpoint v6 and reinstalled v7 instead, but the problem persist.  Just clicking on the drive results in a crash.

If I completely remove Eset Endpoint, then my computer works normally, I have access to all my network drives.
Once I have it installed again, the problem reeappears.

 

Windows 10 version:  1809 build 17763.292

It's been doing that for a little while though.  It wasn't doing it everyday, but now, there it is.  Everyday I boot, I can't access some network drives and I get this error message.

Full hardware specs here:
https://ca.pcpartpicker.com/list/D9CPHN


Eset does not report any infection.  I have tried competing anti-virus products' offline scanners, as well as Eset's tool and they did not report anything abnormal either.

I am lost.

20190207_145033.jpg

Share this post


Link to post
Share on other sites

Please provide me with the generated dump (should be a kernel of full memory dump) as well as with logs gathered with ESET Log Collector.

Share this post


Link to post
Share on other sites

 

Also, I have all the latest Win10 updates, nothing has changed.

Share this post


Link to post
Share on other sites

Hello @viper37,

thank you for providing us with the dump and logs.

I briefly checked them and opened a ticket with our dev team in order to investigate the root cause deeply.

We will keep you posted.

Regards, P.R.

tracking note: P_EESW-3267

Share this post


Link to post
Share on other sites

Hello @viper37,

I got a response from the Dev team. 

The issue will be fixed in EES v. 7.1.2039 and EES v. 7.0.2108.

Fixed build should be available within few weeks.

 

We apologize for the inconvenience caused.

Regards, P.R.

Share this post


Link to post
Share on other sites

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...