Sound crackling / pops / Clicks while playing games and listening to music

[AC_1337]

i guess you mean this

 

[cwsink]

I'm not sure why the Intel Driver and Support Assistant didn't detect it (wouldn't be the first time it let me down) but I think there's a newer driver for your Ethernet adapter here. Please try installing the appropriate x64 version. If there's an Intel PROSet item in your Apps & Features list I'd use that version. Otherwise, I'd use the non PROset installer. Then restart and see if that helps. I'm hoping it will cause a reduction in the number of ndis.sys ISRs and DSRs running on core 0.

 

[AC_1337]

DESKTOP-SFOOQSD.06-12-2022.12-46-04.zip

okay so i really hoped this would fix it but nope i uninstalled my drivers and reinstalled the new ones (see pic)
i installed the PROset Adapter configuration Utility since i couldnt uncheck it.
i have done another trace with the new drivers.
i also ran the tests on the PROset App and i got a really weird error when running the cable test:
running the cable test said that the device said this:
another test directly after said no problems as you can see (i translated it for you)
i changed the cable and got the same results (the cable that works fine on the other setup / acually both cables work fine on the other setup)

Kabeltestergebnisse [12.06.2022 12:47:00] :
Status der Kabellänge : Fehlgeschlagen (Status of cable length: ERROR test unsuccessful)
This device does not have link. Make sure the cable is connected and the speed and duplex settings are configured correctly on the device and link partner.
Status der Kabelpolarität : Fehlgeschlagen (Status of cable polarity ERROR test unsuccessful)
This device does not have link. Make sure the cable is connected and the speed and duplex settings are configured correctly on the device and link partner.
Lokaler Empfängerstatus : Fehlgeschlagen (Local receiver status ERROR test unsuccessful)
This device does not have link. Make sure the cable is connected and the speed and duplex settings are configured correctly on the device and link partner.
Fernempfängerstatus : Fehlgeschlagen (receiver status ERROR test unsuccessful)
This device does not have link. Make sure the cable is connected and the speed and duplex settings are configured correctly on the device and link partner.
Status der Kabelqualität : Keine Fehler festgestellt (no ERROR detected)
Die Kabelqualität ist hervorragend.
Status der Kabelintegrität : Keine Fehler festgestellt (no ERROR detected)
Es wurden keine Kabelprobleme erkannt.
_________________________________________
Kabeltestergebnisse [12.06.2022 12:47:26] :
Status der Kabellänge : Keine Fehler festgestellt (no ERROR detected)
Cable length: 0 meters.
Status der Kabelpolarität : Keine Fehler festgestellt (no ERROR detected)
Cable polarity is normal.
Lokaler Empfängerstatus : Keine Fehler festgestellt (no ERROR detected)
Keine Fehler festgestellt
Fernempfängerstatus : Keine Fehler festgestellt (no ERROR detected)
Keine Fehler festgestellt
Status der Kabelqualität : Keine Fehler festgestellt (no ERROR detected)
Die Kabelqualität ist hervorragend.
Status der Kabelintegrität : Keine Fehler festgestellt (no ERROR detected)
Es wurden keine Kabelprobleme erkannt.

 

[cwsink]

Just to show what I'm looking at during analysis.

Attached is a screenshot of what I believe are the relevant graphs in MXA. The top graph shows ISR/DPC storms and the green lines show points in time where a group of ISRs and DPCs ran long enough to cause audible interruptions in the audio output stream - a green vertical line going above the red horizontal line and into the red area at the top.

The middle graph is the Windows scheduler and I've filtered it to show only activity on core 0 which is the core running the audio output stream.

The bottom graph is the callstack graph which I believe are samples of the callstack of the thread running on a core taken at regular intervals. It's not precise but the samples are taken frequently enough to where it can catch a relevant callstack. There's some luck involved, though.

If I zoom in on one of the green spikes in the top graph (2nd attached picture) the pink box in the middle graph shows an ndis.sys DPC running for almost 3 milliseconds which is far longer than any other ISR/DPC for that 10 millisecond period. The third picture is the same screenshot with all ISR/DPCs showing.

Focusing on the ndis DPC, I look through the callstacks on core 0 in the bottom graph shortly before and during the time that DPC is running. The spike I focused on in the screenshots is an example where the sampling didn't catch the call, unfortunately.

Zooming in on other spikes in the ISR/DPC storm graph, though, I do see some callstacks using ndis.sys which are leaving me confused. For example:

0 / 1
Callstack at time 3898770500 - Not matched - Forzahorizon5 <ForzaHorizon5.exe> (PID-5808) - Thread-1168 (ForzaHorizon5.exe!0x7FF7E4302AC0) - Unit:# 7676
ntoskrnl.exe!KiExitDispatcher
ntoskrnl.exe!KeSetEvent
afd.sys!AfdReceiveDatagramEventCommonHandler
afd.sys!AfdTLDgramReceiveEventHandler
tcpip.sys!UdpDeliverDatagrams
tcpip.sys!UdpReceiveDatagrams
tcpip.sys!UdpNlClientReceiveDatagrams
tcpip.sys!IpFlcReceivePreValidatedPackets
tcpip.sys!FlReceiveNetBufferListChainCalloutRoutine
ntoskrnl.exe!KeExpandKernelStackAndCalloutInternal
ntoskrnl.exe!KeExpandKernelStackAndCalloutEx
tcpip.sys!NetioExpandKernelStackAndCallout
tcpip.sys!FlReceiveNetBufferListChain
ndis.sys!ndisMIndicateNetBufferListsToOpen
ndis.sys!ndisMTopReceiveNetBufferLists
ndis.sys!ndisCallReceiveHandler
ndis.sys!ndisInvokeNextReceiveHandler
ndis.sys!NdisMIndicateReceiveNetBufferLists
e1d.sys!0xFFFFF802A48F9BAB
e1d.sys!0xFFFFF802A48FAEB0
e1d.sys!0xFFFFF802A4900EE0
e1d.sys!0xFFFFF802A4903272
e1d.sys!0xFFFFF802A49026C2
ndis.sys!ndisMiniportDpc
ndis.sys!ndisQueuedMiniportDpcWorkItem
ndis.sys!ndisPeriodicReceivesTimer
ntoskrnl.exe!KiExecuteAllDpcs
ntoskrnl.exe!KiRetireDpcList
ntoskrnl.exe!KxRetireDpcList
ntoskrnl.exe!KiDispatchInterruptContinue
ntoskrnl.exe!KiDpcInterruptBypass
ntoskrnl.exe!KiInterruptDispatchNoLockNoEtw

That it's a Forzahorizon5.exe thread is irrelevant. The thread was taken over by the scheduler and it could have picked any thread. The relevant part (I think) is the callstack shows a driver with the filename e1d.sys which is making use of ndis.sys. But searches don't seem to show what I would consider reliable information about that driver. Can you do a search for that driver on your C: drive and see if you can identify what might have installed it? I can't find that driver anywhere on the two systems I have.

edit: Actually, I just noticed e1d.sys shows up as a miniport driver for the Ethernet adapter in your latest screenshot so I'm guessing it's a legitimate driver from Intel.

 

[cwsink]

Pondering what has changed during your move and problems I've seen crop up after moving a computer to another location, I can think of two things. Your internet connection and the possibility that things came a bit loose inside the computer during transportation. If you haven't already done so, I'd recommend opening up the computer and reseating its components. Memory, power and data cables, GPU, etc. Vibrations during a move seem to cause connections to become somewhat iffy sometimes. I've also seen CPU coolers come loose so I'd make sure the cooler is firmly attached to the CPU by trying to jiggle it a little.

As far as the Internet/network, were there any problems while setting it up at the new location? In the US, it's possible to accidently insert a phone jack cable into an Ethernet port and damage the port, for example. I'm not sure if that's possible in your country. Or did you need to uninstall/reinstall network drivers to get things to work? Does the new ISP require the installation of software to use their network?

 

[AC_1337]

so for the ISP questions its the same provider and also the same rate (i dont know if thats the correct word)
i have used this PC for 10 LAN Parties in the last few years i acually built it extra solid so nothing can come loose but i will check everything again.
what exactly should i look for when searching ndis on my system ? i can find the driver in multiable folders also in System32

 

[cwsink]

I'm actually interested in e1d.sys. Is it an Intel driver? Can you submit it to Virustotal to see what is says about the file?

The ndis.sys driver is a Microsoft driver and not likely to be the actual problem. Instead, it's likely something using ndis.sys as part of what it does. The problem is, just about everything uses ndis.

 

[AC_1337]

seems like a legit driver

 

[AC_1337]

VirusTotal

 

[cwsink]

Have you already tried a network reset? (Network & Internet -> Status -> Network reset -> Reset now)

 

[cwsink]

The other driver that sometimes has similarly long running DPCs is dxgkrnl.sys - another Microsoft driver. They are so close in length it makes me wonder if one is causing the other. Have you tried rolling back to a previous version of the Nvidia drivers?

 

[AC_1337]

Have you already tried a network reset? (Network & Internet -> Status -> Network reset -> Reset now)

i have tried this now but no change

The other driver that sometimes has similarly long running DPCs is dxgkrnl.sys - another Microsoft driver. They are so close in length it makes me wonder if one is causing the other. Have you tried rolling back to a previous version of the Nvidia drivers?

i have no idea what version i should use tbh

 

[cwsink]

If you have a sense of when the problems started I'd suggest downloading and installing a driver from around the same time or earlier. Do you normally use Geforce Experience to update the Nvidia drivers? The manual download page shows the date the drivers were released.

 

[cwsink]

In your original post on 4 June you wrote:

I am trying to fix a audio problem on my PC for the last few weeks.

The Drivers(1).txt file you linked shows your system using the 512.95 drivers released on 24 May. Assuming the system never had the problem before the 512.95 drivers were installed then I'd suggest installing version 512.77. However, if you don't regularly update your graphics drivers, you might need to go to an even older version.

 

[AC_1337]

hey i was on vacation for the last few days :)
i downloaded a driver from 1 year ago where i could not remember having this issue but i still get crackling

 

[AC_1337]

i also checked if everything is plugged in -> RAM CPU GPU CPU Cooler everything seems good no woobles everything sits good

 

[cwsink]

In your original post you wrote the audio glitches will happen after some amount of time playing a game even if nothing else is running. Can you get a 30 second trace of such a game not having the problem and then another 30 second trace after the audio glitches start with some examples of those glitches in the second trace?

 

[AC_1337]

I have to correct myself i hear them from the beginning on now (i guess because im listening for the crackles more) but it gets worse over time. like some kind of memory leak

 

[cwsink]

Can you get a 30 second trace with examples of glitches and no other processes running other than the game?

edit: For example, I see Chrome, Discord, and FH5 running. Can you get a trace with glitches just running FH5?

 

[AC_1337]

ill do that now