New
#11
Hi @Msprg
How did you take your trace? which parameters did you checked in WPR and did the problem occured during the trace record?
Crackly internal sound, some USB devices not working properly
-
-
New #12
That could be useful.
Are the Windows builds of both installations exactly the same, and have driver updates been allowed on your 'clean' installation, or have you blocked WU on the 'clean' installation?
If the former, then presumably your issues relate to something you have subsequently installed.
-
New #13
Hello @zinou,
I made trace into memory, containing "first level triage" and "Audio glitches" from scenario analysis. Performance scenario set to "General", Detail "Verbose".
I have recorded for about just 3 minutes. Still, the trace size got up to more than 1,1GB
About my clean install, I cannot guarantee that they're the exact same build, but what I could do, is manually checking for updates in both OS-es. That could bring them to be more-less system-wise pretty similiar, so IDK if that would do it, you tell me.
Besides I don't have blocked Windows Update or Automatic driver updates on either of the installs and the clean-ish one seems doing much better, regarding both sound and SDR.
-
-
New #15
Yay! It got down to 113 MB. I thought it would be already compressed. I PM link to you, no need to give my trace to the whole internet :)
Edit: Well that won't work, you have inbox stuffed to the roof.
Okay, got you link: https://bit.ly/35jzCJ4 Expires tomorrow
-
New #16
It would certainly help to know if a clean installation of the same build does not have any sound issues.
Win key + r, winver => build no. e.g.
-
-
New #18
I was only playing music through Spotify so cracks in audio only. Regarding video I've never had issues with video glitches as in short term extreme image deformities, just gradual audio/video desync. Crackles in audio happen though still while watching video, exactly just like with music only.
Btw it's nighttime here, so I may become suddenly unresponsive.
-
-
New #19
After looking at your trace, I think your problem is caused by the Intel DPTF (Intel Dynamic Platform & Thermal Framework) driver. I think you have a HP utility that rely on this driver to monitor processor temperature.
The DPC graph shows high number of DPCs generated by the ACPI.sys module, it's the library that contains functions called by other drivers to access the firmware and Bios.
On just one time range, the DPCs triggered by the ACPI module spent 16ms in the CPU. which it's an eternity in CPU time.
The question is who is calling the ACPI module's functions?
The answere can be found in the CPU graph. It's the esif_if.sys driver (the Intel DPTF driver).
The version you have is outdated (2017).
Go on the HP drivers web page, and look if there is a newer version for your computer model and update it.
Let us know if this helped.
-
New #20
Oh wow! I really am impressed, you really did an investigation, didn't you!
I actually have NOT expected to have outdated any Intel related driver/application, as I have "Intel Driver & Support Assistant" installed, which yells at me regularly about new versions availible. Usually just about integrated graphic and intel WiFi/BT drivers though.
So I found these options on HP support site:
And I downloaded and installed the one with the checkmark on the right side. Guess that's a bit newer version, so we will see how it goes, if it will be better or not.
Quote
Related Discussions
