Jump to content

Phil_S

Members
  • Content Count

    35
  • Joined

  • Last visited

Profile Information

  • Gender
    Not Telling
  • Location
    U.K.

Recent Profile Visitors

728 profile views
  1. I can't help except to say that I had exactly the same error messages during automatic update to EIS v13.2.18.0 today. Everything seems to be working OK with no more error messages after a reboot. I have edevmon.sys file version 10.15.30.0 installed in System32\drivers, but whether this is the current file version I can't say.
  2. Thank you @Peter Randziak Everything is still normal so far. If it happens again I will let you know.
  3. Thanks @Peter Randziak, So far, everything is normal since the reboot. If it happens again I'll do as you suggest, but I thought I ought to mention it in case there was an unknown issue with the new release, having found a similar post in the NOD32 AV forum. @Marcos, files attached. Thank you. AppCrash_ekrn_exe.zip
  4. This is all I can find. It's from 24 hours ago and I don't know if it's relevant as according to the Eset log EIS successfully updated at 09:48 hrs today. The application update to 13.2.16.0 was completed at 08:01 yesterday, around 7 hours before this log was created. I have collected the files from C:\ProgramData\Microsoft\Windows\WER\ referred to below and can send them to Eset if required. Log Name: Application Source: Windows Error Reporting Date: 01/08/2020 15:56:57 Event ID: 1001 Task Category: None Level: Information Keywords:
  5. Rebooted. Eset has just successfully checked for and completed an update . ekrn.exe now 125,000 KB memory in use, 0% CPU. Will see how it goes.
  6. Eset updated to v13.2.16.0 yesterday and last completed a successful definition update over 4 hours ago. Wondering why my PC has slowed to a crawl I opened Resource Monitor to find that ekrn.exe is using over 12GB of physical memory, currently 93% memory usage and still increasing. The Eset tray icon is continuously spinning and the program has been reporting "Module update in progress" for at least the last hour that I am aware of, possibly since the last update check over 4 hours ago for all I know. I have tried clicking "Cancel Update" but it is not responding. Current stats for e
  7. No, as I say all updates have completed without any errors since the end of June. I'm afraid I deleted all the notifications that I has, as there have been no problems for three weeks now, and my mailbox was filling up with successful notifications due to the bug in the current version. It is interesting though that my daughter's laptop also has an SSD.
  8. I doubt it's of any help, but since my previous post in this thread on 24th June, I had a flurry of these differential update notifications from her laptop over a period of 3 days, seemingly affecting every download attempt, but since then nothing untoward at all. Since she has changed nothing on her laptop, I suspect some kind of external influence must have been involved.
  9. Well, my daughter appears not to have had any further reports on her laptop since first experiencing the issue in a flurry over 2 days of attempted Eset updates. She has a standard W10 laptop with a single SSD partition and a default W10 installation, so I find the discussion relating to moved swap files and temp folders a bit of a red herring, at least in her case. @Samoreen are you still experiencing the issue? It seems to have stopped in my daughter's case, so the circumstances suggest some outside influence to me?
  10. I have just found this topic as the result of a search on error notifications that I have just started receiving from my daughter's laptop: 24/06/2018 15:29:48 - During execution of Update on the computer xxx-LAPTOP, the following event occurred: Error occurred when applying differential update to base file. This has only started today, but so far I have received several notifications by email from her Eset AV. Unfortunately she is halfway around the world from me (hence the time discrepancy between the pasted notification text and my posting time) and not computer savvy, so I
  11. I reported the same to you here on 19th March after uninstalling Eset AV 11.1.42.0 at your suggestion. I had to reinstall my system from a backup image.
  12. I have nothing to check one way or another Marcos, as I've copied over the entire system from a backup. All I did though was uninstall EAV, which appeared to finish successfully, and reboot into the BSOD. The screen said that a system component was missing or unavailable, and googling 0xc0000225 seems to suggest registry corruption.
  13. Apparently an update should now be available to fix this. Bit late for me, as I took Marcos' advice to uninstall and re-install EAV, rebooted into a BSOD and ended up re-imaging the whole system partition from a backup
  14. Just back from uninstalling Eset AV, rebooting into BSOD 0xc0000225 and reimaging my entire partition from a backup!!! Not the happiest I've ever been
  15. It looks like that will mean I will lose all my settings and I can't export them first because of the password issue!
×
×
  • Create New...