cancel
Showing results for 
Search instead for 
Did you mean: 

rog strix b550-f audio impedance issues

Midnight_Aurias
Level 8

as the subject suggests this is a audio issue when installing the audio drivers for the rog strix b550-f gaming motherboard it reads the impedance wrong for my headphones my z906 can handle 600 ohm

but then comes the issue why i have to uninstall the audio drivers and let windows handle the drivers my headphone impedance also goes to 600 ohm they become oversensitive even having issues picking up audio like footsteps and such while other sounds are more expressed and plugging them in always results in no sound i have to go back and forth between settings for the headphones to finally work

the headphones are the philips fidelio x2hr

note when i first installed the audio drivers it did read the headphones correct at 32 ohm however now even the audio plays in the speakers when defaulted to the headphones my guess that means it only picked up the impedance of the speakerset and applies that to any audio device i connect

removing the audio drivers removes this issue and the headphones work normally again but the audio drivers made gunshots and explosions sounds way more impactful in games then the windows drivers for audio

Driver : Realtek Audio Driver V6.0.9411.1 For Windows 10/11 64-bit

743 Views
1 ACCEPTED SOLUTION

Accepted Solutions

Jiaszzz_ROG
Customer Service Agent

Hello, @Midnight_Aurias 

Due to the ongoing local holidays in our area, our response time may be slower.
We apologize for any inconvenience caused by delayed replies.
Based on your current description, it appears that the correct ohm value is displayed when connecting the Philips Fidelio to the rear panel ports of the motherboard. But there may be an issue with incorrect resistance when using the audio jack on the computer case, especially after reinserting it.
Therefore, we recommend that you double-check the connection between the motherboard and the case to ensure it is correct.
Meanwhile, please consider cross-testing with other computer cases to further troubleshoot the problem.

Thank you.

View solution in original post

8 REPLIES 8

Jiaszzz_ROG
Customer Service Agent

Hello, @Midnight_Aurias 

May I ask if the issue you described occurred only after updating the Realtek Audio Driver V6.0.9411.1? Or were there any other software or hardware changes?
Currently, are you simultaneously connected to both the Logitech Z906 5.1 Surround Sound Speakers and the Philips Fidelio X2HR?
Please provide information on which I/O port each device is connected to, whether it's the front or rear port.
If you connect the headphones separately and remove the speakers, are you able to get the correct impedance value for the headphones?
If possible, please provide a screenshot showing the difference in impedance values.

Thank you.

Fresh Install Speaker ImpedanceFresh Install Speaker ImpedanceRestart Headphone ImpedanceRestart Headphone ImpedanceReplug Headphone ImpedanceReplug Headphone Impedance

the pc is a complete fresh build new os everything

the driver was updated from the driver windows 11 auto installs

it works if i keep reinstalling the driver then the headphones work properly due to the right impedance but that is not really a solution so after this post ill uninstall it again till requested otherwise don't plan on killing my headphones

i found out that the bug is caused when i replug my headphones in the microphone/headphone port of the corsair 4000D case once replugged i can restart the pc all i want it wont show the right impedance till a reinstall of the driver i also tried removing both devices then only connecting the headphones but still it wont show the right impedance it is stuck at 600 no mather what each replug means no audio for the headphone and i gotta go through loops of setting back and forth to trigger it back to life

i always connect both devices to the pc like i did with my previous build which had no impedance issues with the realtek drivers

the logitech z906 is connected through the i/o of the motherboard and the philips fidelio is connected to the case i/o microphone/headphone port

Ive same issue. do you know any solution

my solution still is to use my logitech z906 speaker set aux port still 600 ohm displayed in the realtek audio console but the decoder seems to prevent it bricking the headphones when plugged into it

if you plug in the headphones in the back port of your pc it will show the correct ohm i guess you can purchase a switch if you don't have a speaker set with a aux port otherwise i don't know

i have yet to try a older case kinda stopped bothering with this problem as said my solution was my decoder does not mean the problem stopped existing the front aux/mic port is still useless with microphones or headphones

but i don't know your pc case so technically if you do not have the corsair 4000D i could in theory rule out that it is caused by the case itself which means there is a bug in the software

Jiaszzz_ROG
Customer Service Agent

Hello, @Midnight_Aurias 

May I ask if you have verified whether both devices were tested separately or with the Logitech Z906 5.1 system removed and only the Philips Fidelio X2HR headphones connected?
Additionally, please confirm the results when connecting only the Philips Fidelio X2HR headphones to the rear panel of the motherboard.
Could you confirm that "it works if I keep reinstalling the driver" means that the problem occurs every time you restart the system and only gets resolved when you reinstall the driver?

Thank you.

i only actually tried having them plugged in separately in like getting the logitech z906 out of the rear ports and only replugging the philips fidelio in the front

i just tried puting the philips fidelio into the rear port and it shows the correct ohm then tried it in the front again 600 ohm 

as for now it works if i keep reinstalling the driver after the pc restarts of the driver install the front shows the correct 35 ohm until i plug out the headphones and plug them back in then its straight to 600 no restart and restarting doesn't make it go back to 35 ohm until the drivers are removed and reinstalled

right now it is kind of solved im now using a toslink cable for the speakers and the philips fidelio goes in the rear port

the question now becomes is there a solution for the front connector of the corsair 4000D to show the correct ohm at replug or is it just the case of the pc case is too cheap to support the motherboard previous case was the phanteks a400 but it was to small to fit a full size noctua nh-d15 so that was a rip

Jiaszzz_ROG
Customer Service Agent

Hello, @Midnight_Aurias 

Due to the ongoing local holidays in our area, our response time may be slower.
We apologize for any inconvenience caused by delayed replies.
Based on your current description, it appears that the correct ohm value is displayed when connecting the Philips Fidelio to the rear panel ports of the motherboard. But there may be an issue with incorrect resistance when using the audio jack on the computer case, especially after reinserting it.
Therefore, we recommend that you double-check the connection between the motherboard and the case to ensure it is correct.
Meanwhile, please consider cross-testing with other computer cases to further troubleshoot the problem.

Thank you.

i checked the cable in the motherboard and the one that goes to the case itself both are socketed correctly

i did already mention that my old pc doesn't have this issue but it doesn't have the same motherboard so not really useful as for now i don't really have any other case to rule out the corsair case i know i can frankenstein my old pc to use it and just power the case while all the rest of the components are still in there but wel the weather is hot atm and i stored the case away

found something really stupid out the decoder for the logitech z906 has its own headphone/mic port and even while 600 ohm shows in the realtek audio console the headphones work just fine through it its one of those cases you saw it once and forgot it ever existed till you have to troubleshoot something

thank you for your help and while the problem is not solved alternatives were now found until i can definitively conclude if its the case itself or something with the motherboard ill repost the issue till then have a good day ill mark the last reply as the solution atm