Aller au contenu

Photo

Having Major Problem, ME1 Won't Start


  • Veuillez vous connecter pour répondre
3 réponses à ce sujet

#1
naledgeborn

naledgeborn
  • Members
  • 3 964 messages
I bought another copy of ME1 for PC a while back to start a brand new canon for import. Lost my old copy. Bought it off of one Amazon's vendors. Installed it on my old pc wouldn't get passed the launcher. Waited till I bought this new one. Installed it. Still doesn't get passed the launcher wtf is going on? The "ME stopped working" window pops up right after i click start game. I downloaded the 1.02 patch. Same ****e is goin on. Little help from the BW people or EA people or other forumites would be appreciated.   

#2
SSV Enterprise

SSV Enterprise
  • Members
  • 1 668 messages
Please report your system specifications as described in this thread

Modifié par SSV Enterprise, 02 août 2010 - 02:26 .


#3
Raith_Karris

Raith_Karris
  • Members
  • 48 messages

SSV Enterprise wrote...

Please report your system specifications as described in this thread


Thank you for a useless support reply. You could have provided a couple of possible solutions along with that, Enterprise.



Now, according to the problem description, I suspect you're running on Windows Vista, naledgeborn. Mass Effect tends to malfunction right after the startup screen if you're running on that OS.

Open the game folder in your hard drive, the main folder located within your program files. Look for the .exe file, that bypasses the launcher and starts the game directly (the launcher .exe contains "launcher" in the name). . Try running it directly as administrator. If needed, also try compatibility mode for WinXP. Do this once, and the game should launch normally afterwards. You don't need to repeat this process every time, just do it once and then you can use the launcher again.

Modifié par Raith_Karris, 04 août 2010 - 07:54 .


#4
Gorath Alpha

Gorath Alpha
  • Members
  • 10 605 messages
Given that a large percentage of the times that the OP's error message is prompted in the recent games we deal with here, DA, ME-1, and ME-2, the cause is hardware, and then within that group, by an Intel Tinker Toy graphics chip, then suggesting that an apparent noobshould follow a standard route in describing the problem is an excellent start, while just throwing out WAGs is more likely to confuse the basic issue.   

Enterprise was "more correct" in my opinion, than the WAG is.  And that happened three days ago, so by now, the OP either found an answer without further advice here, or decided to give ME-1 a pass, after all.

I've just scanned all of the threads with "stopped" in the topic line (limited to this forum only), and found that there was an even split between Intel graphics chips and bad Geforce drivers as the reasons for the error message, when there was an actual conclusion reached.  So I exaggerated in my opening sentence (now edited).  I didn't scan tho threads that were about other "stop" c8ircumstances. 

P. S. I may have eliminated Intel as a vector, if the OP was actually running Dragon Age at something close to a normal setting. 

naledgeborn wrote...

 . .. Little help from the BW people or EA people or other forumites would be appreciated.  

 

There never are any of EA's people in the Bioware forums, at least not on an official basis.  I have never seen any Bioware people in this particular forum, other than Chris Priestley (whose decription of the proper reporting form that it would have best for you to have followed, is pinned on top, where you skipped past it). 

There is no similarity between the game engine used to create Dragon Age and the UT3 (UT3-plus for ME-2) that is underlying this game.  The basic requirements may seem similar, but EA screwed them up totally, so they make no sense whatsoever. 

Modifié par Gorath Alpha, 19 août 2010 - 03:45 .