V1903 Causing DPC Latency Hits

Page 1 of 4 123 ... LastLast
  1. fireberd's Avatar
    Posts : 2,043
    Win 10
       #1

    V1903 Causing DPC Latency Hits


    I use my desktop for general PC ops and also for my recording studio. With all versions including 1809 I haven't 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). I've restored my PC back to the 1809 5/22/19 disc image I did before upgrading to 1903. I've run Latency Mon again after restoring and still no issues (with 1809). This has also been reported on the gearslutz forum by another user.
    Here are the Latency Mon screenshots, both for 1903 and 1809.
    V1903 Causing DPC Latency Hits-latency-mon-1903.jpgV1903 Causing DPC Latency Hits-latency-mon-1809.jpg
      My Computers

  2. fireberd's Avatar
    Posts : 2,043
    Win 10
    Thread Starter
       #2

    Update, I ran the Resplendence Latency Mon on my Insider Build 18908 and it too is OK. Its the same hardware (dual boot system) as the 1903 release.
    V1903 Causing DPC Latency Hits-latency-mon-v18908.png
      My Computers

  3. TairikuOkami's Avatar
    Posts : 4,109
    Home 2004 x64 10.0.19041.264
       #3

    Try to set the timer to 0.5 ms via either of those, the second one also deals with the standby memory bug.

    Windows System Timer Tool | vvvv

    Intelligent standby list cleaner v1.0.1.1 Released | Wagnardsoft
    Attached Thumbnails Attached Thumbnails V1903 Causing DPC Latency Hits-capture_05302019_200439.jpg   V1903 Causing DPC Latency Hits-capture_05302019_200151.jpg  
      My Computer

  4. fireberd's Avatar
    Posts : 2,043
    Win 10
    Thread Starter
       #4

    Why only 1903? 1809 (and earlier versions) does not have the problem. The current Insider version does not have the problem. Those linked tweats may fix it but shouldn't have to.
      My Computers

  5. fireberd's Avatar
    Posts : 2,043
    Win 10
    Thread Starter
       #5

    Another update. I decided to give 1903 another try this morning. I downloaded/installed again. Build 18362.145 (I don't know what the other 1903 build number was). I ran Latency Mon for over 5 minutes and no hits. I couldn't do that before. I can only guess either a later build that fixed it or I had a bad install before.

    I'm not marking this solved, yet.
      My Computers

  6. fireberd's Avatar
    Posts : 2,043
    Win 10
    Thread Starter
       #6

    My Latency problem is (apparently) gone with the new 1903 install. I'm marking this solved.
      My Computers



  7. Posts : 4
    Windows 10 EDU
       #7

    I'm still getting some ntoskrnl.exe hits off about 700us, but they come at much farther intervals than before. I could go 3-4 mins before it happens, those huge 3000us spikes have since been resolved either by me turning off more services or that cumulative update the other day. Nobody else is having problems?
      My Computer

  8. fireberd's Avatar
    Posts : 2,043
    Win 10
    Thread Starter
       #8

    On the first 1903 install I also ran across a problem with my MOTU 4pre USB recording interface unit. It was recognized by the MOTU control program but my recording programs (Sonar and Studio One 4.5) did not detect it. I had to Repair the 4pre driver before it was recognized. On the second install, along with no latency problems I did not have the 4pre driver problem.

    I've run Latency Mon for 15 minutes and it was still "happy".
      My Computers


  9. Posts : 4
    Windows 10 EDU
       #9

    Another thing that helped me out was disabling MSI-mode on my network adapter, it for some reason stopped big ntoskrnl.exe spikes.
      My Computer

  10. fireberd's Avatar
    Posts : 2,043
    Win 10
    Thread Starter
       #10

    Here is the Latency Mon, run this morning for 10 minutes.
    V1903 Causing DPC Latency Hits-asus-1903-v2.jpg
      My Computers


 
Page 1 of 4 123 ... LastLast

Related Threads
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 22:10.
Find Us




Windows 10 Forums