F5F Stay Refreshed Hardware Desktop Sure, I can assist with that. Let me know what you need help with regarding your new display setup.

Sure, I can assist with that. Let me know what you need help with regarding your new display setup.

Sure, I can assist with that. Let me know what you need help with regarding your new display setup.

C
chikimonster
Member
151
06-21-2016, 04:16 AM
#1
I recently installed a new display, the LC-M27-FHD-165-C-V3 from LCPOWER. When connected to my NVIDIA GeForce GTX 670 via DP, it functioned properly at 60 Hz. Adjusting the refresh rate in Windows caused the monitor to go black until about 20 seconds passed before reverting. I also tested through the NVIDIA control panel, but the issue persisted. A second monitor connected via HDMI worked fine, allowing a smooth change from 60 to 75 Hz, and the surround sound also operated normally. However, the display remained unresponsive when trying to alter the refresh rate beyond 60 Hz or up to 100 Hz. Windows indicated I had the latest drivers, though no updates were available for my GPU. The most recent driver I downloaded didn’t resolve the problem. Any solutions or workarounds are you looking for?
C
chikimonster
06-21-2016, 04:16 AM #1

I recently installed a new display, the LC-M27-FHD-165-C-V3 from LCPOWER. When connected to my NVIDIA GeForce GTX 670 via DP, it functioned properly at 60 Hz. Adjusting the refresh rate in Windows caused the monitor to go black until about 20 seconds passed before reverting. I also tested through the NVIDIA control panel, but the issue persisted. A second monitor connected via HDMI worked fine, allowing a smooth change from 60 to 75 Hz, and the surround sound also operated normally. However, the display remained unresponsive when trying to alter the refresh rate beyond 60 Hz or up to 100 Hz. Windows indicated I had the latest drivers, though no updates were available for my GPU. The most recent driver I downloaded didn’t resolve the problem. Any solutions or workarounds are you looking for?

R
raza987654321
Junior Member
8
06-22-2016, 06:58 AM
#2
The GTX 670 with HDMI 1.4a and DisplayPort 1.2 support should handle a refresh rate above 60Hz at 1080p when using a quality cable. Test by using the LCPOWER display at a higher refresh with HDMI. If successful, the DisplayPort cable may be the issue. Otherwise, reach out to LCPOWER for help since they guarantee proper operation.
R
raza987654321
06-22-2016, 06:58 AM #2

The GTX 670 with HDMI 1.4a and DisplayPort 1.2 support should handle a refresh rate above 60Hz at 1080p when using a quality cable. Test by using the LCPOWER display at a higher refresh with HDMI. If successful, the DisplayPort cable may be the issue. Otherwise, reach out to LCPOWER for help since they guarantee proper operation.

C
clecle23
Junior Member
49
06-24-2016, 12:07 AM
#3
It seems your setup might be linked to your profile picture and Ryan George. You could test an Ubuntu USB installer to check if Linux affects your monitor's behavior. If not, try connecting via HDMI. Another possibility is that your DP cable lacks sufficient bandwidth for signals above 60Hz, though this appears unlikely. Good luck!
C
clecle23
06-24-2016, 12:07 AM #3

It seems your setup might be linked to your profile picture and Ryan George. You could test an Ubuntu USB installer to check if Linux affects your monitor's behavior. If not, try connecting via HDMI. Another possibility is that your DP cable lacks sufficient bandwidth for signals above 60Hz, though this appears unlikely. Good luck!

X
220
06-24-2016, 04:44 AM
#4
Your display features an HDMI connection. Link your GTX 670 using HDMI and observe the results. This will help identify the problem more clearly.
X
xXStrikeBackXx
06-24-2016, 04:44 AM #4

Your display features an HDMI connection. Link your GTX 670 using HDMI and observe the results. This will help identify the problem more clearly.

M
Marinated
Senior Member
666
06-24-2016, 05:08 AM
#5
Surprisingly, the cable ID wasn't clear to me, but it still worked.
M
Marinated
06-24-2016, 05:08 AM #5

Surprisingly, the cable ID wasn't clear to me, but it still worked.