Home › Lexmark › Lexmark Printer › Lexmark Paper Jam & Service Errors (200.xx, 241.xx, 900.xx, 920.xx, 121.xx): Fixes

Lexmark Paper Jam & Service Errors (200.xx, 241.xx, 900.xx, 920.xx, 121.xx): Fixes

Lexmark Printer display showing GUIDE — FixCode Guide error code graphic

Lexmark's 2xx codes map the paper path — 200 and 201 at the front, 241 to 244 in the trays, 251 at the multipurpose feeder — and its 9xx codes mark the boundary between what an owner clears and what a service engineer repairs: 900, the firmware/RIP family, and the fuser temperature families, 920 to 925 on classic models and 121 on current ones. This guide clears jams the way Lexmark's own jam guides order the work, then treats the service families with the discipline Lexmark's documentation gives them, including the scanner service codes 840 and 841-846 that share their procedure.

Safety first. Lexmark's safety framing for owner work is consistent across its guides: power the printer off before removing cartridges, trays or jammed paper; treat the fuser area as hot (its jam guidance carries the caution that the inside of the printer might be hot, and jammed sheets near the fuser should be handled after the machine cools); and for the service families, unplug the power cord from the wall outlet entirely rather than relying on the power switch — the 900-999 and 841-846 procedures are written that way for a reason. Lexmark also publishes a power-source warning that doubles as troubleshooting for fuser errors: plug the printer directly into a properly grounded wall outlet, because power strips, surge devices and UPS units can starve the fuser of current and manufacture false fuser errors; verify the outlet matches the 110/220 volt rating on the printer's label. Cartridges and imaging units are user-replaceable supplies designed to be swapped with the printer off and no tools; the fuser behind the 121 and 920 families, the RIP/controller board behind 900.xx, and the scanner assembly behind 840/841-846 are service parts in Lexmark's documentation — its guides route every one of those families, once the published power procedure fails, to Customer Support or a service representative, and that routing is the safety instruction, not a sales preference.

Jam numbers are a map of the paper path

Lexmark numbers a jam by where the paper stopped, and once that is understood the 2xx block stops being a catalogue and becomes a route. A sheet's journey through a Lexmark laser starts at a source — a tray (241 for tray 1, then 242, 243, 244 through the optional trays in stack order) or the multipurpose feeder (251) — passes the front input area under and around the cartridge (200, then 201 as it gets further in), crosses the image and fuser sections (the 202/23x territory of the modern table), and exits (the duplex and output families beyond this guide's core scope). Lexmark's modern error-code table (the CS963 guide's printer-error-codes page) publishes this map in its purest form: long blocks of suffixes grouped under the single wording 'Paper jam in [LOCATION]', with the printer's own display supplying the location text — the number locates, the machine narrates. The classic guides say the same thing in door language: the Lexmark W840 jam guide, for example, groups 200, 201 and 202 as one instruction, 'Paper Jam — Check Door A', because from the owner's side of the plastic those three sensor reports are one place to open and clear. Two working rules fall out of the map. First, clear where the code points, completely: a jam is rarely one sheet, and the scrap left in the pointed-at section is the next code already scheduled. Second, read a moving jam as information: a printer whose codes migrate (241 today, 200 tomorrow, a clean week, then 241 again) is reporting one underlying feed problem at whichever sensor catches it, while a printer welded to a single suffix on verified media has localised its own fault to that sensor's stretch of path. Lexmark's jam-avoidance guidance in its guides is the prevention half of the same map: use only recommended media, do not overload sources past their stack marks, and keep media in condition — most of the map is walked because of paper, not machinery.

200.xx and 201.xx: the front path, Check Door A

The 200 family reports the input area — paper that fed and did not arrive through the front path as the sensors expected. Lexmark's modern table lists the 200 block (200.03 through the 200.5x suffixes and their kin) as 'Paper jam in [LOCATION]', and the classic jam guides give the family its working address: 200, 201 and 202 together are 'Paper Jam — Check Door A', the front and side door area, where the sheet's first obstacle course runs under the toner cartridge. The classic owner procedure those guides teach is the one still worth following in spirit on any generation: open the door the display names, remove the cartridge if the model's guide directs it (the jammed sheet is frequently stuck under it), and pull the sheet out gently and completely — then look again, because the family's characteristic failure is the torn corner or the label that stays behind and re-jams the next sheet at the next sensor, converting one clear into a tour of the whole 20x block. 201 is the family's second station: paper that entered and stopped in the next section of the same front path, and in the modern table it appears inside the same jam block (201.91 among the listed suffixes). Treating 200 and 201 as one clear-out, as Lexmark's Door A grouping does, is not laziness — it is the correct unit of work, because the two sensors share one stretch of path and one pile of possible scraps. When the path is provably clean — every scrap accounted for on the removed sheets, which should be checked for completeness like a torn banknote — and the same family returns on fresh, recommended media, the report has changed character: it is no longer announcing paper, it is announcing an input sensor or feed mechanism that believes in paper, and that is a service check for which Lexmark wants the full code, suffix included, quoted.

241.xx to 244.xx: the tray jams, in stack order

The 24x families assign each tray its own jam number, and the order is the machine's physical order: 241 is tray 1, the standard tray, and 242, 243 and 244 follow the optional trays down the stack — Lexmark's modern table names them by hardware: 242 is the optional 550-sheet tray, the 243 block serves the 2 x 550-sheet tray and the 2000-sheet tandem tray positions, and the 244 suffixes appear across both the tandem group and the 1500-sheet tray group, which is why 244 in particular must be read with the display's location text rather than from the number alone. The clearing work is per-tray and unglamorous: pull the named tray, remove the jammed sheet and every scrap from the tray well (sheets crumple at the pick point and hide under the stack), check the stack itself — overfilled past the height marks, guides not set to the media, a damaged top sheet that will simply jam again at the same sensor — reload, and close firmly. The family's most instructive member is the one that is not a jam at all: Lexmark's table separates 241.16 and 241.82-241.84 out of the jam block as 'Paper loading error in [LOCATION]', with a published procedure that never mentions jammed paper — open tray 1, remove and readjust the paper stack, adjust the paper guides if necessary, reload tray 1, close tray 1. A loading error survives any amount of jam-hunting because nothing is jammed; the stack is loaded so the tray cannot feed from it, and readjusting the stack is the whole fix. The diagnostic habit for the whole 24x block follows: a jam that follows a tray (same tray, different paper) indicts that tray's feed rollers or pick mechanism; a jam that follows a stack of paper from tray to tray indicts the media; and a jam that exists only in the report, with the tray and well clean and the stack correct, indicts the sensor the suffix names — shop information Lexmark's suffixes were designed to carry.

251.xx: the multipurpose feeder jam

The 251 family is the manual feed's own report, and Lexmark's jam documentation words it with unusual completeness: a sheet of paper or specialty media failed to feed completely from the multipurpose feeder. The MP feeder earns its separate number because it is the path of exceptions — envelopes, labels, card, transparencies and odd sizes that the trays never see — and its jams are correspondingly more often about the media and its guidance than about the machine: a feeder guide not set to the media's width, a sheet inserted crooked or not far enough, specialty stock the feeder cannot grip. Lexmark's published clearing procedure divides on visibility, and it is worth following literally. If part of the sheet is visible, gently pull the jammed sheet from the front of the multipurpose feeder — gently and in the feed direction, because the part-fed sheet tears easily and a torn half converts a one-minute clear into the invisible case. If the sheet is not visible, the procedure goes inside: open the front door and remove the unit, lift the flap at the front of the printer, remove any jammed sheets — Lexmark notes these may be short lengths of paper, which is the remains of earlier optimistic pulls — then align and insert the unit, close the front door, and press Continue to resume. That phrase about short lengths is the family's lesson in miniature: 251s recur because the feeder hides debris where its users cannot see it, in front of the flap; a 251 cleared only from outside is often a 251 postponed by one job. Media discipline closes the family: one sheet or a small, guided stack of supported specialty media, guides touching its edges, is how the MP feeder is documented to be fed — it is a hand-fed path that happens to hold a small stack, not a fifth tray.

900.xx: the firmware and RIP family

The 900 family is where the paper path ends and the computer inside the printer reports itself. Lexmark's User's Guide files the entire range under '900-999 Service <message>' and gives it one procedure; its service documentation gives the family its anatomy: the E320 Service Manual defines 900 as a controller software error or illegal trap, and the CS510 Service Manual's 900.xx check works through the RIP board — the processor board that rasterises print jobs — its cables, and the firmware, in a deliberate isolation order. That order is the family's real content for an owner, because it encodes the family's central ambiguity: a 900 can be a single corrupt or pathological print job trapping healthy firmware, or healthy jobs arriving at a failing board, and the two wear the same code. Lexmark's service flow separates them by subtraction — disconnect the communications cables, restart into operating mode, print the printer's own pages (error log, menu settings page, network settings page): a 900 on internal pages with nothing connected is the printer's; a 900 that only follows one document from one computer is that document's. The owner's share of the flow is the guide's procedure, performed once and reported honestly: turn the printer off, unplug the power cord from the wall outlet, check all cable connections, plug the cord into a properly grounded outlet, turn the printer back on — and if the service message appears again, contact Customer Support and report the message. What makes that report valuable is context Lexmark's flow tells its technicians to capture, and owners can capture first: the full 900 suffix, what was printing (application, driver, file type) or whether nothing was, and whether the code appears at power-on, on internal pages, or only on sent jobs. A 900 diary of three occurrences is worth more to the diagnosis than a month of power cycling.

920.xx to 925.xx and 121.xx: the fuser temperature families, two generations

The fuser — the heated unit that bonds toner to paper — reports its temperature failures in two numbering generations, and a complete guide must keep both, because the installed base carries both. On classic models the family is 920 to 925 under the words Service Fuser: Lexmark's T65x/X65x support articles define the 920 type precisely — the printer registers the fuser unit, the internal heating element, as not having reached its proper operating temperature — with examples including 920.06, 920.12 and 920.40, and the family stated as 920.01-style suffixes across the 920-925 range. Lexmark's owner procedure for it is a small masterpiece of honest triage: power off for ten seconds or more, power on, and if the printer reaches Ready, print and watch it for a few days; if the error returns at power-up or printing, then work the power source before suspecting the fuser — plug the printer directly into a wall outlet rather than through a surge device or power strip, because strips and UPS units can cause a low-amperage problem that triggers false fuser errors (intermittent ones especially), verify the outlet matches the 110 or 220 volt rating on the printer's power label, and try a different wall outlet before seeking service. On current models the same organ reports as 121.xx, which Lexmark's knowledge base titles a service fuser error and the CS720 Service Manual tabulates suffix by suffix: overwhelmingly 'fuser did not reach the required temperature' at a named stage — during warm up (121.26), with power at 100 percent (121.06), during steady state (121.20), while a page is in the fuser (121.08) — with over-temperature members (121.02, 121.31 fuser too hot) and hardware members (121.03 fuser hardware and driver mismatch, 121.22 open fuser relay), every one of them routed by the manual to the same destination: the fuser service check. The difference between the generations is the user's role: 920-era owners get Lexmark's power-source checks to perform, because they genuinely cure the false share; 121-era documentation gives owners no procedure at all, because the suffix table is written for the technician. In both generations the endpoint is identical — a fuser that cannot reach temperature on a proven wall outlet is a service part, and repeated power cycling is not a treatment for it.

840.xx and 841-846: the scanner service codes on MFPs

On Lexmark multifunction models, the scanner keeps its own small service vocabulary beside the print engine's, and its two entries teach the same user/service discipline as the 9xx families. 840 is the disabled report: Lexmark's guide wording for 840.01 is that the scanner was disabled by the system support person, or the scanner detected a hardware error and disabled itself — and its index form splits the two stories as 840.01, scanner disabled by admin, and 840.02, scanner disabled, contact the system administrator if the problem persists. The first question for an 840 is therefore administrative, not mechanical: in offices, scanners are disabled deliberately, and a disabled-by-policy scanner is re-enabled by the administrator, not repaired. Only when nobody disabled it does the second clause govern — the scanner's own self-check failed and it took itself out of service, which is already a diagnosis the machine performed on itself. 841-846 is the scanner service error range, and Lexmark publishes it exactly as a range: its guide entry is headed '841-846 Scanner Service Error' and gives the shared service procedure — turn the printer off, unplug the power cord from the wall outlet, check all cable connections, connect the power cord to a properly grounded outlet, turn the printer back on, and if the service message appears again, contact Customer Support and report the message. The range treatment is itself the accuracy lesson this guide has applied throughout: any source assigning six distinct individual meanings to 841, 842, 843, 844, 845 and 846 is exceeding Lexmark's published user documentation, whatever its service manuals may contain. An owner with an 841-846 that survives the documented power procedure has a scanner service call, and the full number — again — is the thing to quote.

Unverified suffixes and the limits of this guide

This guide's final section names what it has not defined, because Lexmark's numbering invites invention precisely where its documentation is grouped. Within the 920 family, Lexmark's support articles verify the range 920-925 and define the 920 type — the fuser not reaching proper operating temperature — but no second Lexmark document checked for this guide publishes separate user-level meanings for 921.xx, 922.xx or 923.xx individually, and 924.xx and 925.xx stand in the same position: they are therefore named here as members of a verified family and given no invented per-number definitions, in the short table and in this guide alike. Within the jam block, the modern table's discipline runs the other way: dozens of 200, 202, 231, 232 and 240-series suffixes are published by Lexmark under the single wording 'Paper jam in [LOCATION]', with the printer supplying the location — so beyond the families this guide covers (200, 201, 241, 242, 243, 244, 251), no per-suffix location charts are published here, because Lexmark has not published them in the documents checked and deriving them from the numbers' arithmetic would be fabrication wearing a pattern's clothes. The same restraint covers the 23x duplex-path suffixes and the 202/203 exit-area codes that the classic jam guides mention (the W840 guide groups 202 with 200/201 under Check Door A, and lists 203 as a Check Areas/Exit instruction) — documented as group members in a jam guide, not defined as standalone codes in this batch. An owner holding any of these numbers loses nothing by the restraint: Lexmark's jam clearing is by location, not by suffix theology — open where the display points, clear it completely, and quote the full number to Lexmark if the same suffix keeps returning on a path you have proven clean. The number's job, in the families where Lexmark groups its documentation, is to be reported exactly — and exactness, not elaboration, is what this guide has tried to give every code it contains.

Key takeaways

Clear where the code points, completely: check removed sheets for torn corners, because the scrap left in the pointed-at section is the next jam code already scheduled — especially in the MP feeder, where Lexmark's own procedure warns about short lengths hidden behind the front flap.
Before blaming a fuser for a 920, do Lexmark's power-source checks: direct wall outlet (no strip, surge device or UPS), voltage matching the printer's label, a different outlet — Lexmark documents low amperage as a cause of false, intermittent fuser errors.
For any 9xx or 84x service code, write down the full number, what was printing, and whether it happens on the printer's own pages — that diary is what Lexmark's own service flow asks first.

Resetting the Lexmark printer

Lexmark's documented reset for a standing error is the power-on reset (POR) its service literature names: turn the printer off, and for the service families (900-999, 841-846) Lexmark's User's Guide procedure adds the full form — unplug the power cord from the wall outlet, check all cable connections, connect the power cord to a properly grounded outlet, and turn the printer back on; if the service message appears again, contact Customer Support and report the message. For the 920-family Service Fuser errors, Lexmark's support articles specify the lighter form first: power off, leave the printer off ten seconds or more to give it a chance to reset, power on, and if it reaches Ready and the error does not return, continue printing while watching for recurrence over the next few days. Supply messages (31/32/80/84/88) are not reset at all in Lexmark's documentation — they clear when the named action happens (the cartridge reseated or replaced, the maintenance kit serviced), and the guides' Continue touch is an acknowledgement that lets the printer proceed where the message allows it, not a counter reset. Lexmark publishes no user 'factory reset the error away' procedure for these families, and its menus' Restore Factory Defaults (an administrative settings function in the guides) is documented as restoring settings, not as an error cure — a distinction worth keeping, because a POR that clears a code temporarily is Lexmark's evidence the fault is intermittent, not evidence the fault is gone.

Facts on this page were checked against manufacturer documentation: publications.lexmark.com · publications.lexmark.com · publications.lexmark.com · publications.lexmark.com · publications.lexmark.com · publications.lexmark.com · support.lexmark.com · support.lexmark.com · support.lexmark.com · support.lexmark.com · www.manualslib.com · infoserve.lexmark.com · www.manualshelf.com