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-17T19:43:10+00:00

    Microsoft wants to force the update to 1903 soon.

    I don't understand why they would do that while this critical bug HAS NOT BEEN FIXED YET.

    This is mindblowing, how do they even come up with such decision, as far as I know they never acknowledged the input lag issues!

    I can't use my studio with 1903 installed...stutters all over the place during tracking and playback. Works fine with 1809 for now, untill 1903 is hopefully fixed. Microsoft can't not know about this. I have seen people with brand new computers with latest i9 processors reporting same problem.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2019-07-17T17:25:46+00:00

    Microsoft wants to force the update to 1903 soon.

    I don't understand why they would do that while this critical bug HAS NOT BEEN FIXED YET.

    This is mindblowing, how do they even come up with such decision, as far as I know they never acknowledged the input lag issues!

    Was this answer helpful?

    0 comments
  3. Anonymous
    2019-07-17T17:10:47+00:00

    Having the exact same issue on Ryzen 7 1700. However, it is ntoskrnl.exe + Wdf01000.sys that have the problem:

    I wonder how we can fix this...?

    Was this answer helpful?

    0 comments
  4. Anonymous
    2019-07-16T16:38:06+00:00

    Having the exact same issue on Ryzen 7 1700. However, it is ntoskrnl.exe + Wdf01000.sys that have the problem:

    Was this answer helpful?

    0 comments
  5. Anonymous
    2019-07-10T12:44:50+00:00

    I'm having the same issues and on both of my computers. One is an I7 2nd gen and the other is an I5 3rd gen. I have my DAW computer (I7)  rolled back to version 1809 and works perfectly.  Hope they fix things soon.

    Was this answer helpful?

    0 comments