Jump to content

How to get the cause of high CPU usage by DPC / Interrupt


Recommended Posts


 

 

I try to disconnect the camera, let's see if it fixes!
 

 

 

what happened? Does this fixes the issue?

 

 

Hello,
I tried to unplug the camera and effectively the problem is gone.
Since then the computer works perfectly.
No way to solve it? the camera is faulty? or the cable damaged?
O can also be a problem of windows? or pci card? or driver?
How can I resolve the enigma?
Edited by Lottware
Link to comment
Share on other sites

I've been having a problem over the past year or so where everything becomes slow. Programs stop responding, mostly browsers. I have eliminated certain behaviours over time in an attempt to troubleshoot, such as:

- stream content in different browsers

- don't stream at all

- don't charge cell phone on PC

- disabling Windows sounds

- disable search indexing

 

The reason for disabling sounds, is when the PC gets slow, CPU light on PC would be solid. And sound events would be delayed. Sometimes I would get a sound up to 10 minutes later than when it would fire, say from new Email or IM notification. There have also been times where if the PC is in this slow stage, it will take a very long time to detect inserted USB keys. Another thing that happens is that both Firefox and IE Flash plugins will crash.

 

I have attached a LatencyMon report of 1 minute while the PC is in this state. It appears to me to be related to MSSE, however it is not scheduled to scan until afterhours.

 

Drivers

Drivers_zps4ndkhmcu.jpg

Processes

Processes_zps3gsohcq6.jpg

LatencyMon.txt

Link to comment
Share on other sites

I see no DPC issues:

Total = 182174Elapsed Time, >        0 usecs AND <=        1 usecs,     29, or   0.02%Elapsed Time, >        1 usecs AND <=        2 usecs,  22578, or  12.39%Elapsed Time, >        2 usecs AND <=        4 usecs, 115151, or  63.21%Elapsed Time, >        4 usecs AND <=        8 usecs,  12253, or   6.73%Elapsed Time, >        8 usecs AND <=       16 usecs,  13887, or   7.62%Elapsed Time, >       16 usecs AND <=       32 usecs,  10797, or   5.93%Elapsed Time, >       32 usecs AND <=       64 usecs,   7097, or   3.90%Elapsed Time, >       64 usecs AND <=      128 usecs,    371, or   0.20%Elapsed Time, >      128 usecs AND <=      256 usecs,     11, or   0.01%Total,                                                182174

everything under 1024µs is ok.

 

I only see a high CPU usage from Windows Update. Also the disk is very busy

Link to comment
Share on other sites

  • 2 weeks later...

Hii, Im surprised to see this thread still going after a few years, great work Andre!

 Anyways, I just got hit with this problem, and it seems like it happened after i had quite a massive windows update (after not updating for a long time) 

I followed the steps you have given on the first post, but when i got into the part that viewed the etl file and i cant seem to get the graph that you mentioned. Heres a screenshot 

 

post-402510-0-95836400-1423798453_thumb.

 

A little background 

Im using windows 8.1, 64 bits. 

I have problems with my cabled network connection. I always have to go into my device manager, uninstall the ethernet device, scan for hardware change, and then go into the properties and change its network address to the same one with my wireless to make it work. 

I tried using the wireless connection and disabled the ethernet device but the problem still persists. 

 

Also, i uploaded the etl file if it helps.

 

http://www.mediafire.com/download/3a6a08e4d8pmfp8/DPC_Interrupt.etl

 

Thank you!

Link to comment
Share on other sites

I dumped the ETL into the txt summary and here you can see that the driver DDDriver64Dcsa.sys is the cause:

Total = 38 for module DDDriver64Dcsa.sysElapsed Time, >        0 usecs AND <=        1 usecs,      0, or   0.00%Elapsed Time, >        1 usecs AND <=        2 usecs,      0, or   0.00%Elapsed Time, >        2 usecs AND <=        4 usecs,      0, or   0.00%Elapsed Time, >        4 usecs AND <=        8 usecs,      0, or   0.00%Elapsed Time, >        8 usecs AND <=       16 usecs,      0, or   0.00%Elapsed Time, >       16 usecs AND <=       32 usecs,      0, or   0.00%Elapsed Time, >       32 usecs AND <=       64 usecs,      1, or   2.63%Elapsed Time, >       64 usecs AND <=      128 usecs,      2, or   5.26%Elapsed Time, >      128 usecs AND <=      256 usecs,      5, or  13.16%Elapsed Time, >      256 usecs AND <=      512 usecs,     13, or  34.21%Elapsed Time, >      512 usecs AND <=     1024 usecs,      6, or  15.79%Elapsed Time, >     1024 usecs AND <=     2048 usecs,      0, or   0.00%Elapsed Time, >     2048 usecs AND <=     4096 usecs,      6, or  15.79%Elapsed Time, >     4096 usecs AND <=     8192 usecs,      4, or  10.53%Elapsed Time, >     8192 usecs AND <=    16384 usecs,      0, or   0.00%Elapsed Time, >    16384 usecs AND <=    32768 usecs,      0, or   0.00%Elapsed Time, >    32768 usecs AND <=    65536 usecs,      0, or   0.00%Elapsed Time, >    65536 usecs AND <=   131072 usecs,      0, or   0.00%Elapsed Time, >   131072 usecs AND <=   262144 usecs,      0, or   0.00%Elapsed Time, >   262144 usecs AND <=   524288 usecs,      1, or   2.63%Total,                                                    38

This looks like a Dell driver. Update or remove this driver.

Link to comment
Share on other sites

  • 2 months later...

Hi Andre I hope you can help me. I installed Win8.1 x64 on my 4 core 16GB machine (c 2007) and since then have had dwm.exe exhibit 20% CPU for a couple of minutes every 7 mins or so. My machine is normally fine for the first day after a reboot but it gets steadily worse. Shutting down Outlook seems to immediately stop dwm's high CPU but it may be memory related (even though I rarely exceed 12GB) or GDI as sometimes shutting down Chrome (with typically 20+ windows open) also does the same. I also normally have 15+ applications running concurrently. I have just replaced the GE7300 with a GE210 and it made no difference.

 

I started researching this a month or so ago and have used LatenecyMon and xperf. They both point to nvlddmkm.sys being the culprit.

 

Here's an edited xperf showing the modules with >256us. This trace was taken during one of the high CPU dwm periods.

 

Total = 11946 for module ndis.sys
Elapsed Time, >      256 usecs AND <=      512 usecs,     11, or   0.09%
 
Total = 100191 for module nvlddmkm.sys
Elapsed Time, >      256 usecs AND <=      512 usecs,     61, or   0.06%
Elapsed Time, >      512 usecs AND <=     1024 usecs,     19, or   0.02%
 
Total = 11048 for module tcpip.sys
Elapsed Time, >      256 usecs AND <=      512 usecs,      2, or   0.02%
 
The GUI shows the following have greater than 0.01% duration:
nvlddmkm.sys 0.11%
dxgkrnl.sys 0.07%
USBPORT.SYS 0.07%
tcpip.sys 0.07%
ataport.SYS 0.02%
ndis.sys 0.02%
afd.sys 0.01%
VBoxDrv.sys 0.01%
ntoskrnl.exe 0.01%
 
And relevant LatencyMon output (taken at a different time of course):
 
Highest DPC routine execution time (µs):              93661.044123
Driver with highest DPC routine execution time:       nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 341.44 , NVIDIA Corporation
 
Highest reported total DPC routine time (%):          0.137717
Driver with highest DPC total execution time:         nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 341.44 , NVIDIA Corporation
 
Total time spent in DPCs (%)                          0.451373
 
DPC count (execution time <250 µs):                   3582912
DPC count (execution time 250-500 µs):                0
DPC count (execution time 500-999 µs):                7156
DPC count (execution time 1000-1999 µs):              1
DPC count (execution time 2000-3999 µs):              1
DPC count (execution time >=4000 µs):                 0
 
When dwm is maxing out the system is very unresponsive (even typing is jerky) and it's driving me mad. I hate WIn 8 anyway and am half thinking of downgrading to Win 7 but I can't afford the time to do so.
 
Help!
 
Andy
Link to comment
Share on other sites

the NVIDIA GeForce 210 is simply too slow. The DWM service calls some DWM functions to validate which windows are shown (dwmredir.dll!CWindowContext::GetWindowVisibleRegion).

And the DPCs also come from the nVIDIA driver:
 

Total = 100191 for module nvlddmkm.sysElapsed Time, >      256 usecs AND <=      512 usecs,     61, or   0.06%Elapsed Time, >      512 usecs AND <=     1024 usecs,     19, or   0.02%Total,                                                100191

try a better/faster card

Link to comment
Share on other sites

 

try a better/faster card

Yep :), the Geforce 210 is certainly not a "fast" card, but often these kind of issues are withing the driver, though if the OP cannot afford the time to do the "right thing" ;), surely proposing him to loose HOURS (and I mean it) to try several sets of older (or newer) drivers is not an option.

 

jaclaz

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...