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

[x BlueRobot]

Since you've had a number of issues with different onboard devices then it is most likely the motherboard which is causing these issues. I do recall that the NDIS error you had was because hardware was setting something incorrectly.

 

[xilolee]

You could try to remove the gpu, given that the cpu should have one integrated.

 

[Simon Slays]

Did you remember to NOT select the Nvidia audio driver when you updated your graphics driver?

Hi, I did install the HD Audio from NVIDIA because I use it for my monitors. I used it on my old PC without any conflicts and the motherboard was practically the same as the one I have now just older. It was part of the Hero lineup.

 

[Simon Slays]

You could try to remove the gpu, given that the cpu should have one integrated.

I have taken the GPU out before and used integrated graphics and the issue went away with system interrupts. It’s definitely a conflict between the GPU audio and the integrated audio controller on the motherboard. Why would they conflict though? My old motherboard was an ASUS ROG Maximus XI Hero and I never had any issue like this between the GPU and motherboard.

 

[Simon Slays]

Since you've had a number of issues with different onboard devices then it is most likely the motherboard which is causing these issues. I do recall that the NDIS error you had was because hardware was setting something incorrectly.

I agree that the motherboard is most likely the issue. I never had any issues with my old motherboard when using the RTX 4090. I think I’m going to send the motherboard and CPU back for a replacement. The CPU temps are stupidly high which makes me think that there’s an issue with it as others with the same cooler as me with less fans have better temps than me. When gaming my CPU hits 85C and straight to 89C in Cinebench. Most people with this CPU average 60 to 70C when gaming and 80C in Cinebench. I definitely lost the silicon lottery as the CPU struggles to do -15 or above with curve optimizer (games start stuttering) but Windows works fine up to -40. Everyone else seems to be able to do all core -30 with ease.

 

[x BlueRobot]

I think I’m going to send the motherboard and CPU back for a replacement. The CPU temps are stupidly high which makes me think that there’s an issue with it as others with the same cooler as me with less fans have better temps than me. When gaming my CPU hits 85C and straight to 89C in Cinebench.

That would seem like the best course of action at this point, you shouldn't have to disable onboard devices or amend registry settings in order to avoid Stop 0x133 bugchecks and latency issues. Those temperatures are unusually high, even when the system is under load, like you said, most people max out at 60C-70C.

 

[Nyshone]

I agree that the motherboard is most likely the issue. I never had any issues with my old motherboard when using the RTX 4090. I think I’m going to send the motherboard and CPU back for a replacement. The CPU temps are stupidly high which makes me think that there’s an issue with it as others with the same cooler as me with less fans have better temps than me. When gaming my CPU hits 85C and straight to 89C in Cinebench. Most people with this CPU average 60 to 70C when gaming and 80C in Cinebench. I definitely lost the silicon lottery as the CPU struggles to do -15 or above with curve optimizer (games start stuttering) but Windows works fine up to -40. Everyone else seems to be able to do all core -30 with ease.

I'm currently facing exactly same issue as you and your fix has worked for me with MSI Mode Util. I have 7800X3D and 7800XT and GIGABYTE B650 AORUS ELITE AX V2. However, my CPU works fine with negative curve optimizer offsets and gets good temps with air cooler, so is it really a motherboard problem? Why is it that we have to tinker with registry to have stable system? I have hard time believing my almost brand new components are faulty too, but I also don't feel good having to re-enable MSI mode after every GPU driver update.

I don't wanna send my motherboard back if the issue will persist, so I'm really curious if you got some more information on what could be the actual culprit, because everything you explained in this thread has applied to me as well. I face exact same issue and same fix has worked for me, but it's more of a "bandaid" kind of fix.