viper37 1 Posted February 11, 2019 Share Posted February 11, 2019 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. Link to comment Share on other sites More sharing options...
itman 1,659 Posted February 12, 2019 Share Posted February 12, 2019 This could or could not be related to the issue: http://woshub.com/could-not-reconnect-mapped-network-drives/ . Link to comment Share on other sites More sharing options...
Administrators Marcos 5,074 Posted February 12, 2019 Administrators Share Posted February 12, 2019 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. Link to comment Share on other sites More sharing options...
viper37 1 Posted March 11, 2019 Author Share Posted March 11, 2019 ees_logs.zip Here are the logs. The crash dump is over 1gig and in zip format, it takes forever to compress. I'll come back later with these. Sorry for the delay. Lots of problems currently. Link to comment Share on other sites More sharing options...
viper37 1 Posted March 11, 2019 Author Share Posted March 11, 2019 I tried uploading the logs, but at 99mb the split files were still too large and I don't have enough patience to retry. You should consider allowing 7z as well, in your extension format. Much faster. Anyway, the file:https://1drv.ms/u/s!AgrjqmJUctfrgtk0DqAF8qeW_yd_ZQ Link to comment Share on other sites More sharing options...
viper37 1 Posted March 12, 2019 Author Share Posted March 12, 2019 (edited) Also, I have all the latest Win10 updates, nothing has changed. Edited March 12, 2019 by viper37 Link to comment Share on other sites More sharing options...
ESET Moderators Peter Randziak 1,130 Posted March 12, 2019 ESET Moderators Share Posted March 12, 2019 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 Link to comment Share on other sites More sharing options...
ESET Moderators Peter Randziak 1,130 Posted March 13, 2019 ESET Moderators Share Posted March 13, 2019 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. Link to comment Share on other sites More sharing options...
viper37 1 Posted March 22, 2019 Author Share Posted March 22, 2019 thank you very much! :) Peter Randziak 1 Link to comment Share on other sites More sharing options...
Recommended Posts