F36 appears after heavy cooking
The cooktop was running multiple zones or a large pan for a while, then shut down and showed the code.
Start here: Start with a full cool-down and check for blocked airflow around and below the cooktop.
Cooktop Error Code Help
LG Induction Cooktop F36 Error Code
Direct answer: An F36 error on an LG induction cooktop usually means the unit is seeing a cooling problem or an internal electronics fault. The first things to check are whether the cooktop was overheated, whether the air intake and exhaust areas are blocked, and whether a full power reset clears the code.
Most likely: The most common real-world causes are trapped heat under the cooktop, a cooling fan that is not running right, or a control issue that keeps reading an unsafe temperature condition.
Start with the simple stuff you can see and feel. If the code showed up right after heavy cooking, let the unit cool fully and reset power first. Reality check: induction cooktops protect themselves fast when they think heat is building where it should not. Common wrong move: killing power for ten seconds and calling it reset; give it a full few minutes so the electronics actually discharge.
Don’t start with: Do not start by ordering a control board. A blocked vent path or a fan that is jammed with grease and dust can throw the same kind of fault.
If the code appeared after long high-heat cooking,let the cooktop cool completely before testing again.
If the code comes back cold at startup,suspect a fan, sensor, or control problem instead of simple overheating.
Last reviewed: 2026-04-17
What the F36 code usually looks like
F36 shows up right away on a cold cooktop
The surface is cool, but the code returns almost immediately after power is restored.
Start here: Start with a longer power reset, then move quickly to fan and internal fault suspicion.
One zone was in use before the code
The cooktop may power on, but the error appears when you try to use a burner area.
Start here: Look for heat buildup, fan trouble, or a sensor/control issue triggered under load.
Fan noise changed before the error
You heard rattling, weak airflow, or no fan sound at all before the cooktop faulted.
Start here: Check for blocked intake, debris, or a failed cooktop cooling fan branch.
Most likely causes
1. Restricted airflow under the cooktop
Induction units depend on moving air through the cabinet space. Stored pans, liners, insulation, or tight installation gaps can trap heat and trigger protection codes.
Quick check: Open the cabinet below if there is one and look for anything crowding the underside or vent path.
2. Cooktop cooling fan not running properly
If the fan is seized, noisy, slow, or electrically dead, the cooktop can read rising internal heat and shut itself down with an error.
Quick check: After a cool restart and brief use, listen for normal fan operation and feel for airflow where the unit vents.
3. Temporary control lockup after overheating or power disturbance
A hard reset sometimes clears a false fault after a heat event or voltage glitch, especially if the cooktop otherwise looks and sounds normal.
Quick check: Shut power off at the breaker long enough for the display to go fully dead and stay off for several minutes.
4. Internal temperature sensing or control failure
If the code returns on a cold unit with clear airflow and no obvious fan issue, the cooktop may be misreading temperature or the control may be failing internally.
Quick check: Note whether the code appears before any burner is started or only after a short heating cycle.
Step-by-step fix
Step 1: Let it cool fully and clear the easy heat-load causes
A lot of induction fault codes are honest heat warnings, not failed parts. If the cooktop was worked hard, you want to rule that out before opening anything.
- Turn all cooking zones off.
- If the surface was recently used, wait until the cooktop is fully cool to the touch.
- Remove any pans, griddles, foil, or covers from the surface.
- Open the cabinet or drawer below if present and make sure stored items are not packed against the underside of the cooktop.
- Look for blocked vent slots or heavy dust buildup around visible air openings and wipe accessible areas with a dry cloth.
Next move: If the code does not return after the cooktop cools and the area below is cleared, the problem was likely heat buildup or restricted airflow. If F36 comes back on a cool cooktop, move on to a real reset and then fan checks.
What to conclude: You have separated a one-time overheat event from a repeat fault.
Stop if:
- You smell burning plastic or hot wiring.
- The glass is cracked.
- You see scorch marks, melted trim, or smoke.
Step 2: Do a real power reset
These controls often need more than a quick off-on cycle. A proper reset can clear a latched fault after overheating or a power glitch.
- Turn the cooktop off.
- Switch the correct breaker fully off.
- Wait at least 5 minutes, not just a few seconds.
- Turn the breaker back on and power up the cooktop.
- Test one burner on a low setting with a proper induction-ready pan.
Next move: If the cooktop runs normally and the code stays gone, the fault was likely temporary. If the code returns immediately or within a minute or two, the issue is probably not just a control hiccup.
What to conclude: An instant return points more toward airflow, fan, sensor, or control trouble than a simple reset issue.
Step 3: Check whether the cooling fan is actually moving air
A failed or dragging cooktop cooling fan is one of the strongest causes when an induction unit throws a heat-related code even though the top does not seem excessively hot.
- With power on and one burner briefly running, listen near the cooktop for fan sound after a short delay.
- Open the cabinet below and feel carefully for airflow from the underside vent area without touching internal parts.
- Listen for rattling, scraping, or a fan that starts and stops.
- If the unit is unplugged or breaker-off and you can safely access the underside cover area without disturbing wiring, look for heavy grease, dust mats, or debris blocking the fan intake area.
Next move: If you find and clear obvious debris and the fan returns to normal airflow, the cooktop may run normally again. If there is no fan sound, weak airflow, or obvious fan noise with the code returning, the cooling fan branch is strongly supported.
Step 4: Separate a fan problem from a deeper internal fault
Once airflow is ruled out, you want to decide whether this is a practical component repair or a point where pro diagnosis makes more sense.
- Note whether F36 appears before any burner is used or only after heating starts.
- If the code appears on a cold startup with clear venting and no fan issue, suspect an internal sensor or control reading problem.
- If the code appears only after a short heating cycle and the fan is not running right, treat the cooktop cooling fan as the leading repair path.
- If the fan runs normally, airflow is clear, and the code still returns, stop short of guessing at internal electronics.
Next move: If the symptoms line up cleanly with a dead or noisy fan, you have a reasonable part-first repair path. If the pattern points to internal sensing or control trouble, the next move is service diagnosis rather than random parts.
Step 5: Repair the supported fault or book service with good notes
By now you should know whether this was a heat buildup issue, a likely fan failure, or an internal electronics problem that needs bench-level diagnosis.
- If the code stayed gone after cooling and clearing space, keep the vent path open and monitor the cooktop during normal use.
- If the fan branch is clearly supported, replace the cooktop cooling fan only after matching fitment to your exact cooktop.
- If the code returns cold with normal airflow and fan operation, schedule appliance service and report that F36 returns after full cool-down and breaker reset.
- Write down whether the code appears cold, after a few minutes of cooking, or only during heavy multi-zone use.
A good result: A successful fan repair or airflow correction should let the cooktop heat normally without the code returning.
If not: If the code still returns after airflow correction or a confirmed fan repair, internal control or sensing diagnosis is the next step.
What to conclude: You are either finishing a supported repair or giving the tech the exact clues needed to avoid guesswork.
Replacement Parts
Repair Riot may earn a commission from qualifying purchases, at no extra cost to you.
FAQ
What does F36 mean on an LG induction cooktop?
In practical terms, F36 usually points to a cooling or internal temperature-related fault. The cooktop thinks heat is building where it should not, or it is getting a bad reading from the parts that monitor and manage that heat.
Can I keep using the cooktop with an F36 code?
No. If the code is active, the cooktop is protecting itself. Repeatedly trying to run it can make an overheating or electronics problem worse.
Will unplugging or flipping the breaker fix F36?
Sometimes, but only if the fault was temporary. Give it a full cool-down and a real 5-minute power reset. If the code comes back, especially on a cold unit, there is likely an airflow, fan, or internal component problem.
Is F36 usually a bad control board?
Not usually as the first guess. Restricted airflow and a failing cooktop cooling fan are more sensible checks first. A control problem moves up the list when the code returns cold and the fan and vent path look normal.
How do I know if the cooktop cooling fan is bad?
The strongest clues are no fan sound, weak airflow, rattling or grinding noise, or a fan that starts and stops while the cooktop quickly throws F36. If the fan runs normally and the code still returns, the fault may be deeper than the fan.
Can a blocked cabinet below the cooktop cause this code?
Yes. Induction cooktops need breathing room underneath. Tight storage, liners, insulation, or dust-packed vents can trap heat and trigger a fault even when the glass top itself does not seem extremely hot.