Share via

UGH! Please help with latency issues from Windows Update on Thinkpad

Anonymous
2024-01-19T16:26:58+00:00

At the bottom is my LatencyMon information.

What is happening:

I've been recording podcasts through my Tascam US 4x4 HR audio interface all of 2023 with NO ISSUES! I was a bit hesitant to update Windows all of last year since I had heard of some bugs. Well, I decided to update, and I probably shouldn't have. After the update, my recordings had distortions, pops, static, etc. It actually got recorded into the audio file. I know this because I sent the recording to my phone and played it.

Things I've tried so far: (not in order)

  • Update BIOS
  • Install latest AMD Adrenalin driver
  • Complete reset of Windows 11
  • Change power performance to high
  • Turned off windows defender
  • Ran /scanhealth, /checkhealth, /restorehealth (all good)
  • Disabled Realtek PCIe Gbe Family controller and ran Latencymon (still having issue)
  • Probably tried more than this but i can't remember it all, i've been trying to fix this problem for 2 weeks.

Maybe I should just toss this computer in the landfill and switch to Mac.

Before I do that, does anyone have insight into my problem?

_________________________________________________________________________________________________________

CONCLUSION

_________________________________________________________________________________________________________

Your system appears to be having trouble handling real-time audio and other tasks. You are likely to experience buffer underruns appearing as drop outs, clicks or pops. One or more DPC routines that belong to a driver running in your system appear to be executing for too long. Also one or more ISR routines that belong to a driver running in your system appear to be executing for too long. 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:08:02 (h:mm:ss) on all processors.

_________________________________________________________________________________________________________

SYSTEM INFORMATION

_________________________________________________________________________________________________________

Computer name: LAPTOP

OS version: Windows 11, 10.0, version 2009, build: 22631 (x64)

Hardware: 20QJ0005US, LENOVO

BIOS: R13ET55W(1.29 )

CPU: AuthenticAMD AMD Ryzen 5 PRO 3500U w/ Radeon Vega Mobile Gfx

Logical processors: 8

Processor groups: 1

Processor group size: 8

RAM: 6022 MB total

_________________________________________________________________________________________________________

CPU SPEED

_________________________________________________________________________________________________________

Reported CPU speed (WMI): 210 MHz

Reported CPU speed (registry): 2096 MHz

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): 879.70

Average measured interrupt to process latency (µs): 12.750131

Highest measured interrupt to DPC latency (µs): 871.70

Average measured interrupt to DPC latency (µs): 5.083092

_________________________________________________________________________________________________________

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): 2647.252385

Driver with highest ISR routine execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation

Highest reported total ISR routine time (%): 0.011124

Driver with highest ISR total time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation

Total time spent in ISRs (%) 0.011357

ISR count (execution time <250 µs): 33022

ISR count (execution time 250-500 µs): 0

ISR count (execution time 500-1000 µs): 7

ISR count (execution time 1000-2000 µs): 0

ISR count (execution time 2000-4000 µs): 1

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): 3437.828244

Driver with highest DPC routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

Highest reported total DPC routine time (%): 0.043754

Driver with highest DPC total execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation

Total time spent in DPCs (%) 0.090854

DPC count (execution time <250 µs): 175742

DPC count (execution time 250-500 µs): 0

DPC count (execution time 500-10000 µs): 135

DPC count (execution time 1000-2000 µs): 0

DPC count (execution time 2000-4000 µs): 1

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: msmpeng.exe

Total number of hard pagefaults 4935

Hard pagefault count of hardest hit process: 1006

Number of processes hit: 163

_________________________________________________________________________________________________________

PER CPU DATA

_________________________________________________________________________________________________________

CPU 0 Interrupt cycle time (s): 9.117201

CPU 0 ISR highest execution time (µs): 2647.252385

CPU 0 ISR total execution time (s): 0.437974

CPU 0 ISR count: 32818

CPU 0 DPC highest execution time (µs): 3437.828244

CPU 0 DPC total execution time (s): 3.058934

CPU 0 DPC count: 130960

_________________________________________________________________________________________________________

CPU 1 Interrupt cycle time (s): 0.994367

CPU 1 ISR highest execution time (µs): 3.306298

CPU 1 ISR total execution time (s): 0.000025

CPU 1 ISR count: 11

CPU 1 DPC highest execution time (µs): 323.025286

CPU 1 DPC total execution time (s): 0.017218

CPU 1 DPC count: 2091

_________________________________________________________________________________________________________

CPU 2 Interrupt cycle time (s): 1.320473

CPU 2 ISR highest execution time (µs): 2.394561

CPU 2 ISR total execution time (s): 0.000079

CPU 2 ISR count: 49

CPU 2 DPC highest execution time (µs): 395.252863

CPU 2 DPC total execution time (s): 0.098960

CPU 2 DPC count: 11160

_________________________________________________________________________________________________________

CPU 3 Interrupt cycle time (s): 0.863626

CPU 3 ISR highest execution time (µs): 2.484733

CPU 3 ISR total execution time (s): 0.000026

CPU 3 ISR count: 16

CPU 3 DPC highest execution time (µs): 388.149332

CPU 3 DPC total execution time (s): 0.025751

CPU 3 DPC count: 2885

_________________________________________________________________________________________________________

CPU 4 Interrupt cycle time (s): 1.141901

CPU 4 ISR highest execution time (µs): 2.174141

CPU 4 ISR total execution time (s): 0.000022

CPU 4 ISR count: 13

CPU 4 DPC highest execution time (µs): 363.592557

CPU 4 DPC total execution time (s): 0.048711

CPU 4 DPC count: 5238

_________________________________________________________________________________________________________

CPU 5 Interrupt cycle time (s): 0.830977

CPU 5 ISR highest execution time (µs): 2.144084

CPU 5 ISR total execution time (s): 0.000007

CPU 5 ISR count: 4

CPU 5 DPC highest execution time (µs): 301.023378

CPU 5 DPC total execution time (s): 0.020190

CPU 5 DPC count: 3204

_________________________________________________________________________________________________________

CPU 6 Interrupt cycle time (s): 1.302251

CPU 6 ISR highest execution time (µs): 7.354008

CPU 6 ISR total execution time (s): 0.000171

CPU 6 ISR count: 98

CPU 6 DPC highest execution time (µs): 454.225191

CPU 6 DPC total execution time (s): 0.206079

CPU 6 DPC count: 17384

_________________________________________________________________________________________________________

CPU 7 Interrupt cycle time (s): 1.35830

CPU 7 ISR highest execution time (µs): 2.474714

CPU 7 ISR total execution time (s): 0.000036

CPU 7 ISR count: 21

CPU 7 DPC highest execution time (µs): 219.708492

CPU 7 DPC total execution time (s): 0.030656

CPU 7 DPC count: 2956

_________________________________________________________________________________________________________

Windows for home | Windows 11 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-01-20T11:50:09+00:00

    Hello

    Welcome to the Microsoft Community.

    Regarding your computer recording audio with all sorts of garbled noises.

    I do understand how you feel. I understand that you have performed many operations.

    Here are some possible causes and solutions:

    1. I suggest you go into Safe mode to see if it's the system itself problem. Because Safe Mode enables a minimum number of additional services or apps to rule out issues caused by personalized settings and third-party apps.
      1. On the desktop click "Start" > "Settings" > "System" > "Recovery", under "Advanced startup", select "Restart now".
      2. After restarting, go to "Choose an option" screen, select "Troubleshoot" > "Advanced options" > "Startup Settings" > "Restart".
      3. After restarting, you'll see a list of options. Select 4 or press F4 to start your PC in Safe Mode*. Or if you'll need to use the internet, select 5 or press F5 for* Safe Mode with Networking*.*
      Visit Start your PC in safe mode in Windows (microsoft.com) to view the specific operation steps.
    2. You can adjust the audio enhancement settings for that microphone. Win + R to open "Run", type "mmsys.cpl", press Enter to open Sound > Recording tab > right-click your microphone > Properties > Enhancements tab, adjust the Audio Enhancement*(check or uncheck) and relative settings.* Since enable/disable audio enhancement may have different effects due to different audio hardware properties, so try both.
    3. Graphics Driver:
      • The dxgkrnl.sys (DirectX Graphics Kernel) is mentioned with high DPC routine execution time. Update your graphics driver to the latest version.
      • Make sure you have the latest version of DirectX installed on your system.
      • You can check the DirectX version by running the dxdiag command. Make sure to update to the latest version.
    4. Repair possible corrupted system files Run the following commands to fix possible corrupted system files. Run Command Prompt as an administrator ("Win" logo key + "Q", enter "cmd", select "Run as administrator"), and enter the following commands one by one. These commands require network support, please keep your network stable and smooth. 
       sfc /scannow

 DISM /Online /Cleanup-Image /RestoreHealth

 wsreset.exe

 powershell "Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}"
 for %i in (%windir%\\system32\\*.dll) do regsvr32.exe /s %i
 chkdsk C: /f
      Disclaimer*: Running chkdsk can check the file system and file system metadata of a volume for logical and physical errors. To avoid any trouble for you, please follow them step-by-step, do not cancel or interrupt chkdsk, and back up important data. For more information please refer to this* chkdsk article.

    Best Regards

    Patch - MSFT | Microsoft Community Support Specialist

    Was this answer helpful?

    0 comments