Well, I just read that I should post a debug log. I'll do that when it happens again, but anyway, here's the order of things as they happened to me:

MM Version 4.07.1511, Windows 7 64 bit, CPU: i5 3rd gen
This is what happened:
1. MM is playing for hours
2. Close laptop lid, causing laptop to Hibernate
3. Restart Windows
4. Invoke keyboard shortcut to Play (Play/Pause = CTRL-SHIFT-F12, Global)
5. Access violation occurs on CTRL key event
6. MM still Plays on completion of the key chord
7. Repeated key chord to Pause
8. Identical access violation on CTRL key event
9. MM Pauses, as desired
10. Able to repeat steps 4 to 9 without MM crashing

It's not uncommon. Sometimes the "re-install" fixes issues.

Weird...
So far, after installing the Debug version and running it with Debug View open also...I can't get the thing to error out.
Nice problem to have, I guess!

Got it. Thanks, guys.

I may just see what the increased priority setting does for me first. But if it starts giving this error again anyway, I'll get the debug version and see what I can capture.

Thanks again.

PenaltyShots wrote:OK, I'm confused. So, DebugView only works with the Debug version of MM?

Yes, so http://www.mediamonkey.com/beta/MediaMo ... _Debug.exe and http://technet.microsoft.com/en-us/sysi ... s/bb896647 will allow you to capture the log. Then send the log to support.

debugview is a third party program that you start running before you start mediamonkey. it will record the workings of the system until you stop it and save the file.
that way you can use mediamonkey and make it have the bug show up. you are sure to catch it that way.

the mediamonkey debug version only shows you a debug log when the bug is bad enough to make it pop up the report. it won't catch little twit bugs that drive you crazy that is where the other program comes in handy.
you on win7 or 8 might have to start the debugviewer program in admin mode and let it run. then go back and start mediamonkey as you normally do.
when the bug shows up in mediamonkey let monkey run a few seconds longer and then close it. then go save the debug viewer log. close the debugviewer and zip up the log send it in to the email in the support section at the top of this forum page.

That last post was intended for Lowlander.

I should mention that in the meantime, I set the priority of MM to "above normal". We'll see how that goes.

OK, I'm confused. So, DebugView only works with the Debug version of MM?

I was reading your last message to mean that if I had installed the Debug version of MM, then I'd have to run DebugView in admin mode. Otherwise (regular version of MM installed), I would not.

But it doesn't work, period, with the regular version? And it will only work with the Debug version if running in admin mode?

Thanks.

he could use the 3rd party debug viewer in the how to make a debug report post to capture a huge debug log save it and send it in to support.
that does not need him to install the debug version.

You'll have to in order to capture a debug log.

Rovingcowboy -- No, the Intel Core i7 920 has 4 cores. (Google "Intel i7" -- it's the name of the processor.)

No, I didn't install the Debug version.

PenaltyShots wrote:DebugView doesn't tell me much.

Did you install the debug version of MediaMonkey? If you did you may need run DBGView as Administrator to capture MM's output.

You have 7 cores? Is that what I7 means? It is not a log jam caused by hardware but I'm wondering if it is caused by windows clearing the ram mm gets for his cache, that would take away the sectors he is looking for and give errors of i can't find #300000000...... since windows had removed it, so since it was win98's fault before i'm going with windows again and suggesting it is the way windows clears ram of its files as it might not be able to handle the large number of cores, but that is just a best guess.
i raised the mediamonkey exe to high.

2.66 Ghz Intel Core i7 920 here, with 6GB RAM. Not much else running. I do have a pretty big library, 30K+ tracks, but that would be the only factor that might be a memory hog. I can't think of anything I'm doing in MM that would be a CPU hog, though. The error pops up a lot when MM is just sitting idle, not even playing anything and I'm not doing anything with it either.

DebugView doesn't tell me much. Here's the chunk it recorded when the error popped up last time:

00000252 7499.36376953 [3428] 5796 0000000000000000 ENTER: DllCanUnloadNow
00000253 7499.36474609 [3428] 5796 0000000000000000 LEAVE: DllCanUnloadNow
00000254 7546.63574219 [3428] 4644 0000000000000000 ENTER: DllCanUnloadNow
00000255 7546.63574219 [3428] 4644 0000000000000000 LEAVE: DllCanUnloadNow
00000256 7799.35595703 [3428] 5796 0000000000000000 ENTER: DllCanUnloadNow
00000257 7799.35595703 [3428] 5796 0000000000000000 LEAVE: DllCanUnloadNow
00000258 7846.62109375 [3428] 4644 0000000000000000 ENTER: DllCanUnloadNow
00000259 7846.62109375 [3428] 4644 0000000000000000 LEAVE: DllCanUnloadNow
00000260 8099.35156250 [3428] 5796 0000000000000000 ENTER: DllCanUnloadNow
00000261 8099.35156250 [3428] 5796 0000000000000000 LEAVE: DllCanUnloadNow
00000262 8146.60693359 [3428] 4644 0000000000000000 ENTER: DllCanUnloadNow
00000263 8146.60693359 [3428] 4644 0000000000000000 LEAVE: DllCanUnloadNow
00000264 8399.33593750 [3428] 5796 0000000000000000 ENTER: DllCanUnloadNow
00000265 8399.33593750 [3428] 5796 0000000000000000 LEAVE: DllCanUnloadNow
00000266 8446.59277344 [3428] 4644 0000000000000000 ENTER: DllCanUnloadNow
00000267 8446.59277344 [3428] 4644 0000000000000000 LEAVE: DllCanUnloadNow
[9232] LOG_SYSTEM: [GoogleUpdate:goopdate]: ERROR - Cannot create ETW log writer

Rovingcowboy, can you please elaborate? What did you raise your priority to for MediaMonkey? Above Normal? High?

Thanks, guys.