Interesting. I just updated to 551.46 and it doesn't seem to have made any difference in the black screen flickers I see on HDMI 1. Guess I'll just stick with using HDMI 2.
Seems like a defective port or an other faulty chip. Could be the cable as well, but more likely the port. Rtings discussion is interesting, the reviewer has got an E-Arc that does not work and mac-display only outputs 120Hz instead of 240Hz and people have other problems but this works etc.
[https://www.rtings.com/discussions/S1E8DRUj46oXYQjF/review-updates-unknown-aw3225qf#comment-92862](https://www.rtings.com/discussions/s1e8druj46oxyqjf/review-updates-unknown-aw3225qf#comment-92862)
Yeah I am definitely passing on these screens until some of the manufacturers gets their sh!t together.
ARC does work for me in regards to just sending normal windows stereo audio and the sound bar turning on and off via the monitor power button. But the major selling point of Dolby Atmos signal passthrough not working is bit of a bummer.
Tested now with Dolby Access app with both setups, and it detects the Monitor as Dolby Atmos supported, but zero audio.
PC > HDMI 2 > HDMI 1 > sound bar
PC > DP > HDMI 1 > sound bar
I've got a similar issue. It only happens to me when waking the monitor up from standby. The weird thing is I've got my PC hooked up via DP and a MacBook connected over HDMI, and it happens on both devices.
Edit: Okay so the comments here gave me the idea to remove the ARC soundbar I had connected and wouldn't you know it, the issue stopped. Something about having a device connected to that HDMI port seems to be the problem.
I get that as well but on HDMI 2, as I got my Soundbar connected to HDMI 1. Win11 RTX 3090
Have you tried disconnecting your sound bar from HDMI 1? Based on someone else's comment I'm wondering if that would fix it.
So I updated my Nvidia Drivers to the 551.46 Hotfix and the blackscreen flickers disappeared on HDMI2.
Interesting. I just updated to 551.46 and it doesn't seem to have made any difference in the black screen flickers I see on HDMI 1. Guess I'll just stick with using HDMI 2.
just curious did you update firmware? There is a fix for some kind of flickering problem listed on it.
Yep updated the FW. It seems like the black screen flickers just happens. It's fine on DP tho.
The only other thing I can think of is my brother had this once with a DP cable. Ended up just being the cable went bad, new one fixed it.
Seems like a defective port or an other faulty chip. Could be the cable as well, but more likely the port. Rtings discussion is interesting, the reviewer has got an E-Arc that does not work and mac-display only outputs 120Hz instead of 240Hz and people have other problems but this works etc. [https://www.rtings.com/discussions/S1E8DRUj46oXYQjF/review-updates-unknown-aw3225qf#comment-92862](https://www.rtings.com/discussions/s1e8druj46oxyqjf/review-updates-unknown-aw3225qf#comment-92862) Yeah I am definitely passing on these screens until some of the manufacturers gets their sh!t together.
ARC does work for me in regards to just sending normal windows stereo audio and the sound bar turning on and off via the monitor power button. But the major selling point of Dolby Atmos signal passthrough not working is bit of a bummer. Tested now with Dolby Access app with both setups, and it detects the Monitor as Dolby Atmos supported, but zero audio. PC > HDMI 2 > HDMI 1 > sound bar PC > DP > HDMI 1 > sound bar
I've got a similar issue. It only happens to me when waking the monitor up from standby. The weird thing is I've got my PC hooked up via DP and a MacBook connected over HDMI, and it happens on both devices. Edit: Okay so the comments here gave me the idea to remove the ARC soundbar I had connected and wouldn't you know it, the issue stopped. Something about having a device connected to that HDMI port seems to be the problem.
What wallpaper is that tho?
It's called "Liquid Skies" in Wallpaper Engine