media monkey: access violation at address 00E7537

Post a reply

Smilies
:D :) :( :o :-? 8) :lol: :x :P :oops: :cry: :evil: :roll: :wink:

BBCode is ON
[img] is ON
[url] is ON
Smilies are ON

Topic review
   

Expand view Topic review: media monkey: access violation at address 00E7537

Re: media monkey: access violation at address 00E7537

by Lowlander » Mon Jan 13, 2020 10:49 am

Capture it in a debug log (step 4b) and attach the log to a Support Ticket: https://www.mediamonkey.com/forum/viewt ... p?f=1&t=69

Re: media monkey: access violation at address 00E7537

by pintree3 » Mon Jan 13, 2020 10:38 am

So any tips? Oddly enough the problem is not as re-occurring as it was before. now it;s just once in a while which I find odd. How can a problem only exist sometimes?

Re: media monkey: access violation at address 00E7537

by pintree3 » Wed Jan 08, 2020 12:19 pm

Oops forgot to add that I do not have a "Eureka" directory just the latter one.

Re: media monkey: access violation at address 00E7537

by pintree3 » Wed Jan 08, 2020 12:17 pm

Thanks again Peke but no such files exist anywhere there--including its sub directories
(I don't know if that's a good thing or a bad thing)

Re: media monkey: access violation at address 00E7537

by Peke » Tue Jan 07, 2020 6:10 pm

Hi,
AVs are usually hart to track and mostly specific to situations. Can you look at c:\Users\<USERNAME>\AppData\Roaming\EurekaLog\ or c:\Users\<USERNAME>\AppData\Roaming\MediaMonkey\ contain some *.elf files and if yes upload them and send me PM with links to download.

Do not publish here as they contain Memory dump just in case to be sure.

Re: media monkey: access violation at address 00E7537

by pintree3 » Tue Jan 07, 2020 12:35 pm

I installed the portable version and it did not duplicate the problem by repeating my actions however, by then quickly deleting 2 files in succession the message did pop up. And then going quickl up and down did not pop up any further messages.
Getting a strange feeling about it all, as in I felt if I opened my original MM I also would now not be able to duplicate it, I was correct. It did not duplicate.
It seems to me that MM needs to "get warm" first, like an old car, before the problem pops up.

Re: media monkey: access violation at address 00E7537

by Peke » Tue Jan 07, 2020 11:08 am

Hi,
No, clean portable means it is installed into separate folder like c:\MM5Temp and you can start independent non related Version from c:\MM5Temp\MediaMonkey.exe. No uninstalls needed as after testing you can simply just delete c:\MM5Temp folder and it is gone.

Please note that for portable install you need to check that option in Installer.

Re: media monkey: access violation at address 00E7537

by pintree3 » Tue Jan 07, 2020 6:07 am

Thanks for your help peke. By installing a clean portable version you are saying to uninstall the current normal version first, correct? Assuming so, what would be the following steps if it does replicate and if it doesn't replicate?

Re: media monkey: access violation at address 00E7537

by Peke » Wed Jan 01, 2020 12:48 pm

Hi,
If you install clean MMW as portable can you replicate the crash?

media monkey: access violation at address 00E7537

by pintree3 » Tue Dec 31, 2019 11:30 pm

media monkey: access violation at address 00E7537 in module Mediamonkey.exe Read of addres 00000008

A search here produces no exact results (but similar much older results)
The error occurs when I have many files viewing and I use the down arrow on the keyboard to quickly go down (or up) the list. And either one such window pops up or many one on top of the other.
I have the latest pro version of MM running on the Latest version of Windows 10 home.
I did a complete uninstall of MM using IoBit Uninstaller and then CCleaner and the error keeps on occurring.
Yes, there are 2 plugins that I added (a tag manager and 2 skins) on my MM but this error seems to have come out of nowhere (about 4-6 months now) hence it did not exist before. I would then assume that it has something to do with one of the latest versions of MM possibly now clashing with one of the plugins.
I could easily remove one of the skins if I wanted to but definitely not my tag manager.
Is the only solution for me to uninstall such skins/plugins and see if the error re-occurs? Or is there a way around that?

Top