Issue #1 - 144hz refresh rate was missing in windows (Win10 x64) if FreeSync was enabled for the monitor
Solution: Update the Monitor Software/firmware. original software was version 1004.0, upgrade to 1009.1 resolved the issue and remained resolved moving to 1012.2, 1013.0, and 1016.2 as well.
The path to knolwledge: Hooking up a brand new C32HG70 to a new AMD Rx Vega 64, and windows 10 x64 Enterprise saw the max resolution as 120hz.
Initially to me, the symptom seemed to be that the PnP Monitor default options (60hz, 100hz, and 120hz) when I first plugged in the monitor were maintained even after I download and installed the C32HG7xQQ driver (Mar-2017)... so it almost looked like the driver didn't fully install... well didn't solve the issue anyway.
I tried a new DP cable that I purchased, tried uninstalling/reinstalling monitor drivers, even uninstalled/reinstalled AMD's drivers... all ended up with 120hz being my cap. Then tried lowering the resolution from 1440P to 1080p... still 120hz max.
Finally I thought I'd try disable FreeSync in the monitor settings... and low and behold 144hz finally showed up in windows. Enabled monitor Freesync standard engine again and 144hz dropped off... even tried FreeSync ultimate engine and 144hz was still no where to be seen.
The monitor's OSD always showed 144hz even in freesync mode, it just doesn't translate that to the OS. The end result is that many games (like Grim Dawn) give a list of resolutions/frequencies to pick from in their settings... and they typically inherit windows display settings.... so if the OS doesn't see 144hz as an option, neither does the game.
I did a software/Firmware update from 1004.0 to 1009.1 and 144hz started working like it should!
Issue #2 When I first plugged in my monitor, I noticed the display was heavily inspired by red, and looked rather pinkish.
Solution: Set 6500K color temp in Radeo Settings for monitor.
The path to knolwledge: This was resolved by trial and error (really by accident) of various settings while playing with various settings in Radeon Settings. I've been using intel/nvidia based systems for at least the past decade, so I had alot to learn and experiment with in Radeon Settings. Was very happy to discover this setting. I will also note that some changes I've made while learning (more related to uninstalling/reinstalling drivers) that this 6500K color setting can get lost... so always remember to check it if you notice the pinkish color came back.
Issue #3 There seems to be many threads where people are trying to using the wrong firmware/software version, thinking that the 27" and 32" versions are identical. Often the reported symptom when flashing the wrong firmware is that the display got dimmer.
Solution: Only use the Monitor Software/firmware that matches your monitor.
- http://www.samsung.com/ca/support/model/LC27HG70QQNXZA lists the latest 27" Firmware as 1016.2
- http://www.samsung.com/ca/support/model/LC32HG70QQNXZA lists the latest 32" Firmware as 1016.2
The path to knolwledge: My original software was version 1004.0, and I have upgraded to 1009.1, 1012.2, 1013.0, and 1016.2 without noticing any dimming. All versions specific to my 32" monitor, never renaming a 27" file. I will also provide a quote from the manual related to "dimming"/brightness... "If Response Time is set to Faster or Fastest mode, a decrease occurs in the screen brightness. This is a normal phenomenon and not a product malfunction."
Issue #4 I've read another thread that suggested FreeSync2 may become disabled for this monitor, and what worried me was that it would be delivered by software/firmware update. To me, the real issue here is that Samsung does not provide a change log for their updates so we can see what is changing.
Solution: I don't have one, Samsung would need to provide.
The path to knolwledge: Specific to the FreeSync2 "concern"... as mentioned above, my original software was version 1004.0, and I have upgraded to 1009.1, 1012.2, 1013.0, and 1016.2. With 1012.2, 1013.0, and 1016.2, I do know that I finally paid enough attention to see the FreeSync2 logo slapped on the drawn monitor. So if there is a plan to disable FreeSync2, I assume the inclussion of the logo means it's still active/enabled for 1012.2, 1013.0, and 1016.2 (and I assume for the 1004.0 and 1009.1 versions before it). Kind of sad if I'm pinning my hopes/faith to a logo.
Issue #5 I'm beginning to learn that the Freesync range for this monitor is rather "shallow". The impact is that you'd need to get fairly high FPS to see the freesync kick in, but one could argue that if you had the killer framerates to begin with, was FreeSync really required? Seems that the current shallow freesync range is a pretty big miss.
Solution: The full 48-144hz freesync range is now enabled with the 1016.2 montior firmware!
The path to knolwledge: I wish I knew that hoving my mouse over the Radeon Settings Freesync "badge" would have told me the range when I was back on earlier versions of the monitor firmware, but I can tell you know that with 1013.0 that the FreeSync range is 72-144hz (using Ultimate Engine; Standard Engine is 120-144)... and according to a reddit post, this change likely started back with 1009.1.
I have some pretty aggressive game settings enabled that drop me below 72hz at times (highest settings), but I have two changes happening that will likely increase my minimums. The first is a client update I know is coming to ESO to increase their frame rates (my current game of choice)/ The second is a planned upgrade to my system memory. The old DDR4 RAM I used for my Threadripper is clocked at 2133, and I'd like to get a new kit in the 3200+ range. Based on a post I read (and my memory), one person claimed that the Infinity Fabric improvements moving from 2133 to 3000 brought about 30% increased frame rates. Even if that's only 1/3 true (10% increase), that could be just enough to keep me in the bottom-mid of the 72-144hz range for FreeSync at all times... and perhaps closer to the mid-top of the range depending on what ESO delivers with their client FPS improvement promise. And I guess I should not discount the role played by improvements to the Rx Vega 64 drivers over time, as well as my continued tinkering with Wattman.
Solved! Go to Solution.
I am experiencing color distortion (lines) at the bottom of the screen when starting up the monitor. I can either play with the black level settings (switching it from 20 to 13 response time) to make it go away or wait for it to go away on its own. Will the firmware update resolve this issue?
Hello, I am experiencing distortion (color lines) at the bottom of the screen when I initiallly start the monitor. This was after about a month of use. Sometimes it will reset (go back to normal) if I toggle between the 20 and 13 response time...or I have to wait until it disappears on its own. Will the firmware update solve this? Thanks.
New to gaming monitors, hoping for some help/direction.
I just purchased this monitor for my Xbox one X, but when I attempt to calibrate I have issues. I’m at 1440p, 36 bits per pixel (12 bit) and PC RGB color space. When using the calibration tool in Xbox I can’t see the “closed eye” in the brightness calibration step. If I switch to Standard color space I can see the closed eye but I can’t get it to disappear when adjusting the brightness.
any help appreciated.
Yes lol. Just got it yesterday. Why? No reason. It doesn't even have a description but was hoping it would make hdr more compatible with things.
From what the rep said it will make freesync better and add performance to the monitor. Basically giving me no useful info, it isn't broken tho and works fine so if you like updates go for it.
Nice post. Thanks! Another thing I faced is problem with firmware update. There are two things which are don't allow to upgrade firmware:
1) usb hub. I had to unplug it before was able to init upgrade process
2) only usb 2.0 supported with FAT/NTFS fs
I've tried several USB sticks with the m-HG732CCAA-1016.2[2EB6].bin by itself formated with FAT32/FAT/NTFS. I have the USB hub/cable unplugged to the PC but it always says no valid file found.
I'm finding that with this monitor, it almost seems like there are drop shadows on text. Also seems like it's horizontal scan lines. Text isn't very crisp and clear like I thought it would be. I have ClearType text enabled and tweaked.
UPDATE: I think you will get this kind of error if your firmware file you already have matches the newest .bin file on the USB stick. Others have reported that they simply rename the firmware file for their specific model to a higher number and it will see it. I would say do NOT rename the 27" firmware to the 32" firmware name either. Seems this has caused heat issues for others that did this.