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-06-17T13:05:23+00:00

    Not too sure it can be totally disabled even when its turned off.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2019-06-17T12:55:32+00:00

    I had Control Flow Guard disabled and that didn't really change anything.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2019-06-17T12:53:03+00:00

    My hunch is Microcode is causing this and nobody can figure out how to fix it,but Control Flow Guard is my second guess.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2019-06-17T12:37:03+00:00

    As others stated before, Power Throttling didn't change the spikes (Windows Home, only through registry, since gpedit isn't available for this edition).

    I'm trying now with MSI-mode on drivers.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2019-06-17T11:09:07+00:00

    Yeah you're right.

    By the way, do you know why this issue is NOT listed or pinned as one of the most important ones in the feedback hub etc?

    This is literally killing the whole experience and Microsoft did not acknowledge it at least.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments