ASKO Dryer Error Code F4

F4 on an Asko dryer indicates that fluff or lint has been detected in the fluff filter, the condenser, or both. The code appears at the end of a drying program as a maintenance alert rather than a mid-cycle shutdown. It is telling you that airflow is restricted and cleaning is required. Addressing it promptly helps protect the dryer's heating components from thermal stress.

The F4 code appears after a cycle ends, so the dryer has already completed its run, but continuing to use it without cleaning the filter and condenser is not advisable. Restricted airflow from lint buildup causes elevated internal temperatures, which can stress the thermostat and heating components over time. Cleaning the affected parts before the next cycle is the recommended course of action.

In most cases, resolving F4 costs nothing beyond the time it takes to clean the fluff filter and condenser, as these are routine maintenance tasks. If the 115 degree Celsius auto-reset thermostat has failed and needs replacement, repair costs including parts and labor typically range from around 80 to 200 dollars depending on your location and whether you hire a technician. Keeping up with regular filter cleaning is the best way to avoid any repair costs associated with this code.

Start by removing and cleaning the fluff filter, then locate and clean the condenser unit by rinsing it under running water to clear accumulated lint from the fins. After cleaning both components and allowing them to dry, reinstall them and run a short cycle to confirm the error does not return. If the code persists, check the 115 degree Celsius auto-reset thermostat to ensure it has reset and is functioning correctly.

Simply resetting the dryer without cleaning the fluff filter and condenser will not permanently clear the underlying cause of F4. The error is tied to a physical lint accumulation condition, so the reset may temporarily clear the display but the code is likely to return after the next cycle if the cleaning is skipped. Address the lint buildup first, then confirm the error is gone.