Jump to content

dpit

Members
  • Posts

    8
  • Joined

  • Last visited

About dpit

  • Rank
    Newbie
    Newbie

Profile Information

  • Location
    U.K.

Recent Profile Visitors

1,003 profile views
  1. It always feels uncomfortable to turn down ESET. Is it less risk if I add the network location as a performance exclusion, or disable scanning of network drives?
  2. Disabling it allows the app to immediately launch. Do you suggest this should be disabled for all or was this just proving the problem?
  3. I have real-time file system protection enabled. In addition I have enabled: HIPS, memory scanner, exploit blocker, ransomware shield, IDS, botnet protection, web access, anti-phish, email client, antispam
  4. Simple .Net 7 winform apps start slowly from a network folder. Pausing ESET protection allows the app to start immediately. Being self contained there is significant unpacking when executing the app thus ESET would be busy, but launch can take 10 seconds. If I run the same self contained app from my C drive, there is no noticeable delay. Is this a known problem/work in progress? Any advice please?
  5. Since November I have seen several freezes across out network, with two PCs particularly suffering. The two PCs are lower spec than most which may be part of the issue? I have concentrated on one PC which can freeze up to three times a day. I have set up the machine CTRL/SCROLL BSOD and after checking out the dump file it points at ESET. Is this a common issue out at the moment? Is there more digging to do? LAST_CONTROL_TRANSFER: from fffff80002aca1e9 to fffff80002acac40 STACK_TEXT: fffff880`0af01608 fffff800`02aca1e9 : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff880`0af01610 fffff800`02ac8e60 : 00000000`00000000 fffffa80`037670a0 00000000`00000014 fffffa80`03767010 : nt!KiBugCheckDispatch+0x69 fffff880`0af01750 fffff880`0148ce4e : fffffa80`04331b00 fffffa80`03767010 00000000`00000000 fffff880`0148d3f3 : nt!KiPageFault+0x260 fffff880`0af018e0 fffff880`0148cd21 : fffffa80`03767010 fffff880`01498100 fffff880`01498100 fffff880`01498100 : epfwwfp+0x1e4e fffff880`0af01930 fffff880`0148ffd4 : 00000000`000018e0 fffff880`0af019f0 fffff8a0`002e3740 fffff800`02c7fff8 : epfwwfp+0x1d21 fffff880`0af019a0 fffff800`02d834ae : fffffa80`037cd680 fffffa80`0a5cf450 fffffa80`037cd680 fffffa80`08e8e890 : epfwwfp+0x4fd4 fffff880`0af01a00 fffff800`02da0aaf : 000007ff`fffdd000 00000000`00000001 00000000`00000000 00000000`00000000 : nt!PspExitProcess+0x156 fffff880`0af01a60 fffff800`02d83948 : 00000000`00000000 00000000`00000001 000007ff`fffdd000 00000000`00000000 : nt!PspExitThread+0x4e3 fffff880`0af01b60 fffff800`02ac9ed3 : fffffa80`037cd680 000007fe`00000000 fffffa80`0a5cf450 000007fe`fec326c8 : nt!NtTerminateProcess+0x138 fffff880`0af01be0 00000000`7739dc7a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`0012fe88 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7739dc7a STACK_COMMAND: kb FOLLOWUP_IP: epfwwfp+1e4e fffff880`0148ce4e 48395908 cmp qword ptr [rcx+8],rbx SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: epfwwfp+1e4e FOLLOWUP_NAME: MachineOwner MODULE_NAME: epfwwfp IMAGE_NAME: epfwwfp.sys DEBUG_FLR_IMAGE_TIMESTAMP: 55a8e74d FAILURE_BUCKET_ID: X64_0xD1_epfwwfp+1e4e BUCKET_ID: X64_0xD1_epfwwfp+1e4e ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:x64_0xd1_epfwwfp+1e4e FAILURE_ID_HASH: {e89e3e7a-8961-9f45-a10b-c73e239e2229}
  6. Marc - are you still finding it's just idle state scanning causing the freeze? Has anybody heard anything from ESET on this?
  7. I disabled protocol filtering this morning on the 3 PCs suffering the most and all have stayed alive today...
  8. I have 19 of 24 PCs freezing on ESET endpoint security 6.
×
×
  • Create New...