Install 1903 Windows 10 and resolve performance issues caused by ntoskrnl.exe.
Install 1903 Windows 10 and resolve performance issues caused by ntoskrnl.exe.
- Reddit discussion on high latency in 1903
- GeForce forums about latency spikes
- YouTube video about performance issues
- Insider Windows tips for troubleshooting
Feel free to share any updates or steps you’ve tried!
PowergirlA
05-28-2016, 05:40 PM #1I thought it would be good to check if anyone knows a fix for the problem I’m facing with Windows 10 Update 1903 (Build 10.0.18362.145). The main concern is that my system becomes totally unstable after about 12 hours without a power cycle. This has affected many functions like downloading apps, streaming files to/from NAS, cursor movement, video playback, game loading, voice chat, and Java programs. I’m not alone in this issue. Here are some links you might find useful:
- Reddit discussion on high latency in 1903
- GeForce forums about latency spikes
- YouTube video about performance issues
- Insider Windows tips for troubleshooting
Feel free to share any updates or steps you’ve tried!
1) Temporarily cut off internet—loads dropped, suggesting malware or mining software using your hardware. Consider running "GPU Temp" to check GPU load.
2) Open Task Manager, identify resource-heavy processes, end them, and monitor improvements.
3) Right-click the high-consumption process, navigate to its location (often C:\programdata\hidden), inspect files like nvtray.exe and Temp folder contents, verify legitimacy with VirusTotal, then secure permissions.
Everything appears stable now.
SushiCherry
06-13-2016, 02:15 PM #2It seems you've encountered a similar problem before. Your system temperatures and workloads match what I saw. Whenever I log in with full CPU and GPU usage, I face the same challenges. Here’s what helped:
1) Temporarily cut off internet—loads dropped, suggesting malware or mining software using your hardware. Consider running "GPU Temp" to check GPU load.
2) Open Task Manager, identify resource-heavy processes, end them, and monitor improvements.
3) Right-click the high-consumption process, navigate to its location (often C:\programdata\hidden), inspect files like nvtray.exe and Temp folder contents, verify legitimacy with VirusTotal, then secure permissions.
Everything appears stable now.
Thank you for the update. No malware detected. All processes running are legitimate. Tasker is monitoring GPU usage via Google Chrome, Desktop Windows Manager, and CAM software. System temperatures are within normal limits. Files are stored correctly. Virustotal confirmed no threats present.
Alright, start with a clean boot. Navigate to msconfig, click the "hide all microsoft services" option under the services tab, then tick "disable all" and apply. Open Task Manager, go to the startup section, and turn off any programs you don’t need or suspect. Restart the system and check the load performance. If everything looks normal, return to msconfig, select the services tab again, hide all microsoft services, and enable them one by one, rebooting after each change. Eventually, you might notice the load issue resurface. Then go back to disable services gradually, testing each one until you pinpoint the culprit.
s) on all processors. _________________________________________________________________________________________________________ SYSTEM INFORMATION _________________________________________________________________________________________________________ Computer name: NEXUS-MKIV OS version: Windows 10 , 10.0, version 1903, build: 18362 (x64) Hardware: MS-7A63, MSI, Z270 GAMING PRO CARBON (MS-7A63) CPU: GenuineIntel Intel® Core™ i7-7700K CPU @ 4.20GHz Logical processors: 8 Processor groups: 1 RAM: 32727 MB total _________________________________________________________________________________________________________ CPU SPEED _________________________________________________________________________________________________________ Reported CPU speed: 420 MHz Note: reported execution times may be calculated based on a fixed reported CPU speed. Disable variable speed settings like Intel Speed Step and AMD Cool N Quiet in the BIOS setup for more accurate results. WARNING: the CPU speed that was measured is only a fraction of the CPU speed reported. Your CPUs may be throttled back due to variable speed settings and thermal issues. It is suggested that you run a utility which reports your actual CPU frequency and temperature. _________________________________________________________________________________________________________ MEASURED INTERRUPT TO USER PROCESS LATENCIES _________________________________________________________________________________________________________ The interrupt to process latency reflects the measured interval that a usermode process needed to respond to a hardware request from the moment the interrupt service routine started execution. This includes the scheduling and execution of a DPC routine, the signaling of an event and the waking up of a usermode thread from an idle wait state in response to that event. Highest measured interrupt to process latency (µs): 3283.80 Average measured interrupt to process latency (µs): 42.949099 Highest measured interrupt to DPC latency (µs): 3034.30 Average measured interrupt to DPC latency (µs): 39.917912 _________________________________________________________________________________________________________ REPORTED ISRs _________________________________________________________________________________________________________ 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): 106.219762 Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation Highest reported total ISR routine time (%): 0.000053 Driver with highest ISR total time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation Total time spent in ISRs (%) 0.000057 ISR count (execution time <250 µs): 347 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 _________________________________________________________________________________________________________ REPORTED DPCs _________________________________________________________________________________________________________ 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): 1072.852381 Driver with highest DPC routine execution time: ndis.sys - Network Driver Interface Specification (NDIS), Microsoft Corporation Highest reported total DPC routine time (%): 0.000245 Driver with highest DPC total execution time: ndis.sys - Network Driver Interface Specification (NDIS), Microsoft Corporation Total time spent in DPCs (%) 0.000432 DPC count (execution time <250 µs): 2996 DPC count (execution time 250-500 µs): 0 DPC count (execution time 500-999 µs): 22 DPC count (execution time 1000-1999 µs): 1 DPC count (execution time 2000-3999 µs): 0 DPC count (execution time >=4000 µs): 0 _________________________________________________________________________________________________________ REPORTED HARD PAGEFAULTS _________________________________________________________________________________________________________ Hard pagefaults are events that get triggered by making use of virtual memory that is not resident in RAM but backed by a memory mapped file on disk. The process of resolving the hard pagefault requires reading in the memory from disk while the process is interrupted and blocked from execution. NOTE: some processes were hit by hard pagefaults. If these were programs producing audio, they are likely to interrupt the audio stream resulting in dropouts, clicks and pops. Check the Processes tab to see which programs were hit. Process with highest pagefault count: cam.desktop.exe Total number of hard pagefaults 10 Hard pagefault count of hardest hit process: 5 Number of processes hit: 3 _________________________________________________________________________________________________________ PER CPU DATA _________________________________________________________________________________________________________ CPU 0 Interrupt cycle time (s): 51.849984 CPU 0 ISR highest execution time (µs): 106.219762 CPU 0 ISR total execution time (s): 0.002850 CPU 0 ISR count: 214 CPU 0 DPC highest execution time (µs): 719.334286 CPU 0 DPC total execution time (s): 0.008188 CPU 0 DPC count: 1204 _________________________________________________________________________________________________________ CPU 1 Interrupt cycle time (s): 9.470845 CPU 1 ISR highest execution time (µs): 1.676667 CPU 1 ISR total execution time (s): 0.000127 CPU 1 ISR count: 133 CPU 1 DPC highest execution time (µs): 37.412381 CPU 1 DPC total execution time (s): 0.004166 CPU 1 DPC count: 556 _________________________________________________________________________________________________________ CPU 2 Interrupt cycle time (s): 32.983812 CPU 2 ISR highest execution time (µs): 0.0 CPU 2 ISR total execution time (s): 0.0 CPU 2 ISR count: 0 CPU 2 DPC highest execution time (µs): 1072.852381 CPU 2 DPC total execution time (s): 0.009067 CPU 2 DPC count: 954 _________________________________________________________________________________________________________ CPU 3 Interrupt cycle time (s): 8.017368 CPU 3 ISR highest execution time (µs): 0.0 CPU 3 ISR total execution time (s): 0.0 CPU 3 ISR count: 0 CPU 3 DPC highest execution time (µs): 12.209762 CPU 3 DPC total execution time (s): 0.000273 CPU 3 DPC count: 83 _________________________________________________________________________________________________________ CPU 4 Interrupt cycle time (s): 5.699519 CPU 4 ISR highest execution time (µs): 0.0 CPU 4 ISR total execution time (s): 0.0 CPU 4 ISR count: 0 CPU 4 DPC highest execution time (µs): 74.176190 CPU 4 DPC total execution time (s): 0.000222 CPU 4 DPC count: 83 _________________________________________________________________________________________________________ CPU 5 Interrupt cycle time (s): 5.704484 CPU 5 ISR highest execution time (µs): 0.0 CPU 5 ISR total execution time (s): 0.0 CPU 5 ISR count: 0 CPU 5 DPC highest execution time (µs): 7.857143 CPU 5 DPC total execution time (s): 0.000085 CPU 5 DPC count: 35 _________________________________________________________________________________________________________ CPU 6 Interrupt cycle time (s): 7.433967 CPU 6 ISR highest execution time (µs): 0.0 CPU 6 ISR total execution time (s): 0.0 CPU 6 ISR count: 0 CPU 6 DPC highest execution time (µs): 356.685476 CPU 6 DPC total execution time (s): 0.000652 CPU 6 DPC count: 56 _________________________________________________________________________________________________________ CPU 7 Interrupt cycle time (s): 6.929481 CPU 7 ISR highest execution time (µs): 0.0 CPU 7 ISR total execution time (s): 0.0 CPU 7 ISR count: 0 CPU 7 DPC highest execution time (µs): 9.191190 CPU 7 DPC total execution time (s): 0.000105 CPU 7 DPC count: 48 _________________________________________________________________________________________________________
Raiinbowdash60
06-15-2016, 11:51 AM #5Okay so I've done as you suggested. in the msconfig the system wouldn't let me disable bit defender. All the rest under instructions are off. I ran a test after 24hr to get a base line BUT the problem still persists. _________________________________________________________________________________________________________ CONCLUSION _________________________________________________________________________________________________________ Your system appears to be having trouble handling real-time audio and other tasks. You are likely to experience buffer underruns appearing as drop outs, clicks or pops. One or more DPC routines that belong to a driver running in your system appear to be executing for too long. At least one detected problem appears to be network related. In case you are using a WLAN adapter, try disabling it to get better results. One problem may be related to power management, disable CPU throttling settings in Control Panel and BIOS setup. Check for BIOS updates. LatencyMon has been analyzing your system for 0:10:58 (h:mms) on all processors. _________________________________________________________________________________________________________ SYSTEM INFORMATION _________________________________________________________________________________________________________ Computer name: NEXUS-MKIV OS version: Windows 10 , 10.0, version 1903, build: 18362 (x64) Hardware: MS-7A63, MSI, Z270 GAMING PRO CARBON (MS-7A63) CPU: GenuineIntel Intel® Core™ i7-7700K CPU @ 4.20GHz Logical processors: 8 Processor groups: 1 RAM: 32727 MB total _________________________________________________________________________________________________________ CPU SPEED _________________________________________________________________________________________________________ Reported CPU speed: 420 MHz Note: reported execution times may be calculated based on a fixed reported CPU speed. Disable variable speed settings like Intel Speed Step and AMD Cool N Quiet in the BIOS setup for more accurate results. WARNING: the CPU speed that was measured is only a fraction of the CPU speed reported. Your CPUs may be throttled back due to variable speed settings and thermal issues. It is suggested that you run a utility which reports your actual CPU frequency and temperature. _________________________________________________________________________________________________________ MEASURED INTERRUPT TO USER PROCESS LATENCIES _________________________________________________________________________________________________________ The interrupt to process latency reflects the measured interval that a usermode process needed to respond to a hardware request from the moment the interrupt service routine started execution. This includes the scheduling and execution of a DPC routine, the signaling of an event and the waking up of a usermode thread from an idle wait state in response to that event. Highest measured interrupt to process latency (µs): 3283.80 Average measured interrupt to process latency (µs): 42.949099 Highest measured interrupt to DPC latency (µs): 3034.30 Average measured interrupt to DPC latency (µs): 39.917912 _________________________________________________________________________________________________________ REPORTED ISRs _________________________________________________________________________________________________________ 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): 106.219762 Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation Highest reported total ISR routine time (%): 0.000053 Driver with highest ISR total time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation Total time spent in ISRs (%) 0.000057 ISR count (execution time <250 µs): 347 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 _________________________________________________________________________________________________________ REPORTED DPCs _________________________________________________________________________________________________________ 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): 1072.852381 Driver with highest DPC routine execution time: ndis.sys - Network Driver Interface Specification (NDIS), Microsoft Corporation Highest reported total DPC routine time (%): 0.000245 Driver with highest DPC total execution time: ndis.sys - Network Driver Interface Specification (NDIS), Microsoft Corporation Total time spent in DPCs (%) 0.000432 DPC count (execution time <250 µs): 2996 DPC count (execution time 250-500 µs): 0 DPC count (execution time 500-999 µs): 22 DPC count (execution time 1000-1999 µs): 1 DPC count (execution time 2000-3999 µs): 0 DPC count (execution time >=4000 µs): 0 _________________________________________________________________________________________________________ REPORTED HARD PAGEFAULTS _________________________________________________________________________________________________________ Hard pagefaults are events that get triggered by making use of virtual memory that is not resident in RAM but backed by a memory mapped file on disk. The process of resolving the hard pagefault requires reading in the memory from disk while the process is interrupted and blocked from execution. NOTE: some processes were hit by hard pagefaults. If these were programs producing audio, they are likely to interrupt the audio stream resulting in dropouts, clicks and pops. Check the Processes tab to see which programs were hit. Process with highest pagefault count: cam.desktop.exe Total number of hard pagefaults 10 Hard pagefault count of hardest hit process: 5 Number of processes hit: 3 _________________________________________________________________________________________________________ PER CPU DATA _________________________________________________________________________________________________________ CPU 0 Interrupt cycle time (s): 51.849984 CPU 0 ISR highest execution time (µs): 106.219762 CPU 0 ISR total execution time (s): 0.002850 CPU 0 ISR count: 214 CPU 0 DPC highest execution time (µs): 719.334286 CPU 0 DPC total execution time (s): 0.008188 CPU 0 DPC count: 1204 _________________________________________________________________________________________________________ CPU 1 Interrupt cycle time (s): 9.470845 CPU 1 ISR highest execution time (µs): 1.676667 CPU 1 ISR total execution time (s): 0.000127 CPU 1 ISR count: 133 CPU 1 DPC highest execution time (µs): 37.412381 CPU 1 DPC total execution time (s): 0.004166 CPU 1 DPC count: 556 _________________________________________________________________________________________________________ CPU 2 Interrupt cycle time (s): 32.983812 CPU 2 ISR highest execution time (µs): 0.0 CPU 2 ISR total execution time (s): 0.0 CPU 2 ISR count: 0 CPU 2 DPC highest execution time (µs): 1072.852381 CPU 2 DPC total execution time (s): 0.009067 CPU 2 DPC count: 954 _________________________________________________________________________________________________________ CPU 3 Interrupt cycle time (s): 8.017368 CPU 3 ISR highest execution time (µs): 0.0 CPU 3 ISR total execution time (s): 0.0 CPU 3 ISR count: 0 CPU 3 DPC highest execution time (µs): 12.209762 CPU 3 DPC total execution time (s): 0.000273 CPU 3 DPC count: 83 _________________________________________________________________________________________________________ CPU 4 Interrupt cycle time (s): 5.699519 CPU 4 ISR highest execution time (µs): 0.0 CPU 4 ISR total execution time (s): 0.0 CPU 4 ISR count: 0 CPU 4 DPC highest execution time (µs): 74.176190 CPU 4 DPC total execution time (s): 0.000222 CPU 4 DPC count: 83 _________________________________________________________________________________________________________ CPU 5 Interrupt cycle time (s): 5.704484 CPU 5 ISR highest execution time (µs): 0.0 CPU 5 ISR total execution time (s): 0.0 CPU 5 ISR count: 0 CPU 5 DPC highest execution time (µs): 7.857143 CPU 5 DPC total execution time (s): 0.000085 CPU 5 DPC count: 35 _________________________________________________________________________________________________________ CPU 6 Interrupt cycle time (s): 7.433967 CPU 6 ISR highest execution time (µs): 0.0 CPU 6 ISR total execution time (s): 0.0 CPU 6 ISR count: 0 CPU 6 DPC highest execution time (µs): 356.685476 CPU 6 DPC total execution time (s): 0.000652 CPU 6 DPC count: 56 _________________________________________________________________________________________________________ CPU 7 Interrupt cycle time (s): 6.929481 CPU 7 ISR highest execution time (µs): 0.0 CPU 7 ISR total execution time (s): 0.0 CPU 7 ISR count: 0 CPU 7 DPC highest execution time (µs): 9.191190 CPU 7 DPC total execution time (s): 0.000105 CPU 7 DPC count: 48 _________________________________________________________________________________________________________
AGamersHero
06-15-2016, 05:52 PM #6I completed the tests but the results weren't clear. A clean boot didn’t fix the issue, and the stuttering persisted for a longer time. Running LatencyMon highlighted a few potential causes: ndis.sys, tcpip.sys, dxgkrnl.sys, and ntoskrnl.sys. All references stayed tied to the kernel and network interface... It was a bit surprising that LMG didn’t complain, especially with fiber internet like mine. Maybe Microsoft just doesn’t like it.
DarkBoy__YT
06-15-2016, 09:12 PM #7it's the network card issue—download latencymon when the problem appears. Click start, run a speedtest, and you'll see ntoskrnl.exe and network driver activity causing this. Try updating your LAN card drivers to version 1903 from the vendor site. For me, I'm using Gigabyte Z270-G7 with drivers for version 1809. Search ntoskrnl.exe 1903 and network card ntoskrnl.exe online; many solutions are shared in posts and Reddit threads.
Following xperf usage it looks like the DPC spikes in ntokrl.exe are linked to Patchguard. PatchGuard is a built-in Windows protection against kernel patches (more details available). You might want to turn off PatchGuard using EfiGuard as a temporary fix. This isn't a permanent fix, but it could help if you've installed Windows 1903. The optimal fix would be to upgrade to a fresh, stable version of Windows for the best performance.