The 1903 update ofWindows 10was tested well before its release.
It was a more stable version than October 2018 update.
But it still had a few issues, which includesdpc latency spikes.
On my computer, the start up time was very high and takes long to become active.
It is also slower while doing normal operations like opening some programs andWindows parameters.
It is found that ntoskrnl.exe / dxgkrnl.sys are causing high DPC routine execution time when tested with LatencyMon.
In thisthread on Reddit, lot offeedback is left on Microsoft app, to make it know the issue.
This reduced the amount of start up time and also execution of programs was quick enough.
But I wanted to check whether Windows 10 1903 DPC latency problem was resolved or not.
I was using the latest KB build which had the following version 18362.267.
Starting from Build 10525, Microsoft added a new feature in theMemory Manager called a compression store.
The compression store lives in the System processs working set.
Windows 10, sacrifices memory in exchange for speed.
Instead of writing pages into your HDD, it compresses the pages on the RAM.
This error is more common using NVIDIA graphic drivers.
I use my desktop for general PC ops and also for my recording studio.
With all versions including 1809 I havent had any issues with latency/clicks/dropouts in audio, etc.
Resplendence Latency Mon shows no problems.
However, with 1903 there is Latency problems.
The culprits according to Latency Mon are USB bus and/or High Definition Audio (Realtek).
Ive restored my PC back to the 1809 5/22/19 disc image I did before upgrading to 1903.
Ive run Latency Mon again after restoring and still no issues (with 1809).
This has also been reported on the gearslutz forum by another user.
Source: https://www.tenforums.com/performance-maintenance/133708-v1903-causing-dpc-latency-hits.html
Solutions forhigh DPC latency spike problem in 1903.
If you have updated from 1809 version, you might revert back to the last version.
This solves the problem for many people.
But you may not get the benefits of the new release.
If it does not work out, you might revert back to normal setting.
This service is another name for prefetch or superfetch which existed in Windows 7.
Atleast it will reduce the latency spike.
Upgrade to the Insider Build of 18909 and most-of the time it will be fixed.
Build 18362.145 seems to solve this issue.
Disable MSI mode for Marvell networks cards which could stop the ntoskrnl.exe spikes.
Scan your machine for virus, adware and malware.
Specifically scan the scan theC:\Windows\System32folder, where the above file resides.
Uninstall incompatibility programs which trigger unusual behavior.
Repair repair Windows System Image and Windows Component Store in Windows 10 using the following commands.
Dism /Online /Cleanup-Image /ScanHealthDism /Online /Cleanup-Image /CheckHealthDism /Online /Cleanup-Image /RestoreHealth
14.
Adjust yourWindows 10 for best performanceresults.
This can be done by disabling visual effects.
Open System from Control Panel.
Then press Advanced system tweaks.
On the Advanced tab, under Performance select tweaks.
Check the following controls using Custom.
Show shadows under windows.2.
Show thumbnails instead of icons.3.
Smooth edges of screen fonts4.
Use drop shadows for icon lables on desktop.
These are the minimal controls for a better appearance and performance.
Use Windows Performance Toolkit to find the root cause.
Open cmd in elevated mode (with administrator privileges) and bang out the following command.
pop crack open the file cpuusage.etl and analyze it with Windows Performance Analyzer for the exact cause.
It could be fixed in the next release or KB update.
For now, there are no solutions for the issue, but there is a workaround.
Users said that after reverting to Windows 10 version 1809, the problem disappeared.