Realtek (R) Audio Driver keeps coming back

Question

Realtek (R) Audio Driver keeps coming back

Anonymous

Hello,

this is my last resort. I persued a higher education in IT. I am working as tech support since I graduated. I would not describe myself as helpless when it comes to OS, IT, Office, Windows etc. quite the opposite, but this topic is breaking me.

I have searched now for (a total of combined), 6 hours on this topic. I have seen every reddit post, every thread here, every forum there, here everywhere. The issue I am describing makes no sense to me, still it is a riddle to me to the point I wished an windows developer come to my home and see it and ask him how he can make sense out of all that.

My issue:

About 2 years ago I received my brand new Desktop PC and it worked, however. Whenever my PC would crash, the audio driver would switch from Microsofts High Definiton Audio Driver (MHDAD) to the default driver Realtek (R) Audio Driver (RAD). Which works at first, but then, at some point it will cause a BSOD - Not sure when, but it will eventually - and after the BSOD it then returns back to MHDAD.

This lasts until: When I had my PC cleaned by a company (switched back to RAD), I was on vacation for a week and unplugged by PC and PSU for a week (switched back to RAD) and when my PC no longer had eletricity (after booting, switched back to RAD). Which, in fact works perfectly and even has better audio quality than the MHDAD, but as I said, it will BSOD my PC - and if I restart (not shut down) my PC - RAD will refuse to give me sound. I could just, you know. Use RAD, and just take the BSOD as the price I have to pay for a working PC, but - BSODs are bad.

But now for the weird part. I found a fix which I don't understand. My PC switches back from RAD to MHDAD, if I connect my Headset to the back of my monitor, use the monitor as output device. Then use my PC normally (without microphone though because monitor only has output) shut off my PC, sleep a night over it and the next day (it has to be the next day or else if I plug my headset back into the PC it will give me RAD again) I get MHDAD again.

To get rid of RAD I have tried everything the internet offered me:

Deinstalled RAD in Device Manager under "Audio, Video and Gamingcontroller", then rebooted, done it with & without my headset plugged in before reboot. Both unsuccessful, then did it again, but with deinstalling the software aswell - 4 tries with no success.
I installed the driver from my PC manifacturer (here) after I deinstalled RAD (+ Software) in Device Manager (DM), and without deinstalling RAD beforehand (ofc always reboot, reboot, reboot because you have to complete the install - no success. Windows says: Take RAD, it doesn't work and doesn't produce any sound, but you have to. Also, after the installation, the setup (I in theory just installed), comes up again as if I launched the .exe - guess it knows that RAD took over.
I went to DM -> Audio, Video, Gamingcontroller -> RAD -> Update driver -> Tried both, if I let it do it automatically, it would switch to MHDAD, then asks me to reboot to complete, nope it's RAD again. Then I chose -> search on PC for drivers (manually) -> select from list -> Tried both, MHDAD and Realthek HD Audio Driver -> Rebooted, nope - RAD it is again
Then I went into my BIOS -> more settings, Audio Settings -> Disabled On Board Audio Controller -> RAD wouldn't appear anymore, but when I plugged in my headset - it just, did nothing. No new output device found except my monitors.
Go to DM, -> Sound, Video & Game Controllers -> RAD -> Properties -> Previos Driver (which proposes MHDAD again), reboot to complete install, nope - RAD again.
Searched in Windows Updates for Audio Drivers (yeah as if that is ever useful lol)

The solution to this, presumably, is disabling automatic driver updates (because yes, I have seen my output device change from MHDAD to Realtek HD Audio Driver back to RAD quickly after bootup) but this isn't a solution, this is obviously Microsofts error. Because having automatic drivers for literally everything else is useful and shouldn't be required to turn off just because Microsofts loves RAD so much, until RAD retaliates with BSOD appearently. Turning it off doesn't seem user friendly.

In short:

When my PC loses Power, gets cleaned, or isn't plugged in for a week, Windows chooses the faulty Realtek Audio Driver (RAD) on bootup when I have my Headset plugged into the PC. Then RAD works until I reboot my PC (which I do because every time it happens I kinda forget it stops working - all I remember is Realtek = BSOD, then I reboot, in the hopes it would go away + to also prevent the BSOD).

This lasts until RAD causes a BSOD, or I plug my Headset into the Monitor + let my PC rest for several hours of sleep worth.

Anyway, my questions:

How can I solve this issue permanently once and for all, how can I nuke RAD from my Windows install forever - at this point I could potentially delete it from sys32, but where is it? At this point it feels more like malware than a driver.

Why does Windows switch from RAD to the good and working MHDAD, when I plug my Headset into my monitor, shut my PC off and the next day start it again after several hours. (As I write this, I will edit this post if It really worked - Last time was so long ago, can't really say that with confidence)

Why does my PC switch to MHDAD after it crashes, but literally never if I tell windows to do it?

Why does RAD cause a BSOD consistently?

Why does RAD work on the first boot up after a crash/pc clean/vacation - but stops working If I reboot my PC (No sound comes into my headset).

Could a Bios Update solve the problem (though, the problem also appeared right after I got my PC)?

And lastly, what should I really do? Is it the headset? I can't really try another. RAD doesn't work, but - 99% of time I use MHDAD anyway (or rather, windows allows me to), but not being able to use your PC whenever RAD is there, is very tilting (I just came back from vacation). I wouldn't mind using Realtek HD Audio Driver which I think works as good as MHDAD, but, as I said, windows doesn't really give me that option (and I don't even know how I got it).

I will get some sleep now and hopefully wake up tomorrow with MHDAD again.

Edit: As suspected, the next day. I got MHDAD again. Well the problem is "gone" for now, until my PC loses power suddenly, is cleaned, or switched off for several days.

If any further info is needed, feel free to ask.

Microsoft Windows 10 Home
Version 10.0.19045 Build 19045
BIOS-Version/-Date LENOVO O4MKT1DA, 14.04.2021
Datasheet: Specs

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

3 answers

Answer 1

Your desktop computer has 2 separate audio jacks, therefore you need a Y splitter.

Your computer has 2 audio devices --- a realtek audio device that uses 3.5mm stuff and your hdmi audio device that uses the hdmi cable. If you didn't install the appropriate driver that you will have high definition audio device.

Install your lenovo realtek audio driver using the setup.exe installer. Then using device manager to update using this driver. Download the cab file, then copy the contents to an empty folder and then point the device manager to that folder.

https://www.catalog.update.microsoft.com/Search.aspx?q=6.0.9673.1

Answer 2

Hello Kyo,

thank you for your fast reply. I didn't find a quote option in the text editor (only quote the whole thing). But I will try to answer the questions as thoughtful as I can:

If possible, would you mind sharing more information about this issue with us?

Have you been experiencing the problem since the day you purchased the device?

Or did it start appearing after experiencing some events (for example, BIOS update)?

I bought the PC in February 2022. Since this is more than 2 years ago, my memory is a bit muddy but as far as I can remember (and based on my reddit post about it 2 years ago it went as following:

When I plugged in my Headset the first time, RAD was used intially which didn't work. When I tested the audio by just monitoring the volume bar, there was supposed to be audio but I didn't hear it on my headset (Headset was the output device). Then I did something (can't recall now and 2 years ago because it was just trial and error) **** and I got rid of RAD again, and it worked. Then it happened again, and I got rid of RAD again.

Then few weeks later electricity was cut to my PC and on Boot up RAD again - my friends noticed my mic is different now. Then I restarted my PC and now RAD didn't work entirely. And on the third try I couldn't remove RAD even when I wanted - well then I just plugged my headset into the monitor so I would atleast have sound and on the next day when I plugged it back into the PC it worked again (same as yesterday).

So basically: No it never worked on day one. Also I changed headset in the meantime (to the same one, I bought one as reserve) but problem is still there.
Since according to Windows my Bios Version is still from 2021, I assume a BIOS Update didn't cause this.

But this issue feels like a problem with Windows. What is the point of going into Device Manager -> Sound, Video & Game Controllers -> RAD -> Update Driver -> Browse my computer for drivers -> Choose from list of available drivers -> choosing any other driver - when after did the reinstall to change the driver from RAD to any other, it still uses RAD after the install of the supposed "new driver".

It is like: Yes I would like to change the driver of this device and the UI is helpful and basically just allows you to choose what driver you want to "update" the old one too from the list of compatible ones and then you install the new driver, only to have the old one still. Especially if Windows uses MDHAD after RAD causes a BSOD, so I can't help but think Windows knows that RAD is faulty (even though it's not sentient).

Also, I did this: Uninstalling a driver completely - Microsoft Community **** multiple times + reboot to finish the uninstall and it still came back.

Additionally I can't follow your other steps (to delete the .inf file) because - as predicted in my first post, RAD disappeared entirely and will only come back with the previously mentioned conditions. I might come back to it in a few several months.

My takeaway is:

Why is it so unnecessary hard to change drivers?

Why is it so hard to disable drivers, and not having to nuke them out of my system through some complicated steps

Why can't I choose the default driver for certain devices like I can choose the default program to open certain file extensions? It appears that Windows allows me to choose the driver I want to use, but It just doesn't.

Answer 3

Hi TollerTag,

Welcome to Microsoft Community.

Please note: Members of the Answers community do not interact directly with the product team, core members of the product team are not active in this community.

The device seems to be experiencing component-specific driver state changes.

Windows itself is not designed to force a switch to another type of driver.

Component-specific problems can be related to the circuit design on the motherboard or the overall power environment of the device in addition to the driver as a factor.

Just from limited personal experience, abnormal circuitry signals may pass unintended parameters, leading to abnormal API behavior.

For example, you mentioned that things seem to change slightly after not being connected to a power source.

If possible, would you mind sharing more information about this issue with us?

Have you been experiencing the problem since the day you purchased the device? Or did it start appearing after experiencing some events (for example, BIOS update)?

If you need to avoid automatic driver reinstallation, you may need to remove the driver package associated with a specific driver, that is you may need to remove the specific XXX.inf file. Content in the links below described examples of such behavior.

How Devices and Driver Packages are Uninstalled - Windows drivers | Microsoft Learn

Driver Store-File Repository using huge disk space. How can I reduce - Microsoft Community

Uninstalling a driver completely - Microsoft Community

After the driver "package" is removed from the device, the driver cannot be installed by scanning for hardware changes. Please be careful to back up the driver installation files in advance. | Disclaimer: Please back up all your important data before performing it. | | --- |

To find the inf name associated with a specific driver, you may need to select the specific component in Device Manager and then use "Devices by driver" under the "View" tab.

Open Device Manager - Microsoft Support

If I misunderstand your situation, feel free to correct me and share the information.

Best Regards,

Kyo.Y - MSFT | Microsoft Community Technical Support

Share via

Realtek (R) Audio Driver keeps coming back

3 answers