21 Jul
According to THESYCON the creator of DPC Latency Checker, Windows is not a real-time operating system and processing of streaming data in real-time is a very challenging task for Windows based applications and device drivers. There is no guarantee that certain (periodic) actions can be executed in a timely manner. When I first downloaded DPC Latency Checker, I had no idea how to use it because there are nothing except a moving graph showing my computer’s current latency. Actually it’s pretty simple to use and diagnose your computer’s latency with this tool.
This is what I see when I run DPC Latency Checker on my computer. Most of the time the current latency is pretty low and stays below 500 µs. There are a few spikes here and there but it goes just slightly above 1000 µs.

However if you see occurrence of excessive DPC latency is indicated by a red bar like the image below, it means that your computer has drop-out problems.

To find out which driver is the culprit that causes the excessive DPC latencies, you can try disabling individual devices using Windows Device Manager. Go to Control Panel > System > Device Manager. In Device Manager, disable individual devices, one at a time. To disable a device, right-click on the corresponding item (e.g. on the Ethernet adapter) and choose Disable from the context menu. Windows marks a disabled device with a read cross. After you disabled a single device, carefully watch DPC Latency Checker. When excessive latency values disappear you found the responsible device driver. If there are still exceptional large DPC latencies try the next device.
When you have identified the device driver which is responsible for the drop-outs consult the device vendor’s Web site or customer support to find an update for this driver. If this is not possible you may decide to keep the concerned device disabled while you are using streaming applications.
There are a lot of hardware devices listed in your Device Manager. You should not disable devices that are essential for your computer to function such as keyboard, mouse, IDE/SATA controller, display adapter or any device listed in Device Manager under System devices or Computer. In many cases DPC latency problems are caused by specific types of devices. So you should try the device types listed below first.
Network adapters for Ethernet and Wireless LAN Internal modems Internal sound devices (on-board sound systems) Any PCI or PCI Express add-on card, any PCCard or ExpressCard, e.g. TV tuner cards, ISDN or DSL adapters, modems, etc
[ Download DPC Latency Checker ]
DPC Latency Checker is a free and portable tool that runs on Windows 2000, XP, XP x64, Server 2003, Server 2003 x64, Vista and Vista x64.
Technorati Tags: dpc, latency, dropout, audio, video, streaming
: Copying this article to your website is strictly NOT allowed. However, if you like this article, you can use the HTML code below to directly link to this article.
Extract or Rip Audio from DVD, VCD, AVI, MPEG, MPG, DAT, VOB, MOV, FLV Videos to MP3 Download Any Files From Any Website Including MySpace MP3 How To Record Malaysian Radio Streaming Broadcast On Computer How to Extract Audio from Video and Convert Media File Format Stream YouTube Videos Faster and Smoother Checking Installed Audio and Video Codecs On Your Computer Download and Stream Online Videos Faster Without Buffering Problems
Have computer technical problems? Get FREE help from Raymond.CC FORUM
4 Responses for "Possibly Solving Audio or Video Streaming Drop Out Problem"
apparently my laptop’s built in webcam was causing latency. searching for new driver now.
Nice find, i needed this application as i have the same problem in windows 7, when minmizing/maximizing windows.
I’ve been using this utility for a while. I work work audio recording and this tool showed me I have to disable the wireless driver in order to get rid of dropouts in my HP laptop!
I had a lot of trouble with audio glitches under vista. A dedicated audio card didn’t help (always had the feeling the onboard NIC and audio didn’t work well together). A few days ago I discovered the DPC latency checker and it narrowed the problem to the NIC.
The strange thing was that it was only a minor to no problem problem (low peaks) after a fresh system start, but “evolved” after some hours. In a way this implies that the driver is not the problem per default (according to this article in a way “just” vista is the problem anyway: http://blogs.technet.com/markrussinovich/archive/2007/08/27/1833290.aspx).
Well, the point is: I just used TCPview (http://technet.microsoft.com/en-us/sysinternals/bb897437.aspx) and the winmgr.exe was querying a lot, trying to connect to a dubious IP. Killed it and the DPC peaks vanished. Well, maybe a trojan, just checking…
Anyway, it seems that a “bombing” process can be the problem and just doing as the DPC tool suggests – disabling drivers and already being at the bottom of the problem – might lead the wrong way. It’s more like an indicator…?
Leave a reply