Electrolux Washer Error Code EF5

EF5 means the washer detected an excessively unbalanced load and skipped the final spin cycle to protect internal components from stress. The code is not shown on the display during operation but is stored in the internal fault log for retrieval during a service diagnostic. Your laundry will come out noticeably wetter than normal when this occurs. The most common cause is a load that could not be redistributed evenly inside the drum.

The washer is generally safe to continue using because the machine took a protective action by skipping the spin rather than forcing it through an unbalanced condition. However, if EF5 is being triggered repeatedly, it suggests the suspension system may be worn, and running the machine in that state over time can increase stress on bearings and the drum assembly. Address the underlying cause promptly to avoid more serious mechanical wear.

If the cause is simply an unbalanced or oversized load, there is no repair cost at all. If worn shock absorbers are responsible, parts and labor typically range from around $100 to $250 depending on the model and local labor rates. Suspension rod or spring replacement is generally in a similar cost range. A service diagnostic visit to read the fault log and inspect the machine usually costs between $75 and $150 before any parts are factored in.

Start by opening the door and manually redistributing the laundry so items are spread evenly around the drum, then run a spin-only cycle. If the problem repeats, try reducing the load size or separating heavy items like towels from lighter fabrics. If EF5 logs frequently even with balanced, properly sized loads, inspect the shock absorbers and suspension rods for wear or damage, as those components may need replacement.

Because EF5 is stored silently in the internal fault log rather than displayed on the control panel, a standard power reset will not clear the stored code. The fault log entry is typically cleared using a service diagnostic mode or a technician's diagnostic tool. That said, resolving the imbalance issue itself will prevent new EF5 events from being logged going forward.