Referi Jerator
-
Posts
44 -
Joined
-
Last visited
Referi Jerator's Achievements
-
Alright everyone, I have reached the end of my testing and have confirmed that this is a software issue with Nvidia, so it seems it's beyond our control to resolve. I've updated the original post with the one and only workaround I've found. It's not a complete solution but it's the most painless one. At least you get to keep everything connected. Unfortunately, at this point there is nothing else I can try and/or test so that's the only "solution" I have for you until Nvidia fix their drivers (don't hold your breath as adaptive sync issues have been around for years). I doubt I'll discover anything new at this stage so this is likely the end of the thread, but of course if you have any insights and/or solutions of your own feel free to post them. I wish you all a Merry Christmas and a wonderful new year. Take care and stay safe.
-
Again, there is no mistake or user error. As Mark also explained, there are software issues with multi-monitor setups and adaptive sync which the consumer has no control over and they've been around for years. This is nothing new. You are talking about GPUs and your wording about AMD is false and can easily mislead other users. While it doesn't work flawlessly or in its full range and capabilities, FreeSync is not exclusive to AMD GPUs. Monitors marketed as "G-Sync Compatible" are AMD FreeSync monitors that can also use Nvidia's G-Sync to some degree if you have an Nvidia card and they've been officially certified as such by Nvidia. In any case, this is unrelated to this thread. Okay, are you trolling? This is a troubleshooting thread so please take it seriously. This thread is about multi-monitor adaptive sync setups. Furthermore, it is beyond absurd to expect the user to have two identical monitors in order to combat this matter. The majority of users worldwide have mix-matched multi-monitor setups. Not only taking the cost into consideration if it's a high-end product but space as well, as the circumstances of each individual vary and some setups would simply be impossible just to have identical models, or if you simply need to have a separate screen of different capabilities for your work, or if you just don't want to have two screens of the same size so you can alter their positions accordingly. There are many reasons why demanding identical monitor setups is ridiculous and not a solution in any manner. All of this is self-explanatory. Besides, this isn't even correct as people have been experiencing issues with both single monitor setups and identical multi-monitor setups too, and those issues always involve adaptive sync technologies. Crashes, freezes, stuttering/hiccups, flickering etc. The list of issues people have reported experiencing over the years is long. Overall, multi-monitor adaptive sync setups and adaptive sync in general have issues, this is undeniable. Regardless of sync technology, GPU make, OS or anything really. It's a lottery, and if as you say the driver forces adaptive sync on all connected monitors regardless of capability (which makes no sense as the issues persist even with the secondary monitors powered off) and that causes issues, then you've already admitted that this is indeed a software issue and not the user's fault. You can contact any company's customer support you want, be it GPU or monitor manufacturers, and they will all tell you that issues like these are not intended and should not be occurring regardless of what monitor/GPU setup you have.
-
Was all that with a native (Nvidia module) G-Sync monitor or a G-Sync compatible (FreeSync) one?
-
By the way, what issues are you experiencing with G-Sync and multi-monitor setups if not crashes/freezes?
-
It's strange, yes, but not unique to me. Like I mentioned in my previous posts, G-Sync crashing Windows with a second monitor plugged in is an issue many other people have faced with entirely different monitors and PC specs. So it seems it's a lottery. You might get crashes or you might not. In your case, you didn't.
-
I suppose you are being sarcastic with the user error stuff but the first part of your message might be a possible explanation. Because during my tests I also tried powering off my second monitor and Windows still crashed with G-Sync on, indicating that the drivers were potentially forcing G-Sync on the second non-G-Sync capable monitor even though it was powered off, and even though Nvidia's control panel states that only the primary G-Sync capable screen has G-Sync enabled. The total randomness of the crashes, however, complicates matters. It's also unknown why it leads to a total Windows crash as opposed to only crashing Nvidia's drivers and restarting them. You should also keep in mind that people have reported having such issues even if all of their connected monitors are G-Sync capable. This may indicate that the issue lies with Windows' or Nvidia's multi-monitor feature's support of G-Sync rather than G-Sync capability mix-matches specifically. However, I may have found a workaround. It won't work for everyone as specs and issues vary but it may help some people. I am still testing it though so I'm not going to post an update yet. I'll be back once I've confirmed that the G-Sync crashes have in fact ceased.
-
Hello again Mark, I see. Thank you for the information that this isn't exclusive to G-Sync, but I never said that it is exclusive to it. I assume that's what you meant by my post not being entirely correct. I only said that to me it only happens when G-Sync is enabled with a second monitor plugged in and that it might help other people with similar issues too. Also, I didn't mean to make this update appear as a revelation at all. I only highlighted it in big letters so that people will see it immediately. It's just a discovery I made for my own specs and through my own testing. It's also a new post, so people will know that it's still a thing in 2022 as opposed to having doubts about threads from years ago. Especially people who don't have prior knowledge of the issue like you do. People with the same specs as mine will also have this post to help them check some boxes off their troubleshooting list. Alas, like you said, Nvidia hasn't done anything after so long so they are unlikely to fix anything now. And, also no offense, but if you already knew about the G-Sync dual monitor issue "since years" you could have suggested unplugging my second monitor the first time. All the other info I found on the net was indeed from years ago but only for G-Sync Compatible monitors, which are notorious for having issues. Mine is a Native G-Sync one, but clearly it doesn't matter. Seems Nvidia doesn't care either way. I am glad that you noticed my Nvidia green detail though, hehehe. I made the size big and the format like that so that it was more concentrated, but I've edited the format a bit now. I was going to make some adjustments anyway so that it's not so rough on the eyes since I also thought it looked bad. As you can tell, I, too, am an Enter key enthusiast. Gimme that additional +1. P.S: Just out of curiosity, what other factors besides G-Sync have contributed to other people experiencing issues with dual monitor setups? Are you referring to only Nvidia or Windows as well?
-
Added an important update to the original post regarding the matter. All G-Sync monitor owners, both compatible and native, should read it if you are experiencing similar issues.
-
Yeah, it couldn't be the monitor specifically because this only happens with G-Sync on and suspiciously only when a game is running during pause screens/loading screens, plus the crash is only software level aka only Windows freezes, because the PC continues to work normally in the background (fans spinning normally, all RGBs continue to work etc.). Also this particular PG279QM I received was a total panel lottery win. No backlight bleed, only slight IPS glow, perfect uniformity and no defective pixels. It's essentially a perfect sample. So RMAing this would not be ideal - in fact, it would be a tragedy, especially considering that it's very rarely in stock (my order took a month to arrive) so even getting a replacement would be quite troublesome. Besides, even if I were to send it to ASUS for at least a technical check just in case, they would not be able to test it because like I said this issue is totally random and can't be recreated at will. Especially if it's an issue with my hardware/software (which is the most likely case). However, I also can't blame my GPU because the other people who had crashing issues with adaptive sync enabled were Samsung G9 owners with 3000 series Nvidia GPUs. So it's more likely that this is a driver bug rather than a hardware thing. I am currently testing it without the second monitor plugged in and no crashes so far with G-Sync on, but it's still too early to tell. I will update this thread accordingly whether it crashes again or not. In the meantime, if anyone has any insights to share, please do. Thank you.
-
Hi. As I mentioned, everything freezes. All peripherals stop working and eventually the sound from the speakers/headphones also goes away. Therefore, I don't believe this is a problem with the monitor specifically. Obviously Windows 10 stops functioning entirely and stops sending a signal to all connected devices. Question is why only with G-Sync enabled. It's possible that it's a bug with either Nvidia or Microsoft and G-Sync is crashing Windows 10. It's also possible that my PSU is faulty and can't deal with the fluctuations in power when G-Sync is on. It's even possible that my second monitor was causing this as other people with other monitors reported a similar issue with G-Sync failing if a second monitor is plugged in a while ago. I'm still testing everything but I'm looking for feedback from other people who have had a similar experience.
-
ASUS ROG Swift PG279QM Questions
Referi Jerator replied to Referi Jerator's topic in Troubleshooting
UPDATE FOR ALL PG279QM OWNERS: I found the solution for the locked six-axis saturation setting. If it's locked for you, it means you are either using the default Racing Mode GameVisual or the sRGB one. In order for the axis setting to unlock you must use any other GameVisual (Scenery, Cinema etc.). Hope this helps you, but I'm still looking for your insight regarding the other two questions. Thank you. -
ASUS ROG Swift PG279QM Questions
Referi Jerator replied to Referi Jerator's topic in Troubleshooting
Hello. Are you also unable to see the 3 darkest squares on lagom? Thing is, people who also claimed they can't see them said they fixed the issue by calibrating the axis setting but since it's locked for me I can't do that. Funny because supposedly this monitor is pre-calibrated from the factory and even comes with a calibration report. -
Hello, I've a few questions for PG279QM owners: On lagom.nl's black level test, are the top left 3 darkest black squares normally invisible? I researched this and apparently a lot of other people also had the same thing happen. Is this just how this monitor is? Note: With dark level set to 2 I can see the third square, and on level 3 it appears very clearly. However, regardless of the dark boost level the first two remain invisible. The auto SDR brightness setting makes the monitor's brightness quite dark. Even using a flashlight right on top of the ambient sensor only achieves a slight increase in brightness. Is that the same for you too? What's up with the Six-axis Saturation on the OSD being locked? I can't find a way to unlock it. I'm only using the factory settings (Racing Mode, HDR off). No HDR or sRGB GameVisual which lock some settings. UPDATE FOR ALL PG279QM OWNERS: I found the solution for the locked six-axis saturation setting. If it's locked for you, it means you are either using the default Racing Mode GameVisual or the sRGB one. In order for the axis setting to unlock you must use any other GameVisual (Scenery, Cinema etc.). Hope this helps you, but I'm still looking for your insight regarding the other two questions. Thank you. Thanks.
-
I still need help please.
-
Still looking for help with this.