Could too much memory speed be causing an audio/video stuttering/1-2s desync issue?

Page 2 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.

josefbud

Reputable
Feb 17, 2014
35
0
4,540
Since day one -- from the day I built the PC back in May 2014 to now -- I've had an issue where the audio will stutter for a second or two then usually go back to normal, and sometimes go into a BSOD. It seems mostly random how often it occurs, sometimes it'll only happen once or twice in a day, usually it happens about 6-10 times in a day, but almost every day or every other day it will cause a BSOD or two (ntoskrnl.exe, sometimes combined with AvidMboxMini.sys but not always). Sometimes it happens while gaming, but it seems to happen most often when loading a new page in a new tab. All of the times it's happened in the last year or so, I think gaming has only sent it into a BSOD once. In fact, the last couple of days I've been listening to music and opening links on Reddit that lead to Imgur, and 90% of the time that I open an Imgur link, the music/audio stutters. Ironically, when I remotely accessed my PC from work to confirm the "ntoskrnl.exe" BSOD error while typing this, it came to my surprise that I was logging in after... drumroll please... A BSOD restart. While I was at work. Not even using my home PC.

To clarify on what the stuttering issue is, this is what happens every single time:

    1.) Video continues, but audio stutters; seemingly rapidly repeating the last 1-5ms of audio for about 1-2 seconds.
    2.) Audio goes back to normal, but the video stops in order to catch up and resync
    3.) Video starts again once the two are synced up, and things are back to normal until it happens again


What I've already tried:
For a long time I thought it was because of my Avid Mbox Mini 3rd gen (AvidMboxMini.sys), which doesn't have great Windows support in the first place. So I tried re-installing the drivers and changing the buffer around, but neither helped. Since it's used for actively recording, it's recommended that it be plugged directly into the computer and not via a powered USB hub but I tried it out anyway and that didn't fix the issue either.

Then I realized a lot of BSODs were happening because of ntoskrnl.exe by itself, not just the combination of the two. It also worked perfectly fine on my laptop, which is what I was using for years before I built this PC. So I tried updating my BIOS a few months ago. Weirdly enough, I don't know why but, the issue seemed to be fixed for at least a week or two and then started back up again.

The only thing I can think of is that I either need to replace my Mbox Mini with something else, or I need to get new memory at a lower clock speed to better match the CPU clock. Right now, I have an i7-4770K at 3.5GHz (stock speed) and G.SKILL TridentX 2x8GB DDR3-2400 (10-12-12-31) (F3-2400C10D-16GTX). The FSB : DRAM ratio in CPU-Z is 1:5, and I know that it's preferable for it to be 1:1. My motherboard has even automatically underclocked the memory to 666MHz.

Before I go spending $100-$140 on new DDR3-1600 memory, I wanted to ask if this is even the issue. If it's not the issue, what is the issue? I'm great with computers, have been since even my preteen days, and I even work in IT, but I'm at a complete and utter loss here.

Full Specs:
Motherboard: ASUS Z87-EXPERT
CPU: i7-4770K @ 3.5GHz (stock)
Memory: G.SKILL TridentX 2x8GB DDR3-2400 (10-12-12-31)
GPU: EVGA GeForce GTX 760 4GB SC
Main Storage: Samsung 840 EVO SSD - 500GB
Secondary Storage: WD Black 7200RPM - 3TB
PSU: Corsair HX850 (850W)
 
Solution


Yessir! Thank you so much again for your help :)

And thank you to Tradesman1 as well!

On a sidenote: I can't mark my own reply as the solution. If either of you want to just post a reply saying "unplug the Mbox" or whatever so I can mark it as the solution for anyone who happens to have the same rare issue, go for it. Unless that's against the rules or something. I don't want to start trouble :)


I did consider that. When I first built the computer I'm fairly sure I completely disabled the built-in AC97 audio jacks in the BIOS and simply didn't install the drivers for it until several months later, only installing drivers for the Mbox Mini, but the issue has been with me since that first day. All of the drivers are up-to-date now, I checked on that as well.

Mbox Mini/Pro Tools are mostly (70-85%?) used on high-powered Macs, so their Windows support is just atrocious. If I get bored one day I might try to hook up my older generation Mbox Mini and see if that works better.
 


Are the audio jacks still disabled? If so, enable them and see how it runs.
Edit: Also ensure that your drivers are up to date and the Mbox isn't plugged into a USB 3.0 port
 


I enabled them a little bit before the GTA V release after buying a gaming headset, since I couldn't plug that into the Mbox. I've kept it enabled since then :)

Drivers are definitely up to date. I thought the USB 3.0 port might be an issue, since it was an issue on my laptop, so I plugged it into a USB 2.0 hub that is connected to a USB 3.0 port (I don't have any USB 2.0 ports on my PC). It used to be plugged directly into a USB 3.0 port for a while, until I tried resolving the issue by plugging it into the hub and I just never bothered to put it back even though the issue was still there.

Given how cheap it is, I've been considering buying a PCI-E USB 2.0 card. I bookmarked a couple of them a few months ago and haven't gone back to it.

Edit/Afterthought: Whoever f*cked up the backwards compatibility of USB 3.0 ports is an a**hole.
 
Hahaha the edit made me laugh :)

I'd definitely recommend trying them directly in a USB 2.0 socket attached to the computer rather than a hub, as the hub is still plugged in through 3.0 so might be mixing things up, which the driver isn't handling well so therefore creating audio issues and BSODs. It might be worth grabbing a hold of a PCI-e USB 2.0 card, be it borrowed or bought.

As a last resort, is there anything preventing you from using the Mbox with your laptop?
 


Laptop stays at work now, and plus it's underpowered for doing good studio work... The whole reason I bought the PC was because the laptop wasn't handling it well =\
 


Oh. Well see if a PCI-e USB 2.0 card works first, as you stated in your original post that it worked fine on your laptop, presumably you weren't using 3.0. What OS did your laptop run as well?
 


Yeah, I'll end up giving that a try next...

My laptop runs on Windows 7 Home Premium, and my PC is on Windows 7 Professional.
 


Well, I'm glad I didn't buy a USB 2.0 card/module.

I can't remember why, but I was browsing my motherboard's manual PDF last night and found out that it has 4 of those 9-pin USB 2.0 ports that you usually connect front-panel USB 2.0 to or a little module that goes into a rear slot but doesn't actually plug into a PCI-E port. Closest I could find it referred to is "IDC" and/or "motherboard header" so hopefully you know what I'm talking to.

So I opened up an extremely old (AMD Sempron, 512MB RAM), but literally never used, Compaq PC from work and took out the part of the front panel that had the USB 2.0/FireWire/audio ports and brought it home. Just opened up my PC, plugged in the USB 2.0 ports only, and fired it back up. Plugged in a USB drive and transferred a file to make sure it's fine, then plugged in the Mbox Mini, re-enacted the issue, and sure enough it isn't fixed -_-
 


I mean I could do that, but if it works on the VM and that means I have to reinstall Windows to downgrade to Home Premium, then that's just one thing that's not really worth doing in order to fix this (now minor) issue. Is that the end game with this one?
 


Yessir! Thank you so much again for your help :)

And thank you to Tradesman1 as well!

On a sidenote: I can't mark my own reply as the solution. If either of you want to just post a reply saying "unplug the Mbox" or whatever so I can mark it as the solution for anyone who happens to have the same rare issue, go for it. Unless that's against the rules or something. I don't want to start trouble :)
 
Solution