One DisplayPort Output, Two or Three Monitors? DisplayPort MST Daisy-Chaining, Bandwidth Sharing & Troubleshooting Explained

2026-10-25 ｜ GPU Repair ｜ About 19 minutes ｜ HK GPU Fix Editorial Team

重點摘要

One DisplayPort output can drive several independent monitors, but only through DisplayPort Multi-Stream Transport, where a hub splits one link into separate streams that share the same total bandwidth. This guide explains the topology, the bandwidth limit, and the step-by-step isolation that separates a configuration mistake from a hardware fault.

The Short Answer First

A single DisplayPort output can feed two or three monitors with different content on each screen, but that result is not automatic, and it is not achieved by splitting anything in the way most people first imagine. The technology is called DisplayPort Multi-Stream Transport, usually shortened to MST. In an MST arrangement, the graphics card sends several independent display streams down one DisplayPort link. A branch device — either a monitor with a built-in MST hub or a separate external MST hub — separates those streams and sends each one to its own monitor. Windows can then treat the monitors as an extended desktop, with different content on each screen.

That definition already excludes three common misunderstandings, and clearing them up first saves most of the wasted troubleshooting that follows. First, MST is about display signals, not about electrical power. It has nothing to do with a power cable split between two monitors, a power strip, or sharing one mains lead. A monitor that receives power but no signal, and a monitor that receives a signal but is set to the wrong input, are different problems, and neither is solved by thinking about power distribution. Second, MST is not a simple DisplayPort splitter that copies the same picture to two monitors. Copying the same picture to two screens is mirroring, or duplication, and it is a different mode with different limits; it is covered in the companion guide on duplicated output to a capture card, not here. Third, MST is not an HDMI feature. HDMI itself does not support this kind of daisy-chaining. Once a signal is converted to HDMI or DVI at the end of a chain, the chain ends there, and no further monitor can be chained from that converted output.

The single most important idea in the whole subject is the shared bandwidth limit. All the monitors on one MST chain share one DisplayPort link, and therefore share one total bandwidth budget. Adding a monitor does not add bandwidth. Raising the resolution, refresh rate, or colour depth of one monitor leaves less bandwidth for the others. When the combined demand exceeds what the link can carry, something has to give: a later monitor may not be detected at all, the system may drop resolution or refresh rate automatically, or only a lower combination of settings may work. Most MST failures that look like broken hardware are, on closer inspection, either a topology error, a setting that has not been enabled, or a combination of settings that exceeds the shared budget.

The Topology: Source, Branch, and Sink

Every MST arrangement can be described with three roles, and naming them correctly makes diagnosis far easier. The source is the device that produces the DisplayPort signal: usually a graphics card, or a laptop output that supports DisplayPort Alternate Mode over USB-C, or a Thunderbolt output, in each case as stated in the manufacturer's documentation for that particular device. The branch device is the device that splits the streams: either the first monitor in the chain, if it contains an MST hub, or a separate external MST hub. The sinks are the monitors that actually display a picture.

In a monitor-chained arrangement, the wiring runs in a strict order. The graphics card DisplayPort output connects to the first monitor's DisplayPort input. The first monitor's DisplayPort output then connects to the second monitor's DisplayPort input. If there is a third monitor, the second monitor's DisplayPort output connects to the third monitor's DisplayPort input. In an external-hub arrangement, the graphics card connects to the hub's input, and each of the hub's outputs connects to a separate monitor's DisplayPort input. Both arrangements are the same topology in principle; they differ only in where the splitting happens.

The decisive question in any chain is where the hub actually is. A monitor without a DisplayPort output can only ever be the last monitor in a chain. It can display a picture, but it cannot pass a signal on to another monitor, because there is no output from which the signal could continue. A monitor with two DisplayPort sockets is not automatically a hub either. Both sockets may be inputs, in which case the monitor can accept a signal from either of two sources but cannot forward anything downstream. Before buying a monitor or a hub for chaining, the specification table must be checked for an explicit DisplayPort output or MST output. The presence of two sockets, or the word DisplayPort somewhere in a marketing description, is not evidence of a chaining output.

A related point concerns docking stations. Some docking stations use DisplayLink video technology, and certain models in that family, such as the Dell D1000, D3100, and D6000 series named in Dell's own documentation, do not support MST daisy-chaining. Such a dock should not be treated as an MST hub, even though it provides extra display outputs. Its outputs are produced by a different mechanism, with its own limits, and confusing the two mechanisms leads to settings and expectations that cannot work.

Single-Stream and Multi-Stream: The Same Socket, Two Modes

A DisplayPort link can operate in two modes, and the difference between them explains the most common MST complaint: every monitor shows the same picture. In Single-Stream Transport, or SST, one link carries one picture. Even if a hub or a second monitor is connected behind it, the system recognises only one picture, and any additional monitor that shows anything will show a mirror of that same picture. In Multi-Stream Transport, one link carries several independent streams, and the system recognises each monitor separately, so an extended desktop becomes possible.

The practical consequence is that MST must be enabled where the hardware requires it. Some monitors leave MST switched off by default, and the multi-stream mode must be turned on in the monitor's on-screen display before the system can extend the desktop across the chain. With MST off, the result is mirroring, or only one monitor being recognised, even though the cabling is exactly right. The location and the exact name of the setting vary by brand and model, so this guide deliberately does not invent a universal menu path. The setting is normally found in the on-screen display under a Display or Input related menu, and the wording is typically along the lines of MST, DisplayPort MST, or DP MST, subject to the individual model's manual.

Only the monitors that need to pass a signal further down the chain must support MST and provide a branch function. The last monitor in the chain does not itself need to support MST, because nothing passes beyond it. Dell's official daisy-chaining guidance states the same principle: only the first, or primary, monitor must support DisplayPort 1.2 or later together with MST, while the following monitors do not need to. That principle is worth remembering when a chain mixes old and new monitors. The monitor chosen as the first in the chain should be the one whose specification clearly supports MST, not simply the largest or the newest-looking screen on the desk.

Bandwidth Sharing: One Pipe, Not One Pipe Per Monitor

Bandwidth is the core mechanism of MST, and it is also the mechanism most easily misunderstood. A helpful mental image is a single pipe shared by every monitor on the chain, rather than a separate pipe for each monitor. The pipe has a fixed capacity, set by the DisplayPort version and the link rate actually negotiated. Every stream draws from the same pipe, and the total draw cannot exceed the pipe's capacity.

DisplayPort 1.2, using the HBR2 link rate, provides 5.4 gigabits per second per lane, or 21.6 gigabits per second across four lanes, with a payload of about 17.28 gigabits per second after encoding overhead. DisplayPort 1.4, using the HBR3 link rate, provides 8.1 gigabits per second per lane, or 32.4 gigabits per second across four lanes, with a payload of about 25.92 gigabits per second. Those figures describe the link itself, not a promise about any particular combination of monitors. The actual usable combination also depends on colour depth, chroma subsampling, refresh rate, whether Display Stream Compression is active, the modes declared in each monitor's EDID, and the maximum number of displays the graphics card itself supports.

MST allocates bandwidth within the main link by assigning time slots to different streams. As more monitors are added, or as each monitor's resolution, refresh rate, or colour depth rises, the total demand rises. Once demand exceeds the link's capacity, the system responds in one of several ways, depending on how the graphics card and monitor firmware handle the overload: a later monitor may not be detected or may show no signal, the system may automatically reduce resolution or refresh rate, or only a lower combination of settings may be offered at all. None of those outcomes, on its own, proves that a monitor or a graphics card is faulty. All of them are consistent with a chain that has simply run out of shared bandwidth.

For that reason, this guide deliberately does not publish a universal table claiming that DisplayPort 1.2 always supports a certain number of monitors and DisplayPort 1.4 always supports another number. Such a table would be misleading, because the same version can support different combinations depending on colour depth, refresh rate, compression, EDID declarations, and the graphics card's own display limit. Any specific combination mentioned here, such as two 4K monitors, should be read only as an example whose feasibility depends on Display Stream Compression and on the individual specifications of the card, hub, and monitors involved, not as a guarantee.

Display Stream Compression, or DSC, deserves a careful explanation, because it is often described as if it removed the bandwidth limit entirely. It does not. DSC is a visually lossless compression method that reduces the bandwidth each stream requires, which can make a higher combination possible than would fit without it. DisplayPort 1.2 has no DSC, so high-resolution multi-monitor combinations reach the limit quickly. DisplayPort 1.4 includes DSC, which is one reason its combinations are more flexible. But DSC only helps where every relevant part of the chain supports it. If any link in the chain does not support DSC, that part of the chain cannot use DSC to save bandwidth. DSC also does not remove the graphics card's own limit on the number of displays, and it does not turn a finite link into an infinite one. It widens the room; it does not remove the walls.

Link Negotiation and the Weakest Link

Before any picture appears, a DisplayPort link performs link training: the source and the sink negotiate how many lanes to use and at what link rate, from the lower rates up through RBR, HBR, HBR2, and HBR3. The negotiated rate, not the rate printed on any single box, determines the usable bandwidth of the chain. If any segment of the chain — a cable, a hub, or a monitor — supports only a lower link rate, or if cable quality or length causes link training to fall back to a lower speed, the whole chain's available bandwidth is dragged down by that segment.

Buying a monitor labelled DisplayPort 1.4 does not automatically produce an HBR3 link. The graphics card output, every cable segment, the hub, and every monitor in the chain must all support the higher rate, and link training must succeed at that rate in practice. This is the sense in which MST diagnosis differs from the separate subject of cable bandwidth certification. A guide on cable certification asks whether a particular cable truly delivers its labelled bandwidth and how to tell a genuine rating from a misleading one. This guide asks a different question: given that every segment has some real capability, how does the weakest segment limit the entire topology? The cable is one link in that chain, not the whole story, and replacing a cable cannot fix a limit imposed by a hub or a monitor that only supports a lower rate.

Length matters here as well. A longer cable segment is more likely to negotiate down, and a chain should be verified segment by segment rather than by checking only the first cable from the graphics card. A chain that works with short cables and fails when a long segment is introduced has produced useful evidence about that segment, even if no component is faulty in isolation.

Operating System Differences

The operating system is part of the chain, not an afterthought. Windows generally supports MST extended desktops, with each monitor recognised independently. macOS, by contrast, generally does not support MST extended desktops; when several monitors are connected through an MST hub, macOS typically mirrors the same picture to them, subject to Apple's documentation and the individual device's documentation for the system version in use. This guide does not claim that every Mac and every macOS version behaves identically, because that claim would go beyond the documentation. The practical point is narrower and more useful: a hub that extends correctly on Windows and mirrors on a Mac has not necessarily failed. The difference itself is evidence pointing toward an operating system limitation, and it should be checked against the system documentation for the version in use before the hub or the graphics card is blamed.

A related limitation concerns the total number of displays. An MST hub cannot make a graphics card support more displays than the card itself supports. If the graphics card specification states a maximum number of displays, that maximum remains the maximum, however many outputs a hub provides. Counting physical sockets on a card is also not a reliable guide to its MST capability or its total display limit, because each output's MST capability and the card's overall limit are separate properties stated in the card manufacturer's documentation.

Two smaller behaviours are worth noting as known possible phenomena rather than as faults. Audio routing in MST mode may behave unexpectedly on some systems or firmware versions, with audio not behaving normally in MST mode according to some manufacturers' release notes for particular models; this should be checked model by model and not stated as a general rule. Separately, some MST systems may show a black screen on one monitor at startup when several monitors are already connected, or when a middle monitor in the chain is hot-plugged, requiring a reconnection or a restart to recover, again subject to the individual model and system documentation. Treating those behaviours as proof of a broken cable, without checking the topology and firmware behaviour first, leads to unnecessary replacements.

USB-C and Thunderbolt add a further check. A USB-C monitor connection can only carry a display signal if that USB-C port supports DisplayPort Alternate Mode, and Thunderbolt chaining capability depends on the Thunderbolt generation and the device documentation. The presence of a USB-C socket does not, by itself, mean that chaining is possible. Similarly, where a USB-C monitor also receives power delivery, the power and the display bandwidth are separate matters: a monitor that charges correctly has proven its power path, not its display bandwidth.

Diagnosis in Order: Intention, Specification, Topology, Isolation

Diagnosis should follow a fixed order, and skipping steps is the usual cause of confusion. The principle is simple: confirm what result is wanted, confirm the specifications on paper, confirm the wiring, isolate segment by segment, and only then consider graphics card hardware.

First, establish the intended result. Is the goal an extended desktop, with different content on each monitor, or a mirrored desktop, with the same content on each monitor? If the goal is mirroring, MST is not required at all, and the whole MST diagnosis should not be applied. Many reported MST failures turn out to be mirroring goals pursued with MST tools, or extended goals pursued without enabling MST.

Second, check the specifications before switching anything on. Does the graphics card or laptop output support MST, and which DisplayPort version does it use? How many displays does the graphics card itself support? Does the first monitor, or any monitor that must pass a signal onward, provide a DisplayPort output or MST output? If an external hub is used, what are its input and output specifications? Which operating system is in use, Windows or macOS? And what is the target combination — how many monitors, at what resolution, refresh rate, and colour depth — and does that combination already exceed the chain's total bandwidth on paper? A paper estimate before buying anything is cheaper than a series of purchases made in the hope that one of them will fix the problem.

Third, check the wiring against the required order: graphics card to first monitor input, first monitor output to second monitor input, second monitor output to third monitor input. The most common wiring error is connecting the second monitor to the first monitor's DisplayPort input instead of its output, or connecting a monitor through an HDMI input and then expecting the chain to continue. Both errors look like a dead second monitor, but neither is a fault in the second monitor.

Fourth, check the on-screen display settings on every monitor that must act as a branch. Is MST enabled on that monitor? Is the input source set to DisplayPort rather than HDMI or another input? A monitor set to the wrong input will not forward a chain even if its MST setting is correct, and a monitor with MST disabled will not extend even if its input is correct. Both settings must be right on the same monitor.

Fifth, establish a single-monitor baseline. Take the chain apart and connect the graphics card directly to each monitor in turn, confirming that each monitor on its own reaches its target resolution and refresh rate. If a monitor cannot reach its target on its own, the problem is not an MST problem, and no amount of MST troubleshooting will fix it. The baseline also separates monitor capability from chain capability: a monitor that works alone but fails in a chain points toward the chain, while a monitor that fails alone points toward that monitor, its cable, or its settings.

Sixth, rebuild the chain one monitor at a time. Connect two monitors first and confirm that the extended desktop works with two. Only then add the third. The monitor whose addition breaks the chain identifies the segment to investigate: its cable, its settings, its position in the chain, or the total bandwidth that its addition exceeded.

Seventh, isolate by changing one segment at a time. If a particular cable or monitor is suspected, replace only that segment with a known-good cable of the same specification or a known-good monitor, and observe the change. Replacing the whole chain at once destroys the evidence, because even if the chain starts working, nobody knows which replacement fixed it, and the original fault may return when the old parts are reused.

Eighth, test at a lower total bandwidth. Temporarily set all monitors to a lower combination, such as all monitors at 1080p at 60Hz, or lower refresh rates across the chain, and observe whether all monitors are then recognised. If a lower combination is recognised and a higher combination is not, the evidence points toward the bandwidth ceiling rather than toward a broken monitor. That test does not prove the exact ceiling, but it separates a bandwidth limit from a dead device more cleanly than any single replacement.

Ninth, test Display Stream Compression where the hardware provides a related setting. Try DSC on and off, where the graphics card or monitor exposes that control, and compare the results, subject to the individual model's documentation. Note that switching DSC off will reduce the combinations available, and that reduction is itself not a fault. The purpose of the test is to learn whether DSC is part of the current combination's success, not to leave it in whichever position happens to work without understanding why.

Tenth, update drivers and firmware only after the topology and bandwidth isolation above. A graphics card driver update, or a monitor firmware update where the manufacturer provides one, can resolve a genuine compatibility problem, but driver updates are not a universal remedy, and updating before isolating the chain can mask the real cause or introduce a new variable. Update, then retest the same chain in the same order.

Eleventh, use an external MST hub as a control test where monitor chaining remains unstable. Connect the graphics card to the hub, and the hub to each monitor by a separate cable. If the hub arrangement works while monitor chaining does not, the evidence points toward the monitor's built-in hub or its on-screen settings. If the hub arrangement also fails, the evidence points toward the source, the bandwidth budget, or an operating system limitation. The hub test is valuable precisely because it changes only one variable: where the splitting happens.

Twelfth, and only after all of the above, consider graphics card hardware. Suspicion of a graphics card output or interface is warranted when the single-monitor baseline, the segment-by-segment isolation, the lower-bandwidth test, and the hub control test have all been completed, and a particular DisplayPort output still produces no signal at all. At that point, and not before, a hardware inspection is the sensible next step, with the fee confirmed after inspection as described at the end of this guide.

What the Symptoms Suggest, and What They Do Not Prove

A symptom table is useful only if it is read as a list of priorities, not as a list of diagnoses. Each symptom below points toward the checks to do first, and each row also names the conclusion that should not be jumped to before those checks are done.

The flicker row deserves a note on scope, because flicker appears in more than one guide. A separate guide on multi-monitor standby and flicker deals with wake-from-standby behaviour and intermittent flicker in general. This guide mentions flicker only from the MST angle: a chain operating near its bandwidth limit, or a link repeatedly retraining, can produce flicker or brief blackouts. The standby and wake checks from that other guide are not repeated here, and the MST checks here do not replace them where standby behaviour is the actual complaint.

Boundary Cases

Several boundary cases change the answer, and each is worth stating plainly rather than leaving the reader to guess.

A monitor that supports MST output can act as a middle link; a monitor without that output can only be a chain end, or can join a multi-monitor setup through an external MST hub. Buying a monitor in the belief that it has a chaining output, when its specification table shows only inputs, is the most common purchasing error in this subject, and it is entirely avoidable by checking the specification table before purchase.

DisplayPort 1.2 and 1.4 differ in total bandwidth and in DSC support, but neither version guarantees a particular multi-monitor combination. DisplayPort 1.2, without DSC and with lower total bandwidth, offers fewer high-resolution combinations. DisplayPort 1.4, with HBR3 and DSC, offers more, but still within a total budget and within the graphics card's display limit. A statement that DisplayPort 1.4 will always drive three 4K monitors would be false without qualifications about refresh rate, colour depth, DSC, and EDID, and this guide does not make it.

High-resolution combinations deserve the same caution. A single 4K monitor already consumes a large share of a link. Two or three 4K monitors are feasible only within the combined budget, and their feasibility turns entirely on refresh rate, colour depth, and DSC, subject to the specifications of the particular graphics card, monitors, and hub in use. Any example in this guide should be read with that qualification attached.

Mixed resolutions and refresh rates add a further constraint: the system must satisfy the modes declared in each monitor's EDID at the same time. Some manufacturers' guidance suggests using the higher-specification monitor as the first monitor in the chain, and that suggestion is worth considering where the relevant manufacturer's guide says so, but this guide does not present it as a hard rule. Mixed brands are similar: some manufacturers suggest that same-brand combinations are more likely to be compatible, but cross-brand chains are not automatically impossible. The correct approach for a mixed chain is to check each monitor's specification individually, rather than assuming that a single brand guarantees success or that mixing brands guarantees failure.

A chain that ends in an adapter is finished at that adapter. The last monitor may be connected through an adapter to HDMI, because that monitor is a terminal and nothing needs to pass beyond it, but no further monitor can be chained from behind that adapter. The detailed questions about active and passive adapters, and about protocol conversion between DisplayPort and HDMI or DVI, belong to a separate guide on adapter protocol conversion, and they are not repeated here beyond the single point that conversion ends the chain.

USB-C power delivery is another source of confusion in the same family. A USB-C monitor may receive power correctly while its display chain fails, or vice versa, because power delivery capacity and display bandwidth are separate properties. Receiving power is not evidence that chaining has succeeded, and a chaining failure is not evidence of a power fault.

Finally, the number of physical outputs on a graphics card does not determine how many monitors an MST chain on one of those outputs can support. A card may have three or four physical outputs, but each output's MST capability and the card's total display limit remain as stated in the card manufacturer's documentation. Counting sockets is not a substitute for reading that documentation.

Misconceptions, Corrected in One Place

The power confusion comes first, because it is the most basic. MST daisy-chaining is a display signal topology, not a power distribution arrangement. A power shortage does not turn an extended desktop into a mirror, and an MST setting error does not deprive a monitor of power. Keeping signal and power as separate subjects prevents a whole class of misdiagnosis.

The second misconception is that any DisplayPort socket can chain. Chaining requires three things together: a source that supports MST, a branch device with a DisplayPort output and MST support, and an operating system that supports extended desktops through MST. Missing any one of the three, the chain cannot extend, however good the cabling is.

The third misconception is that a one-to-two splitter is the same as MST. A splitter typically copies one picture to two screens. MST uses a hub or branch device to distribute separate streams so that each screen can show different content. The two devices look similar in a shopping listing and do different things.

The fourth misconception is that HDMI can daisy-chain in the same way. It cannot. HDMI has no MST daisy-chaining, and connecting HDMI outputs together does not create an extended multi-monitor chain.

The fifth misconception is that adding a hub raises the graphics card's display limit. It does not. A hub distributes the streams a card can already produce; it does not increase the number of displays the card can drive.

The sixth misconception is that DisplayPort 1.4 solves every multi-monitor problem. It raises total bandwidth and adds DSC, but the chain remains subject to total bandwidth, EDID declarations, firmware behaviour, and operating system limits.

The seventh misconception is that a cable labelled DisplayPort 1.4 guarantees an HBR3 link across the whole chain. The label describes one segment. The card, the hub, and every monitor must also support the higher rate, and link training must succeed at that rate.

The eighth misconception is that switching DSC on removes the bandwidth ceiling. DSC reduces the bandwidth each stream needs, but it does not make bandwidth infinite, and it only helps where the relevant parts of the chain support it.

The ninth misconception is that a black second monitor means a broken second monitor. Until the single-monitor baseline, the wiring order, the on-screen settings, and the bandwidth budget have been checked, that conclusion is premature.

The tenth misconception is that a mirrored picture on a Mac means a broken hub. The macOS limitation on MST extended desktops should be considered first, subject to the system documentation for the version in use, before hardware is blamed.

The eleventh misconception is that two DisplayPort sockets on a monitor guarantee chaining. Both sockets may be inputs. Only a specification table entry for a DisplayPort output or MST output proves that the monitor can forward a signal.

When Inspection Is Warranted, and When It Is Not

A hardware inspection is warranted when a graphics card output shows a fault on its own, independent of MST. That includes an output that produces no signal when connected directly to a single known-good monitor, or an output that fails in the same way regardless of which monitor, cable, or hub is used. Those findings point toward the output or the card itself, and they are worth investigating as hardware questions.

An inspection is not warranted as a remedy for a chain that has not been configured or budgeted correctly. If a monitor works alone, a chain extends at a lower combination but not at a higher one, or a Mac mirrors where Windows extends, no inspection will change the bandwidth budget, the on-screen setting, or the operating system limitation. The time is better spent on the specification check, the wiring check, and the bandwidth test described above.

If inspection is needed, the workshop is at Shek Mun Dali Plaza Room 1209, reachable by phone on 2186 8010 or by WhatsApp on 6558 6806. Diagnostic and repair fees follow the published three-tier range of HK$400–2,800, with the actual figure confirmed after inspection. There is no Mong Kok shop and no on-site service.

Frequently Asked Questions

Is DisplayPort daisy-chaining the same as splitting a power cable?

No. Daisy-chaining in this guide means chaining display signals from one monitor to the next through a branch device. Power distribution is a separate subject. A monitor can receive power perfectly well while its display chain is misconfigured, and a display configuration error does not affect power delivery.

Why do all my monitors show the same picture instead of an extended desktop?

The most likely causes are that the link is operating in Single-Stream mode rather than Multi-Stream mode, that MST is switched off in the first monitor's on-screen display, or that the operating system does not support MST extended desktops, as is generally the case on macOS. Check the on-screen MST setting and the operating system first, before replacing cables or hardware.

My second monitor has two DisplayPort sockets. Can it chain to a third monitor?

Not necessarily. Both sockets may be inputs. Only a specification table entry stating a DisplayPort output or MST output shows that the monitor can forward a signal. Check that entry before assuming the monitor can act as a middle link.

Why does my third monitor disappear when I add it, while two monitors work?

The usual suspects are total bandwidth and the graphics card's display limit. Adding a third monitor increases total demand on the same link, and a combination that fits two monitors may exceed the link at three. Test the chain at a lower combination, such as all monitors at a lower resolution or refresh rate, to see whether the limit is bandwidth rather than a fault in the third monitor, and check the third monitor alone with a direct connection first.

Does DisplayPort 1.4 guarantee three 4K monitors?

No. DisplayPort 1.4 provides more total bandwidth than DisplayPort 1.2 and adds Display Stream Compression, but any particular combination still depends on refresh rate, colour depth, DSC support across the chain, EDID declarations, and the graphics card's own display limit. Each combination must be checked against the specifications of the actual card, hub, and monitors in use.

Can I chain through an HDMI adapter to a third monitor?

No. An adapter to HDMI or DVI ends the chain, because HDMI does not support MST daisy-chaining and the converted output cannot be chained further. A monitor connected through an adapter can only be the last monitor in the chain.

My monitors flicker only when chained. Is the graphics card failing?

Not necessarily. A chain operating near its bandwidth limit, or a link repeatedly retraining at a lower rate, can produce flicker or brief blackouts. Check the total bandwidth combination, test at a lower combination, and isolate each cable segment before concluding that the card is at fault. If flicker is mainly a standby or wake problem, that is a different subject with its own checks.

The chain extends on Windows but only mirrors on a Mac. Is the hub broken?

Not necessarily. macOS generally does not support MST extended desktops, so mirroring on a Mac while extending on Windows is consistent with an operating system limitation. Check the system documentation for the version in use before blaming the hub or the graphics card.