media monkey: access violation at address 00E7537
Posted: 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?
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?