Aller au contenu

Photo

Game Fails to Save then BSOD During Load After Update


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

#1
cbankston

cbankston
  • Members
  • 5 messages
I just installed the DVD version of Mass Effect 1 on an external HD in a Windows XP system.  I played through the introduction to the point of meeting the navigator then tried a manual save.  I got an error message that there was a problem with saving and the game data was not saved.  I confirmed that there was no save file in the Mass Effect folder in My Documents.  When I restarted the game I had only the option to start a new game.  Since the error message didn't specify what the problem was, how do I get the game to save?

I then installed the 1.02 update and the free DLC.  Now when I try to start the game I get the initial splash screen.  Then shortly after the screen changes to the black full-screen mode I get a blue screen crash with memory dump.  The problems are going from bad to worse.  Is there a way to salvage a workable game from this disaster?

Modifié par cbankston, 17 avril 2010 - 01:25 .


#2
cbankston

cbankston
  • Members
  • 5 messages
I solved the problems.  I no longer get the BSOD during loading since I reinstalled the 1.02 update.  I think I initially had installed the DLC after the update, which may have reverted some vital files to older versions.

I can save games after editing the SavePath in the BIOengine.ini file.

I am wondering why my question got no responses, as I doubt the problems I encountered were unique to my installation.

#3
Kloreep

Kloreep
  • Members
  • 2 316 messages
Remember, this is just a fan forum. The official EA tech support either lurks or doesn't come here at all. If you're lucky, you might get a response from someone who knows what's up, but if not... well, personally, I try not to clutter things up too much if I don't even know where to begin.



I have seen posts about problems re: saving when My Documents is on a partition other than C:, but I don't actually recall seeing that the solution is an easy .ini edit. Good to know.