Crash / Hang at startup splash screen - Fix

[Perturbed Pendejo]

This might help people that experience a hang at the initial loading splash screen. My solution was to delete OpenAL32.dll from the game/bin directory and replace it with another copy from the Windows/System32 folder.

I'm on a Win Vista 64 bit machine using a creative X-Fi usb headset. The version of OpenAl32.dll that works for me is 6.14.357.25 with a file size of a 120 KB.

I usually stay away from using forums but I couldn't find this mentioned anywhere on the net so here you go. If this is common knowledge delete it or whatever.

[Leftie]

I tried all the other tips I could find on the three STALKER forums (run Steam as Admin, disable In-game Steam community, disable special antivirus/firewall run-protection (e.g. Comodo Firewall Defense+)), but nothing helped before this.

A million thanks for the tip, and shame on the game-publisher for releasing such broken BS.

[Plavii]

Hi everyone. Any of you tried after the last update package (mainly KB2670838) for Windows 7 a play Stalker CS? Everything is fine? Sorry for my bad english..

I ask because the game after this update still crashes in DX10 mode. (during startup)

[DayOfTheSheep]

Forcing the game to "run in compatability mode with Win 7" made it work for me.

[DayOfTheSheep]

Αναρτήθηκε αρχικά από Plavii:

Hi everyone. Any of you tried after the last update package (mainly KB2670838) for Windows 7 a play Stalker CS? Everything is fine? Sorry for my bad english..

I ask because the game after this update still crashes in DX10 mode. (during startup)

Have you tried uninstalling the update and seeing if Clear Sky works?

[DayOfTheSheep]

Problem signature:
Problem Event Name: APPCRASH
Application Name: RE5DX10.exe
Application Version: 1.0.0.129
Application Timestamp: 4a531c50
Fault Module Name: d3d11.dll
Fault Module Version: 6.2.9200.16492
Fault Module Timestamp: 50f31443
Exception Code: c0000005
Exception Offset: 000a56b3
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 5129
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

Looks like the update from Microshit broke DX10.

[Plavii]

I tried almost everything but the problem still persists, but I not tried uninstalling the update. And I will not try it, if it is not necessary because this update has helped me crashes in Crysis 3.

So...The problem is not just with me?

[DayOfTheSheep]

Αναρτήθηκε αρχικά από Plavii:

I tried almost everything but the problem still persists, but I not tried uninstalling the update. And I will not try it, if it is not necessary because this update has helped me crashes in Crysis 3.

So...The problem is not just with me?

Set xrengine.exe to "run in compatibility mode Windows 7" and it will work.

[Plavii]

Wow, thanks dude! It works :))

Btw. Is my suspicion correct, there is an error in the update?

[Bobr]

At me game too wasn't started. Removal of the file: "STALKER Clear Sky\_appdata_\user.ltx" helped. It was necessary to adjust game anew only. Because it is the file in which settings are stored.

[DayOfTheSheep]

Αναρτήθηκε αρχικά από Plavii:

Wow, thanks dude! It works :))

Btw. Is my suspicion correct, there is an error in the update?

I'm thinking Nvidia and AMD need too catch up with their drivers.

I ran 3D Mark Vantage which is DX10 and Unigine Heaven in DX10 mode with no problems.

Those being synthetic benchmarks don't emulate real world gameplay so they may not call upon the same API functions that a game is required to use. Which maybe why they didn't crash on me.

So yeah, I think I might just wait for the next set of drivers for my GTX 670 since the latest ones forced me to reload a backup of windows.

[Virulent]

I'm right now having a similar problem with the game no longer starting in DX10 mode. Messing with the combatibility settings don't seem to work. I've tested some other older games that use DX10 like Bioshock and FarCry 2 and they all run fine. I'm guessing it was either the Win7 update or the latest Nvidia drivers that broke CS DX10.

Has anybody had any luck with getting DX10 in CS working?

[DayOfTheSheep]

Αναρτήθηκε αρχικά από Virulent:

I'm right now having a similar problem with the game no longer starting in DX10 mode. Messing with the combatibility settings don't seem to work. I've tested some other older games that use DX10 like Bioshock and FarCry 2 and they all run fine. I'm guessing it was either the Win7 update or the latest Nvidia drivers that broke CS DX10.

Has anybody had any luck with getting DX10 in CS working?

I uninstalled the Windows Platform Update and CS no longer crashes at all. Neither does RE5.

[Bobr]

Αναρτήθηκε αρχικά από Virulent:

I'm right now having a similar problem with the game no longer starting in DX10 mode. Messing with the combatibility settings don't seem to work. I've tested some other older games that use DX10 like Bioshock and FarCry 2 and they all run fine. I'm guessing it was either the Win7 update or the latest Nvidia drivers that broke CS DX10.

Has anybody had any luck with getting DX10 in CS working?

One of the last updates is guilty http://support.microsoft.com/kb/2670838 . It is necessary to remove it

[DayOfTheSheep]

Hmm, I didn't have Virtualization turned on in the bios.
If anyone is still using the windows update can you please check if Virtualization is enabled and report back.

Cheers

[wisesoulhealer]

Guys removal of the file: "STALKER Clear Sky\_appdata_\user.ltx" works, there is no need to remove the new MS plarform update. Those updates, even if they cause a problem on a game or two are necessary for the safety and better behaviour of the operating system. It is the game's developers responsibility to produce patches that correct faults and bugs in their games.