Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by tkmops

  1. Yes, I have a backup. I regularly clean my cache, cookies, temp, etc...using CCleaner, and clear browsing data from my chrome. Passwords are secure(not online anywhere). Will post back soon.
  2. Thanks for the fast response. As I do eBay, and can't afford NOT to have my PC up, I try to limit my re-boots(I've had some BSOD's in the past). I will post back after my next reboot and 'dust bunny' canned air clean up.
  3. You can rename the title, and maybe outline the steps you want to take? It's almost dinner time here, so I'm signing off until tomorrow.
  4. Thanks for offering to help update my system. What should I make the subject...something like 'For AdvancedSetup'?
  5. OK, will do as soon as I can...might be awhile
  6. Whoops, spoke too soon, the bad sound has returned, and PCI/PCI-e bandwidth usage has gone up to 1.82%, after about a day of good sound. I've got web protection turned off again.
  7. Been about 4 hours with good sound and no system slow down or lock-up. Looks like the latest update fixed the issue. Thanks Technos!
  8. Just downloaded the current update(7-13-20) to version package 1.0.26779 component package 1.0.979. Turned Web Protection back on(been off for about 4 months). After 30 mins(before bad sound would start within 10 mins), I'm having good sound, and my PCI/PCI-e bandwidth usage is way down to about .04%. I'm going to play audio for a few hours and post back with results later.
  9. How's the security with Edge? Stand-alone, does it offer the same protection as my Chrome with all my extensions? Or, would I need to add some?
  10. Ah, so then, it's not the Web Protection, by itself, that's causing the bad sound. it's a combination of high bandwidth using programs?
  11. Oh, yeah, I remember those days, when one had to set the IRQ settings on your motherboard to get devices/drives to work together...fun times. So, we think that this is a PCI/PCI-e bandwidth issue? Sounds very possible. When did Malwarebytes start including Web Protection with Malwarebytes Premium? Was it with the update in Feb 2020? If so, then that's the issue, as before Feb 2020, I used to be able to have all my programs running, playing audio, playing video, all with no problem. No, haven't tried MS Edge Chromium or SRWare Iron, but have used Firefox. With C
  12. No, I don't remember the version I was using that worked. It was the version just prior to the Feb 2020 update.
  13. After some experimentation, I found this: Sound OK with Web Protection on, torrent program up, chrome down Sound Ok with Web Protection on, torrent program down, chrome up bad sound with Web Protection on, torrent program up, chrome up So, the torrent program doesn't seem to be the issue, nor the chrome browser. But having them both running at the same time results in the bad sound(RAM issues?) BUT, I used to be able to have ALL my programs running with NO bad sound up until the Feb 2020 MalWareBytes update. Are there any other experiments I s
  14. Yes, but have been for years, when MalWareBytes was not causing sound issues. Should I try stopping my torrent program, turning Web Protection back on, and see what happens? I'll try that now.
  15. Just upgraded to the latest version Malwarebytes version, component update 1.0.972, Update package version 1.0.26203, turned 'web protection' back on, good sound lasted about 10 mins, then reverted back to what it's been since Feb 2020...cracking, popping, with a spiking CPU. Turned Web Protection back off, sound OK now. Did this latest upgrade fix anyone else's sound problems?
  16. Just curious, have the technos found the fix?
  17. For everyone, especially the new people, read this post by 'exile360' from Apr 17:'I suspect that it was the I/O, not RAM usage, that caused the sound to stutter. The issue is likely related to DPC latency, and somewhere between your sound driver and network driver (which is where Web Protection in Malwarebytes comes into the picture) there exists an issue with interference. And this post by 'AdvancedSetup' Staff, on Apr 15:No promise this will fix your issue but you can do the following and let us know. Option 1: Disable Web Protection via the tray icon Option 2: Revert to Malwarebytes
  18. There was a post by one of Malwarebytes technos,(a few weeks back) that to resolve the issue, while they are trying to fix it, we can 'roll back' to a prior version of Malwarebytes. In my mind, that indicates that this 'bad sound' issue(something about increasing the cycles...which puts a strain on your CPU), was due to one of their updates sometime in Feb 2020. Now, even though I've been a IBM mainframe hardware/software tech since the early '70's, I'm not a PC expert. But, there could be a case made, that a combination of Malwarebytes updates AND issues with Realtek audio and
  19. Ah, yes, 'definitions' was the word I was looking for. Thanks for the fast response.
  20. Porthos:While what you suggest might resolve the sound issue, wouldn't that leave a 'hole' in our protection? Or do the updated virus/malware prevention measures reside in other updates? Or, in other words, will 'reverting to an earlier component package version' keep us protected from all current malware, or will there be a gap in our protection?
  21. I have the latest drivers, and Win updates. This has been going on since Feb 2020, hopefully the Malwarebytes technos are still working on this issue. I've still got 'web protection' turned off all the time.
  22. I do, a B75A-G43. But, I've had it for years with no issues, until Feb 2020, when the bad sound started.
  23. Restart(reboot) my PC, or restart Malwarebytes?
  24. Just downloaded and installed an update current version:, package 1.0.23104, component 1.0.875 Turned on 'web protection'(which has been off for a few weeks). Eh, bad sound came back in less than an hour.
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.