Jump to content

MajesticWi

Members
  • Content Count

    28
  • Joined

  • Last visited

Posts posted by MajesticWi

  1. On 1/10/2019 at 1:22 PM, MajesticWi said:

    Discussions about Windows 7 Reliability History caused me to take a peek at my desktop.  According to the log, the machine was pretty stable until 09/19/2018 which is the date I installed version 3.6.1.2711 of Malwarebytes.   Prior to 09/19/2018 I would have an occasional note on the history about Windows not being shut down properly.  This error is related to an unknown application that was slow to close when I shut down the system.   After 09/19/2018 errors related to mbamservice.exe start to appear in the history on a regular basis and after 12/06/2018, when 1.0.508 was installed, is when the hard freezes started happening. 

    Is it possible the problem between Malwarebytes and Windows 7 started with version 3.6.1.2711 and then became worse with the 1.0.508 update?
     

    Since installing 1.0.527 last Friday on my desktop, I have been hard freeze FREE.  No problems what so ever. System is running like it use too.   Knock on wood. 🙂

    Same good results with the 1.0.527 install on my laptop. 

    I've also noticed that 1.0.527 has cleaned up my Reliability History in regards to mbamservice.exe and Windows Shut Down issues. 

     

    MWB.thumb.jpg.ed965211ecff01f7147d0a44e62ff385.jpg

  2. On 1/9/2019 at 3:06 PM, MajesticWi said:

    I don't know if this is related, but I have been doing some experimenting on my own.  Since the hard freeze never occurs for me right after boot up or for a period of time after boot up, I decided to play around with some of the Malwarebyte settings that interact with Windows 7 during my time on the computer.  With Malwarebytes set for FULL protection I have found that if I disable Malwarebytes' Automatically Check for Updates setting and do the updates manually the freeze problem is gone.  So far my testing has been only for 2 days, but prior to this I was experiencing at least one freeze once a day.

      <snip>

    Just to update my previous post....... subsequent trial on my end showed that disabling the Automatically Check for Updates option doesn't totally resolve the hard freeze issue.  It still occurred, but less frequently. 

    I have since reverted my version of Malwarebytes back to the earlier version.  The hard freeze problem has been totally resolved now.

  3. Discussions about Windows 7 Reliability History caused me to take a peek at my desktop.  According to the log, the machine was pretty stable until 09/19/2018 which is the date I installed version 3.6.1.2711 of Malwarebytes.   Prior to 09/19/2018 I would have an occasional note on the history about Windows not being shut down properly.  This error is related to an unknown application that was slow to close when I shut down the system.   After 09/19/2018 errors related to mbamservice.exe start to appear in the history on a regular basis and after 12/06/2018, when 1.0.508 was installed, is when the hard freezes started happening. 

    Is it possible the problem between Malwarebytes and Windows 7 started with version 3.6.1.2711 and then became worse with the 1.0.508 update?
     

     

     

    Reliability Monitor Report.zip

  4. 7 minutes ago, LiquidTension said:

    We do apologise for this issue. We're working hard to track down the cause and provide a permanent solution. Thank you for your understanding.

    I don't know if this is related, but I have been doing some experimenting on my own.  Since the hard freeze never occurs for me right after boot up or for a period of time after boot up, I decided to play around with some of the Malwarebyte settings that interact with Windows 7 during my time on the computer.  With Malwarebytes set for FULL protection I have found that if I disable Malwarebytes' Automatically Check for Updates setting and do the updates manually the freeze problem is gone.  So far my testing has been only for 2 days, but prior to this I was experiencing at least one freeze once a day.

    Ironically I read today an earlier post about " Security Update for Microsoft windows (KB4480970)" possibly resolving the issue.   Since I had that security update installed on Patch Tuesday, I re-enabled the Auto Update setting and the computer hard froze with-in a couple of hours.  I have since disabled the Auto Update feature and will see if my desktop remains freeze free.

    I don't know if the 1.0.508 update contained enhancements for updating Malwarebytes, but I thought I would mention it.

    Thanks LiquidTension for your assistance !

  5. 6 hours ago, LiquidTension said:

    Great, thank you very much!

    One other useful piece of information would be the names of the network adapters present. To check:

    • Press the Windows Key + R on your keyboard at the same time. Type devmgmt.msc and click OK.
    • Expand Network adapters.

     

    Update.........

    Well, the KB44713187 uninstall solution was short lived.   With-in 6 hours it hard froze again.  After uninstalling  KB44713187 the desktop was rebooted several times.  I ran the Support Tool and have attached my logs.

    As noted in my original post this machine dual boots Windows 10 Home x64.  So far no problems with this hardware and that OS.  Windows 10 is running flawless. 

     

    mbst-grab-results.zip

  6. 1 hour ago, LiquidTension said:

    Great, thank you very much!

    One other useful piece of information would be the names of the network adapters present. To check:

    • Press the Windows Key + R on your keyboard at the same time. Type devmgmt.msc and click OK.
    • Expand Network adapters.

    My desktop uses the motherboard's network adapter which is.......

    Intel(R) Ethernet Connection  I218-V 

     

    Thanks again !

  7. 3 hours ago, LiquidTension said:

    Thank you for the information. To confirm, is that KB4471318?

    If it is, would you be willing to temporarily uninstall this update and check if this has any impact on the freezing/lock ups? To do so:

    • Click the Windows Start 29Fou9c.jpg button. Type CMD in the search bar, right-click CMD and click AVOiBNU.jpg Run as administrator.
    • Copy and paste (right-click the Window + Paste) the following into the Command Prompt. Press Enter on your keyboard.

      wusa /uninstall /KB:4471318
       

    <snip>

    Thanks for posting this information.  I will take the liberty of joining your test as well.  On my desktop it was intermittently locking up until 3 days ago when it started doing hard freeze once a day.  Yesterday it did it twice.  I have since uninstalled KB:4471318 and will let you know how it goes.

    System:  Home built desktop.     MSI X99a Sli Plus motherboard  with Windows 7 Pro x64

    No pattern to the freezes.  It has happened when I started a manual defrag, when opening FireFox to browse, after sitting idle (no suspend or hibernate, just screen saver) and when opening Windows Live Mail to name a few instances.

    Thanks for your assistance!

     

  8. Thanks for the advice.  Per this thread I have disabled both Ransomware and Web Protection in Windows 7 so I will see how it goes.  So far no problems.

    An update .......  I did spend some time with the laptop doing the Windows 8.1 Microsoft Updates along with the Malwarebytes 1.0.508 update.  No problems at all with this operating system using Windows Defender as the AV.   Web Protection and Ransomware protection is enabled as well.

  9. Experiencing a hard freeze on two of my systems after the 1.0.58.  These are a hard freeze with the mouse, keyboard and desktop screen froze. Requires pressing the power button to shut down.  Problem does not correct itself if let to wait it out.   

    The latest system was my laptop which has had two hard freezes and one soft freeze.  With the soft freeze the keyboard and mouse were still functional and I was able to crtl - alt- del to Task Manager for a reboot.  The shutdown / Restart button was un-responsive during the soft freeze as well as the desktop icons.  The screen was responsive when opening Task Manager.  The logs from the laptop are attached.  This laptop has.....

    Dual boot with Windows 7 Home x64 and Windows 8.1 x64.  The 1.0.58 upgrade has not been done with the Windows 8.1 install.  Windows Security Essential is my AV.

    The 1.0.508 update was done today on the laptop and the soft freeze problem occurred when I tried shutting the system down after that update.  The two hard freezes then happened later as I used the laptop. The were no previous problems with this laptop.

    My other system is a home built desktop that dual boots Windows 7 Pro x64 and Windows 10 Home x64.  This was updated to 1.0.58 when that update was first released.  In the last two weeks I have experienced two hard freezes that required pressing the power button to shutdown. I had no problem previous to this.   In Windows 10 I have yet to experience any problems with 1.0.58 so I'm guessing it is a Windows 7 issue.  Again Microsoft Security Essentials / Defender is used on the desktop system.   I will submit logs if the problem occurs again on the desktop.

    Thanks for your review!

    mbst-grab-results.zip

  10. I'm a Malwarebyte's Premium owner with 3 subscriptions and have experienced this on 1 PC so far.  I can see having pop-up ads on the Free version, but the Premium version should be just that....... a premium version of the software free nags.   If the marketing folks still wish to annoy their loyal customers, at least provide an opt out option.  On top of that, I don't even own an Android device.  ?

  11. Went to log onto   hXXX://www.bmoharris.com/main/personal   this morning and received a continuous block alert for  bmo.widget.custhelp.com 

    I had no problem yesterday so I assume it is a false positive caused by a recent Malwarebytes update.

    Thanks for your assistance!

    LOG

    Malwarebytes

    www.malwarebytes.com

    -Log Details-
    Protection Event Date: 11/20/17
    Protection Event Time: 7:50 AM
    Log File: c7e3036e-cdf9-11e7-868b-00ffa103fd5e.json
    Administrator: Yes

    -Software Information-
    Version: 3.3.1.2183
    Components Version: 1.0.236
    Update Package Version: 1.0.3300
    License: Premium

    -System Information-
    OS: Windows 7 Service Pack 1
    CPU: x64
    File System: NTFS
    User: System

    -Blocked Website Details-
    Malicious Website: 1
    , , Blocked, [-1], [-1],0.0.0

    -Website Data-
    Domain: bmo.widget.custhelp.com
    IP Address: 74.117.206.68
    Port: [50484]
    Type: Outbound
    File: C:\Program Files\Internet Explorer\iexplore.exe

    (end)

  12. Same problem here.  I was doing my morning routine of visiting various news websites and Malwarebytes 3 did an update.  After that started receiving notice that these websites have been blocked.....

     

    tn.symcd.com

    gn.symcd.com

    ss.symcd.com

     

    Malwarebytes version: 3.3.1.2183

    Component package: 1.0.236

    Update package:  1.0.3281

    Blocks occurred with both Firefox v57 and Internet Explorer 11

  13. I had several issues with versions 3.0x of Malwarebytes and MSE.  First was the shut down issue with Windows 7 which was easy to work around and secondly was the annoying protection off pop ups.  With version 3.05 I had also noticed on boot up that some applications in the Sys Tray took longer to load.  Over time my system also seemed to develop what I would call mini lags during use which I eventually associated with those darn pop ups soon to appear on screen.  I finally said enough to the beta testing and did a clean install of Malwarebytes back to version 2.2.1..  Best decision I made.  I wasn't totally aware of the performance hit that buggy version 3.xx of Malwarebytes was causing until I revert back.  Now my desktop is back to it old responsive self.   Papgeno I recommend you do the same.  In your situation a clean install of version 2.2.x may correct the previous issues you were experiencing before the version 3.xx upgrade.     

  14. I would see the logic in uninstalling MSE, but it worked fine with Malwarebytes v2.xx.  The only change to my system was the Malwarebytes upgrade to version 3.0.  That would leave me to believe MSE isn't the buggy one. Besides other anti-virus programs seem to peacefully coexist with the version 3 upgrade of Malwarebytes. 

  15. Just an update on my v3.05 usage with Windows 7 Pro x64 and with MSE Real Time Protection enabled.......

    I continue to have the long shut down issue.  Initially the v3.05 update took care of the Web Protection pop up issue, but as time went on it re-appeared.  At first the pops were very random, but they slowly increased and now appear regardless if there was any activity or not on the computer.  Now the pops have progressed to appearing at boot up and it is hit or miss on enabling them.  Sometimes it works, sometimes they enable on their own after 5 minutes or so and others times they do not enable unless the system is rebooted.  I've have also noticed a long lag in other applications fully loading at boot up, example: Intel Rapid Storage Technology manager, in the Sys Tray.  I never had this issue with v2.xx of Malwarebytes.

    Since this machine is a dual booter with Windows 10 Home I went ahead and installed v3.05 on it.  So far I haven't encountered any issues with that OS.  I figured this would be a good comparison as to whether the issues with v3.05 are OS or hardware related. 

  16. Hi Ried, I re-enabled it.  Not much point of having MSE installed if Real Time Protection is disabled.  The work around of exiting out of Malwarebytes before shutting down or restarting works with MSE Real Time Protection enabled. 

    As for my other computers, four are various versions of Windows 10 and one laptop that dual boots Windows 7 Pro x64 and Windows 8.1 Pro x64.  At this point I have no intentions of doing anymore upgrades on them until a stable version is released. I'm trying avoid continual patching.

    Thanks for responding

  17. I just installed the v3..05 patch to v3.04.  Not much change with Windows 7 Pro x64 and Microsoft's Security Essentials.  After installing v3.05 and rebooting, the shut down of Windows took less than 30 seconds.  On subsequent reboots the shut down delay returned ranging from 4 1/2 to 6 minutes.  My temporary work around is to close out Malwarebytes prior to shutting Windows down or rebooting. 

    Would be nice if the roll out of v3.05 was delayed.  Not looking forward to upgrading my other 5 computers with this.

    My previous posting in the forum regarding v3.04 and the shut down problem can be viewed by clicking here.

  18. Ried, Glad the information was useful

    Regarding those events in the Event Logs.  The MSIDDR_CC service and MSICTL_CC service are related to a MSI motherboard utility for overclocking, etc.  When I stopped those services from loading at boot up, the only event shown in the Event Logs during the lengthy shut down is the MBAMService service. 

    I think I will re-enable MSE's Real Time Protection now that I know the machine will eventually shutdown.  That I can live.  If by chance it starts shutting down normally I'll know the MSE issue has been resolved.

    Thank-you very much for your time and assistance.  You have been most helpful !!

  19. Ried, Thanks for your assistance.  Turning off MSE Real Time Protection returns things to normal.  A conflict I assume?

    I had some time to do additional experimenting....

    The computer will shut down on its own after 5 to 7 minutes and reboot normally.

    Disabling Exploit Protection, Ransomware Protection and Web Protection individually had no effect in curing the shutdown problem.

    Windows 7 Reliability History shows NO problem.

    Windows 7 Event Logs shows these same 3 events when I let the computer do the lengthy shut down on its own....

    ******

    Log Name:      System
    Source:        Service Control Manager
    Date:          12/8/2016 5:34:15 PM
    Event ID:      7011
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      ********
    Description:
    A timeout (30000 milliseconds) was reached while waiting for a transaction response from the MBAMService service.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
        <EventID Qualifiers="49152">7011</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8080000000000000</Keywords>
        <TimeCreated SystemTime="2016-12-08T23:34:15.680253100Z" />
        <EventRecordID>264045</EventRecordID>
        <Correlation />
        <Execution ProcessID="824" ThreadID="4520" />
        <Channel>System</Channel>
        <Computer>*****</Computer>
        <Security />
      </System>
      <EventData>
        <Data Name="param1">30000</Data>
        <Data Name="param2">MBAMService</Data>
      </EventData>
    </Event>

    *******

    Log Name:      System
    Source:        Service Control Manager
    Date:          12/8/2016 5:34:45 PM
    Event ID:      7011
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      *******
    Description:
    A timeout (30000 milliseconds) was reached while waiting for a transaction response from the MSICTL_CC service.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
        <EventID Qualifiers="49152">7011</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8080000000000000</Keywords>
        <TimeCreated SystemTime="2016-12-08T23:34:45.694705800Z" />
        <EventRecordID>264046</EventRecordID>
        <Correlation />
        <Execution ProcessID="824" ThreadID="4520" />
        <Channel>System</Channel>
        <Computer>*****</Computer>
        <Security />
      </System>
      <EventData>
        <Data Name="param1">30000</Data>
        <Data Name="param2">MSICTL_CC</Data>
      </EventData>
    </Event>

    *********

    Log Name:      System
    Source:        Service Control Manager
    Date:          12/8/2016 5:35:15 PM
    Event ID:      7011
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:     *******
    Description:
    A timeout (30000 milliseconds) was reached while waiting for a transaction response from the MSIDDR_CC service.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
        <EventID Qualifiers="49152">7011</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8080000000000000</Keywords>
        <TimeCreated SystemTime="2016-12-08T23:35:15.709158500Z" />
        <EventRecordID>264047</EventRecordID>
        <Correlation />
        <Execution ProcessID="824" ThreadID="4520" />
        <Channel>System</Channel>
        <Computer>******</Computer>
        <Security />
      </System>
      <EventData>
        <Data Name="param1">30000</Data>
        <Data Name="param2">MSIDDR_CC</Data>
      </EventData>
    </Event>

Back to top
×
×
  • 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.