Poll: ** LG 27GP950 AVAILABLE TO PRE-ORDER NOW - LIMITED AVAILABILITY **

Do you have any black screen issues?


  • Total voters
    78
  • Poll closed .
Had mine for a week and so far no black screens. Only problem so far is the software OnScreen Control & LG Ultragear Control Center cannot detect the monitor under Windows 11. Tried it on my wife's Windows 10 PC and the software works as expected. I've been corresponding with LG but they don't have an answer and when I asked about beta software for Windows 11, they said they didn't have access! With just under a month until launch I expect new software pretty soon.

With yourself not having any issues I can understand you wouldn't normally come into a thread saying I don't have issues.

But the users coming along voting yes without any feedback is abit odd.

The more user input the better chance we might actually get a fix.

Anyway can I ask you are you using the stock cable? Displayport? And if not what length and manufacture are you using?
 
With yourself not having any issues I can understand you wouldn't normally come into a thread saying I don't have issues.

But the users coming along voting yes without any feedback is Anyway can I ask you are you using the stock cable? Displayport? And if not what length and manufacture are you using?
I’m using a 2mtr DP2.0 cable from JupptElectronics. Over the top yes but it works perfectly.
 
was wondering about this myself, been going back and forth on buying a 30 quid 2.0 cable from another supplier as the ones on Overclockers only seem to be 1.4
After reading a Reddit thread on using a DP 2.0 cable I realised I had very little to lose. I paid £28.99 which isn’t cheap but it’s an exceptionally AMAZing cable ;-)
 
After reading a Reddit thread on using a DP 2.0 cable I realised I had very little to lose. I paid £28.99 which isn’t cheap but it’s an exceptionally AMAZing cable ;-)

I have read the same post it really does make sense.

I have spent abit of Google about cable length and if 4k 160hz Full RGB 10bit at 3m is pushing the standards of that cable abit to far.
You add in gsync and Freesync messing about with the frequency.

For a 3m DP 2.0 cable it would cost me £35 it's not something I am willing to do just yet.

Something I have noticed 160hz mode increases the black screen so again the theory of a DP 2.0 cable makes more sense.
 
After reading a Reddit thread on using a DP 2.0 cable I realised I had very little to lose. I paid £28.99 which isn’t cheap but it’s an exceptionally AMAZing cable ;-)


only real question for me is that or go for a hdmi 2.1 cable for a third of the price, reckon it's worth it for 4k 120hz hdr?
 
and on a related note, the availability of the high end cables on Overclockers seem to be non existant for both DP and HDMI, given that more and more of the high end monitors, graphics cards and even TVs that can use them it seems a bit strange.
 
Thanks for doing this I am interested in your findings.
What length cable are you using right now?
The included cable, this one:
- DISPLAYPORT CABLE E239426-Z AWM 20276 30V VW-1 I/II A/B FT1 HONGLIN LM
The one with "5K" on a label on one end. My wife's GN model has the same cable.

I did assume at the time that the cable provided would work fully...
 
The included cable, this one:
- DISPLAYPORT CABLE E239426-Z AWM 20276 30V VW-1 I/II A/B FT1 HONGLIN LM
The one with "5K" on a label on one end. My wife's GN model has the same cable.

I did assume at the time that the cable provided would work fully...

Probably does in lab conditions. Looks like a low end cable that just meets spec. Couple that with data running at or close to 1.4 limits and the slightest inteference could cause a wobble. This would be in line with reports earlier in the thread of removing inteference from local sources and cleaner power delivery to the monitor helping the issue
 
I am actually thinking about buying the 2.0 version because I have a feeling 3m 1.4 4k 160hz is pushing the limit resulting in black screens happening.
Don't forget DSC making every single bit error more destructive to signal, possibly and likely quite often corrupting multiple bits in decrompressed signal.
 
Don't forget DSC making every single bit error more destructive to signal, possibly and likely quite often corrupting multiple bits in decrompressed signal.

Good points maybe I should just run 1.4 without DSC and see. For defo running 160hz the issue is more likely to happen, where when I run 144hz I get a black screen a few times a week so random.

I have just now changed from Full RGB to ycbcr 422 10bit could this maybe help?
 
Back
Top Bottom