57 Fan Error on Laser Jet Pro 200

[symonw]

Hi Everyone, 

I hope someone can help with this. I recently got an error on my LaserJet Pro 200 saying '57 Fan Error'. I did the usual, tried to restart it as per HP instructions, but no luck.

I came across a few options online about the fan being dusty and that the cleaning solve the problem. I opened the cover but the inside was pretty clean to be fair. 

I then ordered a replacement fan and proceeded to replace it using these instructions

 https://www.ifixit.com/Guide/HP+Laserjet+Pro+200+Color+MFP+Fan+Replacement/123450

but, even the new fan is not spinning. 

Any advice would be greatly appreciated. 

[CharlieItuah1]

Remedy: Turn the product power off, wait at least 30 seconds, and then turn the product power on and wait for it to initialize. If you are using a surge protector, remove it. Plug the product directly into the wall socket. Turn the product power on.

[symonw]

Hi, I appreciate your reply, but as I mentioned in my post, I have already tried restarting the printer (switching It off for 30sec and turning it on again), but this doesn't resolve the issue. I'm not using the surge protector.

[CharlieItuah1]

Have you tried a factory reset on the  LaserJet Pro 200? 

To perform a NVRAM/Cold Reset on the hp laserjet pro 200

1. Power down the printer

2. Press and hold the lower left-hand corner of the screen a. This is normally where the progress bar starts loading on the screen

3. Power on the printer

4. Release the left-hand corner once the "Permanent Storage Init" message appears.

Use this video as a guide

https://www.youtube.com/watch?v=WTCJ9fvKRz8

[symonw]

Charlietuah1, I have just done NVRAM/Cold Reset, but still no luck, the error persists.

Since I have tried a couple of new fans and that did not help, is it possible that one of the boards is faulty? I'm also thinking is there another fan on this printer that this message might relate to? I have swapped the fan that is located on the righthand side of the printer near the LCD display.

[CharlieItuah1]

Yes, it could be the motherboard that is causing the error. It needs to be replaced. That seems like the obvious solution right now,