Samsung Odyssey G95NC no picture after R615? Get 617.14

Published September 28, 2026 by OmniMend

Unbranded PC with a dark ultrawide monitor and a working fallback display showing an HDMI recovery path

Scope. Use NVIDIA's fixed-driver path only when a Samsung Odyssey G95NC is connected over HDMI to an NVIDIA GPU on Windows, the screen lost its picture after an R615 driver update, and you still have a safe way to see or control the PC. Keep the fallback path connected, install official driver 617.14 or a later compatible official release that includes the fix, restart, confirm the installed version, and test the same HDMI state once. Another monitor, DisplayPort, another driver branch, or a screen that remains dark needs a broader diagnosis.

Protect the only working display path. Do not uninstall the current driver when the G95NC is your only display and you have no verified fallback. Do not use an unofficial driver package, DDU, registry edits, firmware flashing, or a workplace policy bypass as the first response. Do not hot-plug a damaged cable or port. Shut down and disconnect power if you notice smoke, sparks, burning odor, liquid, severe heat, or physical port damage.

Match all five parts of NVIDIA's fixed bug

NVIDIA's 617.14 release notes name a narrow no-picture failure. Confirm the product, connection, graphics vendor, platform, and timing before treating the driver as the cause.

Check	Required match	If it differs
Display	Samsung Odyssey Neo G9 57-inch G95NC.	Use the actual display model's support path.
Connection	HDMI from the NVIDIA GPU to the G95NC.	DisplayPort or an adapter adds a different branch.
Computer	Supported NVIDIA GPU on Windows 10 or 11.	Use the platform and graphics-vendor guidance for the actual system.
Timing	The G95NC lost its picture after an R615 driver update.	Do not assign NVIDIA bug 6771206 from a dark screen alone.
Symptom	No picture on the G95NC over HDMI while the PC otherwise starts.	No power, visible damage, boot failure, or failure on every display needs another diagnosis.

Samsung lists the US G95NC as model LS57CG952NNXZA. Check the label or the monitor's information screen when accessible. Similar Odyssey names and sizes do not establish the same bug.

Keep a fallback display or remote path

Leave a working secondary monitor or TV connected while you repair the driver path. If you rely on remote access, confirm that it works before changing anything and that the device is authorized for remote support. A fallback should show the Windows desktop and allow you to read the installer result after restart.

If the G95NC is the only display and the screen is completely dark, do not work blind through memorized clicks. Power down normally when possible, connect a known-good display through a supported output, and confirm access first. If you cannot establish a safe fallback, use local technical support instead of removing the current driver.

Record the driver, cable path, and timing

Write down the Windows version, NVIDIA GPU model, installed driver version, G95NC model, selected monitor input, and exact HDMI path. Include any adapter, dock, receiver, switch, or capture device. Note whether the failure began during the driver installation, after the restart, or at the next wake or boot.

Read the driver version in the NVIDIA App, NVIDIA Control Panel system information, or the display adapter's Driver tab in Device Manager. Keep a screenshot or written record. "Latest driver" and "recent update" are too vague to match the R615 report.

If Windows is unstable, every display is dark, or the PC no longer reaches the desktop, use the driver update recovery guide. That condition exceeds the narrow external-monitor fix.

Install NVIDIA's official 617.14 driver

NVIDIA published Game Ready Driver 617.14 on September 22, 2026. Its release notes list G95NC no-picture behavior over HDMI after an R615 update as fixed under bug 6771206. Use the NVIDIA App or NVIDIA's official driver page. Choose 617.14 or a later compatible official release that still carries the fix for the GPU and Windows version.

Computer makers and workplace administrators may control the supported graphics package. Follow the manufacturer's instructions or the organization's software process when the system uses customized or managed drivers. Do not force a generic package past that boundary.

Close graphics-heavy work and save open files. Keep the PC on reliable power and keep the fallback display active. Read the installer result. If the official package fails or reports incompatible hardware, stop and use the NVIDIA driver installation guide rather than repeating the installer.

Restart, read back the version, and retest once

Restart Windows after installation. On the working display, confirm that 617.14 or the chosen later compatible release is installed. Then select the same HDMI input on the G95NC and repeat the original connection test without changing the cable, adapter path, resolution, or refresh rate.

Record whether the G95NC now shows the desktop, remains dark, displays a no-signal message, or appears in Windows without a picture. One successful retest supports the vendor's fixed-bug match. It does not prove that another display problem has the same cause.

What if the G95NC still has no picture?

Stop repeating driver installs. Verify the installed version, monitor input, power state, direct HDMI path, and cable condition. If safe and available, test one known-good HDMI cable and one direct GPU connection without a dock, switch, receiver, or adapter. Keep the fallback display connected until the G95NC path works consistently.

If the monitor is detected but stays dark, or if a known-good cable and fixed driver do not help, follow the external monitor guide. Visible connector damage, liquid, odor, heat, sparking, or failure to power on needs hardware inspection, not another software change.

Keep the DisplayPort wake bug separate

NVIDIA's 617.14 release record also lists a separate open issue, bug 6757568, involving monitors that may fail to wake over DisplayPort after sleep. That is not the fixed G95NC-over-HDMI bug. Connection type, sleep timing, and driver version decide which branch applies.

A cable swap from HDMI to DisplayPort may therefore exchange one symptom for another rather than test bug 6771206 cleanly. Preserve the original connection record and change one variable at a time.

Use OmniMend only for the remaining evidence

NVIDIA controls the driver and fixed-bug record. OmniMend does not install the driver, control the monitor, flash firmware, change a cable or port, bypass managed policy, or guarantee that a display will return.

On a supported Windows 10 or 11 x64 PC with a working display path, OmniMend can collect and organize local Windows, graphics, driver, display, update, and event evidence when the version match is unclear or the G95NC remains dark. Diagnosis starts read-only. Any supported change requires approval and a result check.

If you need that evidence record, review OmniMend's diagnostic scope or download OmniMend. Keep passwords, account tokens, personal documents, and private support details out of any shared report.

Editorial sources

Checked September 28, 2026 against NVIDIA's Game Ready Driver 617.14 page, 617.14 release notes, and official 617.14 feedback thread, plus Samsung's US G95NC product page. NVIDIA supplies the R615 timing, G95NC-over-HDMI boundary, bug 6771206, 617.14 fixed release, and separate DisplayPort wake issue 6757568. Samsung supplies the US model identity. OmniMend added the fallback-display requirement, evidence record, controlled retest, unmatched-symptom routes, and product boundary. No source proves that every G95NC black screen has this cause or that the fixed driver repairs a cable, port, firmware, power, or hardware fault. OmniMend and Psynect Corp are not affiliated with NVIDIA or Samsung.