Win 10 Version 1903 Issues


I did :slight_smile: Is this a prob?

thx for the help.
I’m running a second time, now 0:59h
And some other drivers have probs. Let’s see on google where I find some info.

Interrupt service routines are routines installed by the OS and device drivers that execute in response to a hardware interrupt signal.

Highest ISR routine execution time (µs):              99,733853
Driver with highest ISR routine execution time:       HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation

Highest reported total ISR routine time (%):          0,000247
Driver with highest ISR total time:                   HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation

Total time spent in ISRs (%)                          0,000407

ISR count (execution time <250 µs):                   17169
ISR count (execution time 250-500 µs):                0
ISR count (execution time 500-999 µs):                0
ISR count (execution time 1000-1999 µs):              0
ISR count (execution time 2000-3999 µs):              0
ISR count (execution time >=4000 µs):                 0

DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it is interrupted until the DPC has finished execution.

Highest DPC routine execution time (µs):              1546,449889
Driver with highest DPC routine execution time:       ACPI.sys - ACPI-stuurprogramma voor NT, Microsoft Corporation

Highest reported total DPC routine time (%):          0,022142
Driver with highest DPC total execution time:         rspLLL64.sys - Resplendence Latency Monitoring and Auxiliary Kernel Library, Resplendence Software Projects Sp.

Total time spent in DPCs (%)                          0,049197


No your power settings are not a problem; they are what they should be :slight_smile:. Good luck troubleshooting! (do you hear glitches? If not, don’t worry about the latencymon findings - proof is in the audio pudding, not in latencymon!)


Haha nice saying :slight_smile: Gotta remember it like that :smiley:
Well, on 1703 I sure had some glitches (lately) that’s also a reason why I switched and regarding to latencymon, it’s a big difference, I got a red warnings the moment I started, before 1903.

I also have Process Lasso Running, I’m not sure after months of evaluation if this program really is doing some improvements.


From the latencymon site:

We believe that hard pagefaults are the most common cause of audio dropouts. The effect of a program hitting hard pagefaults while playing audio is usually dramatic. One problem with pagefaults is that they often come in groups so that a row of pagefault causes interruption of the audio stream. Another problem with them is that unlike ISRs and DPCs, putting in more processors into a system will not help you to avoid them. Page faults need to get resolved immediately and any thread that hits them is suspended until the pagefault is resolved. Hitting a hard pagefault on a page file or memory mapped file that is backed on a drive that is spun down because of a power feature may interrupt a program for several seconds until it can proceed.

  • How to avoid hard pagefaults If you have concluded that hard pagefaults are the cause of audio dropouts, you can do any of the following to resolve the problems:

  • Close down unnecessary applications which consume a lot of RAM

  • Close down unnecessary service applications which consume a lot of RAM (the Search Indexer service is notorious)

  • Increase the amount of RAM in your system

  • Increase the working set of the audio application, only an option if you are the author of the software.

  • Make sure audio data is paged-in (resident). Pages of memory are swapped out based on their use counts. If you use Windows for live playing, do a silent run of your software synthesizer. After changing patch on a sampler, touch all keys so that all memory it uses is paged-in to avoid embarrasing scenes.

  • Disable the pagefile altogether. You can disable the pagefile by right-clicking My Computer and selecting Advanced System Settings->Advanced->Performance Settings->Advanced->Virtual memory->Change. Note that if you have no pagefile, the system can run out of memory if not enough memory is available. Also the system will no longer create crash dump files in case of a system crash.


That is what has been tripping me up also - I always have to give the laptop 3-5 minutes before I run C3 with Jamstix, VB3 and IK Leslie. Windows Telemetry is the culprit for both disk and cpu.

How can you have your audio pudding if you don’t decrease your DPC? :sunglasses:


Love it! I’ll have to try and sneak that into a Welsh Floyd show (when we FINALLY (hopefully) get going again! ) :smile:

Scary to think it is the 40th anniversary of the The Wall this year…


With uwt you can tear down the wall.
You don’t need no latencycation!


Back on topic :slight_smile: (but love the wordplay), how are people now finding 1903?

It is now “ready” for my gig PC. I have not installed it yet, and will take a disk image first!


I have no issues and no spikes anymore after blocking the telemetry. Running for a week now and had 2 rehearsals and 2 concerts.


Played 7 shows with it in Northern Ireland the last couple of days - no issues.


Thanks for the comments, guys.

I’ll take a chance on this, but after doing a disk image first. I have rehearsal a week Sunday, so time enough to try it over the next few days.

And, Sven, thanks for that screen shot. I’ve been looking for a tool like that, and, I think this one was mentioned before, but couldn’t remember the name.

Whilst my GIG laptop is OK (but could be better according to Latency Monitor - I’ll post on that another time), I noticed last night that the video laptop for the band was being hammered performance wise - it has not been on for a month, maybe all sorts of things were trying to run. It was at 80% processor utilisation and 100% disk for over 30 mins.

It’s WIN10 PRO, but probably no tweaks have ever been applied to it, and I noticed all sorts of crap running, like ONE DRIVE Installer, Telemetry, Store, Photos, etc. So time to dig in and fix that. Strange enough one of the culprits last night was RtpMIDI (I connect GIGPC and Video laptop via this), but I am guessing it is because I had the LAN Ethernet unplugged whilst I was migrating to a new home hub for WIFI access (4G broadband deal that gives me unlimited data at 20mbps compared to the 2.4mpbs I get on my soggy Welsh landline!!)

Any other Windows performance tuning tool recommendations appreciated.


I haven’t installed 1903 yet, but I just disabled telemetry with the group policy editor, and also the Microsoft Compatibility Appraiser from the task scheduler, and it made a huge difference at start up.

  • Paul


Latest from Pete at gearslutz :


Originally Posted by b0se View Post

So is this actually fixed then? It seems sporadic in its efficacy.

The issue we introduced in 1903 has been fixed.

I suspect many of the other issues brought up are not related to that fix/problem, but folks are paying more attention to reported numbers, or there are other unrelated issues.

Just a hunch, as I do not have any real way to prove that at the moment.



I updated my GIGPC on the weekend (after taking a disk image first!) and so far performance has been fine. I have not noticed anything detrimental so far other than one I was expecting…

This is the Korg USB MIDI Driver issue mentioned over on Korg Forums. Which means the driver is not seen by Windows.

Korg have now released a new driver, but it is best to completely uninstall the existing driver first. And I used USB Oblivion as well to remove all traces of USB port enumerations before installing the new driver.

After that it all seems to work again.

Sadly, however, this Windows Build finally seems to have caused issues with the old Stalwart MIDIOX, which is a huge shame. I have sort of got it working again by running it in XP compatibility mode, but for some reason the MIDI filters do not work, so you cannot filter out MIDI Clock or Active Sensing. I know we have good MIDI monitoring in Cantabile, but I also like to be able to check MIDI outside of Cantabile for some things. Amazingly there is still no real MIDIOX replacement out there. I could only find a few and they were a bit rubbish".


On all my machines 1903 has been a DOG so all are currently rolled back to earlier versions that worked. All suffering from NDIS spikes of around 6 to 7 ms so unusable for music making period. I don’t believe they have addressed the bad they introduced to the product because it has to do with hardware compatibility and it appears that mostly newer systems seem to be OK. This was a bad update from the start for people with older rigs but it’s just my opinion. From a doctors point of view “do no harm” got dropped on the update and lots of things not nice for real time media use got introduced. FWIW I tried it again this morning hoping for an improvement and it still bites… already rolled back.



Sorry to hear that. How old is your computer?


Hey Sven,

Music performance laptops are 6 yrs old, studio computer is 8 yrs old, home computer 5 yrs old. I maintain and repair all my equipment so there have been upgrades, overhauls and general maintenance throughout. I think it will get sorted out but not till one of us who sent in crash reports gives the programmers the reason that our hardware is being affected and not others. On the other hand it might not even be hardware age (I’m trusting internet posts on this) for all I know because I know it’s working really well on some systems. So it might be just me not configuring it correctly. Thanks for asking …



I noticed I activated Gaming modus on my w10 :slight_smile:
Any comments on this modus?


I have read in a couple places that it actually only optimizes the pathway to the GPU for some graphics improvements, and that changes involving audio are not involved at all."pro+audio"



Hi All,

I checked back on the chatter at GS and this is still not resolved for some of us. Pete and the crew at MS are currently still looking into what causes the problems.