Idk if the model we have is the same, but heres the one i have : Samsung G9 Neo LS49AG950NEXXY
with the exact same issues… Some of the things i would suggest doing if you havnt already to alleviate some of the issues are :
Make sure that windows and all of its drivers are up to date! Using CCleaner,steam driver updater, and intel driver updater seems to get basically everything updated.
- Factory reset the monitor
- Use a Vesa Certified 8k DisplayPort 2.1 Cable for the best results and to improve performance even though the cable is kind of overkill.
- https://nvidia.custhelp.com/app/answers/detail/a_id/5411/?=&linkId=100000163736896
- go in and fine tune all the settings in Nvidia Control centers 3D settings. Making sure to turn off Vsync, and enable Gsync.
“Ill be including my settings down below”
- it will help get rid of scan-lines! I would also suggest utilizing some of the other calibration tools on the site once you do finish everything here 😊.
- The last main thing will be calibrating your monitor settings directly!
- Your going to want to use the scan-line calibration tool as much as you can with this particular monitor as it can be hard to tune.
- I will be providing all of my settings for this below as well!
Now if your really adventurous one last thing you can try is using Nvflash to flash your gpu vbios.
“During some of my research while trying to figure out the boot loop issue i found a post saying that this could potentially fix the boot loop as well as some of the other issues present as well as improving stability if done correctly.”
- “this can be potentially dangerous by bricking your gpu bios if done incorrectly… so research it extensively before attempting.
“fyi Im using watercooling so if your running air cooled it might be safer to boot to a newer version of your own GPU’s Vbios!
————————————————————————————————————————
For Nvidias control panel settings this is what i was able to tune the monitor to:
Sidenote:i will be skipping listing any settings that dont affect the calibration of the monitor!
- Change Resolution Tab:
- Under Pc :
- 5120x1440
- Refresh rate 240
- Adjust desktop color settings
- Change colors: all channels
- Brightness:60%
- Contrast:67%
- Gamma:1.00
- Digital vibrance:92%
- Hue:18%
- Set up G-Sync
- Enable G-Sync,G-Sync Compatible
- Enable for windowed and full screen mode.
- Under Nvidia Color settings :
- Desktop color depth: 32-bit
- Output color depth: 10bpc
- Output color format: RGB
- Output Dynamic Range: Full
Monitor Settings that worked and were stable/tuned with the scan-line utilities/a few other ones on the site:
- Under Game:
- Refresh rate: 240
- Response time: Extreme
- Adaptive-Sync: Off
- Low input lag: On
- Black Equalizer: 14
- Virtual Aim point: Off
- Infinity Core lighting: Rainbow
- “idk what this setting does…”
- Screen size: Wide
- Picture Mode:Custom
- Brightness: 100
- Contrast: 100
- Sharpness: 100
- Eye saver mode: Off
- Color:custom
“Oddly enough having red,green,blue at 100 had similar results on the scanlines, but 50 was slightly more stable”
- Red: 50
- Green: 50
- Blue: 50
- Gamma: Mode-1
- Saturation: 50
PIP/PBP: off
- System
- Local Dimming: Off
- Dynamic Brightness: Off
- DisplayPort Version: 1.4
- Auto-Source Switch+
Sadly even with everything I’ve detailed above, it hasn’t fixed the two major issues for me but heres my workarounds till they are fixed:
- Boot loop when monitor is running at 240Mhz during boot.
- Fix:
- turn monitor off until the pc gets to lock screen, and then turn it back on!
- Intermittent black screen:
- Solution:
- press in this order: 1.Control 2.Shift 3.Windows Key 4. B
“Not entirely sure what is causing this particular issue. However what this does is refreshes the display driver. Which if the issue is the monitor it will fix the black screen issue!”
I hope that at least one of these solutions helps in some way, or is at least a stepping stone to hopefully figuring out how to solve the issues if they even can be solved without Samsung taking their ***** time to release an update for the display firmware that probably wont actually fix the issue, and has basically no documentation on what was changed or fixed…
