We had a power outage yesterday, and when the power came back it seems my printer is now fried... when I try to print, I hear a knocking sound, it tries to initalize, it sounds ok then hear this knocking sound and the result is... "Scanner failure Turn power off then on again" I have tired this a dozen times and the printer again trys to initialize with the same result... I cant copy, print or do anything with out this... HELP!! I love this printer!!!!
a 6ya Technician can help you resolve that issue over the phone in a minute or two.
Best thing about this new service is that you are never placed on hold and get to talk to real repair professionals here in the US. click here to Talk to a Technician (only for users in the US for now) and get all the help you need. Goodluck!
- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
By 'scrolls' I guess you mean 'feeds paper'?
If display screen is blank since the outage, try switching off and unplugging the printer for a minute or so, then re plug.
Unfortunately, a power outage often results in surges and brownouts while power is being restored, which can disrupt or damage electronics and electrical devices.
The board may have fried.
There are two things. I most likely suspect that the print head wiper blade has stuck to the print head. Very common problem after a power failure.
Not sure how I didnt see your post before now. But if your still having that problem let me know, I can tell you how to fix it.
Surge protectors are meant to trip whenever an outage occurs to prevent component damage. If possible remove back panel and check if any fuses were burned. If all looks normal then your component is most likely fried.
that error message is nothing to do with the software part, it actaully hardware issue try the following,
1) unplug the machine and connect it to wall outlet directly,
2) unplug the power cord from the printer and press and hold ON for 1 min and release the ON button and plug it back..
3) Disconnect the power cord from the product.Press and hold # and 6 while reconnecting the power cord to the product, and then release both buttons and if printer turns off, turn it back ON and wait until it cmopletes its instialization and if still persists, it a hardware failure...............
if the scanner bulb is not moving, then its an hardware problem. We can try by resetting the printer.
POWER DRAIN:-Turn off the printer, Unplug the power cable from printer and from the wall outlet.Press and hold ON buton for 30-60 seconds.
PARTIAL RESET:-Unplug the printer power cable while its ON, press and hold # and 3 button and connect the Power cord while holding.Wait untill the ON light flashes, then release the buttons.
----(for below reset cartridges must be removed out)---------
SEMI_FULL RESET:-Unplug the printer power cable while its ON, press and hold # and 6 button and connect the Power cord while holding.Wait untill the ON light flashes,or wait for 20 seconds,hen release the button.If the printer goes off dont worry release the button and Push the ON button.
FULL NVM RESET:-Take the Ink Cartridges out, Unplug the printer power cable while its ON, press and hold OK/ENTER and CANCEL button and connect the Power cord while holding the buttons.keep Holding the buttons until the printer goes off ,release the button and Push the ON button.
Unfortunately, if an HP scanner quits functioning, the whole unit is dead. You may want to unplug the printer from its power source and USB cable for about 5 minutes, plug them all back in and then retry. Sometimes, a scanner job can get stuck in the spooler and cause the whole thing to stop working until the job is done (even though there isn't a job to do). I had this issue once and this worked.