Warning: Beware of DPC Latency in Intel PROSet Ethernet NIC Drivers - 2014/15

[RoutedScripter]

So

I just happened to notice I had a big DPC problem after about a year or a little less since i updated the network adapter drivers.

I think I had the 19.3 version, now I got the 20.2.3001.0 PROSet, which didn't fix the problem.

I was playing Kerbal Space Programme and clicks and pops got very annoying, I'm not sure why Starcraft 2, Company of Heroes 2, Sniper Elite 3, Grand Theft Auto 5 and 4 never experienced sound issues, or they manage to compensate and hide the issue.

Hopefully fixing this DPC would fix the flash content and ocoshape stuff from lagging the stream, but Twitch worked fine all the time, just weird.

People say PROSet 19.1 work - please note that PROSet is a package that is applicable for a number of devices, the actual driver version of the specific device would vary and their version number is different.

With the latest Win7 x64 PROSet, my driver version for the 82579V chip is 12.10.29.0 and date: 2.5.2014

The big threads:
https://communities.intel.com/thread/43498?start=0&tstart=0

https://communities.intel.com/thread/54594?start=0&tstart=0

The DPC latency appears from NDIS.SYS driver.

 

[natr0n]

http://www.lucashale.com/timer-resolution/

use this prob solved

leave dpclat open click maximum on timer resolution and see if it drops latency which it should.

 

[RejZoR]

I know there was a compatibility issue with DPC Latency Checker on newer WIndows OS like 8.1 and 10 where latency would show as ridiculously high even though it actually isn't.

 

[Bo$$]

I know there was a compatibility issue with DPC Latency Checker on newer WIndows OS like 8.1 and 10 where latency would show as ridiculously high even though it actually isn't.

he is using it on Win 7

 

[RejZoR]

I think Win7 and Vista were also affected and it really only worked properly on XP. Can't remember 100% now...

 

[Bo$$]

I think Win7 and Vista were also affected and it really only worked properly on XP. Can't remember 100% now...

I've tried it on win 7 before, seems to work... they might have updated it at some stage?

 

[RoutedScripter]

I know there was a compatibility issue with DPC Latency Checker on newer WIndows OS like 8.1 and 10 where latency would show as ridiculously high even though it actually isn't.

Oh I'm "still" on Win7x64 and it doesn't look like I will move away from it anytime soon.

LatencyMonitor reported similar results, that's where I got ndis.sys from.

I will have tweaked win10 on the side but only for DX12 games, I might also make a super tweaked version of Win10 or newer that will use SysPrep and clonezilla image so I don't have to do thousands of tweaks before I can use a reinstalled or a new PC, something I should have done with Win7 but didn't had that much familiarity at the time with all this stuff.

 

[Aquinus]

I'm not actively using the Intel connection on my motherboard but I have exactly the same model however my version is 12.12.50.6. There could be a newer version of the driver. I'm also running Win10.

 

[95Viper]

Quote from Thesycon DPC website:

Windows 8 Compatibility: The DPC latency utility runs on Windows 8 but does not show correct values. The output suggests that the Windows 8 kernel performs badly and introduces a constant latency of one millisecond, which is not the case in practice. DPCs in the Windows 8 kernel behave identical to Windows 7. The utility produces incorrect results because the implementation of kernel timers has changed in Windows 8, which causes a side effect with the measuring algorithm used by the utility. Thesycon is working on a new version of the DPC latency utility and will make it available on this site as soon as it is finished.

Try using LatencyMon
Just released: version 6.50
Version 6.50 comes with support for Windows 10

It has a lot more user control, logging, and detailed info.
The pro and home are the same... the pro version gives you a license for commercial use.
Home is free to use.

 

[RoutedScripter]

There are several workarounds for certain NIC models, one of them is using the older driver, as I continued reading that thread, didn't manage to finish to the end tho, posting here because it seemed such a wide but rarely known issue, just so everyone else checks, it may help other people searching the web in future.