... "MediaMonkey.exe". Read of address 05BEC404.
Everytime I shut down Media Monkey, this error occurs. When I re-open the program, it never shows the last heard songs but songs I played days before. It seems that the prog cannot save its last setting/adjustment/position anymore.
Idea anyone?
Access violation at address 00407F2E in module ...
Moderator: Gurus
Re: Access violation at address 00407F2E in module ...
Send a debug log (step 4b) to support: http://www.mediamonkey.com/forum/viewtopic.php?f=7&t=69
Download MediaMonkey ♪ License ♪ Knowledge Base ♪ MediaMonkey for Windows 2024 Help ♪ MediaMonkey for Android Help
Lowlander (MediaMonkey user since 2003)
Lowlander (MediaMonkey user since 2003)
Re: Access violation at address 00407F2E in module ...
sorry, i didn't get it
a) For crashes and error conditions MediaMonkey will (usually) automatically generate a debug error report and prompt you to send it.
- Please include your e-mail address and a reference to the original bug description in the forum so that we can match the submission to the original bug description.
- In case MediaMonkey crashes before sending the error report, you can find the error report as 'MediaMonkey.elf' (in Portable installations, it is located in \<install>\Portable\ ; on Win7 it's at C:\Users\<user>\AppData\Roaming\EurekaLog\MediaMonkey )
-> where to find this file 'MediaMonkey.elf' ??? searched the PC, not there
b) For functional problems (i.e. no crash or error) or if an error report is generated automatically, you can manually generate a debug log as described below:
- Download the DbgView application from: http://technet.microsoft.com/en-us/sysi ... s/bb896647
- Execute DbgView.
- If you know that the bug triggers a system freeze, configure DbgView to save the log to a file automatically via File > Log to File...
- Execute MediaMonkey_Debug.exe and try to reproduce the bug with a small set of Tracks.
- You'll see logs being generated in DbgView. Save the log messages from DbgView to a file if necessary.
-> same here. where to find this file 'MediaMonkey_Debug.exe' ??? searched the PC, not there
a) For crashes and error conditions MediaMonkey will (usually) automatically generate a debug error report and prompt you to send it.
- Please include your e-mail address and a reference to the original bug description in the forum so that we can match the submission to the original bug description.
- In case MediaMonkey crashes before sending the error report, you can find the error report as 'MediaMonkey.elf' (in Portable installations, it is located in \<install>\Portable\ ; on Win7 it's at C:\Users\<user>\AppData\Roaming\EurekaLog\MediaMonkey )
-> where to find this file 'MediaMonkey.elf' ??? searched the PC, not there
b) For functional problems (i.e. no crash or error) or if an error report is generated automatically, you can manually generate a debug log as described below:
- Download the DbgView application from: http://technet.microsoft.com/en-us/sysi ... s/bb896647
- Execute DbgView.
- If you know that the bug triggers a system freeze, configure DbgView to save the log to a file automatically via File > Log to File...
- Execute MediaMonkey_Debug.exe and try to reproduce the bug with a small set of Tracks.
- You'll see logs being generated in DbgView. Save the log messages from DbgView to a file if necessary.
-> same here. where to find this file 'MediaMonkey_Debug.exe' ??? searched the PC, not there
Re: Access violation at address 00407F2E in module ...
After installing the debug version just launch MediaMonkey as normal.
Download MediaMonkey ♪ License ♪ Knowledge Base ♪ MediaMonkey for Windows 2024 Help ♪ MediaMonkey for Android Help
Lowlander (MediaMonkey user since 2003)
Lowlander (MediaMonkey user since 2003)