Frigidaire Dryer Error Code E52

E52 indicates either a motor relay stuck in the closed position on the main control board (rotary-start models) or a motor fault where the motor has stopped or failed to start (push-button models). Common causes include motor overheating, an overloaded drum, low supply voltage, a wiring issue, or a defective motor or control board. The specific diagnosis depends on the dryer's start type.

No, you should not continue operating the dryer while E52 is active. The error indicates the motor has faulted or a control board relay has failed, either of which can lead to overheating, further component damage, or a safety hazard if the motor circuit remains energized unexpectedly. Leave the dryer unplugged until the fault has been properly diagnosed and resolved.

Repair costs vary based on the root cause. If only a professional service call is needed to diagnose and reset the thermal protector, costs typically fall in the lower range of appliance service fees, often between $75 and $150. Replacing a main control board usually runs between $150 and $350 including parts and labor. A motor replacement is generally the most expensive repair, often ranging from $200 to $450 or more depending on parts availability and local labor rates.

Some causes of E52 are DIY-friendly. You can start by removing the load from the drum, checking that the drum spins freely by hand, and waiting up to 30 minutes for the motor thermal protector to reset before trying again. Checking the circuit breaker and verifying the dryer has proper power are also straightforward steps. However, replacing a control board or motor requires comfort working with appliance wiring and should be done by someone experienced with that type of repair.

A power reset may temporarily clear the code, but if an underlying fault exists, such as a stuck relay, defective motor, or wiring problem, the error will return. On push-button models where the motor overheated, allowing 30 minutes for the thermal protector to reset and removing excess load before restarting may resolve the issue. If the code comes back repeatedly, a component has failed and needs to be diagnosed and replaced.