Aller au contenu

Photo

Windows7 64Bit Black Screen after Splashscreen


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

#1
Ushtarador

Ushtarador
  • Members
  • 8 messages
Hi Guys,

So I wanted to play ME1 again after some time, but when I start the game, I get the (apparently quite common) problem that after the splashscreen my screen turns black and the program locks itself up. The only major things I changed after my last playthrough are a new CPU and Mainboard afair. Game is patched to 1.02 with no DLC installed.

- AMD Phenom II X4, 3.0Ghz
- 4GB Ram
- ATI Radeon HD4850

So far I tried:

- starting directly from the .exe with compatibility to Windows XP SP2/3 and as Administrator
- disabling my antivir
- reinstalling twice
- updated sound driver
- updated graphics driver
- (re)installed DX9

If you got some ideas or need more info please tell me, I really want to play this awesome game again :(

#2
mcsupersport

mcsupersport
  • Members
  • 2 912 messages
How long have you waited before restarting/exiting program??
Cut your core affinity to 1 or no more than 2 cores to play the game.
On my machine it takes 30-60 seconds of black screen before the game picks up and continues.

#3
Ushtarador

Ushtarador
  • Members
  • 8 messages
just tried twice, one time affinity on core0 and the other on core1. Waited for about 5mins but no change :/

#4
Bogsnot1

Bogsnot1
  • Members
  • 7 997 messages
What version of the game do you have?
Steam, EADM/Origin download, Other digital download, disk, or EA value edition disk?

#5
Ushtarador

Ushtarador
  • Members
  • 8 messages
original vanilla edition disk :) it just really bugs me that it worked perfectly before..

Modifié par Ushtarador, 31 octobre 2011 - 11:34 .


#6
Bogsnot1

Bogsnot1
  • Members
  • 7 997 messages
Was it already installed when you upgraded, or did you decide to reinstall after you had upgraded?

If it was already installed, try moving/deleting any autosaves and quicksaves under the various profiles. ME2 has a similar problem where the auto/quicksaves can become corrupt, and causes thegame to crash on loading. Might be a similar thing with ME1.

If a fresh install (I assume you installed and ran config as admin), then try force-running the C++ redistributable package on the disk. It sometimes wont install if the setup detects a newer one, and the game, from memory, requires the 2005 runtimes and the newer ones (2008/2011) wont do the job properly.

#7
Ushtarador

Ushtarador
  • Members
  • 8 messages
Did a fresh install and renamed the profile folder, so that cant be an issue. Installing the 2005 package didnt help.
Remembered the log-file though:

[0.003] Log: Log file open, 11/01/11 01:43:19
[0.003] Init: BioWare Final Build Version: 1.2.20608.0
[0.003] Init: Command line:
[0.003] Init: Base directory: E:\\Programme\\Mass Effect\\Binaries\\
[0.046] Init: CPU Page size=4096, Processors=4
[0.046] Init: High frequency timer resolution =2.939648 MHz
[0.046] Init: Memory total: Phys=1048575K Pagef=2097151K Virt=2097024K
[11.640] Log: Shader compiling for material Nodebuddy_GOOD took 10.11s
[13.686] Log: Failed to load 'Material None.': Failed to find object 'Material None.'
[13.686] Log: Failed to load 'Material None.': Failed to find object 'Material None.'
[13.686] Log: Failed to load 'Material None.': Failed to find object 'Material None.'
[13.686] Log: Failed to load 'Material None.': Failed to find object 'Material None.'
[13.686] Log: Failed to load 'Material None.': Failed to find object 'Material None.'
[13.688] Log: Failed to load 'Material None.': Failed to find object 'Material None.'

Doesnt sound very helpful to me though :/

#8
Bogsnot1

Bogsnot1
  • Members
  • 7 997 messages
Is your E drive your default system drive, or just another drive that you install your games/programs to?
If your My Documents in the default location, or has that been moved as well?

#9
Ushtarador

Ushtarador
  • Members
  • 8 messages
E is my big harddrive with lots of space, system is on C as usual. My Documents is in default location.

#10
Bogsnot1

Bogsnot1
  • Members
  • 7 997 messages
The only other thing I can think of right now is to double check all your BIOS settings (also check for BIOS updates) to ensure everything is running at the right voltages and frequencies.

#11
Ushtarador

Ushtarador
  • Members
  • 8 messages
might have to check, though I guess if that was the case, other programs would have trouble as well.
Should I maybe also check older graphics drivers/sound drivers or something?

#12
Bogsnot1

Bogsnot1
  • Members
  • 7 997 messages
You could try and older revision of the Catakyst drivers. AMD are fairly robust when it comes to supoprting older games, but it couldnt hurt to try.

Sound driver should be ok, unless you have Realtek and Win7, in which case get the latest driver from either your MB manufacturer, or Realtek's website. The default Win7 driver is buggy as hell.

#13
Ushtarador

Ushtarador
  • Members
  • 8 messages
wow, I solved it....

According to this post: http://social.biowar.../index/892933/1

I downloaded the file oalinst from the link there: http://connect.creat...s/AllItems.aspx

Then run the .exe, go to System32, copy OpenAL32.dll and replace the file Mass Effect/Binaries/OpenAL32.dll

seriously what the **** but whatever :)

Modifié par Ushtarador, 01 novembre 2011 - 10:16 .


#14
Bogsnot1

Bogsnot1
  • Members
  • 7 997 messages
Good stuff. Have fun.