Windows Detects the Second Monitor but It Shows No Picture? Input Source, Cable, Mode & Port Diagnosis Guide

2026-11-15 | GPU Repair | 29 minutes | HK GPU Fix Editorial Team

Windows Detects the Second Monitor but It Shows No Picture? Input Source, Cable, Mode & Port Diagnosis Guide

Key Summary

Windows can list a second monitor while that monitor shows nothing, because recognition and picture travel on separate channels. Start with the monitor's own menu, then check input source, projection mode, a lower resolution probe, cable and port, and finally a cross-check with another computer before deciding what is at fault.

Recognition Is Not a Picture

A second monitor is connected, Windows plays its connection sound, and Display settings clearly shows two numbered monitors. The mouse pointer can be pushed across to the second screen, and a window dragged in that direction disappears from the main screen as though it has arrived somewhere. Yet the second monitor itself shows nothing: it stays black, or it displays a brief "No Signal" message and then goes to sleep. The main monitor works normally throughout.

The first reaction is usually to blame the second monitor or the graphics card's second output, and then to spend an evening reinstalling the driver, changing cables, and swapping screens. That reaction skips the central point of this guide. Windows recognising a monitor and that monitor showing a picture are two different achievements, and either one can happen without the other. Recognition proves only that the identity channel is working. A picture needs the identity channel plus the video channel, the correct input source, a display mode the monitor can accept, a working port, and a cable that carries video. When any of those later links is missing, the result is exactly this contradictory state: detected, but blank.

This guide covers Windows 10 and Windows 11 desktop and laptop computers where Display settings shows two monitors, with numbers and an arrangement that can be dragged, while the second monitor persistently shows no picture and the main monitor is normal. A single monitor showing no picture at all is a different problem and is not covered here. The core claim is simple: detection is not a verdict, it is one channel out of two. Use the monitor's own menu first to establish whether the monitor can draw anything by itself, and then work through input source, mode, cable, and port in order, instead of deciding at the start that the monitor is broken or that the driver must be reinstalled.

Two Channels: Identity and Video

A picture travels from the graphics card to the eye along two logically separate channels that happen to share one cable.

The first is the identity channel. Every monitor leaves the factory with a block of identity data inside it, known as EDID. The monitor sends that data to the graphics card over the DDC channel, describing the manufacturer, the model, and the resolutions and refresh rates it supports. Windows receives that description and lists the monitor in Display settings. That is all recognition means: the description arrived.

The second is the video channel. The graphics card sends picture pixels at high speed to the monitor, where the scaler and timing controller process them and the panel displays them. For a picture to appear, the video channel must carry a signal the monitor can accept, the monitor must be listening on the right input, and the mode must be within what the monitor and the cable can handle.

The DDC channel and the video channel can fail independently. They run over different pins inside the same cable, and a fault can affect one while leaving the other untouched. When the identity channel works and the video channel does not, Windows lists the monitor and the screen stays blank. When the position is reversed — video works but identity does not — Windows shows a picture under a generic monitor name, with a shortened list of modes. Those two states are two sides of the same coin, and this guide deals with the first side: identity received, picture missing.

That distinction also separates this guide from neighbouring problems. When a monitor is recognised under the wrong name but still shows a picture, the identity channel itself is at fault. When one output port produces no signal at any stage — boot, firmware screens, and Windows alike — and the fault follows that port wherever it is tried, the port is the subject. When a monitor's backlight is on but no picture and no menu can be produced from the first second, on any input, the monitor's internal picture path is the subject. This guide sits between those cases, and its first fork — the monitor's own menu — is what decides which of them applies.

Three Kinds of "No Picture" Must Be Separated First

People say "the monitor is black" as though that were one fault, but it covers three different situations, and only one of them is this guide.

In the first, the monitor itself switches off or restarts: the power light goes out, or the monitor cycles on and off by itself. That is a power or monitor behaviour problem.

In the second, the monitor stays powered and awake yet shows nothing it was sent: its indicator remains lit or settles to amber standby, the panel stays dark, and a brief "No Signal" notice may appear before it sleeps. This guide deals with this second kind, with one extra Windows condition added: Windows recognises the monitor.

In the third, the computer has gone to sleep, or the display has entered a power-saving state, and the picture does not return on waking. That is a sleep and wake problem, and it is not this guide, because here the second monitor has shown nothing from the moment it was connected, not only after waking.

Naming the kind matters because each kind points at a different layer. A monitor that switches itself off needs a different investigation from a monitor that stays on and reports that it is receiving nothing. Write down which kind is present before changing anything: whether the second monitor shows "No Signal" and then sleeps, whether it stays black with the power light on and no message at all, or whether its power light goes out or flashes. That note, together with which monitor, which cable, which port, whether any adapter sits in between, and whether the boot screen appears on the second monitor, is the record every later step is judged against.

The Five Layers of Suspicion

Once the kind of "no picture" is fixed, the fault can be placed in one of five layers. Each layer has its own decisive check, and the order runs from the easiest to confirm to the deepest.

LayerWhat it coversDecisive check
1. Input source layerThe monitor is listening on the wrong input — the cable is in HDMI while the monitor is still watching DisplayPort — or its automatic detection has settled on the wrong inputSwitch through each input source by hand in the monitor's on-screen display, pausing a few seconds on each, and watch whether the "No Signal" message changes
2. Display mode layerThe projection mode is wrong, the second monitor has been set to disconnected, or the resolution or refresh rate is beyond what the second monitor can acceptTry each Win + P mode, starting with Duplicate; confirm the second monitor is set to Extend rather than disconnected; drop the second monitor to 1080p at 60Hz as a probe
3. Cable and intermediate device layerThe video pins in the cable are damaged, an adapter, switch, or dock is consuming the video signal, or the cable lacks the bandwidth for the mode in useDirect-connection comparison: remove intermediate devices, try another known-good cable, try another port, changing only one thing at a time
4. Port and driver layerOne output port on the graphics card is faulty, the driver output state is confused, or behaviour changed after a driver updatePort matrix: the same cable and the same monitor tried on each graphics card output in turn; reset the graphics driver with Win + Ctrl + Shift + B as a comparison
5. Monitor itself layerThe monitor's scaler, timing controller, or panel video path is faulty, beyond the backlight aloneMenu check plus cross-check: the second monitor on another computer, and a different known-good monitor on the same cable and port

The order is itself the diagnosis. A reader who jumps to layer four and reinstalls the driver has skipped three layers that have nothing to do with the driver, and will usually find the second monitor still blank afterwards, with the same silence and no new information. A reader who works through the layers in order will either find the fault early or arrive at layer five with four layers already ruled out, which is a far stronger position.

The Menu Check: The Most Important Fork in This Guide

Before any of the seven steps, press the second monitor's own menu button and look at what happens. That menu is drawn internally by the monitor, so it can appear even when no signal at all is arriving from the computer. That independence is what makes it decisive.

If the menu appears, the monitor's own picture-drawing path is working: its scaler, timing controller, and panel can produce an image. The fault is therefore upstream of the monitor, in the signal path — input source, mode, cable, port, or driver — and the investigation continues through the seven steps below. If the menu does not appear at all, stop. The fault is in the monitor's internal picture path, and changing cables or drivers will not help; that problem belongs with the guide on a backlit screen with no picture and no menu, and the remaining steps of this guide should not be run.

Note the difference in purpose. In that neighbouring guide, the menu check is used to confirm an internal monitor fault. Here, it is used to exclude one: a menu that appears clears the monitor's own drawing path and sends the investigation upstream. The fork must sit before the seven steps, not in the middle of them, because every step after it assumes the monitor can draw.

"No Signal" Is Good News, Not Bad News

Seeing the words "No Signal" on the second monitor feels like bad news, and most people read it as proof that the monitor is broken. The direction is the opposite. Those words are drawn by the monitor itself, which proves that its scaler, timing controller, and panel picture path all know how to work. The monitor is simply reporting that it is receiving no input. The state to worry about is the one where the monitor cannot even draw those three words — a blank screen with a lit power light and no message at all, and no menu either. That is the internal-path case, and it belongs elsewhere.

This counter-intuitive point decides what to be worried about and what not to be worried about. A monitor that says "No Signal" is a monitor that can draw. The work is to find out why nothing is arriving for it to draw, and that work runs through the layers in order: first whether it is listening on the right input, then whether Windows is sending a mode it can accept, then whether the cable and port are carrying video.

What the Boot Screen Tells You

The picture shown during the first few seconds after switching on is decided by firmware, while the picture after Windows loads is decided by Windows and the driver. Boot-time display choice and the Windows desktop choice are made by separate layers, each unaware of the other, so the boot screen and the Windows desktop can disagree, and the disagreement is itself evidence.

If the boot screen appears on the second monitor but the picture disappears once Windows loads, the fault is in the Windows layer — mode, driver, or setting — because firmware, cable, and port have already proved they can deliver a picture to that monitor. If the boot screen never appears on the second monitor either, the fault may be in the cable, port, input source, or the monitor itself, and the Windows layer is not necessarily the cause. If the boot screen goes to the wrong monitor and then the desktop returns to the intended monitor once Windows loads, that is a different subject — firmware and Windows choosing different screens — and it is not this guide, because in that case both monitors do show pictures, only at different times.

Record which of those three patterns is present before changing anything. It is one of the cheapest pieces of evidence in the whole diagnosis, and it is lost the moment settings are changed without noting it.

The Seven Steps, In Order

The sequence below is the diagnostic method of this guide. The order is deliberate: each step rules out one layer before the next layer is touched, and the input source is re-confirmed after every cable or port change, so that a change in the picture can be tied to the change that caused it.

  1. Describe the fault precisely. Which form of "no picture" is it? (a) The second monitor shows "No Signal" and then sleeps; (b) the second monitor stays black with the power light on and no message; (c) the second monitor stays black but the power light goes out or flashes — that pattern belongs with the guide on monitors that switch themselves off; or (d) the second monitor has a picture intermittently, coming and going — that is an intermittent signal problem, not this guide. Write down the current combination: which monitor, which cable, which port, whether any adapter sits in between, and whether the boot screen appears on the second monitor.
  2. Run the menu check. Press the second monitor's own menu button. If the menu appears, continue below. If no menu appears at all, stop here and follow the guide for a backlit screen with no picture and no menu. Do not run the remaining six steps, because they all assume the monitor can draw.
  3. Check the input source. In the second monitor's on-screen display, switch through each input source by hand — HDMI 1, HDMI 2, DisplayPort, USB-C — pausing a few seconds on each. If the picture appears the moment the correct input is reached, the fault was in the input source layer, and the diagnosis is finished. If every input reports no signal, continue to the next layer. Do not trust automatic detection alone for this step: some monitors jump automatically to an input carrying a signal, while others stay on the last input used, and behaviour varies by brand.
  4. Check the display mode. Press Win + P and try each projection mode in turn, starting with Duplicate. Duplicate mode forces Windows to use a mode both monitors support, so it works as a safe-mode probe: if the second monitor shows a picture in Duplicate, the fault is in the mode layer. Then try Extend. Open Display settings and confirm the second monitor is set to Extend rather than disconnected, and that its number and left-right position match the physical desk layout. Then drop the second monitor to 1080p at 60Hz as a probe: if a picture appears at that lower mode, the original mode was beyond the second monitor or the cable. Note that Duplicate is only a probe, not a setting to keep: it can pull the main monitor down to a mode both monitors share, so return to Extend once the probe has answered its question. If the monitor shows an out-of-range message, that notice shows it received something it could not display; return to a picture through the main monitor or a recovery mode, then test with a single direct connection.
  5. Compare with a direct connection. Remove any adapter, switch, or dock, and connect the graphics card directly to the second monitor. Try another known-good cable, and try another port. Change only one thing at a time, and go back to step three to re-confirm the input source after each change, because a new port or cable may land on a different input. A cable that worked on the main monitor is not proven good for the second monitor by that alone: the fault may be the input source, a mode beyond the second monitor, or the port, rather than the cable itself.
  6. Compare port and driver. Try the same cable and the same second monitor on each graphics card output in turn. If only one port fails while the others work, that output is identified by elimination as the failing one; if every port behaves the same way, the fault is not following a port. A single dead output does not condemn the card as a whole, because the remaining outputs can still be checked separately and basic display function may still be intact. If the problem began immediately after a driver update, rolling back to the previous driver version is a legitimate comparison in the other direction. Press Win + Ctrl + Shift + B to reset the graphics driver and see whether the picture returns. A driver reset is a comparison, not a guaranteed repair, and Microsoft's own documentation describes the key combination as something that may help rather than a promise.
  7. Cross-check and decide. Connect the second monitor to another computer, or to a games console or another laptop. If it shows a picture there, the fault is on the original computer's side — port, driver, or setting — and the monitor should not be replaced. Connect a different known-good monitor to the same cable and port: if it shows a picture, the fault points at the second monitor itself. If the second monitor shows no picture on any computer while its menu still appears, the fault is on the monitor's input or scaler side, and the machine should be brought in with the full record. If the second monitor shows a picture on another computer, the fault is on the original computer's side; do not replace the monitor.

That record should include the monitor model, the cable type and port used, the input source found, the Win + P mode and the 1080p probe result, the driver version, the boot-screen pattern, the menu check result, and the cross-check result. A record that precise lets an inspection start at the right layer instead of repeating the whole sequence.

Diagnostic Logic: Reading the Symptom

SymptomMost likely causeNext step
Display settings shows two monitors, second monitor shows "No Signal" then sleepsWrong input source, or a mode the monitor cannot accept, or video not reaching the monitorMenu check, then switch input sources by hand, then Win + P Duplicate
Menu appears, every input source reports no signalMode layer or cable and port layer at fault; the monitor itself can drawDo the mode comparison, dropping the second monitor to 1080p at 60Hz as a probe
Second monitor black, power light on, no message, no menuMonitor internal picture pathStop; follow the guide for a backlit screen with no picture and no menu
Picture appears in Duplicate but not in ExtendMode or setting layerConfirm Extend is selected, check arrangement, then re-test at 1080p at 60Hz
Picture appears at 1080p at 60Hz but not at the original modeOriginal mode beyond the monitor or the cableKeep the lower mode as the probe result, then check the monitor specification and the cable separately
Boot screen appears on second monitor, Windows shows nothingWindows mode, driver, or settingWin + P modes, 1080p probe, driver reset as a comparison
Boot screen never appears on second monitor eitherCable, port, input source, or monitor itselfDirect-connection comparison, port matrix, cross-check
Second monitor shows a picture on another computer, but not on the original computerPort, driver, or setting on the original computerDo not replace the second monitor; concentrate on checking the original computer
Second monitor black, power light out or flashingMonitor power behaviourFollow the guide on monitors that switch themselves off
Only one graphics card port fails, others workThat portUse a working port and note the faulty one in the record; do not replace the whole card on that evidence alone

Edge Cases That Are Not This Problem

The monitor is recognised as a generic PnP monitor, and resolution or refresh-rate options are incomplete. That is not this guide. In that case the identity itself is wrong, and a picture still appears. Only the identity and video channel mechanism matters here; the recognition diagnosis is not repeated.

One output port produces no signal at any stage, and the fault follows that port. That is not this guide. Only the port matrix idea matters here — the same cable and the same monitor tried on each port in turn — and the port channel diagnosis is not repeated.

The backlight is on but there is no picture at all, and the menu cannot be produced. That is not this guide. Only the menu check matters here as a fork: a menu that does not appear ends this guide at step two.

The monitor switches itself off or restarts. That is not this guide. That belongs with the guide on monitors that switch themselves off; only the three-kind separation of "black screen" is used here.

Plugging in the second monitor makes the main screen flash black and the resolution jump. That is not this guide. In that case the main screen recovers and the second monitor's picture is not the subject; here the second monitor never shows a picture at all.

After the monitor wakes or reconnects, window positions are scrambled. That is not this guide. In that case the picture has already returned normally and only window positions are wrong. Windows pulls stray windows back to the main screen so they do not end up stranded where they cannot be seen — which is why a window dragged to a blank second monitor shrinking back to the main screen is not by itself evidence that the second monitor is broken.

The boot screen goes to the wrong monitor, and the desktop returns to the intended monitor once Windows loads. That is not this guide. Both monitors show pictures there, only at different times.

The resolution or refresh rate is beyond the second monitor, and an out-of-range message appears. That is not this guide as a main subject. Only one point matters here: an out-of-range message means a signal was sent but the panel refused it, and the 1080p probe confirms it.

The picture comes and goes, black for a second or two and then returning by itself. That is not this guide. This guide is about a picture that is persistently absent, not one that drops out intermittently.

The second monitor shows no signal only after waking from sleep. That is not this guide. That belongs with the guides on wake-from-sleep signal loss. Here the second monitor has shown nothing from the moment it was connected.

A laptop lid is closed and the external monitor is the only output. That is not this guide. This guide assumes the external monitor is an additional second screen, not the sole output with the lid closed.

The second monitor shows a picture, but the colours are wrong, tinted, or flickering. That is not this guide. A picture exists there, so the video channel is working, and the fault is in the colour or synchronisation layer.

Six Common Mistakes

  1. Assuming that because Windows recognises the monitor, the monitor must be fine and the fault must be a setting. Wrong. Recognition proves only that the identity channel is working. The video channel, the input source, and the monitor's internal picture path can each fail independently. Only the menu check separates inside from outside.
  2. Assuming that "No Signal" means the monitor is broken. Wrong, in the opposite direction. "No Signal" is drawn by the monitor itself, which proves the monitor can draw. A monitor that cannot even draw those words is the one to worry about.
  3. Assuming that reinstalling the driver will always fix it. Wrong. A wrong input source, a wrong Win + P mode, or a damaged video pin in the cable will not be repaired by any number of driver reinstalls. The driver is the fourth layer; the three layers before it must be checked first, and a driver reset must never be presented as a guaranteed repair.
  4. Assuming that because a cable worked on the main monitor, it must work on the second monitor. Wrong. The same cable working on the main monitor and failing on the second can mean the second monitor's input source is wrong, the mode is beyond the second monitor, or the port is at fault — not that the cable itself is guilty. Run the mode check and the port matrix before blaming the cable.
  5. Assuming that a blank second monitor means the graphics card's second port is broken. Wrong. A faulty port is one possibility, but mode, input source, and cable can all produce the same surface symptom. Only the port matrix — the same cable and the same monitor tried on each port — can say whether a port is at fault, and one faulty port does not mean the whole card has failed.
  6. Assuming that because the pointer moves onto the second monitor, the second monitor must be showing a picture. Wrong. The pointer moving there proves only that Windows has extended the desktop to those coordinates. It does not prove the monitor is displaying them, and a window shrinking back to the main screen is the system's protection mechanism, not evidence that the second monitor is broken.

When to Stop and Bring the Machine In

Stop when all seven steps have been completed and the second monitor still shows no picture on the original computer while showing a picture on another computer — the fault is on the original computer's side and needs inspection with the full record — or when the second monitor shows no picture on any computer while its menu still appears, which points at the monitor's input or scaler side. Stop sooner if the problem is accompanied by a driver crash, a persistent black screen on the main monitor as well, or coloured artefacts on screen, because those signs have left this guide and belong to a hardware inspection.

Bring the machine in with a complete record: the monitor model, the cable type and port used, the input source found, the Win + P mode and the 1080p probe result, the driver version, the boot-screen pattern, the menu check result, and the cross-check result. Inspection takes place at Room 1209, Dali Plaza, Shek Mun. You can call 2186 8010, or reach the shop on WhatsApp at 6558 6806. Inspection is charged at the site's published three-tier fees of HK$400–2,800, with the actual quote following inspection. There is no home-visit service and no Mong Kok shop; inspection is carried out in the shop.

Frequently Asked Questions

Windows display settings shows two monitors — why does the second screen still show no picture?

Because recognition and picture travel on separate channels. Windows lists a monitor when its identity report arrives over the DDC channel. A picture needs the video channel as well, plus the correct input source, a mode the monitor can accept, and a working port and cable. If the video channel is broken, the input is wrong, or the mode is beyond the monitor, Windows will still list the monitor while the screen stays blank. Work through the menu check, input source, Win + P mode, and the 1080p probe in order to find which link is missing.

The second monitor shows “No Signal” and then goes to sleep — does that mean it is broken?

No, and the direction is the opposite of what most people assume. "No Signal" is drawn by the monitor itself, which proves that its scaler, timing controller, and panel picture path can all produce an image. The monitor is reporting that it is receiving no input. The next step is to find why nothing is arriving: switch the input source by hand in the monitor's menu, try Win + P Duplicate, and then test a direct connection with another known-good cable. A monitor that cannot draw "No Signal" or its own menu at all is the one that points at an internal fault.

How does the monitor’s own menu button tell me where the problem is?

The menu picture is generated by the monitor itself, without needing the graphics card, the cable, or any handshake. If the menu appears, the monitor's own picture-drawing path is working, so the fault is upstream — in the input source, mode, cable, port, or driver — and the seven steps continue. If no menu appears at all, the fault is in the monitor's internal picture path: stop, do not keep changing cables or drivers, and follow the guide for a backlit screen with no picture and no menu. The menu check must come before the other steps, because every later step assumes the monitor can draw.

Which input source should I pick for the second monitor, and can auto-detect be trusted?

Pick the input that matches the physical cable: if the cable is plugged into the monitor's HDMI 1 socket, the monitor must be set to HDMI 1, and the same for HDMI 2, DisplayPort, or USB-C. Switch through each input by hand in the monitor's on-screen display, pausing a few seconds on each, rather than relying on automatic detection alone. Automatic detection varies by brand: some monitors jump to an input carrying a signal, while others stay on the last input used. A monitor left on the wrong input will report no signal even when everything else is correct.

Which mode should I try with Win + P, and what is the difference between Duplicate and Extend?

Try Duplicate first, as a probe. Duplicate shows the same picture on both monitors, so Windows is forced to use a mode both monitors support; if the second monitor shows a picture in Duplicate, the fault is in the mode layer. Extend gives each monitor its own part of the desktop, which is the normal working arrangement, and the second monitor should be set to Extend once the probe has answered its question. Also confirm in Display settings that the second monitor is not set to disconnected, and that its number and left-right position match the physical desk layout. Duplicate is a probe, not a setting to keep, because it can pull the main monitor down to a shared mode.

How do I step the second monitor’s resolution or refresh rate down as a probe?

In Display settings, select the second monitor, then lower its resolution to 1080p and its refresh rate to 60Hz, and apply the change. If a picture appears at that lower mode, the original mode was beyond what the second monitor or the cable could handle, and the probe has answered its question. If no picture appears even at 1080p at 60Hz, the fault is not the mode alone, and the investigation moves to the direct-connection comparison and the port matrix. Keep the lower mode only as a probe result to record; the lasting setting should be chosen from what the monitor specification actually supports, once the fault is found.

What is the correct order for swapping cables, changing ports and removing adapters?

Remove intermediate devices first, then change one thing at a time. Start by taking any adapter, switch, or dock out of the chain and connecting the graphics card directly to the second monitor. Then try another known-good cable, and then try another port — one change at a time, re-confirming the input source after each change, because a new port or cable may land on a different input. Changing everything at once and finding a picture proves that something in the chain was responsible, but it does not identify which item it was, and the problem will return the next time that item is used.

How do I use a port matrix to tell whether the graphics card port or the monitor is at fault?

Use the same cable and the same second monitor, and try them on each graphics card output in turn, re-confirming the input source each time. If only one output fails while the others work, that output is identified by elimination as the failing one. If every port behaves the same way, the fault is not following a port, and the investigation moves to the cable, the monitor, or the driver. Then complete the matrix with the cross-check: the second monitor on another computer, and a different known-good monitor on the same cable and port. A single dead output does not condemn the card as a whole, because the remaining outputs can still be checked separately.

The boot screen appears on the second monitor but Windows does not — how is that different from no picture at boot either?

The two patterns point at different layers, because the boot screen is decided by firmware and the Windows desktop is decided by Windows and the driver, and the two do not communicate. If the boot screen appears on the second monitor but disappears once Windows loads, firmware, cable, and port have already proved they can deliver a picture, so the fault is in the Windows layer — mode, driver, or setting. If the boot screen never appears on the second monitor either, the fault may be in the cable, port, input source, or the monitor itself, and the Windows layer is not necessarily the cause. Record which pattern is present before changing anything.

I have tried all the steps above and it still does not work — what should I do next?

Bring the machine in with the full record: the monitor model, the cable type and port used, the input source found, the Win + P mode and the 1080p probe result, the driver version, the boot-screen pattern, the menu check result, and the cross-check result. If the second monitor shows a picture on another computer, the fault is on the original computer's side; if it shows no picture on any computer while its menu still appears, the fault points at the monitor's input or scaler side. Inspection takes place at Room 1209, Dali Plaza, Shek Mun. You can call 2186 8010, or reach the shop on WhatsApp at 6558 6806. Inspection is charged at the site's published three-tier fees of HK$400–2,800, with the actual quote following inspection.

Related articles

Related services

If you need Chip-level GPU repair, see these service pages: