[SOLVED] Could somebody tell me what is causing my high DPC latency in Windows 8.1?

ganon11000 said:
I'll think about switching browser (I have 3 computers and chrome is great for sync)
I downloaded the driver, used athwb.inf and got a BSOD. All worked fine with athwbx.inf.
Now for more Xperf monitoring I guess?
Click to expand...

I'm suggesting to try Internet Explorer only temporary, to see if the integrated Flash player deals with video decoding better.

Yes, you can generate a new XPERF trace.
 
ganon11000 said:
IE Just freezes like it does on all of my PCs (No idea why) So I'll try firefox.
New Xperf:
https://drive.google.com/file/d/0B3-yyU44xFecY3EtbjljN1FTWDg/edit?usp=sharing
Click to expand...

The trace is pretty much the same as it was before. In addition, I see that you haven't followed all the commands I suggested.

By the way, you can try modded drivers (for Windows 7), which should resolved many issues with this Atheros devices:

  1. Download the driver and extract it to C:\Drivers.
  2. Press WIN+R.
  3. Type devmgmt.msc and press ENTER.
  4. Find your Atheros WiFi adapter
  5. Right-click on the device and select Update driver software...
  6. Click Browse my computer for driver software
  7. Enter C:\Drivers in Search for driver software in this location field.
  8. Click Next and wait for the driver to install.
  9. Reboot the system.
 
ganon11000 said:
View attachment 7255
This is what I'm getting when I try that.
Shall I try the laptop without the WiFi card inserted to see if it is the card and not the LAN causing issues?

BTW I'm probably going to buy this as the card I have is a nightmare.
Toshiba Satellite Pro U400 Laptop Wifi Wireless Wlan Board Card PA3655U-1MPC | eBay
And use the official windows 8.1 driver
https://downloadcenter.intel.com/De...1, 64-bit*&DownloadType=Software Applications
Click to expand...

Please follow this guide and retry the driver installation procedure.
 
I have ordered the Intel WiFi Link 5100 for £2 / $3 with 2 day shipping which will "fix" all of the atheros issues.

Tomorrow I will try a different browser, remove the wireless card and use the LAN port.

I don't know if it comes across well, but you have really helped me and I am really greatful :)
 
ganon11000 said:
More audio stutters than ever on LAN (with the wireless card removed). My guess is the LAN driver is causing it?
Click to expand...
Everything is still the same (high CPU by flash, some (not that high) DPC spikes by NDIS.sys), apart from that athwnx.sys was replaced by b57nd60a.sys (Broadcom NetXtreme driver) on the stack and that's a bit strange. I also noticed aswStm.sys (avast! Antivirus driver), which I missed before, on the stack. Could you please completely remove Avast and generate a new XPERF trace?

ganon11000 said:
Before applying the code for the power mode, what does it do?
Click to expand...
It makes sure of the following, when your computer is plugged in:

  • USB devices are not suspended.
  • PCI Express devices are using maximum performance.
  • CPU is always running always running on maximum GHz.
 
ganon11000 said:
This one is using internet explorer, On board LAN disabled (Wireless card reinserted) and your power tweaks applied.
I will remove avast! next and try that but since this has happened on every install without Avast! being installed I highly doubt it is the issue.

https://drive.google.com/file/d/0B3-yyU44xFecT2hjUndHNVg3TXM/edit?usp=sharing
Click to expand...

I'm not sure what you mean "this has happened on every install without Avast!". As I said, DPCs are not what's causing performance issues on your computer so I don't think we know if these minor DPC spikes were or weren't at these installations when you hadn't Avast. Somehow, I think that DPCs will be really really low and without any spikes when you have Avast (NDIS.sys spikes) removed and Bluetooth devices (ACPI.sys) disabled; and, even so, you would still experience performance issues caused by video decoding on CPU.

Please remove Avast and generate a new trace, just to save time analyzing extra traces, that do not provide additional information.

Thank you.
 
Last edited:
I don't mean to butt-in, as Tomas has this covered and there's even reinforcement from Satrow as well, but just to expand a bit on why you were seeing ndis.sys spikes with avast! installed since you mentioned it above.

First off, ndis.sys is the Network Driver Interface Specification (NDIS) driver. Now that we understand what ndis.sys means, we now must understand actually what it does. The Network Driver Interface Specification (NDIS) is an application programming interface (API) for network interface cards (NICs). The NDIS forms the Logical Link Control (LLC) sublayer, which is the upper sublayer of the OSI data link layer (layer 2). Therefore, the NDIS acts as the interface between the Media Access Control (MAC) sublayer, which is the lower sublayer of the data link layer, and the network layer (layer 3).

The NDIS is a library of functions often referred to as a 'wrapper' that hides the underlying complexity of the NIC hardware and serves as a standard interface for level 3 network protocol drivers and hardware level MAC drivers. Another common LLC is the Open Data-Link Interface (ODI). With all of this said, it very much works with your network drivers, and other network related routines, etc. As much as I see avast! interfere and conflict and cause NETIO related crashes, it doesn't surprise me to see it causing high DPC's either.

Regards,

Patrick
 
Patrick said:
I don't mean to butt-in, as Tomas has this covered and there's even reinforcement from Satrow as well, but just to expand a bit on why you were seeing ndis.sys spikes with avast! installed since you mentioned it above.

First off, ndis.sys is the Network Driver Interface Specification (NDIS) driver. Now that we understand what ndis.sys means, we now must understand actually what it does. The Network Driver Interface Specification (NDIS) is an application programming interface (API) for network interface cards (NICs). The NDIS forms the Logical Link Control (LLC) sublayer, which is the upper sublayer of the OSI data link layer (layer 2). Therefore, the NDIS acts as the interface between the Media Access Control (MAC) sublayer, which is the lower sublayer of the data link layer, and the network layer (layer 3).

The NDIS is a library of functions often referred to as a 'wrapper' that hides the underlying complexity of the NIC hardware and serves as a standard interface for level 3 network protocol drivers and hardware level MAC drivers. Another common LLC is the Open Data-Link Interface (ODI). With all of this said, it very much works with your network drivers, and other network related routines, etc. As much as I see avast! interfere and conflict and cause NETIO related crashes, it doesn't surprise me to see it causing high DPC's either.

Regards,

Patrick
Click to expand...
So NDIS.SYS is anything to do with networking?
 
Very much so! This is why when you removed !avast as Tomas advised, the DPC spikes greatly decreased within ndis.sys. Why exactly was !avast causing these high spikes within ndis.sys? It's hard to say, but it's important to note that antivirus suites are very complex and work deep and extensively with the OS in many different ways. Different users have different OS environments as well (i.e different networking software installed, drivers, adapters, etc....), so avast! could have been causing conflicts, therefore you had a high DPC within ndis.sys. It's complex to say the very least.

Anyway, I am not here to confuse you or anything, just adding some extra information regarding ndis.sys.

Regards,

Patrick
 
Patrick said:
Very much so! This is why when you removed !avast as Tomas advised, the DPC spikes greatly decreased within ndis.sys. Why exactly was !avast causing these high spikes within ndis.sys? It's hard to say, but it's important to note that antivirus suites are very complex and work deep and extensively with the OS in many different ways. Different users have different OS environments as well (i.e different networking software installed, drivers, adapters, etc....), so avast! could have been causing conflicts, therefore you had a high DPC within ndis.sys. It's complex to say the very least.

Anyway, I am not here to confuse you or anything, just adding some extra information regarding ndis.sys.

Regards,

Patrick
Click to expand...
Thank you for explaining that :) as you may of guessed I'm a hardware guy who builds machines. I'm really not good at deep issues like this!
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top