Jump to content

AverageJoe

Members
  • Content Count

    19
  • Joined

  • Last visited

About AverageJoe

  • Rank
    New Member

Recent Profile Visitors

520 profile views
  1. Yes, all four of the real-time protection settings including ransomware and web are enabled.
  2. I've noticed improved boot time as well. I have an SSD so it was always "fast" to boot up, relatively speaking, but since the new update, it has shaved off roughly 3 seconds from my welcome/login screen to desktop; quite impressive.
  3. I turned automatic updates back on and forced an update to the 1.0.527 components package this morning and have been running MBAM Premium with all real-time protections fully enabled for several hours now with zero freezes. This is a huge improvement from before where I couldn't go 30 minutes, sometimes even 10 minutes, without a freeze. I will leave it on for the remainder of the day to ensure all is well. There doesn't appear to be any impact to my PC; all programs are running as expected like before the freezing.
  4. For the past week or so, I had just outright disabled MBAM on my PC upon startup waiting to see if a fix would be provided. Since the issue seems to be on-going for quite a while and I'm getting back into the swing of things with my employer and needing to browse the web again, earlier today I went ahead and rolled back to the previous component package outlined in workaround #2 of the pinned thread. I am now running licensed MBAM version 3.6.1.2711 with component package 1.0.482 and update package 1.0.8834 with all real-time protections fully enabled and so far no freezes. Have been able to play Battle.net games and download large internet traffic via streaming (Netflix, YouTube, etc.) as normal. This was the PC where the freezing was aggressive, within a few minutes of startup.
  5. All these posts about people spending days, if not weeks, tearing apart their desktops and checking RAM, video cards, CPUs, motherboards, power supplies, etc. and even buying entirely new hardware to replace the old terrifies me. I can't imagine someone spending so much time going to such great lengths to troubleshoot a problem of this nature, being unable to find out the cause, chalk it up to faulty hardware, replace nearly everything, if not outright upgrade to an entirely new machine, and go to reinstall all their programs and find the freezing problem STILL occurring. I was about to go down that exact same road and was dreading it. Guess I'm extremely lucky I only spent 48 hours looking into it before I started turning to forums for help. I started with Steam and Battle.net since they are my two most used applications and there were a couple forum posts on Battle.net about system freezes during game updates. One Blizzard employee suggested uninstalling all antivirus and anti-malware to let Battle.net install and upgrade as needed and then reinstall the antivirus and anti-malware once finished. The post mentioned MBAM which I too used and found it strange to have to uninstall MBAM to allow a legit application to update, so I wandered on over here for more info and found this thread along with the pinned one. I feel bad for the non-tech savvy users encountering this problem who don't know support forums like this exist and are just googling the problem which yields thousands of different unrelated solutions, or worse, taking their entire desktop/laptop down to the local computer repair shops or Best Buy Geek Squad and flushing hundreds of dollars down the toilet.
  6. When did the freeze first start occurring? January 7th. I had not used my PC near the end of 2018 and the first week of January due to being on vacation for the holidays. What were you doing on the computer immediately prior to the latest freeze? Nothing; was letting it idle and complete all startup apps. Did you notice anything significant occur around the time of the latest freeze (e.g. AV notification, application crash, etc)? My Blizzard Battle.net software had initiated a download for a game update. I had Windows Task Manager opened to the Processes tab just before it froze and it showed "AgentUpdater.exe" was the top running process at the time the freeze occurred. Has a freeze occurred when the computer is idle? Yes. Have you noticed a correlation between high network traffic and the computer freezing? Not really; I don't do much on my computer that consumes large network traffic; most of my freezes have been when idle, thought it could be downloading data in the background. How often does the computer freeze? Almost guaranteed to freeze every time from boot up to the desktop within 5 to 15 minutes. Are you able to reproduce the freeze on-demand? If the answer is yes, what are the steps? I can't reproduce the freeze using a specific application (That I'm aware of yet), but I can "reproduce" it simply by leaving my computer on and idle, it will simply freeze on its own. How old is the computer? Was built in 2014 using parts maybe a year or so older. Was the computer upgraded from XP/Vista to Windows 7? No; clean install of Windows 7 Home Premium. Is the computer fully up-to-date with Windows Updates? Which updates have been installed after the first freeze occurred? Computer was up-to-date prior to the first freeze on January 7th. More updates have been installed since then; see attached screenshot below for full list of updates completed post January 7th freeze. Does the computer have multiple network adapters? If it does, what happens when you disable the adapter currently in use and switch to a different adapter? No, just a single wired network adapter.
  7. I'll try to help out if possible; premium MBAM end-user with a custom built PC. My PC's been freezing since Jan 7th, not a blue screen crash, just hangs on the desktop or whatever application I have open and all inputs become unresponsive. Only way to resolve is a hard reboot. The freezing I've been encountering seems to be aggressive, one time it froze less than five minutes after boot up to the desktop. A couple of other times it's been roughly 10 to 20 minutes into normal use (Web browsing, playing games, opening applications, etc.). Spent a whole day in safe mode toggling programs on and off one by one trying to isolate who was the culprit without any success and it was driving me insane. Various google searches yielded the problem was likely hardware-related and I dreaded having to tear apart my PC to begin troubleshooting for reasons I won't go into. Started checking the official forums of all the software I routinely use and ended up here. Good thing I came across this thread before I started removing RAM, video cards, heatsinks/fans, and dozens of other parts. For now I've just outright exited Malwarebytes immediately after startup (Right-click the notification area icon > "Quit Malwarebytes") and waited a few hours to see what happens; so far so good, no freezes. Might try launching it again later and disabling both the Web Protection and Ransomware Protection like suggested in the workaround. Attached zip file with logs as instructed from pinned thread. Brief overview provided below; I don't have multiple network adapters so I cannot test step #5. OS: Windows 7 Home Premium SP1 x64 CPU: Intel Core i5 4570 @ 3.20GHz RAM: 16GB DDR3 Motherboard: MSI Z87-G45 Network Adapter: Killer E2200 Gigabit Ethernet Controller Storage: 500GB Samsung SSD 850 EVO, two 1TB Seagate ST1000DM003, 3TB Seagate ST3000DM001 Some common programs I use frequently on this PC include Steam and Blizzard Battle.net (Both digital game distribution platforms), Chrome, Firefox, Microsoft Security Essentials (Antivirus), Spybot Search & Destroy, Malwarebytes, Adobe Acrobat, Nvidia GeForce Experience, Notepad++, VideoLAN/VLC Media Player, Microsoft Office 2013, and Microsoft Visual Studio 2013. mbst-grab-results.zip
  8. Yes, I hadn't thought about it scanning the registry earlier than the GUI indicated. Thanks.
  9. Does the "Scan Registry" part of Malwarebytes threat scanner do anything? Reason I ask is every time I run a scan (Threat or custom, doesn't matter), the process seems to skip over the Scan Registry process really fast. Every other process (Scan Memory, Scan Startup Files, etc.) takes anywhere from a few seconds to a minute or so, but Scan Registry finishes in what seems like 0.001 seconds. Not sure if it's actually doing anything.
×
×
  • 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.