Jump to content

OVERKILL

Members
  • Posts

    8
  • Joined

  • Last visited

About OVERKILL

  • Rank
    Newbie
    Newbie

Profile Information

  • Location
    Canada

Recent Profile Visitors

405 profile views
  1. Yes, I had another machine this AM crashing too, uninstalling the two updates from the 7th fixed the issue, so it appears to be an issue between one of those updates (listed in the OP) and EAV.
  2. Just sent you a PM with a link to the full DMP file from the remote workstation.
  3. Settings were default, so if that option isn't on by default, it wasn't enabled. I'm trying to coordinate gaining access to the computer again (she's using it presently with the product uninstalled) and will collect the requested information when possible.
  4. OK, I can get those for you tomorrow. Will the logs be collectable with the product uninstalled or do I need to reinstall it and get it to crash again?
  5. Have a Windows 10 computer that was running 8.0.2028.0 at a remote site and it BSOD'd this AM with the above exception. Upgraded EAV to 8.1.2031 and the BSOD's continue. Windows 10 edition is 21H1, build 19043.1083 It's an AMD Ryzen 3 Pro 1200 based HP EliteDesk 705 G3. Most recent updates, installed 2021-07-07: - Servicing Stack 10.0.19041.1081 - KB5004945 - KB5003537 If I open a browser, this seems to trigger the crash (I'm on the computer remotely at the moment). Address is eamonm.sys+6200. Bug Check code is 0x1000007e I uninstalled the product, and now it is not crashing. I can launch a browser and all is well. Not experiencing this on other systems, most of them are Intel based, this may be the only AMD one in the building.
  6. William: Thank you, I've just submitted it that way. -Chris
  7. This link is still being sent out BTW, same URL. I am seeing them in the SPAM filter today.
  8. Got the same virus on a computer here today, ESET put up all kinds of warnings but now I'm restoring network share data from shadow copies as a pile of folders got hit before I was able to pull the cord on the system that was infected. Concerning was that a scan I ran didn't find anything on the computer despite the fact that the virus was currently active. The link sent in the e-mail is here: [LINK REDACTED] If that'll help anybody at ESET out. -Chris
×
×
  • Create New...