by andyross » Mon Aug 17, 2026 9:20 am
I had a white screen issue after awhile, too, on 3516. I had been doing some work on cleaning up the database, including removing and then re-adding a CD that was doubled up for some reason (originally was in two different folders.) I had no problems with that, but while WiFi syncing with one device, it went white. I had to end-task it. I then restarted it, and after a few seconds, it again went white. The next time, once it started, I quickly closed it normally. After that, it was normal. This was the normal build. It is the first time it has happened, as I have been using 3716 for awhile as it fixed the issue with Event Viewer logging an error while searching for artwork. Not sure if I could easily reproduce it. From the original post, this could be due to being open too long, or something with scanning a folder.
This is the error from Event Viewer:
Faulting application name: MediaMonkeyEngine.exe, version: 2027.0.0.3516, time stamp: 0x6a6a8b2c
Faulting module name: MediaMonkeyEngine.exe, version: 2027.0.0.3516, time stamp: 0x6a6a8b2c
Exception code: 0xc0000005
Fault offset: 0x008fd097
Faulting process id: 0x5208
Faulting application start time: 0x1DD2DD88501938E
Faulting application path: C:\Program Files (x86)\MediaMonkey\MediaMonkeyEngine.exe
Faulting module path: C:\Program Files (x86)\MediaMonkey\MediaMonkeyEngine.exe
Report Id: 2c5bf939-1989-47c2-9038-e6dcc141815c
Faulting package full name:
Faulting package-relative application ID:
I had a white screen issue after awhile, too, on 3516. I had been doing some work on cleaning up the database, including removing and then re-adding a CD that was doubled up for some reason (originally was in two different folders.) I had no problems with that, but while WiFi syncing with one device, it went white. I had to end-task it. I then restarted it, and after a few seconds, it again went white. The next time, once it started, I quickly closed it normally. After that, it was normal. This was the normal build. It is the first time it has happened, as I have been using 3716 for awhile as it fixed the issue with Event Viewer logging an error while searching for artwork. Not sure if I could easily reproduce it. From the original post, this could be due to being open too long, or something with scanning a folder.
This is the error from Event Viewer:
Faulting application name: MediaMonkeyEngine.exe, version: 2027.0.0.3516, time stamp: 0x6a6a8b2c
Faulting module name: MediaMonkeyEngine.exe, version: 2027.0.0.3516, time stamp: 0x6a6a8b2c
Exception code: 0xc0000005
Fault offset: 0x008fd097
Faulting process id: 0x5208
Faulting application start time: 0x1DD2DD88501938E
Faulting application path: C:\Program Files (x86)\MediaMonkey\MediaMonkeyEngine.exe
Faulting module path: C:\Program Files (x86)\MediaMonkey\MediaMonkeyEngine.exe
Report Id: 2c5bf939-1989-47c2-9038-e6dcc141815c
Faulting package full name:
Faulting package-relative application ID: