Departure lounge out here rapidshare. Metacognix - Crashes in the STALKER-SoC Game Crashes in SoC More useful info: Crashes still in the patched game STALKER still has a lot of issues that cause the game to exit, normally called 'Crash to Desktop' or CTD. The best way of dealing with these CTDs is to save your game often, and periodically to named saves. The ZRP has quick-named-save and safe-quicksave features that can be used for this purpose.

Lost Alpha Xr_3da.exe. Ericsson Rbs Software there. Here is problem: All.dll's required by the game (including the MSCVP and MSCVR120.dll's) are in the.

Serious Problems If your PC is shutting down or displaying a BSOD, that is more likely due to a hardware issue. (A lockup or freeze is NOT the same thing; see the next section.) PC Shutdowns If you find your PC shutting down unexpectedly, completely turning off while playing STALKER, you probably are exceeding some system specification. For example, your PC's power supply might be inadequate for supplying the required current for certain parts of the game.

BSODs If your game 'blue-screens' (BSOD - blue screen of death) and reboots: You can stop the reboot to see the specific error. In XP: Start > Control Panel > System > Advanced tab > 'Start and Recovery' Settings button > uncheck 'Automatically restart' under 'System failure'. Click OK on each dialog to exit. BSODs are usually hardware- or driver-related, although they can also be related to other issues. The error module reported on the blue screen can be useful in determining the cause of the crash.

The game is one of the best system stress tests you can run on your PC. If you are getting frequent blue screens, check cooling fans and system temperatures, and consider reducing the video load (lower quality textures and/or resolution, use DX8) and maybe even underclock your CPU and/or video card to test for possible causes.

Lockups, Freezes If your game locks up or freezes during the Synchronizing stage or while playing, this is usually due to an error that was logged but the BugTrap dialog is not visible. It traps most keystrokes and the game window stays on top, so the PC seems locked up. You can kill the game via the Windows Task Manager; in XP you can press ctrl-alt-del, alt-E, E to end the current task. You may be able to avoid most hard lockups by using the -silent_error_mode command line parameter at the end of the target line in the shortcut you use to start STALKER.

The crash might still occur, but the game will simply exit to the desktop most of the times when a crash occurs. This is recommended even if you don't have hard lockup crashes. If you still get hard lockup crashes, consider the solutions in this GSC thread: BugTrap Dialog If you see a screen talking about an error in XR_3DA.exe, it is usually the BugTrap dialog asking you to send in an error report. Don't do it; it doesn't work in STALKER SoC. Instead, find the log file (next paragraphs). Find your log file If your game crashes or locks up, look for the log file that STALKER creates before running your game again.