New
#11
I have the same problem as DarrylGittins.
Does somebody of you have a solution yet ?
Crackling sound and audiodg.exe problems
-
-
New #12
I hate to tell you guys this but this is in fact a driver problem for certain. I had the exact same static sound problems with both my audigy 2 and 2zs cards on two completely different machines. The problem was fixed using the Daniel K drivers. These are the good ones with all the bells and whistles, these are only for the audigy series. You do have to use a torrent to get them though.
It says the drivers are for Vista but work perfectly with Win 7. There is also a Win 7 version of this torrent floating around but they work just as well. You guys with other creative cards should try googling for them. Good luck and don't forget to rep.
Creative Soundblaster Audigy Series Vista Drivers [by daniel k] Torrent Download - Torrent Reactor NET
-
New #13
Audiodg problems ARE related to drivers
I can also confirm that drivers are the big issue with audiodg problems. I'll give you a brief overview of my history of audiodg problems, and my workarounds and solutions thereof:
First off, the build of Windows 7 I'm using now was an upgrade from Windows Vista Ultimate, which was installed in September of 2008. So, technically, I've been on the same "run" of an OS since then. Almost immediately (or within months) of installing Vista, I was having audiodg problems (although I didn't know it was as such at the time). I never have had problems related to cpu or memory usage with audiodg, instead, the problem has always been related to sound "popping" or "crackling" that many (unfortunately) have come to dread.
I have a Realtek onboard sound (don't know the exact model), and although they are better at handling audiodg, it seems Realtek can't shake the "popping" issues. I know other people with realtek boards and the same problem in Vista / 7 (popping issues, but no cpu / memory issues).
What I found in my initial investigation with the problem on Vista was that all the "hand-me-down" suggestions (disabling enhancements, lowering the output quality) had no effect on my system. After trying nearly everything, I eventually found that disabling my network adapter (disabling, not uninstalling) would immediately rectify all sound issues. This was regardless of network usage / cpu / memory usage. I tried a myriad of different experiements with different levels of usage, but, it made no difference. Sound popping would persist as long as the network adapter was enabled. I could have Media Player as the only program running, and the popping would persist, and conversely I could have a bazillion programs on, and I'd have stints where the popping wasn't so bad. However, disabling my network adapter (which was installed on a PCI slot -- it's a Linksys wireless-n adapter with the latest drivers; I also have an internal network adapter which is permanently disabled) would always fully fix the issue.
The sound popping was extremely frustrating, and it nearly led me to doing a clean install of Windows (way back in October 2008). When I could, I would disable my network adapter to listen to pure, uninterrupted music. Re-enabling the adapter would bring the popping back within seconds. However, eventually, the problem just went away, for really no known reason.
What I found out later, after doing a full system defrag (using the -w switch to also defrag files larger than 64 MB), that the sound popping returned. But, after a week or so, the popping disappeared. I ultimately found that performing a full defrag would have temporary effects on the sound popping. It was just something I came to live by.
Eventually, after updating my sound drivers from Realtek (they release updates on a near-weekly basis), I found that the sound popping was completely removed from Vista, even after defrags. My system was running with flying colors.
Forward to October 2009, and I upgrade to Windows 7. Initially, as with the later months of my Vista run, there was initially no sound popping in 7. However, in the last couple of months or so, sound popping has returned, although, not in the severity that it existed in Vista when it was present. The popping seems to have very short stints, or may persist throughout a boot (at which point it often is rectified upon restart). It also now appears to be unrelated to defragging. But, most of the time, it isn't there. There have been one or two occassions where the popping got quite bad, as bad as it was in Vista initially. And, again, disabling the network adapter fixes all issues, as it did in in Vista. But, unlike Vista, there does seem to be a correlation with system usage and the popping in Windows 7. Sound popping is more likely to occur in games now (the opposite seemed to be true with Vista), and in general is more likely to occur when the cpu has more to do.
But, it seems to be all within the drivers. I have yet to upgrade my drivers from the initial upgrade to Windows 7 (which was release R2.35), since then Realtek has offered many more driver updates (currently at R2.47). After updating to the newest drivers, I have yet to report any sound popping problems, but, that could change with time. After all, I went for a couple months in 7 with the same drivers and no sound problems.
In short -- if you continue to have sound popping problems with Realtek sound, explain your situation to Realtek, and hopefully they will improve their drivers in the future. The answer to to audiodg problems has to reside in with the drivers....
-
New #14
The thing is, audiodg may show abnormal cpu or memory use if there are driver conflicts within the system. There's been many here with cracking/popping issues, not all were related to the Realtek drivers. Several have been related to background programs from nVidia, or a virus scanner subsystem that continually scans the hard drive.
Here's a great tool for checking your system's realtime capabilities.
DPC Latency Checker
I've been using Realtek audio on a Gigabyte main board, with a built-in Realtek network adapter. The only problem I had early on was hardware related, my speakers weren't making a solid connection and the Realtek driver kept re-setting thinking I had plugged in a different device. Also have an M-Audio-Audiophile 24/96 audio card installed and running well. Caveat.. I have customized this system for audio use, and have built/sold a couple dozen machines for studio use, starting with WinXP, I may have more processes/services disabled compared to your average user.
Here's a list of the things I remember that have caused audio anomalies.
Older BIOS, update the BIOS to the latest available.
Update the motherboard's inf drivers.
Update your audio card's drivers.
Get the latest Network adapter drivers, (including wireless).
Check Task Manager for any processes using an abnormal amount of CPU.
Update your graphic drivers.
Check Task Manager Processes (and Services) for any background programs related to your Video card, disable them for testing.
Re-boot after installing new drivers.
Ap
-
New #15
Interesting tool. After some use with it, it basically confirms that that the source of problems reside with my network adapter (a WMP-300N linksys PCI wireless-n adapter.... which, for all intents and purposes, has been outstanding for 4+ years running now... they haven't updated the drivers for the device since 2007). That said, since updating to realtek hd drivers R2.47 yesterday, I've had no sound skipping problems, even though I will get lag spikes on the DPC tool. It makes me wonder what the DPC tool looks like when I actually am getting sound popping....
Also, for reference, I have an EVGA nForce 590 SLI AMD mobo, with the latest nForce drivers installed (just came out last month... 15.25 is it? I don't know, either way, since Windows 7 has come out, there have been problems getting the mobo drivers to fully install with the nForce series below 600 I believe... it seems that the RAID driver doesn't get installed, or something along those lines... that problem didn't appear to be fixed in the latest release, either).
One thing I don't understand about the tool... it says that the test interval is is 1000 microseconds. If I remember my scientific units, that translates to a millisecond. However, the x-axis on the graph is clearly in seconds of time. So, one bar on the graph would actually be 1,000,000 microseconds, not 1000. So, I fail to see why they say the test interval is 1000 microseconds.
But anyway, basically, what I found is that on a regular period of 120 seconds (2 min), there would be a spike of about 7.5 milliseconds (with almost near-precision.... unfortunately, in the screenshot I provided, I could only make the width of the window about 100 seconds in time.... but, as soon as the a red bar would fade out after about another 15 seconds, a new one would pop in... it was definitely occuring in 120 second intervals... without fail).
Then, every five periods (this corresponds to 10 minutes), there would be following the regular lag spike, a sequence of several lag spikes in a row (between 5 and 7 I think) all around 13 milliseconds in time would occur.... this happened, like I said, with very precise regularity. In the attached picture, you can see the first lag spike is the one that happens every two minutes, and the sequence following it is the intense one that happens every 10 minutes.
The lag spikes were independent of network utilization (well, to a point, I suppose... my Internet is capped at 512 kbps.... which is far less than the capacity of the network adapter). Zero network utilization would not affect the period of lag spikes, neither would full bandwidth usage.
Of course, disabling the network adapter in the device manager would make ALL lag spikes disappear, permanently (at least for 20 minutes or so while I was watching it in the background while writing this post!).... so, according to that guy called logic, it must be the network adapter. Furthermore, disabling the network adapter causes some short spikes the moment of disabling, and the same for re-enabling the device (a couple lag spikes occur the moment of enabling the device). This may be a natural phenomenon when disabling / enabling devices, I'm not sure.
My guess is that the driver is doing a something like a hardware poll every 2 minutes or so and is thus holding onto the cpu for an extended period of time during this poll, causing the DPC lag spike. ARP queries are sent out every two minutes, right? Maybe it's something to do with something like that. Who knows. It must be faulty driver programming, whatever the case.
That said, like I said, ever since upgrading yesterday to Realtek version 2.47, I've had no sound popping issues, even when these lag spikes occur. Even during those intense lag spikes, I've had music playing in Media Player, and have observed zero audio drop-outs. So, I'd really like to see what the graphs look like when I am getting those drop-outs.
But, it makes me really wonder -- is it really the wireless card that's the problem, or is it the way the card interfaces with other hardware in the system -- i.e. the mobo -- that's the source of the problems? I mean, it gets complicated when the sound is also onboard... sure, I could put the wireless card in another system, and maybe I'd find out that there are no DPC lags on that system... but, then, is that because the mobo drivers of that system are correct, or is it because the network drivers just happen to work more nicely with it? Where does incidence really lie? And then, there was the crazy thing where I'd only notice it in Vista after defragging for about a week or so, at which point it'd disappear.... talk about crazy! If one could analyze the linksys drivers, maybe there's a poll or some op that it does every 2 min., then we could blame linksys. But, without being able to see the drivers, either from linksys, or from nvidia ... it's really impossible to tell....
I contacted Linksys support about it, and, suprisingly, I got a really nice representative about it, who pretty much took all my claims without questioning them, and then said she'd forward the case onto management.... so, hopefully it'll get fixed (not likley, considering the drivers haven't been updated since 2007 for the wmp-300n).Last edited by hannedog; 18 Apr 2010 at 03:30.
-
New #16
Great post hannedog! woof!
I've come to the same conclusion and do believe that a lot of it has to do with the interaction of the onboard hardware devices interacting with the motherboard's BIOS, add to that the way the Win-7 organizes/prioritizes interrupt requests and you have a problem that has many answers. I've been hanging around here for a few months now and that's what I've observed.
One thing that made a huge difference in my system was a BIOS update. Using the DPC latency checker I was seeing spikes in the yellow every 15 seconds, even with all network, Firewire...ect devices disabled in Device manager. Nothing I tried changed the DPC latency, high of 700, low of 110. Updated the BIOS and DPC latency dropped to 47 with only slight variations. If I enabled the HPET (High Precision Event Timer) in BIOS, DPC latency increased to between 80-90, consistent with no spikes.
Users only see, at most, half the actual BIOS settings, probably much less than half. I'm guessing BIOS updates that tune the motherboard for Windows 7 timing are being made and that it will be a few months before driver technology and motherboard tweaks produce consistent results. Possibly a Win-7 service pack as well.
Ap
-
New #17
Wait, when you enabled HPET you got DPC latency increases? I though HPET was supposed to help. Or are you saying the increase is desirable, as long as it's stable, with no spikes? The moment you mentioned BIOS, the first thing I thought of was HPET, and how you can set it to 32-bit or 64-bit mode. On most BIOS, it defaults to 32-bit, which, of course, if you're using 64-bit Windows...
Too bad for me, I've been using the latest BIOS for, about.... oh, 3 years now. EVGA released a couple of updates for the BIOS shortly after it was released, but, pretty quickly thereafter discontinued official support of the 500 series (which, as a result, makes me unable to use AM2+ cpus.... that never has burned me too much though, besides quad-core, AMD's results with AM2+ were extremely disappointing.... and Phenom quite frankly sucked anyway. I disappointingly have found no AM2 cpu that bests in every way the one I currently have... which, is ridiculous, considering mine was released before AM2+ was).
I wouldn't be as optimistic there on that one. Well, not with regard to the "few months" aspect, anyway. I'm not sure how familiar you are with it, but, Windows 7 uses basically the exact same sound engine as Vista. In other words, parties all around the issue have had ample time to work on things... of course, things should eventually improve, but, they just might be slow-coming. Or, it has to do with hardware design that will only be rectified in the newest of hardware / future releases. I doubt I'll ever see a true fix on my system. But, since I can usually circumevent the problem about 90%, it's mostly a liveable thing (I hate it when it starts acting up, though... oh man, there have been a few occasions where the sound popping just likes to spaz out, it's like it has a personality... and I am almost just in utter disbelief at what's happening... but, strangely, only a few times has that happened... just like the loyal dog who only misbheaves a few times.... lol).
-
New #18
No, the HPET latency increase wasn't desirable, but at least there were no spikes.
All I know is HPET is the new multimedia timer that's supposed to offer some big advantages over the older system timers that were being used.
There has to be something noticably different between Vista's audio sub-system and Win7's. Many users have come here with perfectly working Vista systems unable to get Win7 producing similar results... main complaints: Skips, pops cracks.., low volume, no sound & conflicts with other installed devices.
Ap
-
New #19
Well, there are differences, but "noticably" is stretching it. Thing is, it seems a lot of Vista people were able to successfully circumvent the problem in some way... only to have the problem re-appear with Windows 7. I'm one of those people. I've been following this issue for years, since, as I stated, it first plagued me with Vista (I'm on the same system as I was with Vista).... and despite my efforts, the problem seemed to disappear on its own after time.... and came back after Windows 7. My guess is the rise in "re-occurrence" with audiodg issues has more to do with other things that have changed in Windows 7 as opposed to the audio engine. Those other areas caused some misbehaving drivers which conversely affected the sound. And, naturally, once those kind of drivers got cleaned up in the months since 7's release, the audio problems for those people disappear pretty soon after that.
But, unfortunately, as for the core issue itself with audiodg, it seems there's still quite a bit of work to be done. As I never really "fixed" my problem when it was on Vista (instead having the good fortune of it just disappearing), the fact that it reappears on Windows 7 whenever it isn't in a good mood kind of reinforces this idea. Myabe there's some BIOS optimizations that could be done (but won't) for my system? Maybe audiodg could be improved? Who knows. But, given this has been the state of things for... going on almost four years now (since Vista's launch), it's likely not going to be fixed any time soon.... or maybe it'll just get fixed when I finally build a new system (in another two years).
-
New #20
After the BIOS update... I have zero issues.
As a test I just ran WMP playing a DVD, Winamp playing an MP3 file and IE8 playing a you tube video.
Audiodg checked in at 2 to 4% CPU use and the system was still fast and smooth.
Using the Shark007 codec pack.
I do have some of Windows services disabled as well as not loading a bunch of background applets, especially the Realtek audio configuration panel, no need to keep that in the system tray.
From a clean boot, after the system "settles" I have 27 total background processes running.
Ap
Quote
Related Discussions