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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2019-07-29T10:14:30+00:00

    I had the exact same problem with this new Windows build - ntoskrnl.exe was spiking badly at about 6000µs which caused really bad audio dropouts even when simply listening to music in winamp.

    After reading the whole thread I went on and installed the newest update (KB4505903) which almost solved the problem, ntoskrnl was not spiking anymore, but instead some nvidia driver component was, I believe it was dxgkrnl.exe (at the time I had installed nvidia 431.36 driver in my system).

    After installing the latest 431.60 driver the problem COMPLETELY went away. So there you go, maybe this will help out someone out-there.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  2. Anonymous
    2019-06-17T09:51:00+00:00

    Doesn't seem to be related to audio or ethernet drivers, have tried with realtek audio disabled in the BIOS and with a Yamaha AG03 USB audio interface, ntoskrnl.exe was still causing issues.       

    Have also tried with the Intel i211-AT ethernet controller disabled in the bios and without, no change.     

    It's a Windows issue.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2019-06-17T08:49:32+00:00

    If I am not wrong. This issue could be caused by either the audio or LAN drivers.

    I'm guessing that the current drivers are not fully compatible with 1903.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2019-06-16T17:21:16+00:00

    Have tried your proposed solution, it did not mitigate ntoskrnl.exe latency spikes on my Ryzen system.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2019-06-01T06:17:01+00:00

    I already had the latest drivers installed except for the BIOS update.

    Unfortunately, same results (~1,300us ntoskrnl.exe spike) after updating the BIOS to 2004.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments