Audio Glitches in Recordings

[mooshoo1]

Hello everyone! I'm so sorry if this is in the wrong spot . I am a newbie so I thought it was appropriate.

I have been recording from home for about 10 years and I haven't had many problems until I upgraded to the NT1A. I used USB in the past.

My old PC ever since I had the Rode, would sometimes do audio glitches that would totally ruin a recording. It would happen once in a while, but I kind of got used to having to just re-record the parts that were ruined by the glitch. Now that I built a new PC, I was hoping that would eradicate the problem (cause aside from the graphics card and hard drives, most of the pc is new...) or at least reduce a lot of the glitches.



My PC is...
Windows 7 Professional 64-bit
Intel i7-4930k CPU
16GB Ram
AMD Radeon HD 6800 Series
P9X79 LE MOBO
Hyper 212 EVO 650w PSU

I have a CI2+USB Audio Interface by Steinberg, and like I said previously, am using a Rode NT1A.

I have googled audio glitches to no end, and the pictures I am finding of the glitches and possible solutions doesn't really look like the glitch I am getting... it doesn't happen all the time.. but when it does happen it's uncontrollable and seems to never end.

Could this be a power supply issue? It happened on my old PC with a different Power supply as well as my new one, so I'm not 100% sure if that is the issues :S. I really have no idea. Like I said it's been doing that since we got the mic, so I doubt it's the cable. (I read that glitches may start due to dirty XLR cables).

If anyone can help me any to try pin point what in the world that is, that would be awesome! I am new to using Interfaces so I really have no idea what I'm doing.

 

[Pinky]

Failing or inadequate power supply, overheating, bad memory, failing motherboard, failing hard drive, even a failing sound card/device... any and all of these can cause this.

Looking at your specs and assuming there's no hardware failures at the root of the issue... if you have 4 banks for memory and they're all being used (4x4GB?), try removing one pair of memory (2x4GB) and see if that helps. Also, there's a free bootable CD app called memtest that ... you guessed it, tests your memory! That would also be a useful thing to try.

http://www.memtest.org/


If you get ANY errors, there's a problem. It would likely be one or more bad sticks of memory, but could also be a bad power supply, motherboard, cpu, etc. This is a general test in that it checks the memory's ability to write/read data without generating errors, but the underlying cause for the conditions that create the errors can be the components that work in tandem with the memory.
It's a tough thing to troubleshoot.

 

[bouldersoundguy]

Does the machine have wireless? Turn it off and see what happens.

 

[BroKen_H]

It would seem, if you replaced MB, memory, CPU & Power supply and this is a similar sounding glitch, but has only become more frequent. So:

Observations:
The only items that have remained the same are the mike, interface GPU and hard drives. One of these must be the culprit. It almost has to be the mic and/or interface as that's where the problem started.
I can't imagine how a hard drive could cause audio glitches, so let's look at the three that might.

Questions:
Every three seconds, what is the pitch of the glitch?
Can you borrow a mic and interface from someone else and try them in tandem and in combination with your units?
Can you pick up a cheap video card and see if trading that out solves the problem? (This is not likely the problem, but if the rest don't solve, this must be the culprit).

 

[mooshoo1]

My husband seems to have gotten it working now! I wasn't 100% watching my husband cause I was cleaning, lol, but he said he played around with new drivers and deleted a file in Acid.

@ Pinky - I did Memtest already . All is good! Thanks a lot for reading and for the info.

@ bouldersoundguy - It was disabled, and we also unplugged our internet extender. Thanks for the tip.

@ BroKen_H - Yeah when you mentioned about the Interface we realized along side the hard drive and graphics card, it could only be one of a few things. But last night, I had the program I was using the interface in freeze on me 4 or 5 times and everytime the program would not close unless we unplugged the interface, so we figured the interface was our problem. After that my husband played around with it and seems to have fixed the issues. Thanks a lot, if it wasn't for your tip we wouldn't have figured out it was the interface .