While it might feel like your printer has reached its end of life as it hangs indefinitely or prints half-finished pages, don’t worry—this is almost always a configuration or resource management issue rather than a terminal hardware failure. With a few methodical adjustments to how the data is sent and processed, you can get your Lexmark back to peak performance.
| Metric | Details |
|---|---|
| Difficulty | Moderate (Software & Hardware components) |
| Estimated Time | 20 to 45 Minutes |
| Tools Needed | Phillips #2 Screwdriver (for RAM access), Computer with Network Access, USB Cable (optional) |
| Estimated Cost | $0 (Settings adjustment) to $50 (RAM Upgrade) |
Symptoms of Error 37.xx
When your Lexmark printer encounters an Insufficient Memory state, it will manifest through several distinct physical and digital behaviors:
🛑 Safety Precaution: High Voltage
Working with electricity is dangerous. We strongly recommend downloading the official guide.
- Control Panel Alert: The most obvious sign is the LCD display flashing “37 Insufficient Memory” or “37.01 / 37.02 Error.” On older models without screens, the “Error” and “Ready” lights may blink in a specific sequence.
- Partial Prints (The “Split” Job): The printer may begin the job normally but stop halfway down a page, ejecting a sheet that is blank from the middle down, followed by a second sheet containing the error code.
- Extreme Processing Latency: The “Processing” light may blink for several minutes without the mechanical components of the printer (rollers, fuser) ever engaging, as the logic board struggles to “render” the page.
- Spooler Freezing: On your computer, the print queue might show the status as “Sent to Printer” or “Printing,” but the file size will seem to grow indefinitely until the printer eventually times out and resets itself.
What Triggers this Code?
Understanding why your printer is running out of memory is crucial for applying the correct long-term fix. This error is rarely “random”; it is usually a direct result of one of the following factors:
1. Document Complexity and PostScript Overhead: Modern PDFs and high-end graphic design files use “layers.” When you send these to a printer, the printer must “flatten” those layers into a bitmap that the laser can understand. If the file has hundreds of vector paths or complex transparencies, the RAM is filled with calculations before the first drop of toner even hits the paper.
2. Resource Leakage and Firmware Inefficiency: Just like a computer, a printer runs an operating system (Firmware). Over time, small bugs in the code can cause “memory leaks,” where the printer fails to clear out old print data from its cache. This reduces the “net” available memory for new jobs until the system is fully purged or updated.
3. Driver Misconfiguration: Often, the computer sends the data in a format the printer isn’t optimized for. For instance, using a PostScript (PS) driver for a document that could be handled by a simpler PCL6 driver forces the printer to use much more memory for font rendering and page description.
4. Hardware Limitations (Physical RAM): Many base-model Lexmark printers ship with the bare minimum RAM required for text documents. If your office has transitioned to printing high-resolution marketing materials or scanned “Image-only” PDFs, the factory-installed memory may simply be physically insufficient to hold the “image map” of the page.
Troubleshooting & Replacement Instructions
Follow these steps in order, moving from the simplest software solutions to hardware interventions.
Step 1: The Deep Power Cycle and Buffer Clear
Before assuming a hardware failure, you must clear the “stuck” job from the printer’s volatile memory. Warning: Ensure you cancel the job in the Windows/Mac print queue first, or the error will return immediately upon restart. Turn the printer off. Unplug the power cord from the wall and the back of the machine. Wait at least 60 seconds to allow the capacitors on the controller board to fully discharge. Plug it back in and wait for the “Ready” state. This flattens the memory stack and provides a clean slate.
Step 2: Adjusting Print Resolution and Collation
Open the “Printer Preferences” on your computer. Look for the “Quality” or “Advanced” tab. If the resolution is set to 1200 dpi, drop it to 600 dpi. For most text and standard graphics, the human eye cannot tell the difference, but it reduces the memory footprint by nearly 75%. Additionally, turn off “Printer-side Collation.” When this is on, the printer has to store every page of a multi-page document in its RAM before printing. By turning it off, the computer handles the collation, and the printer only has to remember one page at a time.
Step 3: Updating the Firmware via Embedded Web Server (EWS)
Lexmark frequently releases firmware updates to improve memory management. Find your printer’s IP address (usually found under “Network Reports” in the menu). Type that IP into your web browser. Navigate to Settings > Device > Update Firmware. Upload the latest .fls file from Lexmark’s support site. This can resolve “37.xx” errors caused by software bugs that fail to release memory after a job completes.
Step 4: Switching Drivers (PCL6 vs. PostScript)
If you are currently using a PostScript driver (often labeled “PS”), try installing the Lexmark Universal Print Driver (UPD) using PCL6. PCL6 is much more efficient with memory for standard office documents. PostScript is great for color accuracy but is a “heavy” language that often triggers Error 37 on complex files.
Step 5: Physical RAM Upgrade (Hardware Fix)
If the error persists on large files, you likely need a physical memory upgrade. Safety Warning: Turn off the printer and unplug it to avoid electrical shock. Using a Phillips #2 screwdriver, remove the side access panel (usually on the right side of the machine). Locate the SODIMM slot on the controller board. Touch a metal part of the frame to ground yourself and prevent ESD (Electrostatic Discharge) damage. Insert the Lexmark-compatible memory module into the slot at a 45-degree angle, then press down until it clicks. Reinstall the panel and restart the printer. The printer should automatically recognize the new capacity on the start-up “Self-Test” page.
How to Prevent Error 37.xx
Once you have cleared the error, use these maintenance strategies to ensure it does not return during a critical print run:
- Flatten Complex PDFs: When printing from Adobe Acrobat, use the “Print as Image” feature (found under the Advanced button in the Print dialog). This converts the document into a simple bitmap on your PC, offloading the “thinking” from the printer’s limited RAM to your powerful computer processor.
- Regular Buffer Flushes: Make it a habit to restart your printer at the end of every week. This prevents “residual data” from building up in the cache, which can slowly chip away at your available memory over several days of heavy use.
- Disable Unused Protocols: Access the printer’s web interface and disable protocols you don’t use, such as AppleTalk, FTP, or Telnet. Each active protocol “reserves” a small portion of RAM; disabling them frees up more “working space” for actual print jobs.
FAQ
Frequently Asked Questions
Q: Why does this error only happen with certain PDF files?
A: PDFs are often containers for high-resolution images and “invisible” vector data. A 2MB PDF can expand into 100MB of raw data once the printer’s processor attempts to render it for the laser. Using the “Print as Image” setting is the best workaround for these specific files.
Q: Can I use any standard laptop RAM to upgrade my Lexmark?
A: Generally, no. While Lexmark RAM looks like standard laptop SODIMMs, printers are very sensitive to timings and voltage. It is highly recommended to use Lexmark-certified memory or 100% compatible third-party modules designed specifically for your model number to avoid “Invalid Memory” errors.
Q: Does a “37.xx” error mean my printer is broken?
A: Not at all. Think of it like a computer “Out of Memory” warning. It is a resource limitation, not a mechanical failure. In 90% of cases, optimizing your print settings or updating the firmware will solve the problem without needing to spend money on hardware.