cancel
Showing results for 
Search instead for 
Did you mean: 
john-doerty Member
Member

WorkCentre 4265 / MCB Assert error

Jump to solution

Hi everybody!

 

I've got a serious problem with a Xerox WorkCentre 4265.

When I want to print a file, the MFP prints 2 pages, then crashes, restarts, and displays the following error message :

 

roy 404.jpg

 

And do it again and again...

 

Does someone have an idea where it could come from??

 

Thank you in advance ;)

 

John

 

 

0 Kudos
7 Replies
john-doerty Member
Member

Re: WorkCentre 4265 / MCB Assert error

Jump to solution

I got an answer from Xerox Support Level 2. It is a hardware problem (Hard Disk)... So we need a technicial intervention.

 

Thank you anyway ;)

 

John

Community Manager CherylO-Xerox
Community Manager

Re: WorkCentre 4265 / MCB Assert error

Jump to solution

Hi John,

Thanks for coming back and letting us know.  I am sure this will help someone else in the future.

 

Thanks,
CherylO-Xerox
Community Manager

Be sure to click Kudos for those who have helped you.
Select Accept as Solution for posts that have helped to solve your issue(s)!

0 Kudos
john-doerty Member
Member

Re: WorkCentre 4265 / MCB Assert error

Jump to solution

Hi,

 

Actually it was a driver problem!

 

John

restarcik New Member
New Member

Re: WorkCentre 4265 / MCB Assert error

Jump to solution
 
 
I had the same problem
0 Kudos
dr.abdallahzaky New Member
New Member

Re: WorkCentre 4265 / MCB Assert error

Jump to solution

i had the same problem

0 Kudos
donbelt New Member
New Member

Re: WorkCentre 4265 / MCB Assert error

Jump to solution

What was the driver issue if I may ask?  I have had a similar problem.

0 Kudos
john-doerty Member
Member

Re: WorkCentre 4265 / MCB Assert error

Jump to solution

Hi donbelt!

 

It was a conflict between an older version of drivers and a newer one.

So I deleted ALL the Xerox drivers + package in the printmanagement.msc.

Then (just to be sure), I deleted all the Xerox packages in the PNPUtil in CMD.

\\\ CMD / pnputil -e / pnputil -d oemXX.inf

I reinstalled the proper driver, and everything worked just fine! ;)

 

John