UNSOLVED

MARKXIII

updated

3 months ago

M

MARKXIII

1 Rookie

•

3 Posts

•

2 Points

0

104

September 17th, 2025 12:14

Dell XPS 15 7590 – No HDMI signal on Dell P2723D monitors

Hello,

I have a Dell XPS 15 7590 and I’m using multiple external monitors in different locations.

  • At work, I use a Samsung U32R590 4K, which works perfectly when connected directly via HDMI from the laptop to the monitor.

  • At home, I have access to two Dell P2723D monitors (one mine and one my brother’s). With both monitors I experience the same issue when trying to connect them directly via HDMI from the laptop.

If I connect through a Dell WD19S Docking Station, everything works fine. This means:

  • the HDMI cables are working,

  • the monitors are working,

  • the laptop is working,

  • but there seems to be a specific issue only with direct HDMI connection between Dell XPS 7590 and Dell P2723D.

When I connect the laptop directly via HDMI, Windows does detect the monitor (in Display Settings it shows up as “Display 2” and I can change the resolution), but the monitor itself shows no image. The P2723D displays the following sequence:

  1. Scanning for signal

  2. No HDMI signal from your device

  3. Going into Standby mode

I have already installed the latest drivers and BIOS updates. I’ve been dealing with this issue for a couple of weeks and finally decided to ask for help here.

Thank you all in advance!

  • ejn63

    12 Elder

    •

    31856 Posts

    •

    156298 Points

    0

    0

    Posted September 17th, 2025 12:49

    One high resolution monitor will be OK with that dock, but two will not -- the bandwidth of the dock is insufficient to drive two high resolution monitors.

    That dock is USB, not Thunderbolt.  If you want two high resolution displays, you will need a WD19T (or a newer T model).

  • MARKXIII

    1 Rookie

    •

    3 Posts

    •

    2 Points

    0

    0

    Posted September 17th, 2025 15:39

    Thank you for your answer, but I think I need to clarify.

    At work, I don’t use a docking station, and at home I would prefer not to either, although at the moment I have to. At home I only use one monitor, not two (one is mine and the other is my brother’s—he uses a ThinkPad, and both monitors work fine with his laptop). I’ve tested with different monitors, HDMI cables, and other laptops, so I know the hardware is working properly. What I’d like to know is what I can do to avoid using a docking station at home when connecting to a P2723D monitor.

    (edited)

  • DELL-ChrisM2

    Community Manager

    •

    1995 Posts

    •

    10006 Points

    0

    0

    Posted September 17th, 2025 15:53

    * Turn the P2723D off
    * Turn the XPS 15 7590 off

    * Disconnect every cable (including power) and peripheral device from the P2723D
    * Press and hold in the power button for 8 seconds
    * Reconnect only the power cable and HDMI cable to the P2723D

    * Disconnect/reconnect the provided AC power cable to the XPS 15 7590 left side power port and HDMI cable

    * Turn the XPS 15 7590 on
    * Turn the P2723D on

    What happens?

     

    #IWork4Dell

  • MARKXIII

    1 Rookie

    •

    3 Posts

    •

    2 Points

    0

    0

    Posted September 17th, 2025 21:45

    @DELL-ChrisM2​ 
    Thank you for the suggestion and the detailed description. I tried several times, but nothing has changed. I can only add that when I connect the HDMI cable to the computer or turn on the monitor, Windows makes the usual sound indicating that a device has been connected. In the display settings I can see the device, and I am able to change the refresh rate of the P2723D monitor to 60.011 Hz, 59.998 Hz, 59.951 Hz, or 59.938 Hz and nothing helps.

    (edited)

  • kalash969

    1 Rookie

    •

    1 Message

    •

    5 Points

    0

    0

    Posted August 14th, 2026 11:59

    Hi, I want to add my case here as it might help pinpoint this — I'm having the exact same issue on a Dell XPS 15 7590 with a direct HDMI connection to a Dell S2421HN monitor, and I've done extensive troubleshooting today that rules out most common causes:

    Symptoms (identical to OP):

    • Windows detects the monitor correctly (correct name via EDID), shows it as active in Display Settings, allows resolution/refresh rate changes
    • Monitor itself shows "No signal" / goes to standby
    • Connection sound plays on plug/unplug — Windows registers the hot-plug event

    What I've already ruled out:

    • Not the cable — same cable works fine on a different laptop
    • Not the monitor — confirmed with a Linux Live USB (Ubuntu) — HDMI output works immediately, no extra steps, no driver installation. This strongly suggests the HDMI hardware path (TMDS lines) is fully intact, and this is a Windows/driver/firmware-specific issue, not a hardware fault.
    • Not GPU drivers — tried both Intel.com and Dell.com Intel UHD 630 drivers (different versions), same result
    • Not Windows itself — tested in Safe Mode (basic VGA driver) — still no signal, which rules out the "advanced" Intel driver output path as the sole cause
    • Not color format/HDR — checked Intel Graphics Command Center, RGB/8-bit, nothing "fancy" enabled
    • Not EDID corruption — checked with CRU (Custom Resolution Utility), no extension blocks, EDID looks clean
    • Not a fresh-install artifact — this started after a BIOS update roughly a year ago (BIOS was ~2021/2022-era at the time), and persisted through a full clean Windows 10 reinstall via Dell OS Recovery
    • Current BIOS: 1.35.0 — cannot downgrade below 1.32.0 due to Dell's anti-rollback protection on security-patched versions

    Workaround confirmed (matches OP's docking station finding):

    • USB-C/Thunderbolt output works perfectly — same monitor, same laptop, just via Thunderbolt/USB-C-to-HDMI instead of the direct HDMI port

    This points to a Windows-side (driver or GOP/firmware) issue specific to the direct HDMI port on the XPS 15 7590, independent of monitor model (P2723D for OP, S2421HN for me) — since it reproduces cleanly on Linux without issue. Would appreciate if this could be escalated as a firmware/driver bug rather than treated as a monitor/cable/EDID problem, since we've now got at least two independent reports with overlapping symptoms.