Phone Man

Honorary Members
  • Content count

    288
  • Joined

  • Last visited

About Phone Man

  • Rank
    True Member

Contact Methods

  • ICQ
    0

Profile Information

  • Location
    Covington, LA

Recent Profile Visitors

4,368 profile views
  1. On my Windows 10 systems I went to "turn Windows features on or off" and turned SMB 1.0 off. Give it a try and it can always be enable again. Jim
  2. Here are my scan results on my W10 desktop. All scans had every thing checked. 371,000 items. Ver 3.0.6.1469 Scheduled Scan 2:53 min CPU hit 95% Ver 3.1.0.1716 Scheduled Scan 9:40 min CPU hit 30% Ver 3.1.0.1716 Manual Scan Low Priority 9:16 min CPU hit 30% Ver 3.1.0.1716 Manual Scan High Priority 3:46 min CPU hit 95% Jim
  3. My scheduled scans are close in time to the lower priority of the manual scan. Also the CPU usage is lower on both those scans. Lower priority manual and scheduled scans hits max of 30% CPU and Higher priority hits 90%. Jim
  4. I installed over the top of the last Beta and all is good, Jim
  5. John, Check my thread with the same errors. I found what was triggering my errors. https://forums.malwarebytes.com/topic/200412-errors-with-the-new-beta-3111722/ Jim
  6. OK I found out what was going on. There is a problem with Norton Smart Firewall where Facebook will hang. Disabling Norton Smart Firewall will unlock Facebook but some times you have to Recover the Page. When this happen I get the Event 1000 for Edge and also FRST scan shows the Code Integrity error with MB mbae64.dll at the same time. A lot of people at Norton Forum have reported the Facebook hang and linked it to the Norton Smart Firewall. When Facebook hangs just turning off and back on the Norton Smart Firewall will clear Facebook for a while. Jim
  7. Not that I am aware of. I have been checking some options and doing some scan testing. I usually have Edge open when I am on my system. I will monitor my event log and see when it happens and what I am doing at the time. Everything is working fine and I usual don't worry about event errors but I saw another post where someone reported this and that is why I looked into it. I will post back if I see this event again, Jim
  8. I am getting same event errors with the new Beta 3.1.1.1722. I may have gotten them with 3.1.0.1716 but cleared my Event log. Log Name: Application Source: Application Error Date: Thursday, May, 4, 2017 10:53:37 PM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: Jim-PC Description: Faulting application name: MicrosoftEdgeCP.exe, version: 11.0.15063.0, time stamp: 0x58ccbae4 Faulting module name: EdgeContent.dll, version: 11.0.15063.250, time stamp: 0xc697795c Exception code: 0xc0000409 Fault offset: 0x0000000000075817 Faulting process id: 0x2574 Faulting application start time: 0x01d2c537d06db9b1 Faulting application path: C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\MicrosoftEdgeCP.exe Faulting module path: C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\EdgeContent.dll Report Id: d4d4b0fa-db8d-431f-b587-4e3d6799de80 Faulting package full name: Microsoft.MicrosoftEdge_40.15063.0.0_neutral__8wekyb3d8bbwe Faulting package-relative application ID: ContentProcess Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2017-05-05T03:53:37.042052000Z" /> <EventRecordID>5227</EventRecordID> <Channel>Application</Channel> <Computer>Jim-PC</Computer> <Security /> </System> <EventData> <Data>MicrosoftEdgeCP.exe</Data> <Data>11.0.15063.0</Data> <Data>58ccbae4</Data> <Data>EdgeContent.dll</Data> <Data>11.0.15063.250</Data> <Data>c697795c</Data> <Data>c0000409</Data> <Data>0000000000075817</Data> <Data>2574</Data> <Data>01d2c537d06db9b1</Data> <Data>C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\MicrosoftEdgeCP.exe</Data> <Data>C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\EdgeContent.dll</Data> <Data>d4d4b0fa-db8d-431f-b587-4e3d6799de80</Data> <Data>Microsoft.MicrosoftEdge_40.15063.0.0_neutral__8wekyb3d8bbwe</Data> <Data>ContentProcess</Data> </EventData> </Event> I ran FRST64 and in Addition file it showed a bunch of these. Date: 2017-05-04 23:30:17.567 Description: Code Integrity determined that a process (\Device\HarddiskVolume4\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\MicrosoftEdgeCP.exe) attempted to load \Device\HarddiskVolume4\Program Files\Malwarebytes\Anti-Malware\mbae64.dll that did not meet the Store signing level requirements. FRST.txt Addition.txt
  9. I installed over the previous Beta 3.1.0.1716 and all my settings remained. Looking good. Jim .
  10. I have installed the Beta 3.1.0.1716 CP 1.0.115 and the problem with Norton Exploit Prevention is FIXED. All systems a go on the new Beta and this will be the last update on this thread. Jim
  11. Here are my scan results on my W10 desktop. All scans had every thing checked. 371,000 items. Ver 3.0.6.1469 Scheduled Scan 2:53 min CPU hit 95% Ver 3.1.0.1716 Scheduled Scan 9:40 min CPU hit 30% Ver 3.1.0.1716 Manual Scan Low Priority 9:16 min CPU hit 30% Ver 3.1.0.1716 Manual Scan High Priority 3:46 min CPU hit 95% Scheduled Scan must be at High Priority on 3.0.6.1469 and Low Priority on 3.1.0.1716. I like it like that and if I need a faster scan I can change the Priority to High for the Manual Scan, Jim
  12. You have an option to use lower priority on manual scans and it reduced my CPU from 95% to 30%. I have only had one scheduled scan and it ran at 30% CPU but took 9 min so I assume it is on low priority. Jim
  13. Glad to help. Many good people on here to help out. Jim
  14. It is a Malwarebytes file and safe to remove. The new install will install everything it needs. Jim
  15. If you manually try and remove mbae64.sys and it says it is in use then try this. Rename mbae64.sys by adding 1 letter in front of it like Ambae64.sys. Then RESTART your system and then you should be able to remove it. Then try your new install. Jim