No signal issue on Arc 770

[Deximy]

Hello team,

I have met this issue for a long time since I bought A770 in Nov, 2023.

Environment:

CPU: Intel 14900K

MotherBoard: ROG STRIX Z790-A GAMING WIFI

BIOS version: latest (v1801, released on 12/8/2023)

Monitor: Sansung NEO G8

Graphics card: Arc 770

Graphics driver version: latest (v31.0.101.5186, released on 1/18/2024)

Issue Description:

There are two possible symptoms:

In the most time, the monitor will show "No signal" after Windows awakes from sleep. The workaround is hitting the on switch.

Sometimes, the issue will be worse. I can't find any possible way to restore the output. Here are some methods I have tried: 

• hitting the on switch
• switch to HDMI (I am used to use DP as it can support 4K 240HZ display)
• use another cable
• turn off and then turn on my monitor
• reinstall driver with clean mode

All those attempts fail. The only way to restore the output is to reboot the system.

I didn't use any other graphics cards, so it is possible that the issue is caused by driver confliction.

Please let me know how can I troubleshooting this issue as it has bothered me for such a long time. Thank you for your assistance.

[MUC]

Please create a Report for Intel Graphics Drivers and attach the output file here.

[Deximy]

I have uploaded it below.

[Deximy]

got it.

[MUC]

According to the operating instructions (attached), the following applies to the Samsung Odyssey Neo G8:

Vertical Frequency 48 <> 240Hz

Optimum resolution 3840 × 2160 @ 120 Hz

Maximum resolution 3840 × 2160 @ 240 Hz

	Video Timing	H Freq [kHz]	Pixel Clock [MHz]	Sync Polarity H/V	Required bandwidth (10 bpc) [Gbps]	Required bandwidth DSC 3,75:1 [Gbps]	Required bandwidth DSC 3:1 [Gbps]
3840 × 2160 @ 120 Hz	CTA-861	270	1188	+/+	40.09	(10.69)	(13.36)
3840 × 2160 @ 240 Hz	Samsung	540	2376	+/-	80.18	21.38	26.73

The Report for Intel Graphics Drivers shows the capabilities of the display with a preferred maximum of 3840 × 2160 @ 60 Hz.

• Which graphics card do you have exactly (brand and model)?
  
  
• Was the connection type DisplayPort or HDMI when the report was created?
  
  
• Please repeat the report creation with DisplayPort connection type while 240 Hz refresh rate is activated on the monitor:
  
  
  
• Please also create a Report while HDMI connection type is in use (@ 120 Hz).

[Deximy]

Thank you for your assistance.

1. GUNNIR Intel Arc A770 PHOTON 16G OC W X ASIAN GAMES

2. Attached in this reply.

Please note that when I created the report with HDMI, I didn't drop the DP cable, so it showed that there were two monitors called Odyssey G8.

The report named after DP means I generated this report with DP mode activated and HDMI one means HDMI mode activated.

[MUC]

According to the manufacturer, the graphics card only features an HDMI port version 2.0. This means you can output a maximum of 4K @ 60 Hz RGB 8-bit via this port. HDMI 2.1 is not natively supported on the Alchemist DG2 architecture. There are other cards that have a Protocol Converter (PCON) chip on the printed circuit board for this purpose:

The DisplayPort connections support the HBR3 protocol with Display Stream Compression (DSC). The diagnostic files show that the monitor reports via the Extended Display Identification Data (EDID):

Detailed Timing Descriptor: 3840 × 2160

Hfront 176   Hsync 88    Hback 296    Hpol P
Vfront 8        Vsync 10    Vback 72       Vpol P
Display Range Limits: 68-240 Hz V, max dotclock 2380 MHz

Vendor-Specific Data Block:
Version: 2.15
Minimum Refresh Rate: 68 Hz
Maximum Refresh Rate: 240 Hz
Maximum luminance: 139 (1015.241 cd/m²)
Minimum luminance: 6 (0.006 cd/m²)
Maximum luminance (without local dimming): 90 (351.250 cd/m²)
Minimum luminance (without local dimming): 10 (0.005 cd/m²)

This looks good.

Please use a high-quality DisplayPort cable that is not too long but not too short either. Recommendation would be between 2 and 3 meters (6 - 12 ft). Does the monitor use the latest firmware available from Samsung?

[Deximy]

Thank you for your update.

1. I have tried three different cables and it was no help to this issue.

2. Found I was using the old version of firmware. I will have a try and will update if the issue happen again in this thread.