GPU Code 38 in Device Manager: Previous Driver Still in Memory? Restart, Fast Startup & Driver Reload Diagnosis Guide

Key Takeaway
Device Manager Code 38 means Windows cannot load the graphics driver because a previous copy of it is still in memory. It is a loading-timing problem, not proof the card is faulty, and Microsoft's remedy is to restart. This guide separates five suspicion layers and walks through seven steps to trace the cause.
What This Problem Is — and What It Is Not
Picture the scene: the display has dropped to a low resolution, or a game refuses to start, or the screen looks wrong in a way that was not there yesterday. Device Manager is opened, the display adapter is expanded, and there is a yellow exclamation mark. Opening the device's properties and reading the Device status box gives the full message: "Windows cannot load the device driver for this hardware because a previous instance of the device driver is still in memory. (Code 38)."
That message is the whole problem this guide covers, and the first thing to establish is what the message actually says, because the wording is the diagnosis. Windows is not saying the graphics card is faulty. It is not saying the driver file is missing or damaged. It is saying something much more specific: it tried to load the display driver, and it could not, because a previous copy of that driver is still sitting in memory and has not been unloaded. The new load is blocked by the old one still being there.
One honest point must be made before anything else, because it shapes the whole guide: Code 38 is a general Windows device-driver code. It applies to any device whose driver fails to load for this reason, and it is not specific to graphics cards. The same code appears on other kinds of hardware for the same underlying reason. This guide applies the code to graphics cards, because that is where the reader has met it, but nothing in the mechanism below is unique to graphics hardware. The code, the causes, and the remedy are Windows behaviour, and the graphics card is simply the device in question this time.
The steps below are written for the following situation:
- Device Manager shows Code 38 on the display adapter, with the full status message quoted above. A different code number is a different problem, even if the yellow exclamation mark looks the same.
- The problem often appears close in time to a driver change — a driver update, reinstall, card swap, or Windows update — but it can also appear suddenly, for example after a background Windows Update changed the driver. Code 38 is a loading-timing problem, and it appears when a driver is being loaded or replaced.
- The display may fall back to a basic mode: a low resolution, a generic display driver doing the work, or the graphics card simply not being used. The computer still starts, and Windows still runs, but the proper graphics driver is not loaded.
- The steps apply to desktop and laptop computers running Windows. On a laptop, first establish which graphics processor the code belongs to — the built-in screen may be driven through the integrated graphics.
Several nearby behaviours look similar but are not this problem. A device that has been deliberately disabled shows a different code and a downward arrow icon, not a yellow exclamation mark. A driver that fails to load because its signature cannot be verified is a different code again, about signing rather than timing. A driver that fails to load because its files are damaged is a different code with a much wider set of possible causes. And a graphics card that crashes during a game, or goes black under load, is a different problem entirely — this guide is about a driver that cannot be loaded at all, before any game or application has even started. The code number is what separates these problems, which is why Step 1 asks for the full status text to be copied down, not just the number.
Why does the distinction between "cannot load" and "broken" matter so much? Because the remedy Microsoft itself gives for Code 38 is a single word: restart. That is the only official remedy. If the card were faulty, no restart would ever fix it. The fact that a restart is the prescribed fix tells the reader what kind of problem this is: a state problem, not a hardware problem. The seven steps below are built around that fact — they test whether the state can be cleared, and they only move toward deeper causes when the simple clearing steps have failed.
A note on the structure of this guide: the five suspicion layers, the seven steps, and the six misconceptions are the whole structure. Every section below refers back to them, and the numbers stay the same throughout — five layers, seven steps, six misconceptions — so that a result at any step can be traced back to the layer it tests.
Why Restart Is the Official Fix: How Driver Loading Works
To understand Code 38, it helps to understand what Windows does with a driver. A driver is not a program that runs all the time. Windows loads the driver into memory when the device is needed, and unloads it again when the device is no longer in use. Loading and unloading happen constantly, invisibly, every time the computer starts, every time a device is used, and every time a driver is updated or replaced.
Code 38 appears when that cycle breaks at the handover. Windows wants to load the display driver, but the previous copy of the driver is still in memory and has not been unloaded, so the new load is refused. Microsoft's own documentation names three ways this can happen, and these three are the only causes this guide will use, because they are the only ones Microsoft states:
- An incorrect reference count. Windows keeps a count of how many things are still using a driver. If that count is wrong — if the system believes something is still using the old driver when nothing is — it will not unload the old copy, and the new copy cannot load.
- A race between loading and unloading. The new driver is being loaded at the same moment the old driver is being unloaded, and the two operations collide. The new load arrives before the old unload has finished, and it is refused.
- One driver referenced by more than one installation instruction. The same driver is referenced by multiple INF AddService instructions — several installation entries pointing at the same driver service — so the system cannot tell which one is the current version, and the old instance stays loaded.
All three causes share one feature: they are timing problems, not damage problems. Nothing is broken, nothing is missing, and nothing has been corrupted. The old driver simply has not got out of the way yet, and the new driver cannot get in.
That is also why a restart is the remedy. A restart clears memory completely and loads every driver fresh, in order, from a clean state. There is no old copy left in memory to block the new one, because memory itself has been cleared. A restart does not repair anything — there is nothing to repair — it simply gives the loading cycle a clean start.
But there is a catch, and it is the most important idea in this guide: on a modern Windows computer, shutting down is not the same as restarting. That difference is the subject of the next section, and it is the reason Code 38 can survive a shutdown and come straight back.
The Fast Startup Trap: Why Shutting Down Does Not Clear the Old Driver
Fast Startup changes what "shut down" means. With Fast Startup switched on, shutting the computer down does not fully clear the system. Instead, Windows performs a hybrid shutdown: it saves the kernel state, together with the drivers already loaded in memory, into the hibernation file (Hiberfil.sys), and on the next start it restores that saved state instead of loading everything fresh.
That design makes starting faster, but it has a direct consequence for Code 38. If the old driver instance is still in memory at the moment of shutdown, the hybrid shutdown saves it along with everything else — and the next start restores it, stuck copy and all. The computer appears to have been switched off and on again, but the driver state was never cleared. The old instance comes back, the new driver is refused again, and Code 38 is still there. The reader has "restarted" the computer, in the everyday sense of the words, and nothing has changed — because in the technical sense, the computer was never restarted at all.
This is the reason Code 38 can seem stubborn. The reader shuts the computer down, switches it on again, and the code is still there, which looks like proof that the problem is serious. In fact it is proof of nothing except that the shutdown was a hybrid one. A real restart — chosen from the Start menu as Restart, not as Shut down followed by switching on again — loads everything fresh and clears the stuck state. That is why Microsoft's remedy says "Restart your computer" and not "Switch your computer off and on again", and why Step 2 of this guide insists on the distinction.
There is also a way to force a full shutdown without restarting: holding the Shift key while clicking Shut down. That produces a complete shutdown, the saved kernel state is not written, and the next start loads everything fresh — the same result as a restart, reached by a different route. Step 3 uses that as a comparison test, because the result separates the Fast Startup layer from every other layer: if a restart clears the code but an ordinary shutdown brings it back, and a Shift shutdown behaves like a restart, the hybrid shutdown is the cause.
The Five Suspicion Layers
Code 38 can come from five layers, and they must be kept separate. Mixing them together is how a Fast Startup problem gets treated with a driver reinstall, or a leftover driver version gets blamed on a faulty card, and how the real cause survives because the wrong layer was treated.
Layer One: The Leftover State Layer — The Old Driver Instance Has Not Been Unloaded
The first layer is the mechanism itself: the old driver instance is still in memory, for one of the three reasons Microsoft names — an incorrect reference count, a race between loading and unloading, or several installation instructions pointing at the same driver service. The deciding test is timing: did the problem appear after a driver update, a driver reinstall, or a card swap, and does it disappear after a single restart? If a restart clears the code, the problem was in this layer — a leftover state, not a hardware fault — and no further step is needed. This is the layer to test first, because a restart is Microsoft's own remedy and it is also the cheapest test.
Layer Two: The Fast Startup Layer — The Hybrid Shutdown Brings the Old State Back
If a restart clears the code but an ordinary shutdown and start brings it back, the diagnosis moves to this layer. The hybrid shutdown is saving the stuck driver state into the hibernation file and restoring it on the next start, so the old instance is never cleared. The deciding tests are the comparisons in Steps 3 and 4: a Shift shutdown that behaves like a restart points at this layer, and switching Fast Startup off temporarily and watching the behaviour over several days confirms it. If ordinary shutdowns stay clean with Fast Startup off, the hybrid shutdown was the cause. This layer is a setting, not a fault, and the remedy is a setting change, not a repair.
Layer Three: The Driver Version and Leftover Layer — An Old Driver Version Is Still in the System
The third layer is the driver version itself. An old driver version may not have been fully cleared, or Windows Update may have installed an older driver version again in the background after a newer one was put in place, so the new and old drivers are confused at the handover. The deciding test is a comparison of the driver version and the timing of updates: does the installed version match the one that was intended, and did the problem start at the moment of an update? If a clean reinstall of the driver makes the code disappear, this layer was the cause. The detailed removal procedure belongs to the dedicated driver guides, and this guide does not repeat it; it only names the option and the order — the driver's own built-in clean installation option first, and a thorough removal tool only if that fails. What matters here is the comparison, not the procedure.
Layer Four: The Third-Party Interference Layer — Another Program Interferes with Driver Loading
The fourth layer is interference from third-party software. Driver update tools and system optimisation programs can interfere with driver loading at startup, and published guidance lists this as a cause of Code 38. The deciding test is a clean boot comparison: starting Windows with only essential services and seeing whether Code 38 disappears. If it does, a third-party program is a suspect. One rule governs this layer, and it is strict: no specific program may be named as the culprit. The test can only show that something loading at startup is interfering, and the search must then proceed one program at a time. Naming a program without that evidence would be guessing, and guessing is not a diagnosis. Driver updates must only ever come from the manufacturer's official source, never from a third-party driver update program — and a third-party program of that kind is itself a possible source of interference, which is why it should not be used to fix a problem it may be causing.
Layer Five: The Device and Enumeration Layer — Remove and Re-Detect
The fifth layer is the device itself and how Windows enumerates it. Removing the device in Device Manager and then scanning for hardware changes makes Windows detect the device again from scratch and load its driver fresh. The deciding test is what the code becomes after that: if the code disappears, the problem is solved; if the code changes into a different code — Code 43, Code 31, or Code 10, for example — then the Code 38 state was only hiding the next layer of the problem, and the diagnosis must follow the new code instead of staying inside the Code 38 framework. A change of code is itself diagnostic information: it means the removal cleared one blockage and revealed another. Do not keep treating the problem as Code 38 once the code has changed.
Taken together, the five layers give the diagnosis its shape. The leftover state layer asks whether the old driver instance has been unloaded. The Fast Startup layer asks whether the hybrid shutdown is bringing it back. The driver version layer asks whether an old version is still in the system. The third-party layer asks whether another program is interfering with loading. And the device layer asks whether re-detecting the device clears the blockage — or reveals a different code underneath.
The Seven Diagnostic Steps
Work through these steps in order, and change only one thing at a time. The order is part of the diagnosis: the cheap, decisive tests come first, and the heavier tests come only after the cheap ones have ruled out their layers. Before any step that involves changing settings or restarting, note down the readings from Step 1, so that every later result can be compared against them.
Step 1: Copy Down the Full Status Text
Open Device Manager, expand Display adapters, open the graphics card's properties, and read the Device status box on the General tab. Copy the full text down, not just the words "Code 38". Also note when the problem first appeared, and what happened just before it — a driver update, a driver reinstall, a card swap, or a Windows update. A code number on its own is not evidence; the full message, the timing, and the change that came before it are the evidence, and they are also what will be brought to an in-store inspection if the diagnosis ends at the stop line.
Step 2: Restart Once — From the Start Menu, Not by Shutting Down
Choose Restart from the Start menu. Do not shut the computer down and switch it on again — that is a hybrid shutdown under Fast Startup, and it may bring the stuck state straight back. A restart loads every driver fresh from a clean state, which is exactly what Microsoft's remedy prescribes. After the restart, go back to Device Manager and check whether the code has disappeared. If it has, the problem was a leftover driver state, and the diagnosis is finished. If it is still there, move on — but do not repeat the restart hoping for a different result. One restart is the test; a second one tests nothing new.
Step 3: The Shift Shutdown Comparison
Hold the Shift key while clicking Shut down, which forces a complete shutdown instead of a hybrid one, and then switch the computer on again. Compare the result with Step 2. If the code disappears after this full shutdown, just as it did after a restart, the hybrid shutdown is a suspect — the ordinary shutdown was restoring the stuck state. If the code comes back after a Shift shutdown exactly as it did after an ordinary shutdown, the Fast Startup layer is less likely, and the search moves on. The point of this step is the comparison, not the shutdown itself.
Step 4: Temporarily Switch Off Fast Startup and Observe Over Several Days
In the power options, temporarily switch Fast Startup off, and then watch the behaviour over several days of ordinary shutdowns and starts. If shutdowns stay clean with Fast Startup off, the hybrid shutdown was the cause, and the suspicion on this layer grows stronger. If the problem still appears, this layer is ruled out. This step takes time, and that is the point: a single clean shutdown proves little, because a race between loading and unloading may not happen every time. Several days of clean shutdowns is the evidence. Fast Startup is only switched off temporarily for this comparison; whether to leave it off afterwards is a separate decision, and it should be made on the basis of the result, not before it.
Step 5: Remove the Device and Scan for Hardware Changes
In Device Manager, remove the display adapter, then use the Action menu to scan for hardware changes, and let Windows detect the device again. Then read the code again. If the code has disappeared, the problem is solved. If the code has changed into a different code — Code 43, Code 31, or Code 10 — stop treating the problem as Code 38 and follow the new code instead, because the removal has cleared one blockage and revealed another. Do not keep repeating the removal in the hope that Code 38 will return to being the problem; a changed code is a new diagnosis, not a failed test.
Step 6: Cleanly Reinstall the Driver
Use the driver installer's own built-in clean installation option first. Only if that fails should a thorough removal tool be considered — the order must not be reversed. The driver must come only from the manufacturer's official source; third-party driver update software must not be used, because it is itself a possible source of interference. After the reinstall, read the code again and compare. If the code has disappeared, the old driver version or its leftovers were the cause. If it is still there, the driver version layer is ruled out, and the diagnosis moves to the stop line.
Step 7: The Stop Line
If a restart, a full shutdown, switching Fast Startup off, removing and re-detecting the device, and a clean driver reinstall have all been done and Code 38 is still there — or if the code changed into Code 43, Code 31, or Code 10 and the flow for that new code also failed to resolve it — stop. Do not disable the device directly, and do not edit the registry. Neither of those is a fix for Code 38, and both can make the problem worse or hide the evidence an inspection needs. Bring the machine in with the record kept along the way: the full status text from Step 1, when the problem started, what changed before it, the result of the restart, the result of the Shift shutdown comparison, the result of the Fast Startup observation, and the result of the removal and reinstall steps.
A Quick Comparison: The Seven Diagnostic Steps at a Glance
| Step | What to do | What it tests | What the result means |
|---|---|---|---|
| 1. Copy the full status text | Record the full Device status message, when it started, and what changed before it | Whether this is Code 38 and what preceded it | The full message, not just the number, is the evidence |
| 2. Restart from the Start menu | Choose Restart, not Shut down and switch on again | The leftover state layer | The code disappearing means a leftover driver state |
| 3. Shift shutdown comparison | Hold Shift while clicking Shut down, then start again | The Fast Startup layer | Behaving like a restart points at the hybrid shutdown |
| 4. Switch Fast Startup off temporarily | Observe ordinary shutdowns over several days | The Fast Startup layer, confirmed over time | Clean shutdowns with it off point at the hybrid shutdown |
| 5. Remove device and scan for hardware changes | Remove the adapter, then scan for hardware changes | The device and enumeration layer | The code disappearing means solved; a new code means follow the new code |
| 6. Cleanly reinstall the driver | Built-in clean install option first, thorough removal tool only if that fails, official source only | The driver version and leftover layer | The code disappearing means the old version was the cause |
| 7. Stop line | Stop after all steps, or when the code changes and the new code's flow also fails | Whether the problem is beyond home diagnosis | Do not disable the device or edit the registry; bring the machine in |
Boundaries: Problems That Look Similar but Are Not This One
A diagnosis is only as good as its boundaries. Several nearby problems share a yellow exclamation mark, a driver that will not load, or a display that has fallen back to a basic mode, but each belongs to a different guide, and the steps above will not fix them:
- Code 31 is not Code 38. Code 31 means the driver failed to load, and the causes are broad — damaged files, incompatibility, and signing problems are all possible. Code 38 means something much narrower: the old driver instance is still in memory. The two flows must not be swapped, because a broad cause needs a broad search and a narrow cause needs a narrow one.
- Code 22 is not Code 38. Code 22 means the device has been disabled, shown with a downward arrow icon. Code 38 means the driver cannot load, shown with a yellow exclamation mark. The icon and the handling are completely different.
- Code 52 is not Code 38. Code 52 means the driver's signature failed verification, so loading was refused at the signing layer. Code 38 means the old instance is occupying memory, so loading was refused at the timing layer. The layer is different, and so is the fix.
- A laptop with two graphics processors. Before disabling or removing a display adapter on a laptop, establish clearly whether it is the discrete graphics or the integrated graphics. The built-in screen may be driven through the integrated graphics, so disabling the wrong one can leave the screen blank. Identify the card first, then act.
- A company computer. Group policy on a company machine can affect driver loading. If Code 38 appears on a company computer, ask the IT department first instead of changing policy settings yourself.
- Code 38 on other devices. The same code appears on other kinds of hardware — it is commonly described for USB devices, for example — because it is the same Windows code and the same loading mechanism. The mechanism in this guide applies there too, but the device-specific steps differ, and this guide covers the graphics card application only.
The principle is to isolate one thing at a time. A code that disappears after a restart, or after a full shutdown, or after Fast Startup is switched off, or after the device is removed and re-detected, is evidence — and the evidence points in different directions depending on when it disappears. The seven steps are arranged so that each result narrows the field, and the note kept along the way is what turns a yellow exclamation mark into a diagnosis someone else can continue.
Six Common Misconceptions
Misconception 1: "Code 38 means the graphics card is broken."
No. Code 38 is a driver loading-timing problem: the old driver instance is still in memory, so the new driver cannot load. Microsoft's only recommended remedy is to restart the computer. A faulty card would not be fixed by a restart, and a restart is the first test precisely because the problem is about state, not hardware. Start with Step 2, not with the assumption of a fault.
Misconception 2: "Shutting down and switching on again is the same as restarting."
No. With Fast Startup switched on, shutting down is a hybrid shutdown: the kernel state and the loaded drivers are saved into the hibernation file and restored on the next start, so the stuck old driver instance comes back with them. A restart loads everything fresh. That difference is the whole reason Code 38 can survive a shutdown and disappear after a restart.
Misconception 3: "Reinstalling the driver will always fix Code 38."
No. Until the old driver instance in memory has been unloaded, a reinstall cannot load either — the new copy is refused for the same reason the old one was. The restart or the full shutdown has to come first, to clear the old instance, and only then can a reinstall succeed. Reinstalling first is doing the steps in the wrong order.
Misconception 4: "Code 38 and Code 31 are the same thing."
No. Code 31 means the driver failed to load, and the causes are broad — damaged files, incompatibility, and signing problems are all possible. Code 38 means one specific thing: the previous driver instance is still in memory. The causes have already been narrowed to the loading-timing layer, and the two flows must not be swapped.
Misconception 5: "Seeing Code 38 means the card should be replaced immediately."
No. Microsoft's only recommended remedy is to restart. Before any talk of replacing a card, the seven steps should be worked through: restart, full shutdown comparison, Fast Startup observation, removal and re-detection, and a clean driver reinstall. A card should only be suspected after those steps have all failed, not at the first sight of the code.
Misconception 6: "Using a third-party driver update program will take care of it."
No. A third-party program can itself be the source of interference with driver loading, and drivers must only come from the manufacturer's official source. Handing the job to a third-party updater does not fix a loading-timing problem, and it can introduce a new variable — a different driver version, or a program interfering at startup — into a diagnosis that was about state.
When to Stop and Bring the Machine In
Code 38 problems can be found at Step 2, where a single restart clears the code, or at Step 3, where a full shutdown behaves like a restart and points at Fast Startup. If all seven steps have been worked through, one variable at a time, and the code is still there — or if the code changed into Code 43, Code 31, or Code 10 and the flow for that new code also failed to resolve it — stop. Do not disable the device, and do not edit the registry. Further guessing risks changing things that were never part of the problem, and a change made on a guess is not a diagnosis.
Bring the machine in with the notes from Step 1 and the results of each step tried: the full status text, when the problem started, what changed before it, the result of the restart, the result of the Shift shutdown comparison, the Fast Startup observation, and the results of the removal and reinstall steps. 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, quoted after inspection. There is no home-visit service and no Mong Kok shop; inspection is carried out in the shop.
One last point about expectations: a diagnosis that ends at the stop line is not a failed diagnosis. A note that says "Code 38 after a driver update; restart clears it; ordinary shutdown brings it back; Shift shutdown behaves like a restart" is a precise description of where the fault lives, and it is exactly what an in-store inspection needs to start from the right place instead of from the beginning.
FAQ
Q1: Device Manager shows Code 38 on the graphics card. Does that mean the card is broken?
No. Code 38 is a driver loading-timing problem: Windows cannot load the driver because a previous copy of it is still in memory. Microsoft's only recommended remedy is to restart the computer. A faulty card would not be fixed by a restart. Start with the restart in Step 2, not with the assumption of a fault.
Q2: Is shutting down and switching on again the same as restarting?
No. With Fast Startup switched on, shutting down is a hybrid shutdown: the kernel state and the loaded drivers are saved into the hibernation file and restored on the next start, so a stuck old driver instance comes back with them. A restart loads everything fresh. That is why Microsoft's remedy says restart, and why Step 2 insists on choosing Restart from the Start menu.
Q3: Will reinstalling the driver always fix Code 38?
No. Until the old driver instance in memory has been unloaded, a reinstall cannot load either — the new copy is refused for the same reason. The restart or the full shutdown has to come first, to clear the old instance, and only then can a reinstall succeed. Reinstalling first is doing the steps in the wrong order.
Q4: Are Code 38 and Code 31 the same thing?
No. Code 31 means the driver failed to load, and the causes are broad — damaged files, incompatibility, and signing problems are all possible. Code 38 means one specific thing: the previous driver instance is still in memory. The causes have already been narrowed to the loading-timing layer, and the two flows must not be swapped.
Q5: Should I replace the graphics card as soon as I see Code 38?
No. Microsoft's only recommended remedy is to restart. Work through the seven steps first — restart, full shutdown comparison, Fast Startup observation, removal and re-detection, and a clean driver reinstall — before any talk of replacing a card. A card should only be suspected after those steps have all failed.
Q6: Can I just use a third-party driver update program to fix it?
No. A third-party program can itself be the source of interference with driver loading, and drivers must only come from the manufacturer's official source. Handing the job to a third-party updater does not fix a loading-timing problem, and it can introduce a new variable into a diagnosis that was about state.
Q7: How should the seven-step diagnosis be done, and what should I do first?
Step one is to copy down the full Device status text, plus when the problem started and what changed before it. Step two is to restart from the Start menu — not shut down and switch on again — and check whether the code has disappeared. After that, run the Shift shutdown comparison, temporarily switch Fast Startup off and observe over several days, remove the device and scan for hardware changes, and cleanly reinstall the driver from the manufacturer's official source. Change only one thing at a time, and record each result.
Q8: Is Code 38 specific to graphics cards?
No. Code 38 is a general Windows device-driver code that applies to any device whose driver fails to load for this reason, not specific to graphics cards. The same code appears on other kinds of hardware — commonly described for USB devices, for example — for the same loading mechanism. This guide applies the code to graphics cards, because that is where the reader has met it.
Q9: I have a laptop with two graphics processors, or a company computer. Does the same diagnosis apply?
With changes. On a laptop, establish clearly whether the code belongs to the discrete graphics or the integrated graphics before disabling or removing anything, because the built-in screen may be driven through the integrated graphics. On a company computer, group policy can affect driver loading, so ask the IT department first instead of changing policy settings yourself. The restart and Fast Startup comparisons still apply in both cases.
Q10: When should I stop trying things myself and bring the machine in for inspection?
Stop when a restart, a full shutdown, switching Fast Startup off, removing and re-detecting the device, and a clean driver reinstall have all been done and Code 38 is still there; or when the code changed into Code 43, Code 31, or Code 10 and the flow for that new code also failed; or before any step that involves disabling the device or editing the registry. Bring your notes: the full status text, when the problem started, and the result of each step. In-store inspection is at Room 1209, Dali Plaza, Shek Mun, charged at the site's published three-tier fees of HK$400–2,800, quoted after inspection. You can call 2186 8010 or WhatsApp 6558 6806.