Aller au contenu

Photo

ME1: Black Screen after the splash screen


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

#1
Simbiat

Simbiat
  • Members
  • 14 messages
Hi there!
When ME2 was realease I've decided to run through ME1 again, but encountered a problem: when I start the game the splash screen appears (the one with Shepard in the middle) and when it dissapears there is only black sreen.... No movies, no nothing. But the mass effect.exe process is eatingalmost 50% of CPU and almost 300 Mbs of RAM.
I've tried to run both retail and steam versions - all the same. I've tried to run both versions as administrator (and with administrator priviligies), in compitability mode (XP SP3) and with forced DirectX 9 - no result. I've tried reinstalling the retail version, tried deleting .ini files from My Documents and even tried a crack from reloaded, but no result. I also tried running it in windowed mode.
The game has both DLCs installed as well. And I'm running it under Win7 x64. My drivers are up-to-date and I can't find what the problem is and how I can solve it.
Please, can someone advice me on this problem?
Thank you.

#2
Simbiat

Simbiat
  • Members
  • 14 messages
BTW, I have a similar problem with Mirror's Edge, but it hangs on the splash screen.

#3
Simbiat

Simbiat
  • Members
  • 14 messages
BTW I have a similar problem with Mirror's Edge, but it hangs on the splash screen.

#4
Fredvdp

Fredvdp
  • Members
  • 6 186 messages
System specs?

#5
Simbiat

Simbiat
  • Members
  • 14 messages
MB: Asus P5B

Video Card: ASUS GT9600 GT

Audio Card: Asus Xonar HDV 1.3

Processor: Intel core 2 Quad Q9700

RAM: 8 Gbs of Corsair Dominator DDR2 667 MHrz

System HardDrive: Western Digital IDE HardDrive on 160 GB (I'm to lazy to see the exact model)

#6
Simbiat

Simbiat
  • Members
  • 14 messages
A small addition: with such a configuration, but with 4 Gbs of ram, the game ran perfectly smooth on Vista x64... I can try to run in on Virtual Machine under XP or Vista, but that's...Uncomfortable, to say the least.

#7
Anthonzi

Anthonzi
  • Members
  • 1 messages

Simbiat wrote...

A small addition: with such a configuration, but with 4 Gbs of ram, the game ran perfectly smooth on Vista x64... I can try to run in on Virtual Machine under XP or Vista, but that's...Uncomfortable, to say the least.


I am having the some problem on Vista x64.  Black 800x600 screen with a loading ring as mouse pointer.  Have tried both my old disc version and a download from Steam.  Funny thing is that I have played the game on the same computer a year ago.  Might be some Win7 software upgrade issues, or maybe some other earlier changes.  Donno.

#8
Simbiat

Simbiat
  • Members
  • 14 messages
Well it worked fine for me on Vista... But, I'll try to start it on Virtual Machine under XP, maybe there will be some luck there...

#9
Simbiat

Simbiat
  • Members
  • 14 messages
So, does anyone have any clues on what may be the problem?

#10
Simbiat

Simbiat
  • Members
  • 14 messages
Well I've tried running it on Virtual PC (the so-called XP-Mode in Win7), but it says, that "This programm cannot be run remotely"...

#11
CriticalKiller

CriticalKiller
  • Members
  • 12 messages
It's hard to say what it could be.  If I was having this problem, I would uninstall my video drivers using Control Panel; then use the program Driver Sweeper to completely remove remainents of the old drivers; restart my computer and install whatever the latest version of video drivers are available for your graphics card.  The reason I suggest this is because your sypmtoms are similar to what happens when your video card drivers stop working.

If that doesn't fix the problem it's a hardware issue (either with your video card or RAM possibly), because if you have installed the steam and a retail version and get the same issue at the same spot, there's no way it's the game.

Edit- I wanted to add that it's not a Windows 7 issue, as I have the steam version of the game installed on my computer, which has Windows 7 64-bit installed as the operating system

Modifié par CriticalKiller, 26 février 2010 - 08:04 .


#12
Simbiat

Simbiat
  • Members
  • 14 messages
I Know it's not OS related... Well... I can try reinstalling the drivers from scratch... But I doubt it will have any effect at all... But I'll update when ready.

#13
NightLad

NightLad
  • Members
  • 61 messages
For me, it was the Audio. Or rather, a tiny audio file that was conflicting with the program.

On Vista:
I uninstalled a small program called Host OpenAL which is part of the Creative audio install. (It lets other hardware use some of its apps.) You can find the latest verson here if you want to reinstall later: http://connect.creat...al/default.aspx (the program does not seem to affect any others when removed, at least not for me.)

On Windows 7 x64:
It isn't located in the Installed Programs list. Instead, it appears as a .dll.

Search the ME1 install folder for "OpenAL" to locate OpenAL32.dll and remove it.
Run MassEffect as admin.

I hope this helps.

Modifié par NightLad, 26 février 2010 - 11:34 .


#14
Simbiat

Simbiat
  • Members
  • 14 messages
Deleting AL did not help... Besides, I'm using ASUS Xonar :-D

#15
Simbiat

Simbiat
  • Members
  • 14 messages
Reinstalling video-drivers also didn't help. Though I doubt that it's a hardware problem, 'cause when I usde Vista, I had the same hardware and it worked fine... Probably something is blocking something...

#16
Misael

Misael
  • Members
  • 13 messages
You got the bring down the sky patch?? I was having similar problem here on windows XP, after that i got the game to run ( but he crash after the "press enter key" for another problem kkk). Well, i too got the game to work in full screenn 1024 x 768, that is the default resolution for newer games... on window mode i too manage to run... but i tested only in 640x480 only to bring the game to run...
And well... here the game take a while to run... a few minutes in splash screen and few in black screen... only after some delay that he begins to run...

Modifié par Misael, 05 mars 2010 - 08:57 .


#17
Gorath Alpha

Gorath Alpha
  • Members
  • 10 605 messages
Misael:
Minimum System Requirements for Mass Effect on the PC (This varied, depending on whether you looked at EA's site or Bioware's, but both contained video card errors -- so the stupid Radeon naming is omitted below.)

Operating System:
Windows XP or Vista

Processor:
2.4+GHZ Intel or 2.0+GHZ AMD (Celerons and Semprons not included)

Memory:
1 Gigabyte Ram (XP)
2 Gigabyte Ram (Vista)

Video Card:
NVIDIA GeForce 6 series (6800GT or better)

Hard Drive Space:
12 Gigabytes

Sound Card:
DirectX 9.0c compatible sound card and drivers
----------
In December, 2009, the requirements fir ME2 PC were announced, still using the same basic UT engine, and the minimum video cards are the 6800 GS and the Radeon X1600 Pro.

Modifié par Gorath Alpha, 06 mars 2010 - 03:34 .


#18
Simbiat

Simbiat
  • Members
  • 14 messages
Still, has anyone got a solution for my problem? (=

#19
Simbiat

Simbiat
  • Members
  • 14 messages
Today I'll try to install it on VMWare on "clean" XP. Will update you later.

#20
Misael

Misael
  • Members
  • 13 messages
Simbiat you don't say if you have installed the patch 1.02... have tried? And the black screen occur here and take a time to load the game... isn't the case??

#21
Misael

Misael
  • Members
  • 13 messages
There is some info from support.ea.com regarding issues with windows vista, don't know the win7 to say if applies...:



" QUESTION

What can I do if Mass Effect keeps crashing after I installed it on my Windows Vista machine?



ANSWER

Windows Vista users with UAC (User Access Control) enabled may experience a crash to desktop when running Mass Effect after installation.

The solution to this problem is to disable UAC, run Mass Effect PC once and then enable UAC on your Windows Vista Control Panel. Once the procedure has been completed, you will not have to repeat the it unless Windows Vista is reinstalled."

#22
Simbiat

Simbiat
  • Members
  • 14 messages
I''ve reinstalled video drivers once again and cleared the system from them and now everything seems to be fine. Tahoo!