Photoshop Canvas Goes Black but the Interface Looks Fine? Creative-App Canvas Rendering, GPU Switching & Version Diagnosis Guide

2026-11-17 | GPU Repair | 31 minutes | HK GPU Fix Editorial Team

Photoshop Canvas Goes Black but the Interface Looks Fine? Creative-App Canvas Rendering, GPU Switching & Version Diagnosis Guide

Key Summary

Photoshop opens a file to a completely black canvas while every menu, panel, and toolbar still works — a shape that points at the canvas rendering path, not at a dead card. This guide separates the canvas layer from the interface, the driver, dual-GPU switching, and the file itself, using one decisive toggle test.

The Shape of the Problem: Black Canvas, Working Interface

This guide covers one specific shape, and the shape itself is the whole diagnosis. Photoshop opens. The menus respond. The toolbar is there, the Layers panel is there, the file name sits in the tab. Everything about the program looks alive — except the canvas, the one part that matters. Where the image should be, there is only black.

That combination is what makes this symptom different from its neighbours. A program that will not open at all is a different shape. A program that opens and then crashes is a different shape. A display that goes black everywhere, including the desktop, is a different shape. This guide is about a program that works and a canvas that does not, at the same time, in the same window.

The first conclusion most owners reach is that the graphics card has failed, and the first remedy most reach for is reinstalling Photoshop. Both of those first reactions overlook the single fact that defines the symptom: the interface is fine. A dead graphics card does not usually leave the menus perfect and black out only the canvas. A corrupt installation does not usually spare every panel and destroy only the image area. The question is not whether the card works. The question is which rendering path the canvas uses, and where that path breaks.

As #407 already covered, creative software not finding a graphics card at all is a different shape from this one. That guide divides the problem into three appearances: the software offers no GPU choice whatsoever, it lists the card yet the choice stays unusable, or the card looks picked while the processing still falls back to the CPU. Every one of those appearances assumes the software cannot see the card or cannot use it. This guide is the opposite shape: Photoshop sees the card, the interface is normal, and only the canvas is black. The two guides share one piece of logic — that a card visible in Device Manager is not the same thing as a card visible to the software — but they test different layers, and a reader who follows the "software cannot find the card" diagnosis for a black canvas will be testing the wrong thing.

Why the Canvas and the Interface Are Two Different Paths

The key to this symptom is that Photoshop does not draw its interface and its canvas through the same route. The menus, the panels, the toolbar, and the window chrome are drawn through the ordinary interface path that the operating system provides. The canvas — the area where the image itself is composed, zoomed, panned, and redrawn — runs through a separate GPU-accelerated compositing path. The two paths share the same card, but they ask it to do different work through different code.

That separation is why a black canvas with a working interface is a meaningful clue rather than a contradiction. Something can go wrong in the canvas path while the interface path keeps working, because the canvas path is the one that exercises the GPU's compositing, the graphics driver version in use, and the version-specific rendering code of the Photoshop release installed. A fault in any of those three can black out the canvas and leave everything else untouched.

The canvas path also changes with the file. A blank new document, a small JPEG, and a very large layered PSD do not ask the same thing of the rendering path. A large file with many layers, or a file with an unusual colour profile attached, can fail on the canvas while a blank document renders normally. That is why the first comparison in this guide is between files, not between programs: the file itself is one of the variables, and it has to be tested before any layer is blamed.

There is one more point to settle before the layers begin. Turning the GPU off inside Photoshop and watching the canvas come back proves something precise, and it proves nothing beyond that. As #263 already covered for browsers and office software, turning the acceleration switch off and seeing the fault vanish shows only that the fault travels through the accelerated route. It says nothing about whether the card itself has failed, it does not prove the driver is broken, and it does not prove Photoshop is broken. It proves the fault lives somewhere on the GPU rendering path, and the rest of the guide is about narrowing that path down, one variable at a time.

The Five Suspicion Layers

A black Photoshop canvas can fail at five layers, and they must be kept separate. Changing the driver, the Photoshop version, and the GPU setting all at once and finding the canvas back proves nothing about which change did the work, and the black canvas will return the next time only one of those conditions is present. The layers below run from the most direct test to the hardest to isolate, and each one has its own deciding evidence.

LayerWhat it coversDeciding evidence
1. Canvas rendering pathThe GPU-accelerated compositing route the canvas uses, separate from the interfaceTurning "Use Graphics Processor" off brings the canvas back
2. Version regressionA fault introduced by one Photoshop release and absent from the previous oneThe symptom starts with an update and disappears by going back to the earlier release
3. Driver layerThe graphics driver version, the driver branch, and whether the install is cleanA driver update or a clean reinstall changes the symptom
4. Dual-GPU switchingA laptop running the canvas on the integrated GPU instead of the dedicated cardForcing Photoshop onto the dedicated card brings the canvas back
5. File and colour-profile layerThe individual file, its size, or a damaged display colour profileA different file renders normally, or a different profile clears the black canvas

Layer One: The Canvas Rendering Path

This is the layer the symptom itself points at first. The canvas runs through a GPU-accelerated compositing path, and the interface does not. A canvas that is black while the interface is normal is the characteristic shape of a fault in that path, because the path is the one thing that differs between the two parts of the same window.

The evidence for this layer is the toggle test described in the deciding fork below: open Preferences or Settings, go to Performance, switch off "Use Graphics Processor", close Photoshop completely, reopen it, and open the same file. If the canvas is back, the fault sits on the GPU rendering path. That result is a location, not a repair. Switching the GPU off bypasses the acceleration path; it does not fix whatever is wrong with it, and running with the GPU off means giving up the acceleration that the canvas, the zooming, and the panning normally use. The toggle is a test, and it must be treated as one.

A related comparison comes from #272, which covers screenshots and screen sharing where a window looks black in the capture while looking normal to the eye. That guide uses the difference between what the eye sees and what the capture records to separate the drawing surface from the presentation layer. The same thinking applies here in a simpler form: the interface is drawn, the canvas is not, and the split between them is the evidence. What #272 does not cover — and what this guide exists to cover — is the case where the eye itself sees the black canvas, which #272 sends to the application-layer acceleration diagnosis, and which #263 only covers for browsers, office software, and communication software. Creative software was the gap, and this guide fills it.

Layer Two: The Version Regression

A version regression is a fault that appears in one release of Photoshop and was not present in the release before it. It is a version problem, not a hardware problem, and the evidence for it is timing: the canvas was fine, Photoshop was updated, and the canvas went black — or the canvas flickers and flashes in the new release and was steady in the old one.

Two reported cases illustrate the shape, and both must be read as individual reports rather than as general rules. A report about Photoshop 24.3 describes black-and-white flicker on the canvas, discussed on the Adobe community forums and confirmed there by an Adobe community staff member, with the suggested comparisons being the Technology Previews options described below. A separate community report about Photoshop 27.10, dated around 2026-08-31 and involving an RTX 2000 Ada card, describes the interface and the canvas flickering after updating to 27.10, with switching the GPU off or going back to 27.9.1 resolving it for that user. Both are user reports, not Adobe confirmations, and neither one proves that every installation of that release behaves the same way.

The point of this layer is not to collect version numbers. Version numbers change, and a number written as a general standard will be wrong within months. The point is the test: if the symptom began with an update, the version is a suspect, and going back to the earlier release is a comparison that either clears the version or implicates it. If the symptom predates the update, the version layer is not where the fault lives, and no amount of updating or rolling back will settle it.

Layer Three: The Driver Layer

The driver layer is where the canvas rendering path meets the graphics card, and it is the most common trigger point for this symptom. The driver version, the driver branch, and whether the driver was installed cleanly all affect how the canvas path behaves. A driver that is out of date, a driver that was installed over an older one without a clean removal, or a driver release that itself has a problem with a particular Photoshop release can all leave the canvas black while the rest of the system looks normal.

The evidence for this layer is change: updating the driver from the card manufacturer's official website changes the symptom, or a clean removal followed by a fresh install changes it. The clean install matters, because installing a new driver over an old one can leave pieces of the old one behind, and a symptom that survives an ordinary update but disappears after a clean removal points at the install rather than at the version number. A tool such as Display Driver Uninstaller, used to remove the driver completely before reinstalling, is the usual way to make that comparison clean.

One comparison inside this layer needs to be handled honestly, because the published sources disagree about it. A third-party guide argues that using a Game Ready driver causes visual artefacts and that a clean install of a Studio driver is the fix. But as #407 already covered, the Studio and Game Ready branches are built from one shared codebase, and what sets them apart is which software each branch is tested against and how frequently new releases come out. Those two statements conflict, and this guide does not resolve the conflict by picking a side. Switching between the Studio branch and the Game Ready branch is a comparison test, and both statements should be kept in view when its result is read. A branch change that clears the canvas proves that the branch matters for this machine; it does not prove that one branch is the correct one for every machine.

Layer Four: Dual-GPU Switching

This layer belongs to laptops. A laptop with both an integrated GPU and a dedicated graphics card can run Photoshop's canvas on the integrated GPU while the dedicated card sits idle, and the canvas path can fail on the integrated GPU while the rest of the system behaves normally. The symptom is the same black canvas, but the layer is different, and the test is different too.

The evidence is a switch: in the Windows graphics settings, assign Photoshop to the high-performance dedicated card, restart Photoshop, and open the same file. If the canvas comes back, the fault sits in the switching layer. A community report illustrates the shape: a user on an HP Omen laptop with an RTX 5060 Laptop GPU, running Photoshop 27.8 and 26.11.6, reported black horizontal lines appearing only inside the canvas, with the interface completely normal, disappearing entirely when "Use Graphics Processor" was switched off, and stabilising after the laptop was changed from hybrid graphics to discrete graphics. That is one user's result, not an Adobe confirmation, and changing to discrete graphics working for that user does not make it a general repair. It makes it a test result for that machine, and the same test is available to any laptop owner with a hybrid graphics setting.

Some laptops also offer the switch in the BIOS or firmware settings, moving from a hybrid or mixed mode to a dedicated-card mode. That is a firmware-level change, and it should only be made with the machine's own documentation in front of the reader. The Windows graphics setting is the first place to test; the firmware setting is the deeper version of the same test.

Layer Five: The File and Colour-Profile Layer

The last layer is the file itself, or the display colour profile attached to it. The characteristic shape of this layer is selectivity: one file goes black while another renders normally, or the canvas clears when the display profile is changed. A file is not proven damaged by a single black canvas, and the comparison has to be made before any such claim is written down.

Large files are the clearest example. A community report from around 2022, involving Photoshop 23.5 on macOS Monterey, describes PSD and PSB files around 2 GB turning black, with switching the GPU off or changing the ICC display profile as the directions for comparison. That is an old case, and it can only be read as a historical example, not as a description of how current releases behave. But the shape it illustrates is still the right one: when only the large files go black, the size of the file and the memory the canvas path needs for it are part of the question.

The display colour profile is the other half of this layer. A damaged or incorrect ICC display profile can leave the canvas black while the interface, which does not depend on that profile in the same way, keeps working. Recalibrating the display or switching to a different ICC profile is the comparison test for this layer, and changing the monitor or the cable is the exclusion test that sits beside it: if the canvas clears on a different display, the profile or the display chain was involved, and the card itself was not the suspect.

The Deciding Fork: One Toggle That Splits the Problem in Two

The whole guide turns on one test, and it should be done before any other change is made. Switch off "Use Graphics Processor" in Preferences or Settings, under Performance, close Photoshop completely, reopen it, and open the same file that went black.

If the canvas is back, the fault is locked to the canvas GPU rendering path. The card is not proven broken, the driver is not proven broken, and Photoshop is not proven broken. What is proven is the location: the fault lives somewhere on the GPU rendering path, and the remaining layers — version, driver, and dual-GPU switching — are the places to look next.

If the canvas is still black with the GPU switched off, leave the GPU layer behind. The fault is not on the rendering path, because the rendering path is no longer in use. The investigation moves to the file and colour-profile layer: a different file, a different display profile, a different display.

Inside the GPU layer, there is a second fork, and it works by stepping through the Technology Previews options one at a time. First switch on "Use Older GPU Mode (pre 2016)", restart Photoshop, and open the same file. If that does not clear the canvas, switch on "Deactivate Native Canvas" instead, restart, and try the same file again. Change only one setting at a time, and restart Photoshop after each change, because a test that changes two settings at once proves nothing about which one mattered. Whichever level brings the canvas back points at the rendering layer that level replaces. These options are comparison tests, not fixes: running in an older GPU mode or with the native canvas deactivated means running without the current rendering path, and that is a diagnostic result, not a repaired machine.

There is also a third fork, for laptops only. Assign Photoshop to the high-performance dedicated card in the Windows graphics settings, restart Photoshop, and open the same file. If the canvas comes back, the fault sits in the dual-GPU switching layer.

One caution applies to every fork in this guide. Menu names change between releases — newer versions of Photoshop have renamed Preferences to Settings — and the paths given here should be checked against the release actually installed. The Adobe knowledge base article named below is the authority for the current menu paths, and it should be read before any setting is changed.

What the Published Sources Say, and What They Do Not Prove

The published sources for this guide describe individual releases, individual machines, and individual reports, and none of them can be turned into a general rule. They are worth naming honestly, because a reader who only sees one of them can easily mistake a single report for the standard.

Adobe's own knowledge base article, "Resolve GPU and graphics driver issues in Photoshop", last updated 2026-02-23, is the most authoritative source for this guide. It lists GPU-related symptoms including visual artefacts, flickering or flashing canvas, images filled with bright green colour, and partial screen redraws with remnants from other windows. Its guidance includes updating the driver from the card manufacturer's official website and confirming that "Use Graphics Processor" is switched on. That article is the authority for the symptoms and the menu paths, and its version numbers and paths should be read as current at the time of reading, not copied from older tutorials.

The community report about the HP Omen laptop with an RTX 5060 Laptop GPU, running Photoshop 27.8 and 26.11.6, describes black horizontal lines appearing only inside the canvas, with the interface completely normal, disappearing when "Use Graphics Processor" was switched off, and stabilising after the laptop was changed from hybrid graphics to discrete graphics. That is a user report on the Adobe community forums, not an Adobe confirmation, and the discrete-graphics result belongs to that user alone.

A third-party write-up of the Photoshop 24.3 black-and-white flicker describes the problem as a known issue, confirmed by an Adobe community staff member, and gives the first comparison as "Use Older GPU Mode (pre 2016)", followed by "Deactivate Native Canvas", noting that the reports tended to involve older cards or hardware that did not fully support some parts of DirectX 12. That tendency is a description of the reports, not a proof that every affected machine is an old card — and the RTX 5060 case above shows a new card with a canvas problem in a later release, so a version regression cannot be written as an old-hardware problem.

The community report about Photoshop 27.10, dated around 2026-08-31 and involving an RTX 2000 Ada card, describes the interface and canvas flickering after updating to 27.10, with switching the GPU off or going back to 27.9.1 resolving it for that user. Again, that is a user report, not an official confirmation.

The report about 2 GB PSD and PSB files turning black, from around 2022 and involving Photoshop 23.5 on macOS Monterey, is an old case. It can only be read as a historical example of the file layer, not as a description of current releases.

Three conflicts in the sources are set out plainly below, because glossing over them would mislead the reader. First, the Studio driver against the Game Ready driver: a third-party guide says the Game Ready driver causes artefacts and the Studio driver is the fix, while #407 says both branches are built on one codebase and differ only in what they are tested against and how often they ship. This guide treats switching branches as a comparison test and keeps both statements visible. Second, old cards against new cards: one source says the 24.3 flicker tended to affect older cards, while the RTX 5060 case shows a new card with a canvas problem. A version regression is not an old-hardware problem. Third, one third-party document claims that most Photoshop problems are solved by the latest update, attaching a percentage figure to the claim, with no method and no source given. That figure has no basis and must not be quoted.

The Seven Steps

Work through these steps in order, changing one thing at a time and writing down the result after each step. A test that changes two things at once proves nothing about which change mattered, and the black canvas will return the next time only one of those conditions is present.

Step 1: Record the Baseline

Before changing anything, write down the Photoshop version, the graphics card model, the driver version, which file goes black, whether a new blank document goes black too, and whether the black area is the canvas only or the whole program. That note is the baseline every later step is compared against, and it is also the record an in-shop inspection will need.

Step 2: Compare Files

Open a new blank document, then open the file that went black. If the blank document renders normally and the problem file is black, the fault points at the file layer. If both are black, keep going down the steps. This comparison has to come before any setting is changed, because it is the only step that can clear the file layer in one move.

Step 3: The GPU Toggle Comparison

Open Preferences or Settings, go to Performance, switch off "Use Graphics Processor", close Photoshop completely, reopen it, and open the same file. If the canvas is back, the fault is locked to the canvas GPU rendering path. If the canvas is still black, leave the GPU layer behind and move to the file and colour-profile layer. Do not treat switching the GPU off as a repair: it bypasses the acceleration path, and running without it means giving up GPU acceleration.

Step 4: Step Through Technology Previews One Level at a Time

If the toggle test pointed at the GPU layer, work through the Technology Previews options one at a time. First switch on "Use Older GPU Mode (pre 2016)", restart Photoshop, and open the same file. If that does not clear the canvas, switch on "Deactivate Native Canvas" instead, restart, and try the same file again. Change only one setting at a time and restart after each change. Whichever level brings the canvas back points at the rendering layer that level replaces, and that result is a diagnostic finding, not a fix to keep.

Step 5: Compare Drivers

Update the driver from the card manufacturer's official website and test the same file. If the latest driver still shows the black canvas, remove the driver completely with a clean-removal tool and install it fresh, then test again. Comparing the Studio branch against the Game Ready branch is a test, not a repair: both statements about the branches are on record, and a branch change that clears the canvas proves the branch matters for this machine, not that one branch is correct for every machine. Do not write any driver version number down as a general standard — versions change, and the current official release is the reference.

Step 6: The Dual-GPU Comparison, for Laptops

On a laptop, open the Windows graphics settings and assign Photoshop to the high-performance dedicated card, restart Photoshop, and open the same file. If the canvas comes back, the fault sits in the dual-GPU switching layer. Where the laptop offers a firmware option to move from hybrid graphics to a dedicated-card mode, that is the deeper version of the same test, and it should only be changed with the machine's own documentation in front of the reader.

Step 7: Compare Colour Profiles, Then Write the Three-Sentence Conclusion

Recalibrate the display or switch to a different ICC display profile, and test the same file. Try a different monitor or cable as an exclusion test. Then write the conclusion in three sentences: what the symptom is, which change made the symptom appear or disappear, and which possibilities are still not ruled out. That note is the record that makes any further step — including an in-shop inspection — start from evidence instead of from the beginning.

Six Common Misconceptions

Misconception 1: "The interface is normal, so the graphics card is fine"

Wrong. The canvas and the interface run through two different rendering paths. A card can draw the interface perfectly while the canvas path fails, because the canvas path exercises the GPU compositing, the driver, and the version-specific rendering code that the interface path never touches.

Misconception 2: "Switching the GPU off fixed it"

Wrong. Switching the GPU off bypasses the acceleration path; it does not repair whatever is wrong with it. Running with the GPU off means giving up GPU acceleration for the canvas, the zooming, and the panning. The toggle is a test that locates the fault, not a repair that removes it.

Misconception 3: "Installing the latest driver will always fix it"

Wrong. An individual driver release can itself be the trigger point, and a symptom that appears after a driver update points at the driver rather than at the card. A clean removal and reinstall, and a comparison between driver versions, are the evidence — not the version number alone.

Misconception 4: "A new card and a new release cannot have this problem"

Wrong. The 24.3 flicker and the 27.10 flicker are both version regressions, and the RTX 5060 laptop case shows a new card with a canvas problem in a current release. A version regression is not an old-hardware problem, and new hardware is not a guarantee against it.

Misconception 5: "A black canvas means the file is damaged"

Wrong. A single black canvas proves nothing about the file until another file has been compared against it. If a blank document renders normally and only one file goes black, the file layer is the suspect. If every file goes black, the file layer is not where the fault lives, and blaming the file destroys the evidence before the real layer is tested.

Misconception 6: "Reinstalling Photoshop fixes everything"

Wrong. Reinstalling Photoshop changes none of the other layers: not the driver, not the dual-GPU switching, and not the colour profile. Reinstalling before the layers have been separated destroys the clues — the version, the settings, and the exact conditions under which the canvas went black — and leaves the real fault untouched.

Boundaries: Problems That Look Similar but Are Not This One

Several problems look like a black Photoshop canvas but belong to other guides, and naming them here saves the reader from following the wrong diagnosis.

Creative software that cannot find the graphics card at all — no GPU option, a greyed-out option, or work running on the processor despite the card being selected — belongs with #407, which covers that shape in full. A black screen, flicker, or white screen that appears when hardware acceleration is switched on in a browser, in office software, or in communication software belongs with #263, which covers those three kinds of program and draws the boundary at creative software. A window that looks normal to the eye but comes out black in a screenshot or a screen share belongs with #272, which separates the drawing surface from the presentation layer. And a card whose fault is a driver problem that shows up across the whole system, rather than inside one program's canvas, belongs with the driver guides rather than with this one. This guide only covers the shape where Photoshop opens, the interface works, and the canvas alone is black.

When to Stop and Bring the Machine In

Stop when all seven steps have been worked through, one variable at a time, and the layers still cannot be separated. Stop sooner if any step involves opening the machine or changing firmware, or if the canvas problem appears together with artefacts across the whole display, a burning smell, or visible damage — those belong to professional inspection.

Bring the machine in with the notes from the seven steps: the Photoshop version, the card model, and the driver version; which files go black and which render normally; the result of the GPU toggle test; which Technology Previews level, if any, brought the canvas back; which driver versions were compared and whether a clean reinstall was done; for a laptop, which card Photoshop was assigned to and what changed; and which colour profile was in use. That record is what makes an in-shop inspection efficient, because it shows exactly which layers were tested and which evidence each one produced.

In-store 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 (Tier 1 HK$400–780, Tier 2 HK$480–1,380, Tier 3 HK$680–2,800), with the actual price subject to a post-inspection quote. There is no home-visit service and no Mong Kok shop; inspection is carried out in the shop.

A diagnosis that ends at the stop line is not a failed diagnosis. A note that says "Photoshop 27.10, canvas black, interface normal, blank document renders, problem file black, canvas back with GPU off, Older GPU Mode made no difference, Deactivate Native Canvas brought it back" is a precise description of where the fault lives, and it is exactly what an in-shop inspection needs to start from the right place instead of from the beginning.

FAQ

My Photoshop canvas is completely black but the menus and panels all work — is my graphics card dead?

Not necessarily, and the working interface is itself evidence against that conclusion. The canvas and the interface run through two different rendering paths, and a fault in the canvas GPU path can leave the menus perfect. Start with the file comparison, then the GPU toggle test: switch "Use Graphics Processor" off, restart Photoshop, and open the same file. If the canvas comes back, the fault sits on the GPU rendering path, and the card itself is not proven broken.

I switched the GPU off and the canvas came back — is that the fix?

No. Switching the GPU off bypasses the acceleration path; it does not repair whatever is wrong with it. Running with the GPU off means giving up GPU acceleration for the canvas, the zooming, and the panning. Treat the toggle as a test that locates the fault, then work through the version, driver, and dual-GPU layers to find what is actually wrong, and bring the machine in if those layers cannot be separated.

A blank document renders normally but one particular file goes black — is the file damaged?

Not proven. A single black canvas proves nothing about the file until the comparison has been made, and the comparison you have just made points at the file layer — but the file layer includes the file's size and its colour profile as well as damage. Try a different display profile, and try the file on a different display, before concluding the file is damaged. Large layered files can fail on the canvas path while small files render normally.

What are "Use Older GPU Mode" and "Deactivate Native Canvas" — should I leave them on?

They are comparison tests in Photoshop's Technology Previews, not fixes to keep. "Use Older GPU Mode (pre 2016)" runs the canvas through an older rendering mode, and "Deactivate Native Canvas" switches off the current native canvas path. Whichever level brings the canvas back points at the rendering layer that level replaces. Change only one at a time, restart Photoshop after each change, and treat the result as diagnostic evidence rather than a setting to leave switched on.

Should I switch from a Game Ready driver to a Studio driver to fix this?

Only as a comparison test, not as a repair. A third-party guide says the Game Ready driver causes artefacts and the Studio driver is the fix, while #407 says both branches come from a single shared codebase, with the split coming down to validation targets and release pace. Those statements conflict, and this guide does not pick a side. Try the branch change, note whether the canvas clears, and read the result as evidence about this machine, not as a general rule.

The black canvas started right after I updated Photoshop — does that mean the update caused it?

It makes the version a suspect, but timing alone is not proof. A version regression is a fault that appears in one release and was absent from the previous one, and the test is to go back to the earlier release and see whether the canvas clears. The 24.3 black-and-white flicker and the 27.10 flicker are both reported as individual cases, not as universal rules, and neither one proves that every installation of that release behaves the same way.

My laptop has two graphics cards — could that be the cause?

Yes, and it is a layer of its own. A laptop with both an integrated GPU and a dedicated card can run Photoshop's canvas on the integrated GPU while the dedicated card sits idle. In the Windows graphics settings, assign Photoshop to the high-performance dedicated card, restart Photoshop, and open the same file. If the canvas comes back, the fault sits in the dual-GPU switching layer. One reported case, an HP Omen laptop with an RTX 5060 Laptop GPU, stabilised after being changed from hybrid graphics to discrete graphics — that is one user's result, not a general repair.

The canvas is black in Photoshop but fine in other programs — does that rule out the card?

It rules out a whole-system card failure, but it does not rule out the canvas rendering path, the driver version, or the Photoshop release. Other programs do not use Photoshop's canvas compositing path, so a fault that only that path exercises will only show up in Photoshop. That is exactly why this guide tests the canvas path on its own rather than treating "other programs work" as proof that nothing is wrong.

Reinstalling Photoshop did not help — what did I miss?

Reinstalling Photoshop changes none of the other layers: not the driver, not the dual-GPU switching, and not the colour profile. Work through the seven steps in order instead — file comparison, GPU toggle, Technology Previews levels, driver comparison, dual-GPU comparison, and colour-profile comparison — changing one thing at a time and writing down the result after each step. If the layers still cannot be separated, bring the machine in with the notes from those steps.

If all seven steps still cannot separate the layers, what should I bring for inspection?

The notes from the seven steps: the Photoshop version, the card model, and the driver version; which files go black and which render normally; the result of the GPU toggle test; which Technology Previews level, if any, brought the canvas back; which driver versions were compared and whether a clean reinstall was done; for a laptop, which card Photoshop was assigned to and what changed; and which colour profile was in use. The shop is at Room 1209, Dali Plaza, Shek Mun, telephone 2186 8010, WhatsApp 6558 6806. Inspection is charged at the site's published three-tier fees of HK$400–2,800, quoted after inspection. There is no home-visit service and no Mong Kok shop.

Related articles

Related services

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