Audio Clipping/Laggy PC performance according to multiple PC testers (including DPC)

I

Ic3

Member
Joined
May 3, 2014
Posts
7
To whoever can help me,
This issue has started about 2 weeks ago, after I installed new drivers (don't remember which specific one)
I started to notice very minor things, like slight overheating on very basic tasks, clipping sounds on simple events like changing rooms in team speak.
The issue however became very apparent once I launched Counter Strike : GO, last night, It seemed that not only was the game slow and laggy, but the sounds seemed to all mesh up together creating a very distorted audio sound.
I ran DPC latency Checker and got an average of 1014, with the message that some device drivers on this machine behave badly, a similar program gave me the same details, LatencyMon.
My BIOS was recently updated (about 3 months ago) with the latest version, and everything was running just fine.
Any source of help will be very appreciated.
Regards.
 
Some PC specs:
Windows 8.1
Intel i7-3630QM
2.40GHz
32gb RAM
64 bit
nvidea gforce 680m
 
The following is a report error using LatencyMon, if it helps.
_________________________________________________________________________________________________________
CONCLUSION
_________________________________________________________________________________________________________
Your system seems to have difficulty handling real-time audio and other tasks. You may experience drop outs, clicks or pops due to buffer underruns. One problem may be related to power management, disable CPU throttling settings in Control Panel and BIOS setup. Check for BIOS updates.
LatencyMon has been analyzing your system for 0:01:37 (h:mm:ss) on all processors.


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: MSI
OS version: Windows 8 , 6.2, build: 9200 (x64)
Hardware: GT70, Micro-Star International Co., Ltd., MS-1762
CPU: GenuineIntel Intel(R) Core(TM) i7-3630QM CPU @ 2.40GHz
Logical processors: 8
Processor groups: 1
RAM: 32659 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 2395.0 MHz
Measured CPU speed: 1482.0 MHz (approx.)

Note: reported execution times may be calculated based on a fixed reported CPU speed. Disable variable speed settings like Intel Speed Step and AMD Cool N Quiet in the BIOS setup for more accurate results.


_________________________________________________________________________________________________________
MEASURED INTERRUPT TO USER PROCESS LATENCIES
_________________________________________________________________________________________________________
The interrupt to process latency reflects the measured interval that a usermode process needed to respond to a hardware request from the moment the interrupt service routine started execution. This includes the scheduling and execution of a DPC routine, the signaling of an event and the waking up of a usermode thread from an idle wait state in response to that event.

Highest measured interrupt to process latency (µs): 1000.236482
Average measured interrupt to process latency (µs): 5.998279

Highest measured interrupt to DPC latency (µs): 997.243042
Average measured interrupt to DPC latency (µs): 1.780981


_________________________________________________________________________________________________________
REPORTED ISRs
_________________________________________________________________________________________________________
Interrupt service routines are routines installed by the OS and device drivers that execute in response to a hardware interrupt signal.

Highest ISR routine execution time (µs): 97.850522
Driver with highest ISR routine execution time: ndis.sys - Network Driver Interface Specification (NDIS), Microsoft Corporation

Highest reported total ISR routine time (%): 0.030023
Driver with highest ISR total time: ndis.sys - Network Driver Interface Specification (NDIS), Microsoft Corporation

Total time spent in ISRs (%) 0.059291

ISR count (execution time <250 µs): 112868
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 0
ISR count (execution time 1000-1999 µs): 0
ISR count (execution time 2000-3999 µs): 0
ISR count (execution time >=4000 µs): 0


_________________________________________________________________________________________________________
REPORTED DPCs
_________________________________________________________________________________________________________
DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it is interrupted until the DPC has finished execution.

Highest DPC routine execution time (µs): 437.700209
Driver with highest DPC routine execution time: ndis.sys - Network Driver Interface Specification (NDIS), Microsoft Corporation

Highest reported total DPC routine time (%): 0.073230
Driver with highest DPC total execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

Total time spent in DPCs (%) 0.200287

DPC count (execution time <250 µs): 406380
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 22
DPC count (execution time 1000-1999 µs): 0
DPC count (execution time 2000-3999 µs): 0
DPC count (execution time >=4000 µs): 0


_________________________________________________________________________________________________________
REPORTED HARD PAGEFAULTS
_________________________________________________________________________________________________________
Hard pagefaults are events that get triggered by making use of virtual memory that is not resident in RAM but backed by a memory mapped file on disk. The process of resolving the hard pagefault requires reading in the memory from disk while the process is interrupted and blocked from execution.

NOTE: some processes were hit by hard pagefaults. If these were programs producing audio, they are likely to interrupt the audio stream resulting in dropouts, clicks and pops. Check the Processes tab to see which programs were hit.

Process with highest pagefault count: vsserv.exe

Total number of hard pagefaults 143
Hard pagefault count of hardest hit process: 106
Highest hard pagefault resolution time (µs): 49144.791232
Total time spent in hard pagefaults (%): 0.015325
Number of processes hit: 5


_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 4.872116
CPU 0 ISR highest execution time (µs): 97.850522
CPU 0 ISR total execution time (s): 0.460169
CPU 0 ISR count: 112868
CPU 0 DPC highest execution time (µs): 437.700209
CPU 0 DPC total execution time (s): 1.435590
CPU 0 DPC count: 382235
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 2.212857
CPU 1 ISR highest execution time (µs): 0.0
CPU 1 ISR total execution time (s): 0.0
CPU 1 ISR count: 0
CPU 1 DPC highest execution time (µs): 106.194572
CPU 1 DPC total execution time (s): 0.007544
CPU 1 DPC count: 1703
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 1.568945
CPU 2 ISR highest execution time (µs): 0.0
CPU 2 ISR total execution time (s): 0.0
CPU 2 ISR count: 0
CPU 2 DPC highest execution time (µs): 136.721503
CPU 2 DPC total execution time (s): 0.020264
CPU 2 DPC count: 5428
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 2.128981
CPU 3 ISR highest execution time (µs): 0.0
CPU 3 ISR total execution time (s): 0.0
CPU 3 ISR count: 0
CPU 3 DPC highest execution time (µs): 45.663466
CPU 3 DPC total execution time (s): 0.015147
CPU 3 DPC count: 2568
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 1.432508
CPU 4 ISR highest execution time (µs): 0.0
CPU 4 ISR total execution time (s): 0.0
CPU 4 ISR count: 0
CPU 4 DPC highest execution time (µs): 115.911482
CPU 4 DPC total execution time (s): 0.024670
CPU 4 DPC count: 6433
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 2.011591
CPU 5 ISR highest execution time (µs): 0.0
CPU 5 ISR total execution time (s): 0.0
CPU 5 ISR count: 0
CPU 5 DPC highest execution time (µs): 234.892693
CPU 5 DPC total execution time (s): 0.017457
CPU 5 DPC count: 1709
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 1.248709
CPU 6 ISR highest execution time (µs): 0.0
CPU 6 ISR total execution time (s): 0.0
CPU 6 ISR count: 0
CPU 6 DPC highest execution time (µs): 210.466806
CPU 6 DPC total execution time (s): 0.020493
CPU 6 DPC count: 4783
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 1.809457
CPU 7 ISR highest execution time (µs): 0.0
CPU 7 ISR total execution time (s): 0.0
CPU 7 ISR count: 0
CPU 7 DPC highest execution time (µs): 206.027557
CPU 7 DPC total execution time (s): 0.013303
CPU 7 DPC count: 1543
_________________________________________________________________________________________________________
 
Dear,

To properly troubleshoot issues with high/frequent DPCs/IRPs, we require a XPERF trace. Please follow these steps to generate one:

  1. Download Windows Software Development Kit (SDK) for Windows and run the setup.
  2. Select Windows Performance Toolkit feature (all the others can be unchecked) and proceed with the download/installation.
  3. Once the installation finishes, open an elevated Command Prompt by right-clicking on CMD.EXE shortcut in your start menu and selecting Run As Administrator from the context menu.
  4. Type the following command, which will start tracing, in the Command Prompt window you just opened:
    Code: 
    xperf -on PROC_THREAD+LOADER+PROFILE+INTERRUPT+DPC+DRIVERS+POWER+IDLE_STATES -stackwalk Profile -BufferSize 1024 -MinBuffers 256 -MaxBuffers 256 -MaxFile 256 -FileMode Circular
    If you see a yellow warning "xperf: warning: This system is not fully configured for x64 stack tracing" after running the above command, please complete these extra steps (otherwise, proceed to the step #5):
    Read More:
    If you see a red error "xperf: error: NT Kernel Logger: A device attached to the system is not functioning. (0x1f)" after running the above command, please complete these extra steps (otherwise, proceed to the step #5):
    Read More:

    If you see a red error "xperf: error: NT Kernel Logger: Cannot create a file when that file already exists. (0xb7)", please do the following (otherwise, proceed to the step #5):
    Read More:
  5. Perform some activities with your computer for few minutes, making sure the issues you reported are reproduced.
  6. Run the following command, which will stop the tracing, in the command prompt window you already have opened:
    Code: 
    xperf -stop -d C:\CPU.etl
  7. Compress file C:\CPU.etl
  8. Upload the compressed file to a file sharing service (e.g. OneDrive or DropBox).
  9. Share the download link here.
Thank you.
 
https://www.dropbox.com/s/2oqsc8d61vm7rca/CPU.zip?dl=0
This is the requested link.
Thank you for your time.

TomasD said:
Dear,

To properly troubleshoot issues with high/frequent DPCs/IRPs, we require a XPERF trace. Please follow these steps to generate one:

  1. Download Windows Software Development Kit (SDK) for Windows and run the setup.
  2. Select Windows Performance Toolkit feature (all the others can be unchecked) and proceed with the download/installation.
  3. Once the installation finishes, open an elevated Command Prompt by right-clicking on CMD.EXE shortcut in your start menu and selecting Run As Administrator from the context menu.
  4. Type the following command, which will start tracing, in the Command Prompt window you just opened:
    Code: 
    xperf -on PROC_THREAD+LOADER+PROFILE+INTERRUPT+DPC+DRIVERS+POWER+IDLE_STATES -stackwalk Profile -BufferSize 1024 -MinBuffers 256 -MaxBuffers 256 -MaxFile 256 -FileMode Circular
    If you see a yellow warning "xperf: warning: This system is not fully configured for x64 stack tracing" after running the above command, please complete these extra steps (otherwise, proceed to the step #5):
    Read More:

    If you see a red error "xperf: error: NT Kernel Logger: A device attached to the system is not functioning. (0x1f)" after running the above command, please complete these extra steps (otherwise, proceed to the step #5):
    Read More:

    If you see a red error "xperf: error: NT Kernel Logger: Cannot create a file when that file already exists. (0xb7)", please do the following (otherwise, proceed to the step #5):
    Read More:
  5. Perform some activities with your computer for few minutes, making sure the issues you reported are reproduced.
  6. Run the following command, which will stop the tracing, in the command prompt window you already have opened:
    Code: 
    xperf -stop -d C:\CPU.etl
  7. Compress file C:\CPU.etl
  8. Upload the compressed file to a file sharing service (e.g. OneDrive or DropBox).
  9. Share the download link here.
Thank you.
Click to expand...
 
OK, the issue seems to be with interrupts, not DPCs. High interrupts are caused by the video subsystem (DirectX, Intel GPU driver). Unfortunately, I have no way to tell what might be the root cause for the issue. Hence, there are few general suggestions in cases like these:

 
TomasD said:
OK, the issue seems to be with interrupts, not DPCs. High interrupts are caused by the video subsystem (DirectX, Intel GPU driver). Unfortunately, I have no way to tell what might be the root cause for the issue. Hence, there are few general suggestions in cases like these:

Click to expand...

Ok so I checked the drivers, and they're completely up to date, both the integrated and main graphics card, you mentioned something about disabling one GPU?
Is there a reason as to why I should do this?
GPU temp is moderate, nothing above 70 under stress.
I don't really understand what re-seating is, clearing the contacts?
On another forum, they gave me different suggestions, some being uninstalling my bit defender, while others suggest I roll back my drivers until the issue is solved, but this approach seems very iffy, mainly because it may mess with the system driver files.
 
Ic3 said:
Ok so I checked the drivers, and they're completely up to date, both the integrated and main graphics card, you mentioned something about disabling one GPU?
Is there a reason as to why I should do this?
Click to expand...
Is there a reason not to? Why would you need two different GPUs working simultaneously?
 
TomasD said:
Dear,

To properly troubleshoot issues with high/frequent DPCs/IRPs, we require a XPERF trace. Please follow these steps to generate one:

  1. Download Windows Software Development Kit (SDK) for Windows and run the setup.
  2. Select Windows Performance Toolkit feature (all the others can be unchecked) and proceed with the download/installation.
  3. Once the installation finishes, open an elevated Command Prompt by right-clicking on CMD.EXE shortcut in your start menu and selecting Run As Administrator from the context menu.
  4. Type the following command, which will start tracing, in the Command Prompt window you just opened:
    Code: 
    xperf -on PROC_THREAD+LOADER+PROFILE+INTERRUPT+DPC+DRIVERS+POWER+IDLE_STATES -stackwalk Profile -BufferSize 1024 -MinBuffers 256 -MaxBuffers 256 -MaxFile 256 -FileMode Circular
    If you see a yellow warning "xperf: warning: This system is not fully configured for x64 stack tracing" after running the above command, please complete these extra steps (otherwise, proceed to the step #5):
    Read More:

    If you see a red error "xperf: error: NT Kernel Logger: A device attached to the system is not functioning. (0x1f)" after running the above command, please complete these extra steps (otherwise, proceed to the step #5):
    Read More:

    If you see a red error "xperf: error: NT Kernel Logger: Cannot create a file when that file already exists. (0xb7)", please do the following (otherwise, proceed to the step #5):
    Read More:
  5. Perform some activities with your computer for few minutes, making sure the issues you reported are reproduced.
  6. Run the following command, which will stop the tracing, in the command prompt window you already have opened:
    Code: 
    xperf -stop -d C:\CPU.etl
  7. Compress file C:\CPU.etl
  8. Upload the compressed file to a file sharing service (e.g. OneDrive or DropBox).
  9. Share the download link here.
Thank you.
Click to expand...


Some MB have a single card Video card PCI master to be used, vs SLI with two card. Does this have DirectX 11, 11.1 or 11.2 (w8.1) installed?
 
"Process with highest pagefault count: vsserv.exe" vsserv.exe = BitDefender. Bitdefender Free is close to completely uncontrollable (and based on an older engine than the main product).

The machine is a notebook (it's running a mobile GPU, geforce 680m), many of these are dual GPU (eg. Intel for basics, ATI/nVidia for 3D). If you stray away from the notebook makers' drivers for the graphics, you are much more likely to run into problems.
 

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

Back
Top