S.T.A.L.K.E.R.: Call of Pripyat

S.T.A.L.K.E.R.: Call of Pripyat

[CC] Black Mamba May 1, 2014 @ 6:41pm
Misery Crashes
Hey, every time I try to "Enter the Zone", my Xray engine has a core crash or something. Anyone know how to fix this or what could be causing it?
< >
Showing 1-12 of 12 comments
[CC] Black Mamba May 1, 2014 @ 6:55pm 
The exact name of the failing piece is xrCore.dll, if that narrows it down at all.
naomha May 1, 2014 @ 7:17pm 
What are your specs? One easy way to bring about a solid boot is to make sure you're playing with god rays and sun rays to minimal and full screen AA to off. Also make sure you're playing in native Hz and your screen size is the ideal size for your monitor.
Edgy Cunt May 1, 2014 @ 7:31pm 
Try reinstalling it, I used to have similar problems with crashes and loading errors. I reinstalled Misery 2.1 and it's working fine now.
warcatt00 May 2, 2014 @ 10:39am 
Originally posted by CC Black Mamba:
The exact name of the failing piece is xrCore.dll, if that narrows it down at all.

Actuly the error info from the log is what is needed, like this example below...


FATAL ERROR

[error]Expression : fatal error
[error]Function : CInifile::r_section
[error]File : E:\stalker\sources\trunk\xrCore\Xr_ini.cpp
[error]Line : 342
[error]Description : <no expression>
[error]Arguments : Can't open section 'wpn_pm'


This example shows that this crash was by this ltx file that I renamed to make this example crash. It can't find it, so it stopped and gave a reason why. This is the part that I or anyone else that understands the system would need to see.

If you only have this to show for...

stack trace:

Then its a memory dump. Which like Chris Savage said, you need to reinstall it.

This is at the very bottom of your crash log txt. Pending on your system, after a bug crash, you can get away with just pasteing in note pad off the back after.
[CC] Black Mamba May 2, 2014 @ 12:36pm 
Expression : data
Function : CVirtualFileReader::CVirtualFileReader
File : D:\prog_repository\sources\trunk\xrCore\FS.cpp
Line : 545
Description : c:\program files\steam\steamapps\common\stalker call of pripyat\gamedata\textures\item\item_flash_bump#.dds
Arguments : Not enough storage is available to process this command.


"C:\Program Files\Steam\steamapps\common\Stalker Call of Pripyat\bin\xrCore.dll" at 001B:0021E12E, xrDebug::backend()+174 byte(s)
"C:\Program Files\Steam\steamapps\common\Stalker Call of Pripyat\bin\xrCore.dll" at 001B:0020CD20, CVirtualFileRW::~CVirtualFileRW()+560 byte(s)
at 001B:72676F72
at 001B:AF17EF77
at 001B:01FEEA0A

And I have two AMD X2 Dual Core 6000+ processors.
warcatt00 May 2, 2014 @ 6:22pm 
Originally posted by CC Black Mamba:
Expression : data
Function : CVirtualFileReader::CVirtualFileReader
File : D:\prog_repository\sources\trunk\xrCore\FS.cpp
Line : 545
Description : c:\program files\steam\steamapps\common\stalker call of pripyat\gamedata\textures\item\item_flash_bump#.dds
Arguments : Not enough storage is available to process this command.

Arguments : Not enough storage is available to process this command.

Looks to me like a vmem issue, How full is your hard drive? Your vmem should be atlest about a min of 3gig for this kind of game play. Games will use about 2 of it leaving 1gig free.


gamedata\textures\item\item_flash_bump#.dds

Better than that, what is the size of this texture first?

I have the data base build unpacked from my CD version, And I am not finding this file anyware. This must be a mod texture, I can tell you this, Stalker by default is a memory eater, You can expand it untill it locks up, because it has no real boundries.

Most of the default textures are 1kb up to 342 kb, if this texture is way bigger, then trying to display that and what ever was added by the mod, such as spawns and so forth, could cause the crash.

or if the file is crupted or missing, which then like what Chris Savage said, you need to reinstall the mod.
--------------------------------------------------------------------------------------------------------------------------------------
>This was the core program working (everything in STALKER works off its own little core programs within the core)

-Function : CVirtualFileReader::CVirtualFileReader
--------------------------------------------------------------------------------------------------------------------------------
>This is the source trunk, I belive this is were the controller works out of, or retreives from.

-File : D:\prog_repository\sources\trunk\xrCore\FS.cpp
--------------------------------------------------------------------------------------------------------------------------------
>This is a script line, The file source is the script this line came from. Since it is the xrcore, it is not accessable to veiw..

-Line : 545
--------------------------------------------------------------------------------------------------------------------------------
>This is what it was doing or processing when this happend, will most likely be the Cause.

-Description : c:\program files\steam\steamapps\common\stalker call of pripyat\gamedata\textures\item\item_flash_bump#.dds (This file-->item_flash_bump#.dds)
--------------------------------------------------------------------------------------------------------------------------------
>The reason of the CTD (crash To Desktop)

-Not enough storage is available to process this command.
--------------------------------------------------------------------------------------------------------------------------------

I am kind of suprised it didn't try just bumping through auto debug so it could continue to play with out the CTD.

I hope this helps your understanding...
Last edited by warcatt00; May 2, 2014 @ 6:26pm
ArdanS May 5, 2014 @ 8:14pm 
I know misery requires that you run the X-ray engine.exe as admin. Try setting it by right clicking and going under properties.
[CC] Black Mamba May 7, 2014 @ 2:22pm 
The first one is from the Windows crash report
Problem Event Name: APPCRASH
Application Name: xrEngine.exe
Application Version: 1.6.0.2
Application Timestamp: 4b275197
Fault Module Name: xrCore.dll
Fault Module Version: 1.6.0.2
Fault Module Timestamp: 4b25fc61
Exception Code: 80000003
Exception Offset: 0001e12e
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 4105
Additional Information 1: c3fd
Additional Information 2: c3fd62fe81b1c65e85762970c6680588
Additional Information 3: 1f5f
Additional Information 4: 1f5f1e03b5fc58187a34bb38d618b63d

This one is from XRay Engine
xrEngine.exe caused BREAKPOINT in module "C:\Program Files\Steam\steamapps\common\Stalker Call of Pripyat\bin\xrCore.dll" at 001B:0021E12E, xrDebug::backend()+174 byte(s)
EAX=17CA8C60 EBX=0020FEC0 ECX=17CA8C68 EDX=17CA8DD3
ESI=002488C8 EDI=00000008 FLG=00000212
EBP=0011B8D8 ESP=0011A8D0 EIP=0021E12E
CS=001B DS=0023 SS=0023 ES=0023 FS=003B GS=0000

I also have 24 GBs of memory free, and around 2.1 GB of Video RAM
warcatt00 May 7, 2014 @ 7:23pm 
Originally posted by CC Black Mamba:
The first one is from the Windows crash report
Problem Event Name: APPCRASH
Application Name: xrEngine.exe
Application Version: 1.6.0.2
Application Timestamp: 4b275197
Fault Module Name: xrCore.dll
Fault Module Version: 1.6.0.2
Fault Module Timestamp: 4b25fc61
Exception Code: 80000003
Exception Offset: 0001e12e
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 4105
Additional Information 1: c3fd
Additional Information 2: c3fd62fe81b1c65e85762970c6680588
Additional Information 3: 1f5f
Additional Information 4: 1f5f1e03b5fc58187a34bb38d618b63d

This one is from XRay Engine
xrEngine.exe caused BREAKPOINT in module "C:\Program Files\Steam\steamapps\common\Stalker Call of Pripyat\bin\xrCore.dll" at 001B:0021E12E, xrDebug::backend()+174 byte(s)
EAX=17CA8C60 EBX=0020FEC0 ECX=17CA8C68 EDX=17CA8DD3
ESI=002488C8 EDI=00000008 FLG=00000212
EBP=0011B8D8 ESP=0011A8D0 EIP=0021E12E
CS=001B DS=0023 SS=0023 ES=0023 FS=003B GS=0000

I also have 24 GBs of memory free, and around 2.1 GB of Video RAM


Actuly the error info from the log is what is needed, Just like this example below...


FATAL ERROR

[error]Expression : fatal error
[error]Function : CInifile::r_section
[error]File : E:\stalker\sources\trunk\xrCore\Xr_ini.cpp
[error]Line : 342
[error]Description : <no expression>
[error]Arguments : Can't open section 'wpn_pm'


This example shows that this crash was by this ltx file that I renamed to make this example crash. It can't find it, so it stopped and gave a reason why. This is the part that I or anyone else that understands the system would need to see.

I need this part of the log, the other part you have is a standard crital stop log, I need the fatal error part. If it crashes on you again, try to just open note pad and click on paste if need be. It works for me all the time. Worst comes to worst, copy the whole log from top to bottom and past that so it can be veiwed.. I can't or any one else can't with out this info bro..
Last edited by warcatt00; May 7, 2014 @ 7:24pm
[CC] Black Mamba May 8, 2014 @ 3:06pm 
FATAL ERROR

[error]Expression : data
[error]Function : CVirtualFileReader::CVirtualFileReader
[error]File : D:\prog_repository\sources\trunk\xrCore\FS.cpp
[error]Line : 545
[error]Description : c:\program files\steam\steamapps\common\stalker call of pripyat\gamedata\meshes\dynamics\weapons\wpn_m4a1\wpn_m4a1_hud.ogf
[error]Arguments : Not enough storage is available to process this command.
By the not enough storage, I assume its video ram. Cause I did manage to get it to work when I turned everything to low.
warcatt00 May 8, 2014 @ 5:16pm 
Originally posted by CC Black Mamba:
FATAL ERROR

[error]Expression : data
[error]Function : CVirtualFileReader::CVirtualFileReader
[error]File : D:\prog_repository\sources\trunk\xrCore\FS.cpp
[error]Line : 545
[error]Description : c:\program files\steam\steamapps\common\stalker call of pripyat\gamedata\meshes\dynamics\weapons\wpn_m4a1\wpn_m4a1_hud.ogf
[error]Arguments : Not enough storage is available to process this command.
By the not enough storage, I assume its video ram. Cause I did manage to get it to work when I turned everything to low.

Thankyou that is the one!!! ...and very good your own, your on the right track, also props to you for the trouble shoot.

It maybe eaither system mem or the video ram, if you are spouting well over 2gigs system and a pagefile of about 4gig, it just maybe video.

This is from the readme file for the MISERY 1.0 version I have

If you experience a CTD (Crash To Desktop) with a Crash log saying:
"Not enough storage is available to process this command".
Then you will need to either turn off background music or turn your graphical settings down
as this crash is caused by the mod using too much of your system memory (RAM).
Maybe you will even have to do both to avoid the problem.

So you maybe onto something...Good job!
[CC] Black Mamba May 9, 2014 @ 12:55pm 
Alright, thanks for all the patience and help.
< >
Showing 1-12 of 12 comments
Per page: 15 30 50

Date Posted: May 1, 2014 @ 6:41pm
Posts: 12