Hi hz: Thank you very much for contacting the Intel® Graphics communities. We will do our best in order to try to fix this problem.
Just to let you know, there are some graphics drivers that contain different audio versions, so, what we can do next will be to un-install the current graphics driver from device manager and then install version 4821. After that, please get into device manager again, look for “Sound, video and game controllers” right click on it and test both audio versions to confirm if the games work fine that way:
Additionally, Steam has its own forum support, we recommend to submit your inquiry on their forums as well in order to get further technical assistance and suggestions on this subject:
Any further questions, please let me know.
1 of 1 people found this helpful
Hi, thanks for your response!
Okay, I compared the current driver with the older driver and can now confirm that the problem occurs with graphics driver package 22.214.171.12449 (win64_15600.4849.exe), which contains Intel Display Audio driver 10.24.0.1.
But it turned out that the HDMI audio works fine with graphics driver package 126.96.36.19921 (win64_154521.4821.exe), which contains Intel Display Audio driver 10.22.1.100.
I also tried the newer graphics driver 188.8.131.5249 and then downgraded only the HDMI Intel Display Audio driver to 10.22.1.100, but even that combination still didn't work.
Something must have been broken with the new graphics driver package. It is odd that this affects only some games and not all programs using HDMI audio.
Hope you can fix this for the next upgrade!
hz: You are very welcome. Thank you very much for providing those results we really appreciate your feedback. In order for us to do further research on this matter, please provide the information requested on the link below:
Any questions, please let me know.
I am having the exact same issue... Unfortunately the link provided to follow (in the last post) was referencing one specific game and thus does not help us with the underlying issue affecting other games.
For example I have a game that will recognize and use the Realtek sound card when there are headphones plugged into my NUC7i5BNH, but does not recognize any sound card when just using the Intel Display Audio with hdmi. This is using the latest 184.108.40.20644 (220.127.116.1144) display driver. However if I uninstall it, reboot, and install 18.104.22.16878 (which has the Display Audio driver 10.22.1.100) the game recognizes the Display Audio and works as it should.
This issue was introduced at least 5 months ago and needs to be fixed. Please provide us (your loyal customers) an update and ETA on resolution so our expectations can be properly set.
Thank you for joining the thread.
In order to assist you better with the specific problem, you are having in your Intel® NUC system. I recommend creating a new thread. Please make sure you add all of the details of your computer so we can get more information about the problem.
I believe this is the same issue that was reported here: No HDMI Audio in Fallout 4 even though the games are different. We closed this since it was determined that this issue is actually coming from the games code. You see, when the application launches, the driver does a 'modeset' with a max delay of 8 seconds (max time defined by the HDMI specification) during which the audio gets disabled. It is at this point that the application checks for audio presence (shows disabled), hence audio drop occurs. The application(s) that run into this problem need to be updated so they detect the audio for more than 8 seconds upon launch. The reason why this issue doesn't occur on previous drivers is because due to a code bug, they were taking longer than 8 seconds for 'modeset'. However this was actually undesired behavior since it affects plenty of other scenarios.
Intel has been reaching out to most developers so they can look into this and fix their code, but if you have a list of affected applications or games please let us know so we can attempt reaching out to the respective devs as well.
By the way, a temporary workaround I have observed is making sure that the game resolution matches the one set in Windows* (e.g. in the game settings set 1920x1080 if that is the one you have in Windows*).