Jump to content

LiquidTension

Staff
  • Content Count

    4,192
  • Joined

  • Last visited

Community Reputation

2 Neutral

3 Followers

About LiquidTension

  • Rank
    Malwarebytes Staff

Recent Profile Visitors

8,917 profile views
  1. Hi David, According to the most recent FRST logs, you still have a local system proxy configured which is likely the cause of your issue. Given you manually removed it previously, it's apparent there is something present on the machine that is regenerating it. You could start off by experimenting with a clean boot to see if a particular installed program is responsible. Beyond that, using something like Sysmon or boot time Process Monitor (assuming it's being regenerated at boot) may give you an indication of the source. I've attached a Sysmon config file that will monitor for and rep
  2. Thank you for the new troubleshooting data. Was C:\Windows\MEMORY.dmp created after this most recent BSOD? If it was, could you upload to WeTransfer.com please and share the download link. Thank you!
  3. @Hardhead This means the Malwarebytes Service took longer than normal to stop during Windows shut down. Unless you're actively experiencing issues at shut down, it's not something to be concerned by.
  4. Thank you for the report. We are investigating this issue and hope to address this with a fix as soon as possible. We'll update the forum when the issue is resolved.
  5. Thank you for the report. We are investigating this issue and hope to address this with a fix as soon as possible. We'll update the forum when the issue is resolved.
  6. You'll find the values in the following key: HKU\S-1-5-18\Software\Microsoft\Windows\CurrentVersion\Internet Settings If these are removed, do you still encounter the same issue?
  7. Thank you. This is the issue: "Exception details: text=SSL Exception: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed" You mentioned no proxy is in use, but the logs do indicate the presence of the following local system proxy configuration: ProxyEnable: [.DEFAULT] => Proxy is enabled. ProxyServer: [.DEFAULT] => localhost:8080 Do you recognise this?
  8. Hello, We have an open defect for this particular BSOD. To confirm, does this BSOD only occur when both uTorrent and Malwarebytes Web Protection are running? How often does it occur and are you able to reproduce it consistently? I've sent you a follow-up message with additional troubleshooting steps if you are able to consistently reproduce the issue.
  9. Thank you. That confirms it was indeed the known issue which should be addressed in the latest released component update.
  10. This is not an issue with the Malwarebytes installation process. The software in question (QQPCMgr) is preventing the Malwarebytes installer service from writing to the registry. This is an issue that should be taken up with and addressed by the vendor of the other software.
  11. Hi @brad03, Could you gather logs with the Malwarebytes Support Tool please and attach the output to a post so we can confirm there isn't an underlying issue here that needs fixing. https://support.malwarebytes.com/hc/en-us/articles/360039023453-Upload-Malwarebytes-Support-Tool-logs-offline Thank you!
  12. Hello, Thank you for the troubleshooting data. Unfortunately, there are various Windows Filtering Platform collisions between Malwarebytes Web Protection and other network filtering software. We are actively looking into potential solutions. In the meantime, you will need to keep Web Protection disabled whilst using Private Internet Access. See here: https://support.malwarebytes.com/hc/en-us/articles/360051090194 I've sent you a message with follow-up steps if you're able to consistently reproduce this BSOD.
  13. Hi @David H. Lipman, Thanks for the report. Could you run the Malwarebytes Support Tool please and gather logs: https://support.malwarebytes.com/hc/en-us/articles/360039023453-Upload-Malwarebytes-Support-Tool-logs-offline This will assist us in determining the source of the issue. Thank you.
  14. Great, thank you. We'll look out for your log file.
  15. Hi there, Thanks for the report. Just to let you know we are aware of this issue and are actively looking into it. If you encounter any further problems, please let us know.
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.