Hi many thanks for your helpful advice and having checked the current firmware version on the printer it is running Ver. 2.110 and states that it does not require updating. I'm not surprised really as this printer was purchased only recently (6 months ago) and was working perfectly in conjunction with Lightroom until the last 4 weeks. Any other thoughts would be appreciated. I just completed a google check for the part in the fault description - Fault Module Name: CNMUIBQ.DLL and see that it is a file associated with Canon. I enter and set up colour matching for paper profiles using my older printer (Canon ip4800) from Lightroom 6 with no problem at all. I can't work it out.
So, the firmware is up to date. How about the driver version in Windows I asked?
Remove the driver in Windows and reinstall it.
Hi, thanks for keeping with me.
Un-installed and re-installed the latest driver several times now-even done a registry clean between uninstalling and installing the latest driver available on the site but still crashes.
No one any ideas??
I have spoken to Canon and they say that the problem is with the registry and that it is beyond their capability to fix it which is not good as I now have a very expensive printer that I can no longer profile my printing papers. Very Sad & Upset.
Here is the event log.
xmlns="http://schemas.microsoft.com/win/2004/08/events/event">- <System><Provider Name="Application Error"
Qualifiers="0">1000</EventID><Level>2</Level><Task>100</Task><Keywords>0x80000000000000</Keywords><TimeCreated SystemTime="2016-06-23T17:28:00.000000000Z" /><EventRecordID>65697</EventRecordID><Channel>Application</Channel><Computer>Malcolm-PC</Computer><Security />
</System>- <EventData><Data>lightroom.exe</Data><Data>188.8.131.52</Data><Data>571b61a0</Data><Data>CNMUIBQ.DLL</Data><Data>0.3.0.0</Data><Data>53fe0982</Data><Data>c000041d</Data><Data>00000000000e457f</Data><Data>2fe8</Data><Data>01d1cd743d8773ac</Data><Data>C:\Program Files\Adobe\Adobe Lightroom\lightroom.exe</Data><Data>C:\Windows\system32\spool\DRIVERS\x64\3\CNMUIBQ.DLL</Data><Data>d4e740a2-3967-11e6-b772-94de80c9e865</Data>
Hi, I may perhaps help.
I've got the same problem starting yesterday when I installed a little application due to manage the internal naming of ICC profiles, i.e. intended to make the ICC profile name more user friendly in Photoshop or Lightroom: "CANSON_Baryta_310g_CanonPro1", instead of "cifa_pixmapro1_baryta310".
At the same time, i'd downloaded new versions of the CANSON's ICC profiles for my CANON Pixma Pro-1.
Seems the new Canson profiles or the rewritten ones have got some corruption which prevents the CANON Driver to correctly read the available ICC profiles in C:/Windows/system32/drivers/color.
Having done the same operations as you, i.e. driver and Canon application reinstallations without success, i've got the idea that it could be related to the ICC profiles management or corrupted ICC's.
I've then consequently created a "backup" subdirectory in the icc "color" directory, and have moved there all the Canson and CANSON rewritten icc files.
The problem have been solved.
I suggest you to do the same, i.e. move away all the uncertain icc profiles until you get the Canon Printer properties /driver to work, and then replace one by one all the icc files so as to determine which of your ICC's is corrupted.
1 person found this helpful
You absolutely nailed it and thank you so much you are a star. Very astute of you to notice that I was using this profile renaming software and unloading all the canson ICC profiles got the printer colour profiling back working for me.
I had spent 3 - 4 days talking to Canon who to be fair tried hard to understand the problem but in the end gave up and referred me to either Microsoft (Who can be a bit like roll Royce in denying anything can be wrong with their products so don't need a direct support line) or to live with it which considering the investment in their product was disappointing in the least.
Nice finding ...
I'd also logged a Canon Ticket, before imaginating such a cause for my problem, but by email and it hadn't yet been taken into account.
* called back,
* closed the case,
* asked them to notice the root cause and the solution,
* and also asked to log a lab ticket so has to have the lab engineer include some prevention mechanism into the driver/software: a single corrupted ICC file among many others in the Windows Color directory shouldn't crash a driver especially without any error code.
This Canon driver is quite bit of scrap anyway: having to walk such a long way simply to be sure that your choice for icc/software management of the colors instead of driver management is well checked is not the best implementation i've ever seen. :-(