Jump to content

bithead

Members
  • Content Count

    6
  • Joined

  • Last visited

About bithead

  • Rank
    New Member
  1. Running without Ransomware Protection enabled, it took longer, but over the weekend the PC went comatose again. Guess I'll try without running MWB at all and see what happens...
  2. exile360 - Thanks for the additional explanation. As for me being suspicious, I'd say it's general paranoia more so than suspicion. Although I will admit that while writing my previous reply from a mobile device, I missed your "experts" rating off to the side.
  3. ram220 - Thanks for the confirmation. Of course another solution is to uninstall MWB and move on to something else. This trial period is not making the product look very appealing.
  4. While that may be true about arwlib.dll, turning it off would not fix the cause of the problem. If that dll is the culprit then it seems that it is misbehaving in a way that over time consumes resources that are never released back to the OS. And, no offense intended, but who is to say you're not baiting me to disable the ARW feature, thereby opening myself to a ransomeware attack?
  5. Here are the logs. mb-check-results.zip
  6. I've been running the free version of MWB for about a year on a PC running Windows 10 Education 64-bit. On 4/9 I received a message indicating that an update existed and opted to install it. I was surprised that the update also installed the Premium Trial version in the process, considering that my 14-day trial was over many months ago. I leave this PC on 24x7, and on the morning of 4/10 I found it to be unresponsive. After several minutes of trying to get to where it could be gracefully shut down, I gave in and held down the power button until it powered off. On 4/12, this happened again, and again on 4/13. On 4/13, I ran chkdsk in case all of the ill-advised power-cycling had created new problems - it was running when I left for the weekend. On Monday 4/16, all seemed OK - chkdsk claimed not to find any problems and the PC was working. Then on the morning of 4/17, the same issue occurred. On 4/17, I uninstalled MWB and on 4/18, all was OK again. On 4/18 I reinstalled the Premium Trial v3.4.5. On 4/19 (today), the PC was unresponsive again. Reliability Monitor shows one MWB crash on 4/10, the morning after the update, but none since then: Source Malwarebytes Service Summary Stopped working Date ‎4/‎10/‎2018 3:58 AM Status Report sent Description Faulting Application Path: C:\Program Files\Malwarebytes\Anti-Malware\mbamservice.exe Problem signature Problem Event Name: APPCRASH Application Name: mbamservice.exe Application Version: 3.1.0.643 Application Timestamp: 5ab294e4 Fault Module Name: arwlib.dll Fault Module Version: 3.0.0.613 Fault Module Timestamp: 5aa00e7b Exception Code: c0000005 Exception Offset: 00000000000740a9 OS Version: 10.0.16299.2.0.0.256.121 Locale ID: 1033 Additional Information 1: d8c4 Additional Information 2: d8c441bd4da5afc4fe4d1382535a0af4 Additional Information 3: e237 Additional Information 4: e237b1077cfe4cdb6fa9f1a1f1352556 Extra information about the problem Bucket ID: f8ebba856b271b24a932adb7713cbe29 (1815704603174157865) The only other AV on this machine is Windows Defender, and it has been running on it "forever". It seems the 3.4.5 version of MWB is at odds with something on this PC, causing it go comatose in the middle of the night, and I'm looking for a cure that doesn't involve the power button. TIA for any assistance.
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.