Initialization error/Access violation...

[brassmonkey001]

I am having no end of trouble with Mediamonkey lately. I keep getting "Error during initialization error" and then "Access violation at address xxxxxxxx in module 'iglicd32.dll'. Read of address 000000xx." The x's vary depending on which file I try and access.
I have tried uninstalling and reinstalling several times but it just isn't working for me.
Any ideas?

[Lowlander]

Are you using MediaMonkey 4.0.7? If not start with upgrading to it.

[brassmonkey001]

Yep, latest version.

[Lowlander]

In that case it is best to send a debug log (step 4b) capturing this error and send it to support so the developers can look to see why you see this: http://www.mediamonkey.com/forum/viewtopic.php?f=1&t=69

[rovingcowboy]

I read this but thought you had it fixed, my guess is that mm is trying to open a song that is stuck in the registry hotkeys as being in player because of a crash and the registry is not cleaned out thus causing monkey to keep trying to read a crashed and not loaded file.

I would run auslogic's free registry cleaner and see if it fixes the error,.

[brassmonkey001]

Thanks rovingcowboy, I tried your suggestion but with no success.
If I wipe all traces of MM from my computer then reinstall it seems to work fine until I try and attach an image file to the songs then it goes wrong and has to be totally wiped again. It's not enough to simply uninstall it, I have to make sure any traces of MM are deleted too. I also empty the recycle bin as well to be sure. Then, if I try and add an image I'm back to getting endless error messages and have to shut it down with the task manager and wipe it again.
ANy more suggestions?

Merry Xmas.

[rovingcowboy]

Sounds like its still a messed up hotkey? Maybe it was saved in system restore and keeps getting put back in? But still the registry cleaning should fix it until the next reboot? Maybe you could get the debug viewer program from link in the how to do bug report post, run that third party program start mm do all steps you do when it crashes then save the debug report, close debug viewer and close any of mm left running after crash and send report file in email to support email link found in the support section at top of page on this website.

Also maybe the file format doesnt support embeding images to tags,?

[Peke]

Well According to http://www.processlibrary.com/directory ... 32/402145/ problem lies in GPU Driver Have you recently tried http://www.intel.com/p/en_US/support/detect/graphics and/or http://downloadcenter.intel.com/ ?

[kdeemer]

Same thing happens to me; every time I try to add an image to an album (mp3 tags), I get an Access Violation in MediaMonkey.exe and the error window refers to the last track that was played.

MM 4.0.7.1511
Win 7

[Lowlander]

I believe this was an old bug and I haven't seen it reported on recent versions. So it may be best that you capture this in a debug log (step 4b) and send it to support: http://www.mediamonkey.com/forum/viewtopic.php?f=1&t=69

[kdeemer]

I have the same issue; Every time that I play a track and terminate it with ctl-o, the track seems to get stuck in the registry and gives me an Access Violation error when I try to edit any properties.

MM 4.0.7
Win 7

[brassmonkey001]

Well According to http://www.processlibrary.com/directory ... 32/402145/ problem lies in GPU Driver Have you recently tried http://www.intel.com/p/en_US/support/detect/graphics and/or http://downloadcenter.intel.com/ ?

I can't get that to run either!

[katleen_farine]

I still have this same error me too...

[martinstephenbanks]

Has anyone got a solution to this yet? Mine is so bad now that I can't even use Mediamonkey. The box pops up the second I do anything. So if I try to open Properties so I can edit track names and burn in a CD I can never get to the box behind this silly popup error

I REALLY would hate to move on from Mediamonkey but I am not sure what to do when I can't even use it.

[Lowlander]

I'd suggest trying 4.1.1.1702: http://www.mediamonkey.com/forum/viewto ... 02#p386802

If you still see it capture it in a debug log (step 4b) and send the log to support: http://www.mediamonkey.com/forum/viewtopic.php?p=341