Aller au contenu

Photo

Not Compatible with 64 bit?


77 réponses à ce sujet

#51
DargaardKeep

DargaardKeep
  • Members
  • 26 messages

BhagwanX wrote...

So I've done just about everything in this thread, and I've got no love at all. Those of you who are actually in the game, is it even fun?


Yes. ME3 is very fun.

It is as good as ME2.

Sorry to hear about your problem.

I hope that Bioware/EA will fix it for you soon.

#52
DiebytheSword

DiebytheSword
  • Members
  • 4 109 messages
It worked on my 64 bit enviroment just fine, so I doubt its that.

#53
Snapa

Snapa
  • Members
  • 4 messages

Delta Serpentis wrote...

Ok - More information

When you run the masseffect3.exe, it actually kicks off a thing called masseffect3_activation.exe.  This is copied and run from Drive:Users<user>AppDataLocalTempmtka_tmp (there's lots of logs there for me but no exe).  I suspect this attempts to decrypt the encrypted masseffect3.exe but fails for some reason and corrupts the exe, hence the strange error message.

This is all guess work, but it seems plausible

Can anyone confirm this?

Delta


After following this amazing post, I tried something with that temp folder too.

1. I uninstalled both Origin and ME3.
2. Reinstalled.
3. Tried to run the game, same **** again.
4. Updated the game and after I launched it I noticed the temp folder (when it asks your permission to modify your files or something) went to the temp folder, and deleted all those .log files that had Mass Effect 3 mentioned. My folder was in C:\\Temp\\mtka_tmp
5. Ran the game again, now straight from the exe, and it took me to the release date check for the first time and the game started just fine!

I hope this works for you guys too.

#54
Nismoo

Nismoo
  • Members
  • 2 messages
Wow finally a solution that worked for me! Been trying everything since launch day including uninstalling/reinstalling/updating etc. Cleared out the temp folder as suggested and it finally went to the release date checker:)

Huge thanks to you guys for working this out!

Snapa wrote...

Delta Serpentis wrote...

Ok - More information

When you run the masseffect3.exe, it actually kicks off a thing called masseffect3_activation.exe.  This is copied and run from Drive:Users<user>AppDataLocalTempmtka_tmp (there's lots of logs there for me but no exe).  I suspect this attempts to decrypt the encrypted masseffect3.exe but fails for some reason and corrupts the exe, hence the strange error message.

This is all guess work, but it seems plausible

Can anyone confirm this?

Delta


After following this amazing post, I tried something with that temp folder too.

1. I uninstalled both Origin and ME3.
2. Reinstalled.
3. Tried to run the game, same **** again.
4. Updated the game and after I launched it I noticed the temp folder (when it asks your permission to modify your files or something) went to the temp folder, and deleted all those .log files that had Mass Effect 3 mentioned. My folder was in C:Tempmtka_tmp
5. Ran the game again, now straight from the exe, and it took me to the release date check for the first time and the game started just fine!

I hope this works for you guys too.



#55
vandoug

vandoug
  • Members
  • 83 messages
Just want to add my case here. I installed Origin and ME3 from disc on my Win7 64bit PC. I got the incompatible issue. Then I did the 40M bytes update via Origin client window. It triggered the Release Date Check and the decryption process upon the finish of the update. ME3 launches fine now for me.

#56
82JiminyCricket

82JiminyCricket
  • Members
  • 40 messages
I can get to the Release Date Checker just fine, but during the decryption process it starts 'dinging' and gets to about 80% and shuts down and tries to launch ME3 only to say "Mass Effect ™ 3 has stopped working."

#57
SolesurvivorOne

SolesurvivorOne
  • Members
  • 3 messages
Yep exactly! Decryption starts, ends at 80% - you can hear a "ding ding" - then the decryption window disappears.
It will download the 40 Mb Patch again, Decryption starts - crashes at 80% and so on...

#58
SolesurvivorOne

SolesurvivorOne
  • Members
  • 3 messages
Could someone tell me the filesize of a working MassEffect3.exe?
My .exe after downloading that 40.1 Mb Patch is 42.078.464 Bytes
After executing it and decryption (crash?) it is 22.368.640 Bytes

#59
Soup0rMan

Soup0rMan
  • Members
  • 12 messages
Same problem, 1055t, windows 7 64 bit, I use a ssd for boot. So far I have reinstalled the game, origin and windows with the same error everytime, I also cleared origins cache also. This is ridiculous no mods have picked up on this, and on other threads the mods actually had the nerve to write "looks like this is resolved"

#60
Soup0rMan

Soup0rMan
  • Members
  • 12 messages
Forgot to mention I have also repair installed and patched of course, however it will make me download/install the 40mb patch everytime

#61
SolesurvivorOne

SolesurvivorOne
  • Members
  • 3 messages
Nah. Its far from resolved. The decryption process is obviously not working right for some people..

#62
Shiava

Shiava
  • Members
  • 2 messages

Soup0rMan wrote...

Same problem, 1055t, windows 7 64 bit, I use a ssd for boot. So far I have reinstalled the game, origin and windows with the same error everytime, I also cleared origins cache also. This is ridiculous no mods have picked up on this, and on other threads the mods actually had the nerve to write "looks like this is resolved"



Also using an SSD, same problem

#63
Shiava

Shiava
  • Members
  • 2 messages

Snapa wrote...

Delta Serpentis wrote...

Ok - More information

When you run the masseffect3.exe, it actually kicks off a thing called masseffect3_activation.exe.  This is copied and run from Drive:Users<user>AppDataLocalTempmtka_tmp (there's lots of logs there for me but no exe).  I suspect this attempts to decrypt the encrypted masseffect3.exe but fails for some reason and corrupts the exe, hence the strange error message.

This is all guess work, but it seems plausible

Can anyone confirm this?

Delta


After following this amazing post, I tried something with that temp folder too.

1. I uninstalled both Origin and ME3.
2. Reinstalled.
3. Tried to run the game, same **** again.
4. Updated the game and after I launched it I noticed the temp folder (when it asks your permission to modify your files or something) went to the temp folder, and deleted all those .log files that had Mass Effect 3 mentioned. My folder was in C:Tempmtka_tmp
5. Ran the game again, now straight from the exe, and it took me to the release date check for the first time and the game started just fine!

I hope this works for you guys too.


The log file deletion trick worked!

#64
BhagwanX

BhagwanX
  • Members
  • 9 messages
Can you break this down a little more for me? I understand in principle what you're talking about but have no idea how to make this change.

I've deleted every temp file I can find in the directories, have run the .exe straight from the binaries folder (both as an admin and not, in compatibility mode and not), and get exactly the same crash message I had before, but this time without even a release day check. I only get the release day check through Origin after a fresh pressing of both the "update game" and "repair installation" options.

Here's my recurring ME3 crash messeage, no matter how I try to start the game

Problem signature:
Problem Event Name: BEX
Application Name: MassEffect3.exe
Application Version: 1.1.5427.4
Application Timestamp: 4f46d052
Fault Module Name: MassEffect3.exe
Fault Module Version: 1.1.5427.4
Fault Module Timestamp: 4f46d052
Exception Offset: 007f0dd1
Exception Code: c0000409
Exception Data: 00000000
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional Information 1: 9caf
Additional Information 2: 9cafc8ac6960cc8cbd1e7048459f5ce6
Additional Information 3: aa08
Additional Information 4: aa08b93f35e8570edfe6a3b0ef32ef82

Modifié par BhagwanX, 08 mars 2012 - 07:03 .


#65
Snapa

Snapa
  • Members
  • 4 messages

SolesurvivorOne wrote...

Could someone tell me the filesize of a working MassEffect3.exe?
My .exe after downloading that 40.1 Mb Patch is 42.078.464 Bytes
After executing it and decryption (crash?) it is 22.368.640 Bytes


My working .exe is 22 368 640.
Before the activation it was ~40MB.

Seems that the first exe ain't a game executable at first, it's just the activation. After a succesful activation it creates the smaller executable file.

#66
DABhand

DABhand
  • Members
  • 344 messages
MKTA_TMP folder is a securom folder. So people having probs with Securom on 64bit OS's?

#67
noraging

noraging
  • Members
  • 16 messages

DABhand wrote...

MKTA_TMP folder is a securom folder. So people having probs with Securom on 64bit OS's?


Are you on Mac BootCamp too? I have a problem with this error

"MassEffect3_activation.exe has encountered a problem and need to close. Sorry for the inconvenience" Then it asks me to send the error report to microsoft or not and then nothing happen. 

Anyone has a clue?

#68
noraging

noraging
  • Members
  • 16 messages

Snapa wrote...

SolesurvivorOne wrote...

Could someone tell me the filesize of a working MassEffect3.exe?
My .exe after downloading that 40.1 Mb Patch is 42.078.464 Bytes
After executing it and decryption (crash?) it is 22.368.640 Bytes


My working .exe is 22 368 640.
Before the activation it was ~40MB.

Seems that the first exe ain't a game executable at first, it's just the activation. After a succesful activation it creates the smaller executable file.


You have the problem with the"MassEffect3_activation.exe" too? Me too, but I have this message.

"MassEffect3_activation.exe has encountered a problem and need to close. Sorry for the inconvenience" Then it asks me to send the error report to microsoft or not and then nothing happen. 

Anyone has a clue?

#69
DABhand

DABhand
  • Members
  • 344 messages

noraging wrote...

Are you on Mac BootCamp too? I have a problem with this error

"MassEffect3_activation.exe has encountered a problem and need to close. Sorry for the inconvenience" Then it asks me to send the error report to microsoft or not and then nothing happen. 

Anyone has a clue?


No I am on PC, was just generally asking people if they had problems majorly centred around the securom temp folder and deleting the logs etc resolved their problem or not?

#70
noraging

noraging
  • Members
  • 16 messages
SUCK THAT EA I SOLVED IT WITHOUT THE NEED OF YOUR HELP!

IF THERE IS ANYONE THAT HAVE THE SAME PROBLEM AS ME THAT YOU CAN'T RUN ME3 ON YOU MAC BOOT CAMP: Window XP. DO THE FOLLOWING.

You have to go get the crack and hopefully you don't need any dlc. It might work, but to be on the save side because you gonna need your bought ME3

**Please update your game before doing this

1) go the pirate bay
2) Search Mass effect 3 for "MASS EFFECT 3 100% WORKING CRACK" torrent.
3) Extract the file somewhere
4) Get the torrent, but you will only have the crack application that is exactly MassEffect3.exe
5) Notice that your original file is ~41MB, replaces it with 21MB crack in C:\\Program Files\\Origin Games\\Mass Effect 3\\Binaries\\Win32
6) Low AND BEHOLD IT WORKS.

Don't bother ask for help, EA and Bioware will turn you down immediately if you us bootcamp.

#71
DABhand

DABhand
  • Members
  • 344 messages
Oh lordy that wasn't the smartest thing to do >.<

That also doesn't help figure out what the problem was in the first place, only that the protection could be the cause. Which still leads me to believe its a Securom Issue.

#72
Soup0rMan

Soup0rMan
  • Members
  • 12 messages
still not working, i did notice in my installerdata.xml it has my local as ru_RU
and this string as well <eula name="Mass Effect™ 3 Лицензионное соглашение с конечным пользователем">/Support/eula/ru_RU_eula.rtf</eula>


anyone with the english version working want to copy and paste the top part of their installdata.xml so i can see if thats the problem

#73
Clay Campbell

Clay Campbell
  • BioWare Employees
  • 2 messages
The Origin team has just released an update to fix the release control problem. If you are experiencing this issue please right click on your game in the Origin library and select "Check For Update." This should fix this issue.

#74
Soup0rMan

Soup0rMan
  • Members
  • 12 messages
works, thank you!

#75
BhagwanX

BhagwanX
  • Members
  • 9 messages
Not so much, really. While the release date check problem has certainly disappeared, it's because the game won't launch at all. I hardly see this as an improvement.