eS356 that's lost it's little mind. I'm am too.

[blackcat4866]

All the jams are E010, but that was easily resolved. The screw had backed out of the sector gear on the back of tray #1. No other jam or error codes.

Here is the strange part:
I can copy and print out of tray #1 (LT) all day long, all functions. When I copy or print from tray #2 (LTR-R) about 14 pages into the job the engine shuts down ... but the display blithely continues to read "Ready (printing)". I tell the machine: "Dumbass! You are not printing!", but it doesn't seem to help. I can review the Job Status pages, and yes, it still thinks it's copying. I only waited 15 minutes, but I get the impression that it would continue forever.

Observations:
Several of the 6S-2/08-xxxx maintenance values are corrupted. The value it seems to like is 99999999. When I backed up SRAM from the EEPROM (08-4582) the values remained corrupt, so I've concluded that both the EEPROM and SRAM are corrupted. I did have some success with Printer All Clear (08-9090). Now both EEPROM and SRAM are zero'ed out. Next I formatted the HDD (white drive) and reloaded the System and HDD files. No change whatsoever in the symptoms.

Tentative conclusions ( ... very tentative):
Since the HDD acted completely normal during the re-format and firmware loading, and because it seems to work normally with tray #1, I think that perhaps the HDD is OK. I suspect either the SRAM and/or the System board. On another occasion I had some bizarre 6S-2/08-xxxx maintenance values on an eS2500C, and it turned out to be a combination of the NVRAM and the logic board. The other symptoms were different, and also completely bizarre.

Does any of this sound familiar? =^..^=

[blackcat4866]

... I suspect either the SRAM and/or the System board. ... =^..^=

The SRAM resolved this one. It's three pages in the manual to re-load the data to the SRAM, but everything ran like it should. 130 minutes of nervous anticipation.

The only thing that I may choose to do differently is when asked to select HDD encryption setting, I probably will select #2 for Performance Priority, rather than #1 Security Priority. I think that the screen response is noticeably slower on #2. =^..^=