Create an account on the HP Community to personalize your profile and ask a question
10-19-2022 05:32 AM - edited 10-19-2022 07:28 AM
My printer worked fine until someone decided it was a good idea to store it next to wood shavings, some of which have made their way into the printer.
It keeps reporting a paper jam in tray 2, even with no paper in sight, and the entire tray being taken out. It would make sense for said wood shavings to be interpreted as jammed paper.
I have taken off all exterior panels, I have flipped the printer around into every orientation, and used compressed air to blow out as many wood shavings as possible, from every crevice I could get at, especially in the paper tray area. I have fully reset the printer's memory, and it keeps reporting the same jam.
Obviously there must be some sort of logic behind the paper jam error, some sort of condition must be fulfilled for it to report as such, like a sensor covered in wood dust, or a shaving caught in some gears.
This printer was in perfect working condition before this incident, and I will do whatever it takes to get it up and running again. It's long out of warranty, and I'm not afraid of disassembly. Does anyone know of spots I should be checking? Alternatively, does someone know where I can find a disassembly manual if it comes to that?
Update: Poking around in the event log is giving me an error code 13.0314. Codes 13 just means jam which I'm aware of, but I can't find any documentation for the rest of the code.
10-30-2022 05:20 AM
Welcome to HP Support Community. This is a great place to post questions and find answers.
Thank you for posting your query, I will be glad to help you.
I see that you are facing paper jam issues with your HP Color LaserJet Pro M254nw.
Please follow the steps from this document.
Let me know if this works
Take care and have a good day.
Please click “Accepted Solution” if you feel my post solved your issue, it will help others find the solution. Click the “Kudos/Thumbs Up" on the bottom right to say “Thanks” for helping!
Didn't find what you were looking for? Ask the community