Direct answer: On an LG induction cooktop, an F33 code usually means the unit is seeing a fault it cannot clear on its own, most often tied to unstable power, poor cooling airflow, or a failed internal control or fan circuit.
Most likely: Start with a full power reset at the breaker, make sure the cooktop is cool and the air inlets are not blocked, then see whether the code returns immediately or only after a burner runs for a few minutes.
First separate when the code appears. If F33 shows up the moment power comes back, think control or power issue. If it shows up after cooking for a bit, think cooling problem first. Reality check: error codes often point you to an area, not a single guaranteed bad part. Common wrong move: cycling the touch panel on and off over and over instead of doing a real breaker reset.
Don’t start with: Do not start by ordering a cooktop control board just because the display shows a code. A bad reset, heat buildup, or supply issue can look the same at first.
The display shows F33 before you start a pan heating cycle, or it comes back within seconds of turning the cooktop on.
Start here: Start with a full breaker reset and basic power-supply clues before suspecting a failed cooktop touch control board.
The cooktop works cold, then throws F33 after several minutes, especially on higher heat settings.
Start here: Start with cooling airflow and fan behavior, because heat-related faults often show up only after the cabinet warms up.
One section quits heating or triggers the code sooner while other zones may still respond for a moment.
Start here: Look for a localized internal fault, but still rule out overheating and blocked ventilation before replacing parts.
A breaker reset buys you a short window, then the code comes back during normal use.
Start here: That pattern leans away from a simple glitch and toward a cooling fan problem or failing cooktop control electronics.
Induction controls can latch a fault until power is removed long enough to fully discharge. A weak or unstable supply can also bring the code back right away.
Quick check: Turn the cooktop off and reset it at the breaker for a full 5 minutes, not just a quick off-on flip.
If F33 shows up after cooking for a while, trapped heat under the glass is a strong fit. Tight drawers, stored pans, or blocked intake paths can push the unit into protection.
Quick check: Let the cooktop cool completely, then check underneath and around the cabinet opening for anything crowding the vent path.
A weak or dead cooling fan lets the unit start normally when cold, then fault once internal temperatures climb.
Quick check: Run a zone briefly and listen for the internal fan. If the code appears with no fan sound or no moving air, that branch gets stronger.
If F33 appears immediately after reset, with normal airflow and no heat buildup, the control side becomes more likely.
Quick check: If the code returns cold, fast, and consistently on restored power, internal electronics are the leading suspect.
This is the safest first move and it clears a lot of false starts on induction units. A quick tap on the power button is not the same thing.
Next move: If the code stays gone and the cooktop runs normally, you likely had a latched fault or brief power glitch. If F33 comes back right away, move to power and control clues next. If it comes back only after cooking, skip ahead with cooling in mind.
What to conclude: Immediate return points more toward supply or internal electronics. Delayed return points more toward overheating or fan trouble.
You want to know whether the cooktop fails cold or only after it warms up. That saves a lot of guessing.
Next move: If the cooktop runs several minutes with no code, the fault may be intermittent and heat-related rather than a constant control failure. If the code appears cold with no heating attempt, internal control trouble is more likely. If it appears after warming up, stay on the cooling path.
What to conclude: Cold failure usually points to control or supply issues. Warm failure usually points to airflow restriction or a failing cooktop cooling fan.
Induction cooktops depend on moving air under the unit. A blocked cabinet space can trigger a fault without any bad part at all.
Next move: If the code stays away after clearing the space and dust, overheating was likely the trigger. If airflow is clear and F33 still returns after a few minutes of heating, the cooling fan itself becomes the stronger suspect.
A working fan is one of the clearest field clues on a heat-related F33 complaint. You are checking behavior, not doing live electrical testing.
Next move: If you can hear the fan come on and the cooktop now runs longer without fault, the problem may have been restricted airflow rather than a dead fan. If there is no fan sound or airflow and the code appears after warming up, plan on a cooktop cooling fan replacement or professional confirmation.
By now you should know whether this is a simple reset issue, a ventilation problem, a likely fan failure, or a control-side fault.
A good result: If the cooktop runs through several normal heating cycles without F33, the repair path was correct.
If not: If F33 remains after reset, clear airflow, and the likely repair, the unit needs professional diagnosis for internal power electronics.
What to conclude: A repeat F33 after the basic checks usually means the problem is inside the cooktop, not in your cookware or day-to-day use.
Repair Riot may earn a commission from qualifying purchases, at no extra cost to you.
In practical terms, F33 means the cooktop has detected a fault it cannot ignore. The most useful split is whether it happens cold or only after heating. Cold and immediate points more toward control or power trouble. Delayed and heat-related points more toward airflow or cooling fan trouble.
Only if it clears after a proper reset and stays gone through normal use. If it keeps returning, especially with heat or a burning smell, stop using it until the cause is found. Repeated faulting can stress internal electronics.
A full power reset can clear a latched fault, but only if power is removed long enough. On many built-in cooktops that means turning the breaker off for about 5 minutes. If the code comes right back, the reset did not solve the underlying problem.
Usually not as the main cause. Wrong cookware can cause poor heating or pan-detection complaints, but an F33 code is more often tied to the cooktop's own cooling, control, or power side. Still, use a known induction-ready pan during testing so you are not chasing two problems at once.
Not always. Control boards get blamed too early on error-code calls. If the code shows up only after the cooktop warms up, check airflow and fan behavior first. A control board becomes more likely when F33 appears immediately after reset with the unit still cold.