[Solved] [PC] Kasumi: Stolen Memory DLC Crashing at the end of loyalty mission.
The ME2 DLC Kasumi: Stolen Memory is crashing at the end of the loyalty mission.
I have no trouble doing the mission itself, but when I get to the mission summary and want to press [EXIT] the screen goes black (not blank) and it crashes to desktop, everytime at the same place.
I checked on the old board for any solutions and it seems they found 1, but it isn't working for me.
Old board thread of the problem: http://social.bioware.com/forum/1/topic/106/index/2452757/1.
I've tried everything that thread suggested and even the "add parameter" fix didn't work. They seemed to think that the problem was that the game was trying to use a loading screen that wasn't there. So my next step is trying to replace that loading screen with another one. Though I think it won't work.
I've contacted the Support but the problem was forwarded to the game specialists, they would look into the problem. But that can take years, especially since this problem was noticed 3 years ago and still no official fix of the problem.
Now I am trying to get some attention here so we can hopefully fix this problem (somehow) otherwise hope I can get my money back, don't want to pay for anything that wont work.
There is another thread that posted the same problem, but not much attention to it.
Here: http://answers.ea.com/t5/Mass-Effect-2/DLC-crashing/m-p/344680#M958
My computer specs are as follows:
CPU: i5 3570k
GPU: Gigabyte geforce gtx 660 2gb overclocked version
Motherboard: Asus P8Z77-V LX
PSU: Corsair HX-850
RAM: Corsair Vengeance LP 4x 4gb. (16gb)
OS and Game drive: AData SSD 128 gb.
Software:
OS: Windows 7 ultimate 64bit Latest update
GPU Nvidia drivers latest update
Mass Effect 2: Latest update and all DLCs except Genesis.
Modified Coalesced for better mouse sensitivity. (Have tried doing it without modified also)
[Edit: clarification] Step 6 of the following solution should be sufficient to fix the problem at hand. (You don't need to preform the other steps.) Best course of action is to create that shortcut on the Desktop and run the Game from there.
Here is a more detailed description:
Go to the ">drive<:\Program Files (x86)\Origin Games\Mass Effect 2\Binaries" folder and right click on the "MassEffect2.exe" > send to > Desktop (create shortcut).
Now go to the Desktop and right click the shortcut > Properties.
Click in the "Target" field and then use your right arrow key to bring the cursor to the end of this line (directly after the quote mark (") ). Copy and past this:
" -nomoviestartup" without the quote but with the space before the (-) in the "Target line. Should look that way: ...Binaries\Win32" -nomoviestartup
Click "OK" and start the game from the shortcut on your desktop.(Note: If it is not working for the "MassEffect2.exe" create a shortcut to the "ME2game.exe" and add the line there.)
This should also work for crashes at the end of the Shadow Broker DLC.
For Steam users the solution is in this post.
____________________________________________________________
I was able to do it now without crashing! Here is what I did:
- Uninstall with revo uninstaller (or similiar programs) to remove all the files for me2
- Install everything from the CD (or download from origin if you don't have the physical edition)
- Stop all the dlcs from download via origin.
- download all DLCs from https://social.bioware.com/user_entitlements.php
- install DLCs via the installers you downloaded in step 4. If promted by windows "This program might not have been installed correctly" press "Reinstall using recommended settings"
- Make a shortcut from Masseffect2.exe in the Binaries folder of your mass effect 2 folder. Add in target the parameter "-nomoviestartup" without the quoatation marks " and after \MassEffect2.exe" so in the end it will look like this at the end: "\Binaries\MassEffect2.exe" -nomoviestartup (just so it is right)
- If "awc.dll failed to load" comes up, just go into origin and right click on Mass Effect 2 and press repair.
- Play and hopefully it will work.
I don't know why it worked now but hey, I'm not complaining^^.