[SOLVED] Why do 151...169 Hz not work but 170 Hz works?

[Beginner Macro Device]

The monitor in question is MSi G2712. RX 6700 XT is the GPU in question as well. The monitor is connected via DP, FreeSync is enabled. DP overclocking is also enabled.

I can work just fine with 170 Hz, also not a single issue working with 150 Hz, yet 151 to 169 Hz range goes black screen if this is the exact RR I enable via Windows settings. Running, say, 160 FPS in game when I set the screen to work at 170 Hz is going with no hinch so there's no real problem going on.

It's just me experiencing SLIGHTEST of smearings at 160+ Hz but 160 sharp is still a tad better than 150. I'm currently dirtyhacking it via capping games to 160 FPS but I can't cap my desktop the same way. Response time calibration doesn't solve this. It's either too slow or too fast at 170.

WHY? What can I do to lock my display to 160 Hz?

 

[kiddagoat]

You have FreeSync on. I would just cap the FPS of games to 2-3 frames below the refresh rate. The monitor will report what refresh rates it supports. Anything outside of what is reported by the monitor isn't supported.

 

[Beginner Macro Device]

PRETTY PLEASE TRY READING WHAT I WROTE.

 

[Onasi]

My theory is that the base refresh of the panel is lower and 170Hz is an MSI OC with probably non-standard timings which might explain this behavior. Yes, I know that MSI themselves don’t advertise it as an OC, but 170 is not a common standard refresh for panels. This is just speculation, mind, since I cannot find the actual panel model for this display, so it’s impossible to confirm or deny.
Not sure if you tried, you haven’t mentioned in the OP, but you can try messing around with CRU and see if it gets you anywhere.

 

[Beginner Macro Device]

you can try messing around with CRU

Completely forgot about it. Will do later tonight.

 

[kiddagoat]

What I am referring to the Extended Display Identification Data - Wikipedia

This will tell you what is reported by the firmware of the monitor.

 

[Beginner Macro Device]

and see if it gets you anywhere.

Case solved but it's still a mystery to me. Why did it not work from Adrenalin?

 

[Onasi]

@Beginner Macro Device
Probably has to do with scuffed/incorrect values (or outright lack of a proper 160Hz mode) by default in MSIs base EDID, like @kiddagoat said. These things happen. With CRU you edited said EDID and perhaps the values it set were more palatable for the firmware/panel/Allah/whatever. In this case I’d just say job’s done (zug-zug) and not fuss too much about the “why’s”.

 

[Beginner Macro Device]

job’s done (zug-zug)

I prefer StarCraft...

But thanks.