02-03-2015 02:54 PM
Xerox 7428 is unstable. Seems to freeze-shutdown without warning. Blue buttons and energy saver lights all flash and the device does not respond to on-off switch. Must be disconnected from mains and reconnected to start.
Anyone know cause or solution ?
Solved! Go to Solution.
02-04-2015 11:08 AM
Thanks V Andreev
When this total failure occurs, powering off the machine and powering it back on restore it to full health without need to clear print queues etc. - BUT- it has to be switched off at the wall not the device.
The failure stops the machine responding at all (except with the flashing lights), it won't even power down when the on-off switch is operated.
From a layman's perspective this looks more like a hardware issue than a rogue print.
Do you have any other ideas on the strength of the above?
The Spool Disk Initialisation has been tried, but I don't think this has any more effect on our issue than a total system power down.
The failure seems to occur on approx a weekly basis. There have been no changes in client or server drivers since the machine was stable.
02-04-2015 11:24 AM
I know very well this problem and it's mostly provoked by a corrupted print job (means that the machine doesn't understand what she have to print). However, please check the last fault codes in the machine memory.
02-05-2015 04:22 AM
Thanks again V Andreev
I have checked the fault code history, and there are 3 errors around the time of the machine hang.
Two of these are paper jams according to this list
but the third 024-370 isn't shown.
I have searched for other code lists without success - do you know the meaning of this error message?
02-05-2015 06:05 AM
Many thanks for your continued support with this issue.
I have spoken to our Xerox distributor and they guided me to a support page on the Xerox site.
This gives the following information relating to the 024-370 error code
Basically this seems to suggest that the problem is with the format of a specific print job and goes on to detail how to set the image quality for that print.
Can you tell me why you think this is RAM related?
It certainly does appear more like a hardware issue to a layman like me, given the complete lockup of the device.