Teamspeak screws up my computer..

Heya peeps, I'm kind of desperate for help here.

I joined up recently, and I've been longing for some good drops with you. But teamspeak does not seem to agree with my computer in any way whatsoever.

Hardware:
Intel i5 750
8 GB RAM
120 GB SSD
ATI 7870
Logitech G35 headset

Symptoms:
When I run MWO at the same time as teamspeak I get increasing amounts of CPU usage after each match. In the end, my whole computer is borderline unusable.
The teamspeak process is fine, it uses quite low amounts of CPU. What fucks things up seems to be that TS injects it's codec into the windows audio service (audiodg), and that in turn uses the DPC service for realtime audio. When I check what is hogging my CPU, it's the DPC service in windows.

The DPC service doesn't get better even after I've shut everything down, it still hogs resource like crazy. Only remedy seems to be a reboot.

Diagnostics:
Have tried both 32 bit and 64 bit TS. Have tried using both wav and directsound in it. Have disabled all plugins (including overlay). Googled for the problem, and it seems that there are some ppl who have had problems with TS and DPC, but most were years old and didn't have any relevant info on how to solve the problem (tried a few things, nothing worked).

I downloaded a small application that graphs DPC latency, and it's quite clear that it increases a bit every time I run MWO. For the first match, it's not that bad. In the second match, I start to get some jerkiness. In the third match, it's unplayable. Interestingly, when I run testing grounds it doesn't get bad as quickly (can go 4 testing grounds until I get a noticale increase in DPC latency).

I have updated my sound drivers. Made no difference. Tested different USB ports, made no difference.
I've disabled all other sound sources on my rig (ati hdmi sound, built-in AC97), made no difference.

MWO itself works fine, can run it well at max settings. I usually run mumble (which I find to be vastly superior to TS3, but that's another story) for voip at the same time with a friend who can only play mondays-wednesdays, and I've never had any problems. Something is wonky with TS3.

Conclusion:
Somehow, MWOs sound system and TS appear to royally hate each other on my rig.

Plea:
Help me Obi-Wan Kenobi, you're my only hope!

Any ideas are welcome at this stage. Except stuffing a lobster up my bum. That's just stupid.

 

Hmms.. Haven't tried switching to the built in audio. Gonna give it a try.

 

Did you try uninstalling the G35 drivers?

 

What OS are you running? I just did a little googling and it looks like Win8 changed the procedure for processing audio, which in turn leads to the higher latency times. Now why that would be connected to increase resource/cpu use, I have no idea.

If you can find a download, you might also try an older version of TS3 to see if that produces the same effect. Other than that....I don't have ideas for you either.

 

Regular windows 7 64bit.

 

Other thread on this forum suggested running both as admin. But it was for the overlay issue.

I think you've tried every reasonable thing imaginable. I usually dismantle my whole rig and let windows find all devices again + updated drivers. Seems to work on most hw related problems.

 

Also i don't know if there is different clients for ts?

 

I don't know if it will make any difference or not. I'm running the same headphones and OS with absolutely no problem (after I set it to always run as admin--it wouldn't do push to talk before that).

Here is a link to a download page for older versions of TS3. It might be worth a shot for you Arete.
http://ftp.4players.de/pub/hosted/ts3/releases/

 

I used to have a similar problem with ventrilo. Whenever I would run ventrilo and speak it would increase the size of the audiodg process. After about a day's use that process would be taking up almost 2 gigs of ram on its own and I had to restart. If I used voice activation instead of push to talk it happened even more quickly. The problem was solved when I updated my audio drivers and windows.

 

I'll get to some thourough testing tomorrow night, can't be arsed to go out boozing anyways Thanks for all the tips.


Meanwhile, I'm rocking the com-1d a bit.

 

A few random thoughts:

If you have an old soundcard laying about, you might try installing it as a test.
You might try disabling your onboard sound in the BIOS and see if the problem goes away.
(Both of the above are meant for testing only, not as long term solutions.)

I'd also try removing all but one stick of ram and see if the problems gets worse (indicative of memory leaks)
Is your virtual memory filling up? Does increasing/decreasing page file size make any difference?
Does your DPS latency get worse in high action games? (with lots of noise data generated by shooting/ getting shot)
does firehosing machine guns the whole game bring on a faster crash?
Does it get worse through the match, or just a step worse before/after each game? (watch the lag)
If you leave MWO and teamspeak on for several hours does the problem worsen even though you aren't playing?
Have you run a test of your RAM?

If you have a spare hard drive, you could do a test total rebuild of your OS and install only MWO and TS to see if the problem recurrs.
There are often Microsoft certified drivers and manufacturer's drivers available on the website which are different. Have you tried both?
Have you loaded up the CPU, GPU and Network Meter gadgets, to see realtime how much usage they're getting? The Disk gadget, to see if you're thrashing the virtual memory for some strange reason?

Does the problem recur if you hang out on TS, but don't run MWO?
Is the progress of the problem directly associated with MWO usage regardless of frequency of usage?
Does logging out and back into windows cure the problem as well as a reboot?
have you tried playing MWO/TS under another user account on your same PC? Do problems experienced on each of the accounts add to each other?

Good luck and please let us know what happens.

 

I'm going to a much more basic question: Are you running BOTH TS and MWO in admin mode? I couldn't tell from your OP if you were running MWO in admin along with TS.

Does startup order matter? (i.e. if TS is up before MWO or visa versa).

 

I feel your pain. I just got my pc up and running. Ts works fine until I turn on the overlay. When I do that I can drop as a pug just fine but when im in a group I disconnect every time. I turn off overlay and everything is peachy. :-/

 

Hadn't even thought of running TS in admin mode, have tested it now and first testing at least looked ok. Could be logged in on TS and no adverse effects on the computer after three rounds of MWO. Will try joining up for a few drops and see what happens when there's someone on TS that's talking too.

 

Try running both MWO and TS as administrator. I had the same problem and doing that fixed it for me.

 

Admin mode for either or both made no difference unfortunately. Did try running on the integrated sound now, and that seemed to work. At least, no increased DPC latency while playing and being in a channel where ppl talked. Will get my old headset from work on monday and test it out for real.

Would be kind of sucky if the G35 doesn't work with TS. It's a bloody nice headset.

 

PLENTY of people are using those, I would doubt they don't work with 1 of the big 3 VOIP apps (Ventrilo, Skype and TS)...which is what most people need a headset with mic for anyway.

You're probably down to a driver conflict at this point. About the only suggestions I have right now are the usual advice you get for any windows installation: Doesn't work? Reboot it! Didn't work? Reinstall it!

 

didn't work for me unfortunatley.

 

I'll try reinstalling TS and see if that works.