[SOLVED] High Definition Audio Controller causing BSOD, extreme latency with nvlddmkm.sys and hdaudbus.sys which is causing freezes/lag.

[Simon Slays]

Hi guys,

I'm in desperate need of help with my newly built PC as I have spent over a week trying to solve the issue but I'm getting nowhere which is why I need your expertise. Firstly, I built my computer and I know how to build one as I had one previously that worked great. After building it I went and installed the latest BIOS along with a fresh install of Windows 11 using the media creation tool and put in my old Windows activation key from my previous motherboard as I was able to retrieve it from the command prompt. I then installed the latest graphics drivers after using DDU to clean any remnants of previous drivers that were added when Windows got installed along with the latest chipset drivers for AMD. I then began to install all of my favourite games and software such as Afterburner and everything seemed fine. Then I decided to go back to the BIOS and enable EXPO I, which is when all of my issues started. Every time I saved a setting in the BIOS it would cause my PC to boot terribly slow along with freezes and sometimes a black screen. If it would make it to Windows it would sometimes BSOD or it would only just about run but would constantly freeze or lag. I know it's not an issue with EXPO I being activated because when I restart the PC I have no freezing issues whatsoever and the computer is stable with minimal latency in latencymon. The issue only seems to start whenever I change something in the BIOS and try to boot back into Windows. It doesn't seem to matter what I change in the BIOS as I have changed things that wouldn't affect system stability such as disabling the monitoring of my CPU fan or disabling the iGPU. The strange thing is, once I restart the PC after getting or not getting into Windows, I can use the PC without any latency or latency that is nowhere near as bad as shown in Latencymon. On some of the freezes in Windows I would also receive what appears to be artifacts but I'm not 100% sure (see images below).

I then started to troubleshoot by disabling USB Root Hubs in device manager which made no difference. I then thought that perhaps I had screwed the AIO pump onto the CPU too tightly as I have heard that can cause all sorts of BSOD issues so I removed it, added thermal paste and remounted without making it too tight; this made no difference either. Then I ran a Memtest86 twice on the DRAM as I thought that was the reason behind the freezes, it wasn't as it passed all tests on both runs (see image below). I then decided to start removing pieces of hardware such as the graphics card. This seemed to fix it as the PC would boot normally and I could change BIOS settings to my hearts content without there being any freezing issues or latency in Windows. I then thought to myself that the PCI-E slot is perhaps faulty, the GPU itself, the GPU drivers are conflicting or there's a power delivery issue with the Cablemod 90 degree adapter. I then put the GPU back in and reinstalled one of the older drivers to see if it fixed the issue, it didn't. I then removed the 90 degree adapter and tried with just the 12VHPWR from the PSU and it too made no difference. I then decided to flash the GPU BIOS to see if it was bugged and see if that would fix the issue, it didn't.

After a full week of scouring the internet in search of an issue similar to mine, I finally came across one and decided to try and copy what they did to resolve the issue. I began disabling almost everything I could in device manager that coincided with the drivers that were showing the highest DPC latency and ISR's which was Nvlddmkm.sys and HDAudBus.sys which happened to be sound drivers and graphics drivers. I finally landed on High Definition Audio Controller under System Devices and decided to disable it. Lo and behold, it was this the entire time that was causing the extremely high latency up in the hundreds. The problem I am facing now is that when this is disabled, my Nvidia High Definition Audio also gets disabled and I am no longer able to use my monitors sound. I have tried uninstalling all of the Realtek drivers but they always seem to come back after a reboot. I feel like there's either a hardware issue with the GPU or the Motherboard. If not a hardware issue then there's a conflict between the audio drivers of my GPU and the Motherboard but I'm not sure how to go about fixing it.

Like I said previously, I can use the PC normally after a restart as long as I don’t change anything in the BIOS. So due to this I have been able to game on the system and everything seemed fine when I play Jedi Survivor which makes me believe that the GPU is fine unless there’s a problem with it’s audio controller. I could just restart the PC every time I want to use it or never enter the BIOS after setting it up but that’s not really a true fix. Or I could just disable the High Definition Audio Controller forever but then I’m left without audio.

I have created a Google Drive with all of my Minidumps in so that you can take a look, I have looked at them myself and it's pointing to hardware failure but I'm not a pro at reading the code. I get the error DPC_Watchdog_Violation in all of them which I know can also be due to a misbehaving driver: Minidump - Google Drive

I have made a YouTube video so that you can see exactly what happens when I save something in the BIOS and boot up the PC. I had to constantly retake the video as the PC would sometimes just black screen after leaving the BIOS but I got lucky and managed to get into Windows. Please take a look at the video, It's around 9 minutes long. I tried to restart the PC in the video to show that it works fine after restart but as you will see in the video, the PC just froze on restarting. After the video ended I got another BSOD (see image below).

YouTube Video:
View: https://youtu.be/oTpZS4GizL8


Artifacts when the freezes happen:
View: https://imgur.com/a/JDbbFWK
View: https://imgur.com/a/byZ3axY

Memtest86 pass:
View: https://imgur.com/a/ozZ5qjn

BSOD after YT video:
View: https://imgur.com/a/JCkpn5P

Latency after BIOS change and no PC restart:
View: https://imgur.com/a/puz0non
View: https://imgur.com/a/gP9JFtG

Latency after PC restart:
View: https://imgur.com/a/TGlZMYA

Latency with High Definition Audio Controller disabled:
View: https://imgur.com/a/s5EsqoA
View: https://imgur.com/a/srSBNZ5

Event Viewer errors:
View: https://imgur.com/a/p99XnoY
View: https://imgur.com/a/g0GEDtw

Reliability monitor:
View: https://imgur.com/a/UkV4fgx


Things I have tried thus far:

1. Reinstalling Windows after wiping all drives
2. Reinstalling latest BIOS or going back to an older BIOS version either by installing it in the BIOS or using BIOS flashback with PC turned off
3. Reinstalling Windows on my old NVME to see if my new one is faulty
4. Updating to latest Nvidia drivers and also an older one after using DDU in safe mode
5. Removing GPU and using CPU's onboard graphics (stopped the issue until I put GPU back in)
6. Reset the CMOS with the dedicated button on the Motherboard as well as removing the CMOS battery
7. Reinstalled AIO to see if pump was too tight potentially causing freezes
8. Ran Memtest86 on DRAM
9. Removed Cablemod 90 degree adapter
10. Disabled all root hubs
11. Updated all drivers I could think of
12. Followed many guides on the internet about using basic commands in command prompt such as sfc /scannow, dism, etc.
13. Disabled automatic driver installs in Advanced System Settings
14. Begged the PC to work

PC Specs:
Motherboard: ASUS ROG Crosshair X670E Hero
CPU: AMD Ryzen 7 7800X3D
GPU: ASUS ROG Strix RTX 4090 OC
DRAM: Corsair Dominator Platinum 6000Mhz CL30 32GB (2x16)
NVME: Samsung 990 Pro 2TB
NVME: Intel 760p 2TB
HDD: Seagate Barracuda Sata III 4TB
PSU: ASUS ROG Strix 1000W Aura Edition
Cooler: NZXT Kraken Elite

I am honestly at my wits end and would really appreciate any help to try and solve what is causing my PC to be unusable with High Definition Audio Controller enabled. Please let me know if you think it's a possible hardware issue as I will just return the parts under warranty. Have a good day/night and thanks for reading.

 

[xilolee]

Hi!

This seems more a question for your motherboard and ram manufacturers.
I.e., the question could be something like:

I enabled "EXPO I".
Why is the system not stable when I change some other unrelated settings in the bios?

Did you try "EXPO II"?
What frequency do they reach? The max should be 5200, according to your CPU specs.

 

[Simon Slays]

Hi!

This seems more a question for your motherboard and ram manufacturers.
I.e., the question could be something like:

Did you try "EXPO II"?
What frequency do they reach? The max should be 5200, according to your CPU specs.

Hi sorry for the late response, the issue still persists even if I have EXPO II or no EXPO enabled. The DRAM reaches 6000Mhz when either EXPO I or EXPO II is enabled.

The thing I don’t understand is why my PC works fine if I disable the High Definition Audio Controllers in device manager. With these two controllers disabled I am able to change anything in the BIOS without any latency issues or BSOD’s.

 

[ubuysa]

All four dumps have the same bugcheck; DPC_WATCHDOG_VIOLATION. DPCs are Deferred Procedure Calls, they form the back-end of device interrupt processing and are executed from a DPC queue when a processor has no other work to do. The DPC code forms part of the device driver (as does the Interrupt Service Routine (ISR) that is called when the device raises an interrupt). There are time limits on how long a single DPC can run for and on how long the whole DPC queue takes to run. This is because the processor running DPCs isn't available for other work.

Two of your dumps indicate that the total time for all DPCs was exceeded and two indicate that a single DPC ran for too long. The former (all DPCs) can only be debugged with a kernel dump, minidumps don't contain enough detail, however, it's very likely that the DPC that ran for too long was also the cause of the collective DPCs exceeding the timeout as well.

The stack trace of one of these single DPC timeouts shows the likely cause...

1: kd> knL
 # Child-SP          RetAddr               Call Site
00 ffffa700`40dc6c68 fffff804`19abbbf9     nt!KeBugCheckEx
01 ffffa700`40dc6c70 fffff804`19aba744     nt!KeAccumulateTicks+0x539
02 ffffa700`40dc6cd0 fffff804`19ab8bd3     nt!KiUpdateRunTime+0xf4
03 ffffa700`40dc6e90 fffff804`19ab805a     nt!KeClockInterruptNotify+0x763
04 ffffa700`40dc6f40 fffff804`19b4b3be     nt!HalpTimerClockInterrupt+0x10a
05 ffffa700`40dc6f70 fffff804`19c2da4a     nt!KiCallInterruptServiceRoutine+0x19e
06 ffffa700`40dc6fb0 fffff804`19c2e2b7     nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
07 ffffa503`4203deb0 fffff804`158c12ac     nt!KiInterruptDispatchNoLockNoEtw+0x37
08 ffffa503`4203e040 fffff804`1c32c218     WppRecorder!WppAutoLogTrace+0x17c
09 ffffa503`4203e0a0 fffff804`1c38919e     ndis!WPP_RECORDER_SF_qL+0xb8
0a ffffa503`4203e100 fffff804`619f94ad     ndis!NdisWriteErrorLogEntry+0x21e
0b ffffa503`4203e1b0 fffff804`619c7610     Netwtw10!utilDbgAssertRelease+0x1cd
0c ffffa503`4203e220 fffff804`619dc7cb     Netwtw10!tidQueueOsPacketProcessDone+0x240
0d ffffa503`4203e2b0 fffff804`619989e9     Netwtw10!preTxProcessTidQueue+0x89b
0e ffffa503`4203e510 fffff804`61a502ce     Netwtw10!dpTxFlowMapSglAndSendPacketApi+0xee9
0f ffffa503`4203e650 fffff804`61984648     Netwtw10!oscMiniportSendNetBufferList+0x29e
10 ffffa503`4203e6e0 fffff804`61f156e4     Netwtw10!oscWdiTxEngineDataSend+0x2d8
11 ffffa503`4203e760 fffff804`61f14f34     wdiwifi!CTxMgr::ServiceQueues+0x1e4
12 ffffa503`4203e7e0 fffff804`61f14ceb     wdiwifi!CPort::SendNetBufferLists+0xa4
13 ffffa503`4203e870 fffff804`1c323c0c     wdiwifi!MPWrapperSendNetBufferLists+0x18b
14 ffffa503`4203e8d0 fffff804`1c323aee     ndis!ndisMSendNBLToMiniportInternal+0x10c
15 ffffa503`4203e9a0 fffff804`1c35645f     ndis!ndisMSendNBLToMiniport+0xe
16 ffffa503`4203e9e0 fffff804`1c3561a9     ndis!ndisIterativeDPInvokeHandlerOnTracker<0,void __cdecl(void * __ptr64,_NET_BUFFER_LIST * __ptr64,unsigned long,unsigned long)>+0xcb
17 ffffa503`4203ea40 fffff804`1c35a8d1     ndis!ndisInvokeIterativeDatapath<0,void __cdecl(void * __ptr64,_NET_BUFFER_LIST * __ptr64,unsigned long,unsigned long)>+0xd9
18 ffffa503`4203eab0 fffff804`1c323644     ndis!ndisInvokeNextSendHandler+0x15b21
19 ffffa503`4203eb00 fffff804`1c5e17e3     ndis!NdisSendNetBufferLists+0x184
1a ffffa503`4203ebf0 fffff804`1c5e12e0     tcpip!FlpSendPacketsHelper+0x2d3
1b ffffa503`4203eca0 fffff804`1c5e07b6     tcpip!IppFragmentPackets+0x2f0
1c ffffa503`4203ed80 fffff804`1c5dfff6     tcpip!IppDispatchSendPacketHelper+0xc6
1d ffffa503`4203eed0 fffff804`1c5de561     tcpip!IppPacketizeDatagrams+0x326
1e ffffa503`4203f040 fffff804`1c5c38d4     tcpip!IppSendDatagramsCommon+0x481
1f ffffa503`4203f200 fffff804`1c5db3fa     tcpip!IpNlpFastSendDatagram+0x364
20 ffffa503`4203f2c0 fffff804`1c5d972f     tcpip!TcpTcbHeaderSend+0x62a
21 ffffa503`4203f5c0 fffff804`19a2a1da     tcpip!TcpPeriodicTimeoutHandler+0xf3f
22 ffffa503`4203f7d0 fffff804`19a299e4     nt!KiExecuteAllDpcs+0x54a
23 ffffa503`4203fd20 fffff804`19c34d65     nt!KiRetireDpcList+0xfe4
24 ffffa503`4203ffb0 fffff804`19c34d0f     nt!KxSwapStacksAndRetireDpcList+0x5
25 ffffa503`4506f330 fffff804`19a2c0c9     nt!KiPlatformSwapStacksAndCallReturn
26 ffffa503`4506f340 fffff804`19c344db     nt!KiDispatchInterrupt+0xd9
27 ffffa503`4506f430 fffff804`19c2db11     nt!KiDpcInterruptBypass+0x1b
28 ffffa503`4506f460 00007ffd`30e40356     nt!KiInterruptDispatc

These are push-down stacks so you read them from the bottom up. You can see that a networking operation was in progress using the wireless adapter. We see calls to the Microsoft ndis.sys, tcpip.sys, and wdiwifi.sys drivers, but we also see several calls to the third-party wireless adapter driver Netwtw10.sys. Immediately following these calls is a call to the ndis!NdisWriteErrorLogEntry+0x21e function, so there was clearly some error generated by these Netwtw10.sys calls and that error is what led to the timeout and BSOD. Note that the other single DPC dump is identical.

The version of Netwtw10.sys that you're running is old, dating from January 2021...

1: kd> lmDvmnetwtw10
Browse full module list
start             end                 module name
fffff804`61940000 fffff804`61f0b000   Netwtw10   (pdb symbols)          c:\mysymbols\Netwtw10.pdb\42EF26F0E11E4BF7A755A09F951ADBDF1\Netwtw10.pdb
    Loaded symbol image file: Netwtw10.sys
    Mapped memory image file: c:\mysymbols\Netwtw10.sys\600420155cb000\Netwtw10.sys
    Image path: \SystemRoot\System32\drivers\Netwtw10.sys
    Image name: Netwtw10.sys
    Browse all global symbols  functions  data
    Timestamp:        Sun Jan 17 13:31:33 2021 (60042015)
    CheckSum:         00544275
    ImageSize:        005CB000
    File version:     22.0.1.5
    Product version:  1.0.1.0
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.6 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    Information from resource tables:
        CompanyName:      Intel Corporation
        ProductName:      Intel® Wireless WiFi Link Adapter
        InternalName:     .sys
        OriginalFilename: .sys
        FileVersion:      22.0.1.5
        FileDescription:  Intel® Wireless WiFi Link Driver
        LegalCopyright:   Copyright © Intel Corporation 2011
        Comments:         NDIS650_MINIPORT

As you can see from the above Netwtw10.sys is the Intel wireless adapter driver, and this is the most likely cause of all four BSODs.

I would suggest you download and run the Intel Driver & Support Assistant and use that to look for driver updates for your Intel devices (including the wireless adapter).

BTW. Regarding the audio driver, if you have installed the Nvidia audio driver (when you installed the latest version of the Nvidia graphics driver) this may be contributing to your audio driver issues. I have seen the Nvidia audio drivers cause issues for others. If you don't actually need the Nvidia audio driver I suggest you not install it. IMO the best way to resolve that is to uninstall the graphics driver using DDU and then reinstall it again, taking care to uncheck the box for the audio driver.

 

[Simon Slays]

All four dumps have the same bugcheck; DPC_WATCHDOG_VIOLATION. DPCs are Deferred Procedure Calls, they form the back-end of device interrupt processing and are executed from a DPC queue when a processor has no other work to do. The DPC code forms part of the device driver (as does the Interrupt Service Routine (ISR) that is called when the device raises an interrupt). There are time limits on how long a single DPC can run for and on how long the whole DPC queue takes to run. This is because the processor running DPCs isn't available for other work.

Two of your dumps indicate that the total time for all DPCs was exceeded and two indicate that a single DPC ran for too long. The former (all DPCs) can only be debugged with a kernel dump, minidumps don't contain enough detail, however, it's very likely that the DPC that ran for too long was also the cause of the collective DPCs exceeding the timeout as well.

The stack trace of one of these single DPC timeouts shows the likely cause...

1: kd> knL
 # Child-SP          RetAddr               Call Site
00 ffffa700`40dc6c68 fffff804`19abbbf9     nt!KeBugCheckEx
01 ffffa700`40dc6c70 fffff804`19aba744     nt!KeAccumulateTicks+0x539
02 ffffa700`40dc6cd0 fffff804`19ab8bd3     nt!KiUpdateRunTime+0xf4
03 ffffa700`40dc6e90 fffff804`19ab805a     nt!KeClockInterruptNotify+0x763
04 ffffa700`40dc6f40 fffff804`19b4b3be     nt!HalpTimerClockInterrupt+0x10a
05 ffffa700`40dc6f70 fffff804`19c2da4a     nt!KiCallInterruptServiceRoutine+0x19e
06 ffffa700`40dc6fb0 fffff804`19c2e2b7     nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
07 ffffa503`4203deb0 fffff804`158c12ac     nt!KiInterruptDispatchNoLockNoEtw+0x37
08 ffffa503`4203e040 fffff804`1c32c218     WppRecorder!WppAutoLogTrace+0x17c
09 ffffa503`4203e0a0 fffff804`1c38919e     ndis!WPP_RECORDER_SF_qL+0xb8
0a ffffa503`4203e100 fffff804`619f94ad     ndis!NdisWriteErrorLogEntry+0x21e
0b ffffa503`4203e1b0 fffff804`619c7610     Netwtw10!utilDbgAssertRelease+0x1cd
0c ffffa503`4203e220 fffff804`619dc7cb     Netwtw10!tidQueueOsPacketProcessDone+0x240
0d ffffa503`4203e2b0 fffff804`619989e9     Netwtw10!preTxProcessTidQueue+0x89b
0e ffffa503`4203e510 fffff804`61a502ce     Netwtw10!dpTxFlowMapSglAndSendPacketApi+0xee9
0f ffffa503`4203e650 fffff804`61984648     Netwtw10!oscMiniportSendNetBufferList+0x29e
10 ffffa503`4203e6e0 fffff804`61f156e4     Netwtw10!oscWdiTxEngineDataSend+0x2d8
11 ffffa503`4203e760 fffff804`61f14f34     wdiwifi!CTxMgr::ServiceQueues+0x1e4
12 ffffa503`4203e7e0 fffff804`61f14ceb     wdiwifi!CPort::SendNetBufferLists+0xa4
13 ffffa503`4203e870 fffff804`1c323c0c     wdiwifi!MPWrapperSendNetBufferLists+0x18b
14 ffffa503`4203e8d0 fffff804`1c323aee     ndis!ndisMSendNBLToMiniportInternal+0x10c
15 ffffa503`4203e9a0 fffff804`1c35645f     ndis!ndisMSendNBLToMiniport+0xe
16 ffffa503`4203e9e0 fffff804`1c3561a9     ndis!ndisIterativeDPInvokeHandlerOnTracker<0,void __cdecl(void * __ptr64,_NET_BUFFER_LIST * __ptr64,unsigned long,unsigned long)>+0xcb
17 ffffa503`4203ea40 fffff804`1c35a8d1     ndis!ndisInvokeIterativeDatapath<0,void __cdecl(void * __ptr64,_NET_BUFFER_LIST * __ptr64,unsigned long,unsigned long)>+0xd9
18 ffffa503`4203eab0 fffff804`1c323644     ndis!ndisInvokeNextSendHandler+0x15b21
19 ffffa503`4203eb00 fffff804`1c5e17e3     ndis!NdisSendNetBufferLists+0x184
1a ffffa503`4203ebf0 fffff804`1c5e12e0     tcpip!FlpSendPacketsHelper+0x2d3
1b ffffa503`4203eca0 fffff804`1c5e07b6     tcpip!IppFragmentPackets+0x2f0
1c ffffa503`4203ed80 fffff804`1c5dfff6     tcpip!IppDispatchSendPacketHelper+0xc6
1d ffffa503`4203eed0 fffff804`1c5de561     tcpip!IppPacketizeDatagrams+0x326
1e ffffa503`4203f040 fffff804`1c5c38d4     tcpip!IppSendDatagramsCommon+0x481
1f ffffa503`4203f200 fffff804`1c5db3fa     tcpip!IpNlpFastSendDatagram+0x364
20 ffffa503`4203f2c0 fffff804`1c5d972f     tcpip!TcpTcbHeaderSend+0x62a
21 ffffa503`4203f5c0 fffff804`19a2a1da     tcpip!TcpPeriodicTimeoutHandler+0xf3f
22 ffffa503`4203f7d0 fffff804`19a299e4     nt!KiExecuteAllDpcs+0x54a
23 ffffa503`4203fd20 fffff804`19c34d65     nt!KiRetireDpcList+0xfe4
24 ffffa503`4203ffb0 fffff804`19c34d0f     nt!KxSwapStacksAndRetireDpcList+0x5
25 ffffa503`4506f330 fffff804`19a2c0c9     nt!KiPlatformSwapStacksAndCallReturn
26 ffffa503`4506f340 fffff804`19c344db     nt!KiDispatchInterrupt+0xd9
27 ffffa503`4506f430 fffff804`19c2db11     nt!KiDpcInterruptBypass+0x1b
28 ffffa503`4506f460 00007ffd`30e40356     nt!KiInterruptDispatc

These are push-down stacks so you read them from the bottom up. You can see that a networking operation was in progress using the wireless adapter. We see calls to the Microsoft ndis.sys, tcpip.sys, and wdiwifi.sys drivers, but we also see several calls to the third-party wireless adapter driver Netwtw10.sys. Immediately following these calls is a call to the ndis!NdisWriteErrorLogEntry+0x21e function, so there was clearly some error generated by these Netwtw10.sys calls and that error is what led to the timeout and BSOD. Note that the other single DPC dump is identical.

The version of Netwtw10.sys that you're running is old, dating from January 2021...

1: kd> lmDvmnetwtw10
Browse full module list
start             end                 module name
fffff804`61940000 fffff804`61f0b000   Netwtw10   (pdb symbols)          c:\mysymbols\Netwtw10.pdb\42EF26F0E11E4BF7A755A09F951ADBDF1\Netwtw10.pdb
    Loaded symbol image file: Netwtw10.sys
    Mapped memory image file: c:\mysymbols\Netwtw10.sys\600420155cb000\Netwtw10.sys
    Image path: \SystemRoot\System32\drivers\Netwtw10.sys
    Image name: Netwtw10.sys
    Browse all global symbols  functions  data
    Timestamp:        Sun Jan 17 13:31:33 2021 (60042015)
    CheckSum:         00544275
    ImageSize:        005CB000
    File version:     22.0.1.5
    Product version:  1.0.1.0
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.6 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    Information from resource tables:
        CompanyName:      Intel Corporation
        ProductName:      Intel® Wireless WiFi Link Adapter
        InternalName:     .sys
        OriginalFilename: .sys
        FileVersion:      22.0.1.5
        FileDescription:  Intel® Wireless WiFi Link Driver
        LegalCopyright:   Copyright © Intel Corporation 2011
        Comments:         NDIS650_MINIPORT

As you can see from the above Netwtw10.sys is the Intel wireless adapter driver, and this is the most likely cause of all four BSODs.

I would suggest you download and run the Intel Driver & Support Assistant and use that to look for driver updates for your Intel devices (including the wireless adapter).

BTW. Regarding the audio driver, if you have installed the Nvidia audio driver (when you installed the latest version of the Nvidia graphics driver) this may be contributing to your audio driver issues. I have seen the Nvidia audio drivers cause issues for others. If you don't actually need the Nvidia audio driver I suggest you not install it. IMO the best way to resolve that is to uninstall the graphics driver using DDU and then reinstall it again, taking care to uncheck the box for the audio driver.

Hello, I really appreciate the detailed response. I had already installed the latest drivers using the Intel driver & support assistant as I thought the drivers on my motherboard manufacturers page wasn’t working. Perhaps it’s not properly installing the drivers as I did notice that in the events tab it says “Device not started” and in the information page it says “Device PCI\VEN_8086&DEV_2752&SUBSYS_00248086&REV_1A\&&2b067c3e&0&000000400011 had a problem starting”

I also reinstalled Windows 11 again yesterday and everything was fine until I booted back into the BIOS and turned off my iGPU and then the PC BSOD before it made it into Windows. The system shouldn’t have BSOD if the root cause of the problem was the Wi-Fi adapter as I currently have driver version 22.220.1.1 installed which is dated as 03/04/2023. I have another minidump if that would be helpful at all?

I have gone into Advanced System Settings and changed it so that it creates a full dump and doesn’t auto restart so I will try and force a crash again today to get a full dump.

When I look into device manager it seems that many of my devices such as my Ethernet controller also says that the device had a problem starting. Which doesn’t seem to make much sense as I am currently using it and it seems to be working fine.

 

[x BlueRobot]

I have gone into Advanced System Settings and changed it so that it creates a full dump and doesn’t auto restart so I will try and force a crash again today to get a full dump.

The default settings would have been fine, they produce Minidumps and a single kernel memory dump. A full memory dump is going to be too large to download and isn't required. Could you also please follow these posting instructions: Blue Screen of Death (BSOD) Posting Instructions - Windows 11, 10, 8.1 and 8

I wonder if this is actually a hardware issue?

0a ffffa5034203e100 fffff804619f94ad ndis!NdisWriteErrorLogEntry+21e 
    Parameter[0] = ffff928c2a6131a0
    Parameter[1] = 00000000c0001392
    Parameter[2] = 0000000000000002
    Parameter[3] = 0000000056524457

# for hex 0xc0001392 / decimal -1073736814
EVENT_NDIS_INVALID_VALUE_FROM_ADAPTER netevent.h

That error code then corresponds to the following error message: "The network adapter hardware provided an invalid value."

Source: NdisWriteErrorLogEntry function (ndis.h) - Windows drivers

You should be able to find some NDIS related errors in your System event log if logging has been set up for the network adapter. Unfortunately, I can't get much information from the Minidump alone.

1: kd> !netadapter -handle ffff928c2a6131a0


MINIPORT

    Cannot dereference pointer

    Ndis handle        ffff928c2a6131a0
    Ndis API version   [Unreadable version value]
    Adapter context    ffff928c2aa53060
    Driver             0 - [Unreadable Miniport driver]  [Unreadable version value]
    Network interface  0
    Ndis verifier      [Unreadable value]

    Media type         802.3
    Physical medium    [Unreadable value]
    Device path        String with 152 characters [Buffer at ffffe600ed3d38b0 is not available]
    Device object      Cannot load field 'DeviceObject' in '_NDIS_MINIPORT_BLOCK'  More information
    MAC address        [MAC address at ffff928c331a5f40 is unavailble]

 

[Simon Slays]

Here is the things you requested from the posting instructions, I hope they will help you find what the issue is:

http://speccy.piriform.com/results/ZpTDCcENdW0J3H0YRbHeFfF

When I started Speccy it did come up with an error about not being able to read cpuz. Not sure if that's important or not.

 

[Simon Slays]

The default settings would have been fine, they produce Minidumps and a single kernel memory dump. A full memory dump is going to be too large to download and isn't required. Could you also please follow these posting instructions: Blue Screen of Death (BSOD) Posting Instructions - Windows 11, 10, 8.1 and 8

I wonder if this is actually a hardware issue?

0a ffffa5034203e100 fffff804619f94ad ndis!NdisWriteErrorLogEntry+21e
    Parameter[0] = ffff928c2a6131a0
    Parameter[1] = 00000000c0001392
    Parameter[2] = 0000000000000002
    Parameter[3] = 0000000056524457

That error code then corresponds to the following error message: "The network adapter hardware provided an invalid value."

Source: NdisWriteErrorLogEntry function (ndis.h) - Windows drivers

You should be able to find some NDIS related errors in your System event log if logging has been set up for the network adapter. Unfortunately, I can't get much information from the Minidump alone.

1: kd> !netadapter -handle ffff928c2a6131a0


MINIPORT

    Cannot dereference pointer

    Ndis handle        ffff928c2a6131a0
    Ndis API version   [Unreadable version value]
    Adapter context    ffff928c2aa53060
    Driver             0 - [Unreadable Miniport driver]  [Unreadable version value]
    Network interface  0
    Ndis verifier      [Unreadable value]

    Media type         802.3
    Physical medium    [Unreadable value]
    Device path        String with 152 characters [Buffer at ffffe600ed3d38b0 is not available]
    Device object      Cannot load field 'DeviceObject' in '_NDIS_MINIPORT_BLOCK'  More information
    MAC address        [MAC address at ffff928c331a5f40 is unavailble]

I forgot to quote you on the previous reply so I'm just doing it now. I also found these errors in Event Viewer.

 

[x BlueRobot]

Thanks, please see if you can disable the wireless adapter from your BIOS settings otherwise try and disable the device from device manager. Let's see if the system continues to crash or at least provides a different bugcheck.

 

[Corday]

Wouldn't usually jump in the middle like this, but since on-board graphics worked, that indicated GPU problem which happens to include drivers for High Definition Audio Controller from Asus.

 

[Simon Slays]

Thanks, please see if you can disable the wireless adapter from your BIOS settings otherwise try and disable the device from device manager. Let's see if the system continues to crash or at least provides a different bugcheck.

I just set "Load Optimized Defaults" in BIOS and then disabled the Wi-Fi controller under Onboard Devices Configuration and as soon as I saved and went into Windows, it froze with extremely high latency in Latencymon and a BSOD. I also disabled the Wi-Fi controller in Device Manager prior to this. I would like to send you a Kernel Memory Dump file but it says that it's too big for the server to process. Here is another mini dump and a live kernel report.

 

[Simon Slays]

I'm not sure if this is helpful, but this is what it says in the Memory dump:

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
DISPATCH_LEVEL or above.
Arg2: 0000000000001e00, The watchdog period (in ticks).
Arg3: fffff8035c11c340, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding the cumulative timeout
Arg4: 0000000000000000

Debugging Details:
------------------

Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_47e775611dee294c\nvlddmkm.sys, Win32 error 0n2
Page 1501d2 not present in the dump file. Type ".hh dbgerr004" for details
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: TickPeriods ***
*** ***
*************************************************************************

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1234

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 4925

Key : Analysis.IO.Other.Mb
Value: 0

Key : Analysis.IO.Read.Mb
Value: 0

Key : Analysis.IO.Write.Mb
Value: 0

Key : Analysis.Init.CPU.mSec
Value: 734

Key : Analysis.Init.Elapsed.mSec
Value: 8597

Key : Analysis.Memory.CommitPeak.Mb
Value: 98

Key : Bugcheck.Code.DumpHeader
Value: 0x133

Key : Bugcheck.Code.KiBugCheckData
Value: 0x133

Key : Bugcheck.Code.Register
Value: 0x133

Key : Dump.Attributes.AsUlong
Value: 1800

Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1

Key : Dump.Attributes.ErrorCode
Value: 0

Key : Dump.Attributes.LastLine
Value: Dump completed successfully.

Key : Dump.Attributes.ProgressPercentage
Value: 100

Key : WER.OS.Branch
Value: ni_release

Key : WER.OS.Timestamp
Value: 2022-05-06T12:50:00Z

Key : WER.OS.Version
Value: 10.0.22621.1


FILE_IN_CAB: MEMORY.DMP

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b


DUMP_FILE_ATTRIBUTES: 0x1800

BUGCHECK_CODE: 133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff8035c11c340

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

TRAP_FRAME: ffffab018c3ebc50 -- (.trap 0xffffab018c3ebc50)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffab0190af8000 rbx=0000000000000000 rcx=0000000000000001
rdx=ffffe08f167f2000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff803e08f2b3a rsp=ffffab018c3ebde0 rbp=ffffab018c3ebee0
r8=0000000000000040 r9=0000000000000000 r10=0000fffff803e08f
r11=ffff9afdd0a00000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
HDAudBus!HdaController::Isr+0x9a:
fffff803`e08f2b3a 488b4658 mov rax,qword ptr [rsi+58h] ds:00000000`00000058=????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME: System

STACK_TEXT:
ffffab01`8c3eb918 fffff803`5b69baf1 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff803`5c11c340 : nt!KeBugCheckEx
ffffab01`8c3eb920 fffff803`5b69b36c : 0000027c`d6f65ae6 ffffab01`8c3d1180 00000000`00009824 00000000`00000202 : nt!KeAccumulateTicks+0x231
ffffab01`8c3eb980 fffff803`5b699421 : 00000000`00000000 ffffab01`8d705800 ffffab01`8c3d1180 00000000`00000000 : nt!KiUpdateRunTime+0xcc
ffffab01`8c3ebaf0 fffff803`5b698e39 : fffff803`5c05fe20 ffffab01`8d705830 ffffab01`8d705830 00000000`00000009 : nt!KeClockInterruptNotify+0xc1
ffffab01`8c3ebb90 fffff803`5b720c6c : 00000001`6ac2be58 ffffe08f`139a9480 ffffe08f`139a9530 fffff803`5b7aea91 : nt!HalpTimerClockInterrupt+0x109
ffffab01`8c3ebbc0 fffff803`5b82e24a : ffffab01`8c3ebcd0 ffffe08f`139a9480 fffff803`e090a0c8 fffff803`5b7254aa : nt!KiCallInterruptServiceRoutine+0x9c
ffffab01`8c3ebc00 fffff803`5b82eab7 : ffffab01`8c3da100 fffff803`5b697569 ffffab01`8c3d9f80 00000000`00027100 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffab01`8c3ebc50 fffff803`e08f2b3a : 00000000`00000000 00000000`00400a02 ffffab01`8c3ebef8 ffffe08f`13ece8c0 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffab01`8c3ebde0 fffff803`5b720d3d : ffffab01`8d705780 fffff803`5b6b2b6c ffffab01`8d705830 ffffab01`8c3d1180 : HDAudBus!HdaController::Isr+0x9a
ffffab01`8c3ebf50 fffff803`5b82dfcf : fffff382`ea8465a0 ffffab01`8d705780 fffff382`ea8467b8 fffff803`5b82e24a : nt!KiCallInterruptServiceRoutine+0x16d
ffffab01`8c3ebf90 fffff803`5b82e297 : 41a01e26`00000000 00001f80`00000200 00000000`00000000 ffffe08f`1cb2cb80 : nt!KiInterruptSubDispatch+0x11f
fffff382`ea846520 fffff803`5b836ee0 : fffff803`a370deb5 00000035`00000000 00000035`00000000 41a01e26`bc1ca12a : nt!KiInterruptDispatch+0x37
fffff382`ea8466b8 fffff803`a370deb5 : 00000035`00000000 00000035`00000000 41a01e26`bc1ca12a 00000000`00000000 : nt!guard_dispatch_icall+0x20
fffff382`ea8466c0 fffff803`a370e50a : 00000000`00000000 ffffe08f`1cb29000 00000000`00000000 00000000`00000000 : nvlddmkm+0xcdeb5
fffff382`ea8466f0 fffff803`a370be69 : ffffe08f`1cb29000 00000000`00611d40 ffffe08f`1396c040 00000000`00611c00 : nvlddmkm+0xce50a
fffff382`ea846720 fffff803`a3b36d1e : ffffffff`00000000 fffff803`00000000 ffffe08f`2a4f1068 00000000`00000216 : nvlddmkm+0xcbe69
fffff382`ea8467a0 fffff803`a3b2d011 : ffffe08f`00000209 ffffe08f`1d702000 fffff382`ea846848 ffffe08f`1cb29000 : nvlddmkm+0x4f6d1e
fffff382`ea846810 fffff803`a372a05b : 00000000`00000000 fffff803`00000003 00000000`4d525600 fffff803`a3ffdf74 : nvlddmkm+0x4ed011
fffff382`ea846890 fffff803`a3728d24 : fffff803`a4082248 fffff382`ea840002 ffffe08f`22eb0002 ffffe08f`1e809000 : nvlddmkm+0xea05b
fffff382`ea8468d0 fffff803`a3729de5 : ffffe08f`2ce02350 ffffe08f`1cb29000 ffffe08f`22ebc000 ffffe08f`22ebd401 : nvlddmkm+0xe8d24
fffff382`ea8469c0 fffff803`a372a8ca : ffffe08f`1cb29000 00000000`00000000 ffffe08f`1cb29000 fffff382`ea846b90 : nvlddmkm+0xe9de5
fffff382`ea846a30 fffff803`a36dbae7 : ffffe08f`1cb29000 ffffe08f`22ebc000 ffffe08f`1cb29000 ffffe08f`22ebc000 : nvlddmkm+0xea8ca
fffff382`ea846a90 fffff803`5b6b3f6c : 00000000`00000000 ffffab01`8d7056f0 ffffab01`8d7056f0 fffff382`ea8474c0 : nvlddmkm+0x9bae7
fffff382`ea846dd0 fffff803`5b6b2f5a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExecuteAllDpcs+0x42c
fffff382`ea847310 fffff803`5b830eee : 00000000`00000000 ffffab01`8c3d1180 00000000`00000000 ffffe08f`1396c040 : nt!KiRetireDpcList+0x1ba
fffff382`ea8475c0 00000000`00000000 : fffff382`ea848000 fffff382`ea841000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e


SYMBOL_NAME: HDAudBus!HdaController::Isr+9a

MODULE_NAME: HDAudBus

IMAGE_NAME: HDAudBus.sys

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 9a

FAILURE_BUCKET_ID: 0x133_ISR_HDAudBus!HdaController::Isr

OS_VERSION: 10.0.22621.1

BUILDLAB_STR: ni_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {ff5d8ed2-7893-7823-bca7-8d261625006d}

Followup: MachineOwner
---------

1: kd> lmvm HDAudBus
Browse full module list
start end module name
fffff803`e08f0000 fffff803`e091f000 HDAudBus # (pdb symbols) C:\ProgramData\Dbg\sym\hdaudbus.pdb\691906F6CFE0D26A9A47B19860C9E5E41\hdaudbus.pdb
Loaded symbol image file: HDAudBus.sys
Mapped memory image file: C:\ProgramData\Dbg\sym\HDAudBus.sys\442521932f000\HDAudBus.sys
Image path: \SystemRoot\System32\drivers\HDAudBus.sys
Image name: HDAudBus.sys
Browse all global symbols functions data
Image was built with /Brepro flag.
Timestamp: 44252193 (This is a reproducible build file hash, not a timestamp)
CheckSum: 00036F5E
ImageSize: 0002F000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Information from resource tables:

 

[x BlueRobot]

Okay, please keep the Wi-Fi adapter disabled since it should hopefully at least stop those Stop 0x133 bugchecks which seem to be network related. The other set of Stop 0x133 bugchecks do seem to be either graphics or audio related.

Could you please zip up the MEMORY.dmp file and then upload it to either your Google Drive or something like WeTransfer?

 

[Simon Slays]

Okay, please keep the Wi-Fi adapter disabled since it should hopefully at least stop those Stop 0x133 bugchecks which seem to be network related. The other set of Stop 0x133 bugchecks do seem to be either graphics or audio related.

Could you please zip up the MEMORY.dmp file and then upload it to either your Google Drive or something like WeTransfer?

Here is the memory dump file: Memory Dump - Google Drive

Edit: it may take like 10 minutes as it's not currently finished uploading. I thought it was a small file.

 

[Simon Slays]

Okay, please keep the Wi-Fi adapter disabled since it should hopefully at least stop those Stop 0x133 bugchecks which seem to be network related. The other set of Stop 0x133 bugchecks do seem to be either graphics or audio related.

Could you please zip up the MEMORY.dmp file and then upload it to either your Google Drive or something like WeTransfer?Sor

Sorry it took so long to upload, I accidentally restarted my PC when there was only 2 minutes remaining on the upload. It's finished uploading now though.

 

[x BlueRobot]

Edit: it may take like 10 minutes as it's not currently finished uploading. I thought it was a small file.

That's why I suggested you place it inside a .zip before uploading it

Have you tried using the latest Realtek/Nvidia audio driver from your motherboard support page? I assume that the current driver you have from Nvidia is the latest studio ready driver and not game ready? The studio ones tend to be more stable.

Under sound devices, there is another device for ASUS Utility and its driver seems to belong to Intelligo Virtual Audio Cable, do you know what this is or use it at all? Is it related to Cablemod which you mentioned in your initial post?

 

[Simon Slays]

That's why I suggested you place it inside a .zip before uploading it

Have you tried using the latest Realtek/Nvidia audio driver from your motherboard support page? I assume that the current driver you have from Nvidia is the latest studio ready driver and not game ready? The studio ones tend to be more stable.

Under sound devices, there is another device for ASUS Utility and its driver seems to belong to Intelligo Virtual Audio Cable, do you know what this is or use it at all? Is it related to Cablemod which you mentioned in your initial post?

I have the latest Game Ready hot fix driver installed for my GPU. I have tried older ones after using Display Driver Uninstaller to remove the old drivers from my PC but it didn’t fix the issue. I also game more than anything else on my PC so I’d rather use the Game Ready drivers.

As for sound devices, I only have my wireless gaming headset and the onboard sound from the motherboard as well as the sound from the graphics card. The ASUS utility was installed when I installed something to do with AI Noise Cancelling from ASUS but I installed this way after the problems started so I don’t think that’s the cause.

Last night I was messing with my driver installs again and deleting all of the hidden devices in device manager and everything seems somewhat stable with max DPC latency at 0.3ms coming from nvlddmkm.sys which is the Nvidia driver. The only reason it is stable though is because I have disabled the High Definition Audio Controller under System Devices in device manager, if I enable this again, that’s when the computer goes into meltdown mode. Could it be that my onboard audio for my motherboard is faulty?

 

[Simon Slays]

I forgot to mention that I can also alter my BIOS settings as much as I want with the two High Definition Audio Controllers disabled. It no longer freezes and blue screens once leaving the BIOS, but once I enable them again and go back into the BIOS and change something; the computer starts freezing and crashes with DPC_Watchdog_Violation. I’m not sure how the High Definition Audio Controllers would cause that.

I think a driver from the audio is conflicting with the GPU, because when the GPU is not in the PC the issue goes away even with High Definition Audio Controller enabled. But as soon as I place in a GPU that’s when the issue starts and the nvlddmkm.sys and hdaudbus.sus become the two highest offenders in Latencymon. I also noticed that if I leave High Definition Audio Controller enabled and restart the PC, all of the issues miraculously go away. So could it be something that is only affecting the boot up process? As it only starts to show up when I save and exit the BIOS screen.

It could also be that the GPU or the Motherboard perhaps have faulty audio controllers?

 

[x BlueRobot]

I suspect that issue is more likely to be related to the motherboard itself since you have had issues with the wireless network adapter too. Do you have another graphics card you can use? Even if you have to borrow one, it can help us determine if it's that particular card which is causing an issue or something very odd is happening with your motherboard.

 

[Simon Slays]

I suspect that issue is more likely to be related to the motherboard itself since you have had issues with the wireless network adapter too. Do you have another graphics card you can use? Even if you have to borrow one, it can help us determine if it's that particular card which is causing an issue or something very odd is happening with your motherboard.

I think I may have actually fixed the issue finally. I found another forum (System interrupts, Latency, HDaudbus.sys) from 2017 on Sysnative and the person had a similar issue to me with hdaudbus.sys causing high latency and system interrupts. The fix was to change the HD Audio Controller to MSI mode in the registry. I also installed the MSI Utility V3 and set the same there for the GPU and HD Audio Controller and now when I change settings in the BIOS, the computer actually works without any BSOD, freezes, lag or distorted audio. I hope this is helpful to anyone in the future and thank you so much for your help x BlueRobot. The only thing that shows up in Latencymon now and very rarely spikes is dxgkrnl.sys which is to do with DirectX. I have reinstalled DirectX but this issue still persists. It's nowhere near as bad as the other issue though.