Skip to main content

Windows 8 audio clicks and glitches narrowed down to Malwarebytes

Ever since I got my Windows 8 PC, I have been having serious problems with audio.  Basically all sound playback on my system experiences a brief  but frequent click, skip, glitch, stutter, whatever you prefer.  I can reproduce the issue on any sound card or firewire sound interface (devices tested include the onboard Conexant SmartAudio HD, my external Phonic Helix 12, and my Edirol FA-101).  All of them seem to have audio clicks, with the firewire interfaces' clicks seeming more harsh for whatever reason.



At first, as an audiophile, it was just hugely obnoxious - but then I realized it was also an issue on recordings made via my sound interfaces.  This, to a home recordist, is more than just a serious problem, it's a deal-breaker.

After I got done grumbling about how Microsoft took a great thing (Windows 7) and "fixed it", I got down to business trying to figure out exactly what was causing this issue.  I found out the glitch is very easy to isolate when listening to a study tone.  I used a tone generator plugin in Reaper.  The click happens about every 5-10 seconds...  Never more than 12 seconds apart.

Next I used msconfig to pare down the suspect services.

One of these services is it! Actually, it's MBAMService

Later I determined that MBAM website blocking seems to be more specifically tied to the issue.

By disabling startup services in progressively smaller groups and rebooting a lot, I finally narrowed it down to Malwarebytes, my anti-malware protection tool of choice.  Specifically, the issue goes away immediately when I disable the website blocking feature.

So of course, on one hand, I'm pretty happy.  It means I don't have to reformat my computer and start all over. On the other hand, I do have ask the question, why was this never an issue until I started running Windows 8? I've been an MBAM user for many years.  Clearly there is some kind of minor compatibility issue between MBAM and Windows 8.  I wonder how long it will be before this is figured out.  In the meantime, it looks like I'll have to remember to disable website blocking before I start a recording session.

Anyway, I hope this post saves someone who is experiencing a similar issue some time. Lord knows I found a TON of Google results for the keywords "Windows 8 audio click"...  Mostly forum posts by people looking for help, and I saw very few resolutions.  My bet is that a bunch of those are people running MBAM.
Labels:

Comments

Anonymous said…
This comment has been removed by a blog administrator.
1:35 AM
Scott McGrath said…
There is a thread on this at the Malwarebytes support forum:

http://forums.malwarebytes.org/index.php?showtopic=123263
9:27 AM
tim gueguen said…
I'm using Win7 and had the same problem. Fortunately Malwarebytes was the only program I had installed just before the problems started, so it was pretty easy to determine the source.
4:37 PM
Post a Comment

Popular posts from this blog

Reaper, Linux, and the Behringer X-Air - Complete Studio Solution, Part 1

Introduction and Rationale This is part one of a major effort to document my experiences with recreating my home studio, entirely using Linux.  Without getting into too many of the specifics, a few months ago I decided that I was unhappy with Windows' shenanigans - to the point that I was ready to make a serious attempt to leave it behind.  For most in this situation, the obvious choice is to switch to Mac OS.  With its proven track record, support, and options for multimedia production, it is naturally the first alternative to consider if your goal is to simply use something other than Windows. For me the choice was not so simple. I despise Mac OS and, in general, the goals and philosophies put forth by Apple in an effort to ostensibly provide users with an "easy" working environment.  It does not help that I have also failed to find any aspect of the Mac OS UI intuitive, but I realize that this is a subjective matter. With my IT background and user-control* favori
Post a Comment
Read more

An Alternative Take on AI Doom and Gloom

 I've purposely held my tongue until now on commenting about "AI" (or, more specifically as has come to be known, GAN or Generative Adversarial Networks).  It seems like it is very in-style to complain about how it has made a real mess of things, it is displacing jobs, the product it creates lacks soul, it's going to get smart and kill us all, etc. etc.  But I'm not here to do any of that. Rather I am going to remind everyone of how amazing a phenomenon it is to watch a disruptive technology becoming democratized From the time of its (seeming) introduction to the public at large, around November of 2022, to late 2023, the growth and adoption rate has been nothing short of explosive. It features the fastest adoption rate of any new technology ever, by a broad margin.  To give a reference, the adoption rate for AI image and text generation, real-world uses, in just 12 months is comparable to all of that of the another disruptive technology, the World Wide Web, takin
Post a Comment
Read more

RANT TIME: Why do replies to a message I sent go to my spam folder?

Despite what one would think/hope, sending a message to a given address does not inherently give Google a high confidence that a reply from this address is expected (and, for example, that it should bypass spam checks). I have confirmed with Google's tech support that there is no way to automatically have this happen. The user can do the following: 1. Add the address to your contacts list in Gmail. 2. Check spam folder for replies, and mark it as "not spam" if something ends up there, which should influence the fate of future replies received. I can also approve an address at the domain level, i.e. if it is a big vendor or similar. I've had to do this with several of our Chinese vendors. I regularly ask engineering and purchasing to give me a list of the supplies we deal with, so I can approve them as a preventative measure. For what it's worth, all of the false positive instances of reply -> spam we have experienced have involved the sender's email server
Post a Comment
Read more