Xerox “117-325” — NVM read/write error (contract manager / NVRAM)
Joe B.
Expert ★★★★★ 27,853 satisfied customers
Specialities: Xerox fault codes, NVM read/write errors, ESS / controller boards, firmware & AltBoot, embedded print controllers
Xerox 117-325 NVM read/write error — contract manager RTC / NVRAM access, safe NVM reset & board checks
Technician
A couple of details so I don’t guess:
• Which Xerox model is this (VersaLink, AltaLink, Color 560/570, C70, etc.)?
• Does the device boot to the home screen and then show fault code 117-325, or is it stuck on a white/boot splash with the error?
• Has anything changed recently — firmware upgrade, power outage, NVM/ESS board replacement, HDD/SSD swap, adding a controller kit?
This code is usually tied to NVM (non-volatile memory) access — if the controller can’t read or write NVM properly, you’ll see 117-325 and the machine will stop.
Technician
On many Xerox platforms, 117-325 is a “NVM read/write error” or “Contract Manager RTC / NVRAM fail”. In plain English: the controller (ESS / system board) is trying to talk to its NVRAM chip and can’t reliably read or write the data. Causes I see most often:
• Interrupted firmware load or AltBoot damaged the NVM tables.
• Sudden power loss during a write left corrupt NVM entries (bad checksums, invalid values).
• Failing NVM device / RTC hardware on the ESS or image processor board.
• Mismatched NVM after swapping boards or HDD/SSD without doing the proper NVM backup/restore.
Good news: sometimes a controlled NVM reset or clean firmware reload clears the 117-325 fault. The risky part is that random NVM writes can disable options or calibration, so we’ll focus on safe paths you can actually do and flag the points where a Xerox service tech may be needed.
Technician
Step 1 — Cold reboot and power quality
1) Power the Xerox off with the hard switch (if present), then unplug it from the wall for at least 60–90 seconds.
2) While it’s unplugged, disconnect any USB drives, card readers, external print servers and leave just power and network.
3) Plug it back in directly to the wall (no flaky surge strip/UPS), then power on and watch carefully when the fault code 117-325 appears — at splash, at “Please wait”, or after attempting to go Ready.
If the error still comes back exactly the same, we’ll look at:
• Whether the device is running current firmware for your model (some releases fix NVM access faults).
• If the 117-325 started immediately after a failed update or AltBoot stick, which points to corrupt NVM or system image rather than pure hardware failure.
Technician
General rules I give for Xerox NVM read/write faults:
• Use the exact firmware build recommended for your model/serial (wrong family images can break NVM layout).
• Prefer a normal firmware update via the web UI or remote services if the machine will still boot to Ready. When it won’t boot, techs usually use a controlled AltBoot with Data Backup — but that’s a service-level procedure.
• Avoid “clean” AltBoot or anything that wipes user data/NVM until you have a good reason and a backup plan; these can reset licenses, meters, color calibration and network settings.
Because you’re already stuck at 117-325 during boot, the safest DIY actions are: verify power, reseat easy connections, then try a basic NVM reset from diagnostics if the device will let you into service mode. For deeper AltBoot, it’s usually best to have a Xerox tech or talk it through live, so you don’t lose key features.
Technician
Safer approach I usually walk owners through:
• First, in diagnostics, look for any menu that shows an overall NVM status, checksum, or RTC status without changing values. Sometimes you’ll see that a particular NVM block is flagged as corrupt.
• If your model has a documented “software reset” or “factory defaults” option that does not erase metering/licenses (often under maintenance), that can clear minor NVRAM glitches without going into raw NVM addresses.
• Only if you have the correct service documentation and know the exact NVM location for a soft reset of the controller would you touch NVM read/write — and even then, take photos of current values before changing anything so a tech can reverse it if needed.
For a 117-325 that repeats after a gentle software reset, the next step is usually to decide between:
• A supervised AltBoot with data backup, or
• Testing/replacing the ESS or NVM module if the controller simply can’t write to NVRAM anymore.
Technician
Step 2 — Visual and connection checks (power safe, low-risk)
• Power the device off, unplug it, and wait a full minute before touching anything inside.
• Gently reseat the ESS/controller board connectors, especially harnesses that go to the NVM/RTC module or storage devices (HDD/SSD, compact flash depending on model). Look for partially seated plugs or corrosion.
• Check that any add-on boards (Fiery, PostScript, fax kits) are fully seated; if they were added just before the 117-325 error, temporarily remove them and see if the fault changes.
• Inspect for obvious damage: burned components near the NVRAM, leaking batteries on the RTC/NVM section, or bent pins.
These checks won’t fix a truly failed NVRAM chip, but they can cure a loose connection that causes intermittent NVM read/write errors and 117-325 faults after vibration or shipping.
Technician
• Soft NVM corruption (often after a bad update or power hit): a tech can usually clear it with the correct combination of diagnostics, NVM resets and AltBoot with data backup. Your settings may need to be re-entered, but no boards get replaced.
• Hard NVRAM/RTC failure on the ESS: even a clean firmware and NVM reset won’t stick, the fault code comes back, and at that point board replacement is normally the cure.
• Mixed cases: sometimes a tech backs up the configuration, does a “clean” system reload, re-initialises certain NVM tables, and then restores configuration to bring the machine back without hardware.
The key is not to wipe NVM blindly. If we work through it together, we can usually tell from the behavior whether you’re in the “software fix” camp or whether it’s time to price an ESS or NVM module before you put more hours into it.
Technician
• 117-325 — commonly tied to contract manager / RTC hardware problem or NVM read/write fail on some Xerox controllers.
• 117-326 — often points to software processing faults in the NVRAM area (how the system tries to access NVRAM).
• Other “NVM write failed” or “failed to write NVM” codes typically indicate the controller tried to commit settings and couldn’t.
The troubleshooting patterns are similar: confirm power, firmware and environment, then decide between soft NVM repair and hardware replacement. If you share your exact model and build, I can help interpret any companion codes and suggest the least risky next step.
Technician
If you’d like help deciding whether your 117-325 can be cleared in software or needs parts, open the chat and I’ll walk through your exact model and options.
Quick answer: the accepted fix
Accepted approach when a Xerox printer shows fault code 117-325 or an NVM read/write error: power the device off completely, remove external accessories, and verify stable mains power. If possible, apply the correct firmware for your model and perform a non-destructive software reset. When the machine still stops with 117-325, have a technician check NVM status in diagnostics, reseat the ESS/NVM connections, and decide between a supervised NVM reset or AltBoot with data backup versus replacing the controller/NVRAM hardware.
Why Xerox shows 117-325 NVM read/write error
The 117-325 fault code on Xerox devices typically indicates that the controller cannot reliably access the NVM (non-volatile memory) area where configuration, meters and timing data are stored. During boot, the ESS expects to read NVRAM tables and the RTC (real-time clock); if those reads fail or checksums are wrong, the system triggers an NVM read/write access error and halts to avoid running on corrupt data. Power cuts, incomplete firmware updates, damaged NVRAM chips and mismatched configuration after a board or HDD swap are common triggers for these NVM access faults.
How to confirm if the 117-325 error is software or hardware
To separate a software NVM corruption from a hardware NVRAM failure, watch how the device behaves after each step. If a firmware update and gentle factory/software reset change the symptoms, allow you into diagnostics for longer, or temporarily clear 117-325, that points to an NVM data problem that may be recoverable with controlled resets and a clean system image. If the Xerox reboots straight back to 117-325 NVM read/write error no matter what you do, or logs “failed to write NVM” faults whenever it tries to save settings, the underlying NVRAM/RTC section on the ESS is likely failing and a controller or NVM module replacement becomes the practical fix.
Xerox 117-325 — quick troubleshooting tips
Most 117-325 NVM read/write errors come from corrupt NVRAM tables, failed updates or aging controller hardware.
Quick path: confirm stable AC power, remove extra accessories, and do a full power cycle. If you can still reach the UI, apply the recommended firmware level for your Xerox model and use any documented software/factory reset that does not wipe licenses. Avoid random NVM read/write changes; instead, have a technician check NVM status and fault history, reseat ESS and storage connections, and only then decide on a supervised NVM reset, AltBoot with data backup, or ESS/NVRAM replacement. This approach preserves configuration while giving you the best shot at clearing the 117-325 NVM error safely.
Disclaimer: This information is AI-generated and intended for general guidance only. For advice specific to your environment, please consult a verified expert on Whizz-Tech before making decisions.
Getting Started Is Easy
Ask for help, 24/7
Members enjoy round-the-clock access to 12,000+ verified Experts, including tech support, mechanics, vets, and more.
Expert will respond in minutes
We match you with an Expert who specializes in your situation. Talk, text, or chat — whichever you prefer.
Save time & money
No scheduling hassles or expensive consults. Membership can save you significant time and money each month.
FAQ
What does Xerox fault code 117-325 NVM read/write error mean?
On many Xerox devices, fault code 117-325 indicates a problem accessing non-volatile memory (NVM) — the controller cannot reliably read or write the NVRAM or contract manager/RTC data it needs during startup. The machine halts with an NVM read/write error to prevent running on corrupt configuration, and will stay offline until the underlying NVM or controller issue is resolved.
Can I clear a 117-325 NVM error myself without replacing boards?
Sometimes. If the root cause is soft NVM corruption after a power cut or failed update, a controlled combination of firmware update, software reset and supervised NVM repair can clear 117-325 without hardware replacement. Avoid random NVM read/write changes; instead, start with power checks, safe resets and a proper firmware level, then let a technician decide if deeper NVM work is appropriate.
When does a Xerox 117-325 fault require ESS or NVM replacement?
If the printer instantly returns to 117-325 NVM read/write error after firmware and soft resets, or repeatedly logs “failed to write NVM” faults whenever it tries to save settings, the NVRAM or RTC hardware on the ESS/controller board is likely failing. In those cases, replacing the ESS or NVM module is usually the reliable long-term fix, followed by configuration and calibration to restore normal operation.
What is the difference between 117-325 and 117-326 on Xerox?
Both are NVM access faults. In many Xerox fault code lists, 117-325 relates to a hardware problem with the RTC / contract manager, while 117-326 points more to software processing issues in the NVRAM area. The troubleshooting steps overlap: verify firmware and power, then decide between repairable NVM corruption and a failing controller that may need replacement.
Sources
- Screwloose IT — Xerox fault codes including 117-325 Contract Manager / NVM
- XWK Tech — How to fix 117-325 / 117-326 NVM access errors
- Xerox Support — Failed to write NVM fault overview
Filed under: Printers
Related articles
- Printer says “Offline” and won’t print — what should I check first?
- My printer “forgot” my Wi-Fi — the saved network is gone
- Printer Wi-Fi settings reset by itself — why did it forget my network?
- My printer keeps popping up “Set up Wi-Fi” again — why won’t it stay connected?
- Why does my printer need Wi-Fi setup again? It was working yesterday.
- My printer Wi-Fi setup keeps failing — what am I doing wrong?
- Printer Wi-Fi setup is confusing — why won’t it connect to my network?
- Printer Wi-Fi setup is too complicated — what do I check first without messing it up?