5100cn - verticle line omitted on magenta test page
Hello, I hope someone will be able to help me out, I've spoke to Dell tech help several times with no success. There is 1 verticle line that is being omitted from the magenta test print. Always in the exact same spot, right side about 1" from edge of paper. I have checked all of the rollers, drum, etc. The only thing I can find is on the fuser/separator roller, there is some damage or scratching on the right side of the red roller.
So far, I have tried (on Dells direction) replacing the magenta toner and the Transfer Roller. Both of these did not solve the problem at all.
Re: 5100cn - verticle line omitted on magenta test page
Sound like the drum could be the problem have you replaced that? if the fuser was the problem it would have the toner but would not have been fused or had marks on the page. this would be my best on this issue
- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
Yes...carefully pull the majenta cartridge out and inspect it. Does it look like its leaked? Pull the shutter back and see if there is excess toner on the drum. My experience based on what you've said here is the cartridge may be going bad or experiencing "blowback". Blowback is when the waste side of the cartridge gets to full and it starts coming back out over the cartridge drum. If you have you're old cartridge still handy put that one back in and run a few pages and see if it clears up. Hope this helps!
Could have a corrupt driver. Disconnect
the printer or at least be sure it is turned off. I'd do
both and when the CD software program asks you to connect the printer
to the USB port, do so and it should again work properly.
Hope this helps. Bud
This should fix your issue. I won't say it is a common failure, as the machine overall is very reliable, however for this problem the magenta developer is the most common failure for the 5100 and 5110.
Check your email shortly for the document and additional comments.
download Gassan-Mac-9-MR2RC2.sit from dell site (printer site, drivers, mac os) and unpack it with stuffit expander. it contains drivers for mac os 9 and mac os x. then just install it and select driver from the list when adding modifying printer
There is no real solution to this problem that I've been able to find. And I myself have not been able to find anyone that has the service manual for this color printer.
Here is what happened with my printer. I normally use this one company for compatible toner cartridges for our office printers. I've never had any issues with their HP, Brother, Canon Phaser or Dell laser products - EVER. When I went to re-order my Dell 5100cn toners again from them - ordered 2 black and 1 each cyan, magenta and color - none of the toners worked right. When they were installed, the machine produced that 009-363 restart printer message.
Now this company has ALWAYS taken care of me. We thought maybe the chips in the toners were outdated or something compared the the recent firmware update my printer had recently had. So they shipped out a complete new order for me. But the second set of toners did the same thing. So they sent one of their Dell Certified technicians to the office - we are on a cleaning plan with them so he just looked at the Dell printer while he was there doing the other work. He could not find anything physically wrong with the first or second set of toners, but yet they would not work in my printer. He even tried going through the menu options to select "allow non-Dell toners" too - thinking that maybe the printer just wasn't liking the Dell compatibles. I never had to do this before with their Dell compatibles, but it was worth a try. But even when selecting that, the printer still produced the 009-363 restart printer message. He took the toners back with him, and left me with a set of Genuine Dell toners - just to get me through what was happening so I wasn't down a printer.
The company called me and said when the technician returned with the compatible Dell toners they'd shipped me, they installed them in their test Dell 5100cn printer and they worked fine! So it was appearing that the problem might have been my machine or something.
I searched online everywhere, and the supply company I used also spoke with Dell tech support on my behalf - but got no where with Dell as usual - their Tech Support is totally useless!
About a month goes by, and my supply company says that they received a new shipment of Dell chips that have a newer firmware than even what my printer has, and that they'd like to send their technician out again to test them out in our machine. The tech came by, installed all of the toners - and they worked!
So it definitely was something to do with the firmware that was on my printer versus the firmware that was on the chips in their toners. My printer for some reason did not like that "lot" of toners they had made using those chips. And when they produced their next lot with the new firmware chips, the printer accepted everything ok.
Since then I've used their Dell compatibles with no issues. I think it was just a fluky thing as it hasn't happened since. Overall I think you just need to find a company like mine that continuously produces new toner cartridges using new Dell chips in their toners. Once in a while you might get a fluky one like we did, but my company definitely took care of us. Just try to find a company that has a good cartridge - you don't have to keep buying the expensive Dell brand - especially when they don't even know what the problem is caused by either.
We have over 50 of these printers and a few have had the magenta bleeding problem. On everyone of them the problem was corrected by going to the clean developer function under Maintenence from the Menu and choosing to clean the magenta color. Usually have to run it a couple times but it has always corrected the problem so far.