[wdmaudiodev] Re: Increasing Timer Resolution results in erratic Scheduling/DPC Latencies on Windows 10

  • From: "Matthew van Eerde" <dmarc-noreply@xxxxxxxxxxxxx> (Redacted sender "Matthew.van.Eerde" for DMARC)
  • To: "wdmaudiodev@xxxxxxxxxxxxx" <wdmaudiodev@xxxxxxxxxxxxx>
  • Date: Wed, 8 May 2019 16:42:51 +0000

Devendra was running RS4 already when he grabbed the logs, so this is something 
else.

________________________________
From: wdmaudiodev-bounce@xxxxxxxxxxxxx <wdmaudiodev-bounce@xxxxxxxxxxxxx> on 
behalf of Vincent Burel (VB-Audio) <vincent.burel@xxxxxxxxxxxx>
Sent: Wednesday, May 8, 2019 12:18:22 AM
To: wdmaudiodev@xxxxxxxxxxxxx
Subject: [wdmaudiodev] Re: Increasing Timer Resolution results in erratic 
Scheduling/DPC Latencies on Windows 10

Hello,

It’s maybe about the virtual memory management bug reported in this list in 
February 2018, producing big interruption in Real Time process
“WIN10 Major Issue for Audio Processing (OS special mode for small buffer)”

Article:
https://www.facebook.com/notes/vb-audio-software/finally-windows-10-could-support-audio/1646244165445117/<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.facebook.com%2Fnotes%2Fvb-audio-software%2Ffinally-windows-10-could-support-audio%2F1646244165445117%2F&data=01%7C01%7Cmatthew.van.eerde%40microsoft.com%7C872f45eccf504d2c16b108d6d3856fdc%7C72f988bf86f141af91ab2d7cd011db47%7C1&sdata=UuMWwpzY5c6sEBEAiIEu8t7j3yprZO5g%2B8ker5bgbVs%3D&reserved=0>

Stress Test/ Validation tool
https://forum.vb-audio.com/viewtopic.php?f=11&t=519&p=1255<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fforum.vb-audio.com%2Fviewtopic.php%3Ff%3D11%26t%3D519%26p%3D1255%26fbclid%3DIwAR1kV4xIl5jfirrNujMxlYQ0Nh6PF4_6WR_kOhgdIVTWHFwWMHeZIGrPGlA&data=01%7C01%7Cmatthew.van.eerde%40microsoft.com%7C872f45eccf504d2c16b108d6d3856fdc%7C72f988bf86f141af91ab2d7cd011db47%7C1&sdata=eW3MkBVA9G1Et7cSCAy5dHxejR5kgu7L1A310dxx4AM%3D&reserved=0>

This has been corrected in Windows RS4 version (May 2018).

Regards
Vincent Burel


De : wdmaudiodev-bounce@xxxxxxxxxxxxx [mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] ;
De la part de AI Developer
Envoyé : mercredi 8 mai 2019 02:20
À : wdmaudiodev@xxxxxxxxxxxxx
Objet : [wdmaudiodev] Re: Increasing Timer Resolution results in erratic 
Scheduling/DPC Latencies on Windows 10

As it turns out, I had already started to update Windows (from 1803 -> 1809) 
while working to collect more information. So I let it finish the update.

But now, after the update, I'm no longer able to duplicate this behavior!

Either there's something related to this that's fixed in Windows (or other 
drivers which got updated alongwith), or maybe some other driver which was 
causing this behavior is no longer being loaded.

I will keep checking. Sometimes this issue takes longer to reproduce.

Thanks.
Devendra.

On Tue, May 7, 2019 at 4:48 PM AI Developer 
<developer@xxxxxxxxxxxxxxxx<mailto:developer@xxxxxxxxxxxxxxxx>> wrote:
Okay, will do that.

Thanks.
Devendra.

On Tue, May 7, 2019 at 4:21 PM Matthew van Eerde 
<dmarc-noreply@xxxxxxxxxxxxx<mailto:dmarc-noreply@xxxxxxxxxxxxx>> wrote:
Thanks. I’m looking at the logs, and I don’t see any calls into the Windows 
audio stack. So the Microsoft.Windows.Audio.KernelStreamingEndpoint/Glitch 
events I was hoping to see, that would tell me where to look, aren’t being 
induced.

Can you add logs (you can reuse the same problem report) of audio glitching 
from an app that uses the Windows audio APIs – say, Chrome?

________________________________
From: wdmaudiodev-bounce@xxxxxxxxxxxxx<mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx
<wdmaudiodev-bounce@xxxxxxxxxxxxx<mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx>> on 
behalf of AI Developer 
<developer@xxxxxxxxxxxxxxxx<mailto:developer@xxxxxxxxxxxxxxxx>>
Sent: Tuesday, May 7, 2019 6:44:22 PM
To: wdmaudiodev@xxxxxxxxxxxxx<mailto:wdmaudiodev@xxxxxxxxxxxxx>
Subject: [wdmaudiodev] Re: Increasing Timer Resolution results in erratic 
Scheduling/DPC Latencies on Windows 10

Here's the link to the problem report:

https://aka.ms/AA51wnl

Thanks.
Devendra.

On Tue, May 7, 2019 at 10:12 AM Matthew van Eerde 
<dmarc-noreply@xxxxxxxxxxxxx<mailto:dmarc-noreply@xxxxxxxxxxxxx>> wrote:
Start by filing a problem report in Feedback Hub. Include “recreate my problem” 
logs of the problem in action.
Then send me a link to the problem report.
https://matthewvaneerde.wordpress.com/2016/09/26/report-problems-with-logs-and-suggest-features-with-the-feedback-hub/<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmatthewvaneerde.wordpress.com%2F2016%2F09%2F26%2Freport-problems-with-logs-and-suggest-features-with-the-feedback-hub%2F&data=01%7C01%7Cmatthew.van.eerde%40microsoft.com%7C872f45eccf504d2c16b108d6d3856fdc%7C72f988bf86f141af91ab2d7cd011db47%7C1&sdata=nT4f8mq3eW%2FERmwkmVfVW0iNbzdVXK3U3%2BFO6%2BPgLgw%3D&reserved=0>

________________________________
From: wdmaudiodev-bounce@xxxxxxxxxxxxx<mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx
<wdmaudiodev-bounce@xxxxxxxxxxxxx<mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx>> on 
behalf of AI Developer 
<developer@xxxxxxxxxxxxxxxx<mailto:developer@xxxxxxxxxxxxxxxx>>
Sent: Tuesday, May 7, 2019 7:03:38 AM
To: wdmaudiodev@xxxxxxxxxxxxx<mailto:wdmaudiodev@xxxxxxxxxxxxx>
Subject: [wdmaudiodev] Increasing Timer Resolution results in erratic 
Scheduling/DPC Latencies on Windows 10

We've come across a few Desktop PCs (and at least one MacBook Pro running 
BootCamp) where this happens.

It doesn't matter how the resolution is increased, whether from user mode by 
timeBeginPeriod() or in kernel mode via ExSetTimerResolution() - the result is 
the same.

Once the resolution is increased, from time to time (with a gap of  5 - 30 
seconds), there will be scheduling delays.

The delays can be seen in various forms (all coinciding):

- LatencyMon (from Resplendence) reports an Interrupt to Process latency of 
about 10 - 12 milliseconds from time to tim.
- Our NDIS Protocol driver receives network packets about 10-12 milliseconds 
late from time to time.
- A simple user mode program calling Sleep(1) will wake up after 10-12 
milliseconds from time to time.

[Needless to say, this results in audio dropouts]

At the same time, LatencyMon does not indicate any specific DPC or Interrupt 
taking a long time (max. reported is about 500 microseconds).

Also checked with Windows Performance Toolkit (xperf). Once again, there's no 
indication of any driver spending that much amount of time in ISRs or DPCs.

Further, I've tried disabling all non-essential devices (WiFi, Ethernet, 
BlueTooth, Audio devices, other USB devices) and services (VirusScan, FireWall, 
etc..) and background apps.

LatencyMon suggested disabling Power Throttling (also did that), and updating 
the BIOS (also did that). But that also didn't help.

Also tried disabling dynamictick, and enabling platfrom clock, etc.. Once 
again, none of this helps.

I'm surprised that this has not come up before!

Any suggestions on where to look for or how to solve this would be greatly 
appreciated!

Thanks.
Devendra.





Other related posts: