An update and work around on this topic. Hope it will work for you too.
Since 4.0.5 the performance was improved on x64 machines by enhancing the address space to 4 GB but this cause for some of us in ripping problems and system crashes (blue screens). The reason is a low level problem between x64 systems and device drivers what cannot be fixed from MM. The problem only happens by ripping in „Secure read". There are three possible work arounds to solve or handle this problem:
1) Check, if there is an update available for your CD/DVD/BR device driver and firmware. Check if the problem is solved with the update. If not, you need to look for the next two work arounds.
2) The problem happens by ripping with "Secure read". The two other options "Standard read" and "Jitter corrected read" do not cause this problem. Use this instead of "Secure read". If you need "Secure read" then the next and last work around is maybe a solution for you.
3) This solution will restrict the enhanced address space back to <2GB. For doing so you need a tool called "CFF Explorer" to modify the file header parameter for "MediaMonkey.exe" and "MediaMonkey (non-skinned).exe". You maybe want to make a backup of these two files before you try to do the next steps. You can find the link of the tool and screenshots at the end of this post. Looks more complicated as it is in real.
3a) Install the program and start it as
administrator.
3b) Open "MediaMonkey.exe" from its program directory.
3c) Choose in the left "File Header" (the right window will be filled then)
3d) Click in the right at line "Characteristics" at "Click here". Then the characteristics window will open.
3e) Look on line "App can handle > 2 GB address space", disable the check box and click after this the "ok" button
3f) Click in the main window the save button for saving the file and accept overwriting original file "MediaMonkey.exe"
3g) Repeat Step 3b) to 3f) for file "MediaMonkey (non-skinned).exe".
3h) Close "CFF Explorer" and start MediaMonkey
After this, MediaMonkey will work for ripping mode "Secure read". Keep in mind that you need to do part 3 for each update of MediaMonkey as long as the low level problem between your x64 system and device drivers isn't solved by Microsoft and / or your device manufacturer - or do not use rip mode "Secure read".
At the end I like to thank Ludek Stoklasa, who figure out the problem and gave me the tips for this work around.
Links:
CFF Explorer:
http://www.ntcore.com/exsuite.php
CFF Explorer Screenshots:
http://www.ls-uk.info/forum/index.php?topic=54930.0
MM Bug report ticket
http://www.mediamonkey.com/support/inde ... etid=17676
MM KB article, see Item 5:
http://www.mediamonkey.com/support/inde ... ticleid=43
).
