I suffered a BSOD crash, and now the game refuses to start up. I get a message saying

XR_3DA.exe caused BREAKPOINT in module "E:\GOG Games\S.T.A.L.K.E.R. Shadow of Chernobyl\bin\xrCore.dll" at 0023:0028CC85, xrDebug::backend()+165 byte(s)

I know that in theory by backing up saves and restoring I could return this to working order, but there MUST be a less annoying way to fix this. I've already have had to do it three times

3rd time Stalker has resulted in BSOD and same corruption? What OS are you running? On Win7, BSOD are becoming very rare, usually triggered by a buggy driver or some corrupted data that runs in ring-0 space.

Make sure your video drivers are up to date and that you don't have any other hardware issues like insufficient power supply or some bad RAM. Software-based memory testers are easy enough to find and use, but checking a power supply is a bit more difficult. Do you get issues like this on any other system-intensive games? Also, try running an error check against your E: drive to see if anything odd comes up.

To fix the problem at hand, I believe you can just uninstall the game and choose "no" when it gives you the choice to delete the save games. Then just re-install and you should be able to pick up where you left off.

THIS - and get your system checked as well to be sure (as ekj7 suggested).

At the moment I'm running SHOC in Windows 7 (I *could* give it a try on Wine...I don't have significant problems with any other games to date. The rig is an i7 with a GForce... whatever (don't recall which).

I knew about uninstalling and keeping the saves. I was hoping for a simpler, faster fix. Oh well :(

Have you tried adding SoC to the list of Data Exectution Prevention? - Sometimes helps with lag / stability in some games.

Instructions here: http://www.gog.com/forum/general/saints_row_3_lag_anyone_got_a_solution/post15

hi, i have a similar problem with stalker soc:

I've played the game to agroprom without any problems. But suddenly the game starts crashing when i try to reload a savegame. This means, i can start the game and load the last savegame without any issues. But if i reload the savegame (e.g. after dying), without quitting the game and go to the desktop, i get the "XR_3DA.exe-breakpoint"-crash.

This is only happening when i am reloading a savegame... the load-process after the gamelaunch dit not cause this problem.

The hint on that link above, didn't work for me.

so can anyone help me?

thanks!


edit: reinstalling did not fix the problem

Having just skimmed the Dez0wave forum (Stalker mod team) for anything, seems it might be related to patch incompatability with mods.
http://www.dezowave.com/forum/viewtopic.php?f=2&t=309&p=3681&hilit=XR_3DA.exe+breakpoint#p3681
http://www.dezowave.com/forum/viewtopic.php?f=2&t=305&p=3672&hilit=XR_3DA.exe+breakpoint#p3672

So - are you using any mods? - if so what version is your game?

Edit: also about halfway down this thread, its suggest turning off EAX - http://forums.steampowered.com/forums/showthread.php?t=2029116
Edit2: this might help also
http://forums.steampowered.com/forums/showpost.php?p=32730326&postcount=14

no i don't have any mods installed. It is the "vanilla" version from gog.com.

Deactivating EAX did not work.

The log-file says:

FATAL ERROR

[error]Expression : assertion failed
[error]Function : CInventory::DropItem
[error]File : E:\stalker\sources\trunk\xr_3da\xrGame\Inventory.cpp
[error]Line : 220
[error]Description : InSlot(pIItem)

I cleared the inventory and saved again... still crashing. I am wondering, why the file-path starts with E:\ ... i don't have any volume with that letter... it seems like one of the save-files is corrupted... older saves are working fine.

Bit odd regarding the drive / file path then. might actually be worth contacting gog support regarding the issue then.

Other than that, and the links I've provided, I suggest trying to load from the autosave from level change and go from there.

I think the link in Edit:2 details setting the no prefetch command and a few other things too (in case you missed it).

thanks for your help. I will contact the gog.com support...i think thats the easiest way :)

No worries - let us know what they say / come up woth to help.

The reference to the Inventory.cpp file is a debug aid put in there by the developers. It is not referencing any file on your hard drive, it's a reference to the source code file the devs would have used, so the path refers to the dev's hard drive.

May I ask you, what was the solution to your problem?
I have the same, and the only way through was to go from autosave into Prypiat to autosave out of it without saving at all, then I was upon the bridge. From then on I could save normally again. Weird.

steff

There are several causes of crashes to desktop in Pripyat in SoC. It would help if you have the last few lines of your log file handy just after you crash while in Pripyat. You can try to troubleshoot it that way.

Info on this can be found here.

The problem smp had is eliminated with the ZRP. I'm not sure what you experienced, Lemon_Curry, but you might want to take a look at some of the other pages at that ZRP site linked above, like the Bugs In STALKER page.

The ZRP works well enough with existing saves, although I'm not sure if you have to load the autosave for the Pripyat level to fix the problem you are having.