Lexmark “900.43 Service RIP” — firmware crash on print

Joe B.

Reviewed for technical accuracy

Specialities: Windows/Mac print drivers, Lexmark firmware, PostScript/PCL, Print servers

Fix Lexmark 900.43 / 900 Service RIP — firmware crash, bad print job, corrupt font, RIP/formatter reset

Technician

Hey! We’ll tackle the Lexmark “900.43 Service RIP” message. That code means the printer’s RIP/formatter crashed while processing a job (often PostScript/PDF).
Quick triage questions: does it crash only on certain documents or from one PC/app? USB or network (RAW 9100/IPP)? Any recent firmware update, driver change, extra memory/HDD, or option like a finisher?

Customer

It’s a network printer. The error pops up as soon as we print a PDF from Chrome or Acrobat. After power cycling, it comes back when the same user prints again.

Technician

Got it. The 900.43 variant is a firmware crash on print. Root causes are usually: a corrupt print job (PDF/PostScript), a bad font or plug-in, outdated engine firmware, or a flaky network print path (IPP filter, RAW 9100). Less common: failing DIMM/HDD or a USB device.
We’ll: 1) purge the queue and block the offending job; 2) switch to a stable PCL/Universal v4 driver to test; 3) update Lexmark firmware via EWS/USB; 4) clear NVRAM/RIP cache; 5) reseat memory/options if needed.

Customer

Where do I purge the stuck job and stop it from auto-resending? We use a Windows print server.

Technician

Step 1 — Clear the corrupt job
• On the print server, open Print Management → Printers > your Lexmark queue > Pause Printing, then Cancel All Documents.
• On the printer, hold Cancel/Stop to delete the active job; then power it off for 30 seconds to flush the RIP.
• Unpause and test from another PC/app with a small test page. If the error is gone, the original job was the trigger.
Tip: disable “Keep printed documents” and any pull/secure-print system temporarily so it doesn’t re-inject the bad file.

Customer

After clearing, a test page prints fine. It crashes again only with that complex PDF. Should we change drivers?

Technician

Step 2 — Test with another driver/protocol
• If you’re using PostScript, install the Lexmark Universal PCL XL or Microsoft IPP Class driver and print the same file.
• In driver Advanced, try Print as image (for PDFs), disable Advanced Printing Features, and set Spool print documents → Start printing after last page is spooled.
• If printing via IPP, test direct RAW 9100 to bypass filters, or vice versa. This isolates a RIP/PostScript issue from a transport issue.

Customer

On PCL the file works. We still want PS for graphics quality. Should we update the printer firmware?

Technician

Step 3 — Update Lexmark firmware
• Open the printer’s Embedded Web Server (EWS) → Firmware or Device → Update. Upload the latest .fls file from Lexmark for your exact model.
• No network? Put the firmware on a USB stick and update from the control panel.
• After update, power-cycle and re-test the same PDF using the PostScript driver.
Note: Firmware specifically addresses 900 Service RIP defects, corrupt font handling, and RIP stability.

Customer

If it still throws 900.43, what next? Could memory or options cause it?

Technician

Step 4 — Clear RIP cache & NVRAM; reseat options
• From the control panel: Settings → Device → Maintenance → run Clear Print Data/Jobs, then Restore Factory Defaults (keeps network if you choose partial reset).
• Power off. Reseat/temporarily remove: memory DIMMs, optional hard disk/SSD, and finishing options. Boot and test bare-bones.
• If the crash stops, add components back one by one to find the faulty part (bad DIMM is a classic 900 Service RIP trigger).

Customer

We also use secure/pull printing. Could that re-queue the bad job and crash the firmware again?

Technician

Yes. In pull-print systems, the original corrupt PostScript/PDF can be re-released to the device and re-trigger the 900.43 firmware crash.
• Purge jobs on the server, clear user caches, and delete any Hold Print/Bookmarks stored on the Lexmark.
• If your DMS creates PDFs, export with PDF/A or rasterize (Print as Image) until firmware is updated.

Customer

After firmware and driver changes, PS prints fine. Any best practices to prevent 900 Service RIP in the future?

Technician

Final checks & prevention:
• Keep Lexmark firmware current; schedule updates during maintenance windows.
• Standardize on one Universal driver per model (PCL for stability; PS for graphics) and lock queue options.
• Prefer RAW 9100 or a single protocol; avoid multiple print paths to the same device.
• Limit custom fonts/macros; if needed, download as soft font instead of relying on device fonts.
• Document a quick rollback: switch driver to PCL, clear queues, power-cycle — this prevents downtime if 900.43 reappears.

Customer

Perfect — the 900.43 Service RIP error is gone and our PDFs print. Thanks!

Technician

Summary: For Lexmark “900.43 Service RIP — firmware crash on print”, clear the corrupt job, test with a stable PCL/Universal driver, update the printer’s firmware, reset the RIP/NVRAM, and reseat memory/options. Need hands-on help performing the update or rollback? Open the chat.

Quick answer: the accepted fix

Accepted fix for Lexmark 900.43 Service RIP: purge the queue and block the offending PDF/PostScript job, switch drivers (test with PCL), update to the latest Lexmark firmware via EWS/USB, then clear NVRAM/RIP cache and reseat memory/HDD. Return to PostScript after the update if needed.

FAQ

Step-by-step (Windows print server)

1. Pause queue → Cancel All Documents; power-cycle the printer.
2. Install Lexmark Universal PCL XL (or Microsoft IPP Class) and test.
3. Update firmware via EWS/USB; reboot and re-test with PS.
4. Run Restore Defaults, clear RIP/NVRAM; reseat memory/options.

Note for macOS environments

1. Switch the queue to Generic PCL/IPP or enable Print as Image in Acrobat.
2. Update Lexmark firmware and reinstall the PS PPD only after stability is confirmed.

Sources

• Microsoft — Troubleshoot printer problems
• Lexmark — Firmware & Drivers (by model)
• Adobe — PostScript & PDF print guidance

Matt ● replies in < 1 min

Technician Expert

⭐⭐⭐⭐⭐ Trusted by 27,000+ customers

Alex · Expert's Assistant

Start Chat

5 Tech Support Specialists are online right now.