Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Thats steam system information, copy/paste that here.
also do them cmd ( google them how to do )
DISM.exe /Online /Cleanup-Image /Restorehealth
SFC /Scannow
this might not help, but try see it as ruleout other system issue.
even check disk on evey hard drev, as i said you dont want things discover later with the system.
Also the problem only appeared yesterday, those same titles played fine before.
Also, non-Steam games don't have this issue, even when playing more demanding ones.
Steam doesn't do anything with audio, so the fault would be with something else.
Check the audio driver control panel app (if there is one) to make sure stuff like virtual surround, DTS-X and all that sort of stuff is disabled. Make sure format is set to PCM at a frequency your AVR supports, disable any enhancements that might be on by default, unplug/disable headset in case it's trying to switch to that automatically for some reason.
I already disabled all "improvement effects" in the control panel, tried to both enable and disable Dolby Access, music plays perfectly well outside of Steam (games too), and the AVR indicates it's receiving a multi-channel input, which means a PCM signal. Also tried setting it to stereo, nothing changed.
I tried to set it to 24 bit / 196 kHz, which works fine (but the Steam problem still happens), went back to 16 bit / 48 kHz, same thing.
The output device is not being switched, I already checked that. Nor is it being disconnected.
Also never had this problem before, been using the GPU for 3 years and no issue so far
Knowing that this specific setup works, it'd be less time consuming to start fresh and install all the drivers again than it would be to fumble around trying to find a solution with no clues to go on.
This bug only happens when the AVR or the TV is selected as the audio output.
I'm currently playing a Steam game on the TV but with a speaker connected to the case's Jack 3.5mm port and it works like a charm.
I have absolutely no idea where to search from this...
I did reinstall Windows 3 weeks ago, and I don't have a lot of programs installed, so nothing guarantees that it would work properly after reinstalling :(
Possibly the cable? Maybe the resolution, refresh rate, color depth and/or format are incompatible?
I had an receiver once that technically supported 192khz with a 1080p signal but actually didn't unless I turned off PLII.
Have you tried using the TV speakers with HDMI and taking the receiver totally out of the equation?
I can't test the speakers without the receiver as these are passive speakers, they require 6-channel amplification to work.
When using any other device than my PC, sound plays perfectly fine.
I just made a little hack in which I disable the AVR's sound output in Windows, plug in a USB to Optical converter I bought a few years ago, and plug the optical into the AVR's inputs. Not great, and it only supports stereo, but it works. So that'll do until I figure out what's the problem with this system.
The idea is to run HDMI audio directly to your TV and then output via the TV speakers, not the surround speakers. This tests whether the issue is with the the PC or the receiver.
If removing the AVR and surround speakers entirely still gets you the same issue when just using the built-in TV speakers, then you know it's a problem with the PC. If it works fine, then it's an issue with the receiver, or an issue in some part of the connection between receiver and TV.
I'll try that when I get back and tell you how it went.
So it would be related to the display adapter? I really don't get what's happening here...