[SOLVED] High DPC latency and popping noises

I installed the RST and it just made it worse. (I've uninstalled it)
here's the updated latencymon stats
Read More:
 
The HdAudbus.sys has a latency problem with the ethernet disabled while I'm listening to music.
Read More:
 
Could you re-try without glasswire, avira antivir, Malwarebytes? (use ms defender and firewall)
And then provide a new trace?

Speccy found you are using two disks (WD 720rpm and Samsung SSD), instead Msconfig and the trace show you are using three disks (another Seagate 540rpm).
Do you know why?
How are they connected?
 
Last edited:
Forgot to mention, I have added that Seagate HDD from my old broken laptop.
Maybe you have missed the seagate hdd part at the newer speccy link? Because I can find the seagate hdd at the last speccy link.

I've switch back to bitdefender.
I have stopped the Glasswire from starting up when windows starts.

Here's the newer speccy link for extra information.
http://speccy.piriform.com/results/GHFlpviTXbHsAuChG7stod5

Newer trace
 
Yup. I've missed it. :)

Could you try to see if the problem is still present with MS defender and firewall, without any other third party AV/FW (that should be uninstalled)?
 
You could try to run driver verifier; please read CAREFULLY the following instructions:

  • Only for windows 8, 8.1, 10 users (Win7 users, WinVista users, XP users, shouldn't have this problem): change the bcdedit bootmenupolicy setting from standard to legacy, then restart your PC and see if you are able to make appear windows advanced boot options (SAFE MODE included!) with the good old F8 key.
    See the hidden instructions if you don't know how to do it.
    Read More:
  • Create a restore point
  • Create a system image
  • Read the guide about Driver Verifier - BSOD related - Windows 10, 8.1, 8, 7 & Vista (click).
  • Read some other tutorials/guides and WARNINGS on internet.
  • Enable verifier
    You can use either the standard method, or the EXPERIMENTAL instructions at the end of this post.
    No need to use them both.
    By the way, in the experimental instructions I modified some verifier settings:
    • I've added NDIS/WIFI verification, because it seems you (PC Cheah) have this problem.
    • I've added the parameter /bootmode resetonbootfail: this should reset driver verifier if it should cause the pc to go in BSOD loop state (see next point).
      This option is incompatible with windows 7 and windows vista (it should be skipped by them).
  • If you'll get a very fast BSOD after you logged into windows, you'll need to go to safe mode to reset verifier settings.
    From an elevated command prompt:
    Code: 
    verifier /reset
  • Post here the new verifier dump


Danger

I created the following method to speed up things a bit, to enable verifier settings like written in Jcgriff's verifier thread, using only third party drivers (hence excluding microsoft drivers).
This was tested only on Windows 10 home x64 (and partially on windows 7)



  • download nirsoft driverview and decompress its folder (leaving its default name) on your desktop, i.e. on the desktop there should be the driverview folder (with its files in it):
  • open notepad, copy the following text and save the file on your desktop as EnableVerifier.ps1:
    Note:
    Code for 64bit windows versions

    Read More:
    Note:
    Code for 32bit windows versions

    Read More:
  • From an elevated command prompt, run:
    powershell -executionpolicy unrestricted "%userprofile%\desktop\EnableVerifier.ps1"
    Click to expand...
  • It should appear something like:
    Read More:
  • Reboot your machine and wait the verifier dump (i.e., verifier should force a new BSOD, identifying the problem).
 
Last edited:
Re-try with this code:
Read More:
And this command:
powershell -executionpolicy unrestricted "%userprofile%\desktop\EnableVerifier.ps1"
Click to expand...
 
Last edited:
Put driverview.exe directly in c: then retry with the following code and command:
Read More:

powershell -executionpolicy unrestricted "c:\users\PC` Cheah\desktop\EnableVerifier.ps1"
Click to expand...

If it still won't work, use the standard method (i.e., do it manually from verifier GUI).
 
Actually I ran the verifier after you post the latest reply. Until now and it almost 24 hours and the verifier doesn't get any problems with it. No bsod but still high ISR routune on the HDAudbus.sys and DPC routine on the NDIS.sys.
Read More:
 
Back
Top