HP Printer Error Codes Explained
Quick answer
HP printer error codes are grouped by family: 13.XX codes are paper jams, 49.XX are firmware crashes, 50.XX are fuser heating failures, and 59.XX are motor faults. The two digits before the dot name the system involved; the digits after narrow the cause. Power-cycle once — a code that returns usually means a hardware repair.
Every HP LaserJet error code follows the same pattern: the two digits before the dot name the system that failed, and everything after the dot narrows down why. Once you can read the family, you know within seconds whether you're dealing with a two-minute fix or a part that needs replacing.
How to read an HP error code
Take 50.2 as an example. The 50 tells you the fuser — the unit that heat-bonds toner to the page — reported a fault. The .2 tells you it failed during warm-up. Newer LaserJets use longer codes like 13.B2.D1 or 50.2F, but the logic is identical: family first, detail after.
One habit that saves a lot of time: read the code off the printer's own control panel, not off Windows. Windows will often just say the printer is in an error state or offline — the panel gives you the real diagnosis. Write down the full code, including everything after the dot, before you power-cycle. The code is the single most useful thing you can give a technician.
The error families we see most in offices
Across our service records, a handful of families account for most of the error-code calls on business LaserJets — led by paper-path jams, then motor faults, fuser faults, and firmware crashes. Here's the map:
| Family | What it points to | Usual outcome |
|---|---|---|
| 13.XX | Paper jam — the digits tell you where the paper stopped | Clear the path; repeat jams mean worn rollers or a sensor |
| 49.XX | Firmware crash — often triggered by a specific print job | Power-cycle; if it persists, firmware update |
| 50.XX | Fuser (heating) failure | Cool-down and retry once; a returning code means fuser replacement |
| 51.XX / 52.XX | Laser/scanner assembly fault | Hardware — usually a repair visit |
| 55.XX / 59.XX | DC controller / motor faults (59.F0 is a common one on color models) | Hardware — motor or drive-train work |
| 10.XX | Supplies memory — the printer can't read a cartridge chip | Reseat or replace the cartridge |
| 30.XX | Scanner/ADF fault on MFPs | Check for obstructions; recurring codes are hardware |
| 79 / 80.XX | Firmware or network-card fault | Disconnect network, power-cycle, update firmware |
What to try before calling anyone
- Write down the full code — including the digits after the dot.
- Power-cycle properly. Turn the printer off at its own power switch, wait 30 seconds, and turn it back on. For fuser (50.XX) codes, leave it off for 20–30 minutes so the fuser actually cools.
- Reseat the obvious suspects. Toner cartridges, paper trays, and rear-door/duplexer covers all have switches and contacts that a half-seated part can trip.
- Check for a stuck job. A corrupt print job can crash the firmware (the classic 49.XX pattern). Clear the print queue before you retry.
- Note what triggered it. If the code appears every time one person prints one kind of document, that detail points straight at the cause.
Codes that usually end in a repair
Some codes are worth one retry and no more. In our experience, these are the ones that come back:
- 50.XX that returns after a full cool-down — the fuser is at end of life. Here's the full 50.XX breakdown.
- 59.XX motor codes — a drive motor or its circuit is failing; power-cycling only postpones it.
- The same 13.XX jam code, over and over — especially with no paper visible. That's rollers or a sensor, not paper. The 13.XX guide covers it.
- 49.XX that survives a firmware update — at that point the formatter board is the suspect.
If Windows is only telling you the printer is in an error state with no code on the panel at all, that's usually a different problem — start here instead.
If a code keeps coming back after a power cycle and the basic checks, the printer is telling you a part is failing — that's a repair, not a settings fix. Our technicians see these exact codes every week, and the full code you wrote down usually tells them which part is failing before they arrive.
From our service records
Our technicians have logged 350+ repairs involving 13.XX, 49.XX, 50.XX, 59.XX errors for businesses across our network.
See our recent work in Los Angeles, CA, San Antonio, TX, Austin, TX.