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-07-27T22:16:20+00:00

    I get pretty consistent test results with the KB4505903 update, but not ready to install 1903 on my DAW computer...going to wait. 

    Was this answer helpful?

    0 comments
  2. 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
  3. Anonymous
    2019-08-17T00:59:43+00:00

    Thanks Artur, I'll remember to come back here if needed in the future.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2019-08-17T10:02:16+00:00

    Same here.

    Only difference is that I replaced the NVIDIA graphics card by one from ATI which instantly solved any spikes from dxgkrnl.

    The new one is by far not als powerful as the old one but at last I can run my audio software again w/o any dropouts.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2019-08-17T12:21:32+00:00

    Google - MSISupported to turn on Message-Signalled Interrupts for the devices.

    Was this answer helpful?

    0 comments