Windows 10 v1903 - ntoskrnl.exe & ISR/DPC latency spikes

Anonymous
2019-05-31T18:33:50+00:00

Hi,

After updating to 1903 LatencyMon associates ntoskrnl.exe with large latency spikes on the order of ~1,300µs. Same results with KB4497935.

I posted here too as I thought it could be related to the GPU driver:

https://forums.geforce.com/default/topic/1120890/geforce-drivers/win10-ver-1903-ntoskrnl-exe-large-latency-spikes-/

Others are also reporting similar symptoms. E.g. in some instances this results in noticeable audio clicks/pops.

https://www.reddit.com/r/Windows10/comments/bu34xv/update_1903_high_dpc_latency_issues/

Are you seeing similar results?

Does anyone at Microsoft acknowledge this?

It should be easily reproducible.

Thanks,

Howard

SOLUTION:

KB4505903 seems to have significantly mitigated the ntoskrnl.exe latency spikes for many users.

Windows for home | Windows 10 | 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

68 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2019-06-22T20:19:05+00:00

    Hi All, I too was having this problem when I was downloading a large file. System was shooting up to 60% and it was lagging horribly. I did however find a solution that has worked for me. I downloaded tcpoptimizer from speedguide and selected optimal. Not sure what exactly changed in the settings from default to optimal but I rebooted and downloading at 80 mb/s now and system is idling at 5%. Let me know if this works for anyone else. Thanks.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2019-06-25T17:42:35+00:00

    Unfortunately I do not have a solution, but can report that I have the exact same problem with DPC latency spikes caused by ntoskrnl.exe after upgrading to 1903. All drivers and BIOS are up to date (even reinstalled to see if this would help, but did not). Will be rolling back.

    I wonder if the problem is solved now.

    I am also experiencing the same problem.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2019-06-25T18:37:02+00:00

    can you let us know what the tool is?

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2019-06-25T18:50:01+00:00

    I rolled back to 1803 and problems are gone.I blocked the feature update until MS gets a handle on all the issues that our out there.The dropped frames I was getting are gone so its a conflict with 1903.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2019-06-28T10:50:04+00:00

    I have been using LatencyMon to track the spikes. 

    Short story

    Try removing any third party Anti-Virus product active on your system and reboot.  Worked for me!. Worth a try?

    Long story...

    In a Galaxy Far Far.. (sorry couldn't stop myself)

    Can I just say that I had exactly the same issue with the spikes, but much more prevalent - VERY high.  It was affecting audio severely as well as the speed of the system (the mouse would slow horribly too).   Techy bit - Interrupt to DPC latency and reported DPC execution time counts (µs) spike well over 2000 (sometimes showing 22000!)

    It was doing this randomly -  every few seconds, but *could* then be OK for a minute, then start again.  The seeming culprits were with NDIS, DX and USB component drivers.

    From another forum it was advised to boot to safe mode, after disabling ALL startup programs, and none Microsoft services (this is achieved in Win10 via 'MSCONFIG').

    I did as suggested, and rebooted into Safe mode.  It turned out it was that basic that it wouldn't let LatencyMon run.  It unfortunately disabled my audio too.  The mouse seemed fine though!!

    I restarted into what I though was 'normal' mode, and behold! no latency spikes.  I kept running LatencyMon, and after 30 mins, still no spikes.  It was then I noticed my Anti-virus was disabled.  The system services had not restarted.  Sooo, re -ran MSCONFIG, ensuring 'Normal startup' was selected in the General tab, and rebooted.

    And guess what - my AV solution was active, and the latency back with it.  To make sure, I uninstalled the AV client (BitDefender Total Security 2019), rebooted, and left LatencyMon running for hours.  The system has gone back to normal with no appreciable spikes!!!

    NOTE: There is a slightly higher count of Hard Faults than I would have expected, however I believe this is another Win10 1903 introduced quirk.  I'm not witnessing any noticeable side effects.

    Was this answer helpful?

    0 comments