Error Appeared Right After Servicing: Board Locked, Not Dead

An error appears immediately after a service, and damage is assumed. Whether the board is broken or merely holding a state.

By Team Snowflake | Updated 24 Aug 2026

Teaching case based on recurring Snowflake service patterns; identifying details are combined.

How this presents

An error appearing immediately after a service visit, on equipment that ran normally beforehand. Power was interrupted at the unit during the work. The system behaves normally in every respect apart from the displayed error.

Setup: Samsung Wall-mounted10-12 yearsOfficeMarina East
Misread as: Damage caused during servicing, with a part now needing to be replaced.
Check first: Whether the system behaves normally in every respect except the display

What else produces this

A system behaving normally while showing a fault is the pattern that separates a record from a condition. If something were genuinely wrong, the behaviour would show it. What produces a display without a symptom is a latched state, and the commonest cause of one is an interruption at the wrong moment, which is exactly what a service visit provides. That makes the sequence of the visit more informative than any test.

Normal operation in every respect apart from the display separates a stored state from a live fault.
An error first appearing immediately after that visit ties it to the work rather than to the machine.
Power interrupted during the work gives the board a reason to latch a state it never cleared.
No repeat after a full, correctly performed reset confirms that nothing was actually wrong underneath.

Why it happens

Control boards latch certain states so a fault cannot be hidden by the system simply restarting. Cutting power at an unexpected moment can leave the board holding a state it was never told to release, and it keeps displaying that state indefinitely because nothing has instructed it otherwise. The equipment is entirely healthy underneath. The display is reporting a moment rather than a condition.

What resolution involves

A full reset is carried out to the manufacturer's procedure, which clears the stored state and returns the display to normal. It is worth being clear about what this is and is not: a reset is a legitimate answer to a latched state and never a legitimate answer to a live fault. Anything that returns after a proper reset was a condition, and it needs finding rather than clearing again.

How to tell it worked

A run of several days with no return of the code at all. A fault that comes back after a correct reset was never a stored state, and clearing it a second time would be avoiding the question.

Before you approve a quote

A latched fault is a record, not a condition

A system behaving normally while showing an error is displaying a memory, not a symptom.
A code that appears immediately after a visit usually belongs to something that happened during it.
A reset is the right answer to a latched state and the wrong answer to anything that returns.

Questions this case answers

Error code appeared right after servicing: is the control board dead?

The board is holding a latched state rather than failing: certain faults are latched deliberately so a system cannot hide a genuine problem by restarting itself, and cutting power at an unexpected moment can leave that state set with nothing to release it.

What happens if power is cut while the aircon is still running?

The board can latch a state and keep displaying a stored error even though the equipment is healthy underneath. The way to tell it from a live fault is behaviour: a live fault shows in how the system runs, while a stored state does not.

Should a board be replaced on a unit still under warranty?

No. This board was healthy underneath, and a full reset cleared the stored state. If the code returns after a correct reset, that is a genuine condition to find rather than another part to order.

Is a reset the same as switching the aircon off and on again?

A reset is carried out to the manufacturer's procedure to clear the stored state, while simply interrupting power at the wrong moment is what latches it. That is why an error appearing straight after a visit is worth reading as a latched state first.

Describe your situation

Tell us what’s going on. Symptoms, setup, photos, anything we should know. We’ll assess and come back with the right next step.

WhatsApp us