#[1.55.5] unexpected loading error 17

1 messages ยท Page 1 of 1 (latest)

lament lagoon
raw arrow
#

That's "game files corrupted". Please start with verifying game integrity.

lament lagoon
raw arrow
#

Looking at the logs, it seems that you run out of the memory when loading your game. Please quit other applications, or just reboot your system and try again.

lament lagoon
raw arrow
#

Let me get you the line from the logs.

#
ERROR: Condition "!mem" is true. Returned: nullptr
   at: Memory::alloc_static (core\os\memory.cpp:77) - Condition "!mem" is true. Returned: nullptr
WARNING: png_image_finish_read: invalid argument
lament lagoon
raw arrow
#

this is the most important part on the top of the logs; the game requested memory from your OS, and didn't get any.

lament lagoon
# lament lagoon

Here you see the spike, in my memory, it did not reach over 80% if that

raw arrow
lament lagoon
#

Is there any way to fix that?

raw arrow
#

Please quit other applications, or just reboot your system and try again.

#

If that doesn't help, get me another log dump after reboot, we'll see what I can figure out from there.

lament lagoon
#

I just boosted my PC up today again, so I will see

#

My GPU now

#

Let's see if it works properly

raw arrow
#

Again, the error was for your RAM, not VRAM. This chart does not show that.

#

you want to look at this one:

lament lagoon
#

Seems to work now

#

I did nothing different from yesterday tho

#

That is why I say it seems semi random

raw arrow
#

you probably had your memory used up by other software

lament lagoon
#

As I said I had the exact same things open yesterday as today

raw arrow
#

your logs show several instances of game requesting memory and getting denied by your OS; this usually means that all your memory is used up with some other software.

lament lagoon
#

Lemme test a few things in game to see what happens memory wise

lament lagoon
#

Context, just got done with a dive, returned back home, as the ship was autopilot, it crashed.

#

It went well all day, and when it happens once, it keeps happening until I restart my PC.

#

Tried to hop into the simulation to test a setting I changed in tuning, and it crashed once more

raw arrow
#

Is this still about the loading of the game, or was that meant for #1283884004734668884 ?

#

[1.55.5] unexpected loading error 17

#

Anyway, here are relevant parts of the logs:

ERROR: Condition "status != 0x8CD5" is true.
   at: RasterizerStorageGLES3::_render_target_allocate (drivers\gles3\rasterizer_storage_gles3.cpp:7271) - Condition "status != 0x8CD5" is true.
ERROR: Condition "!mem" is true. Returned: nullptr
   at: Memory::alloc_static (core\os\memory.cpp:77) - Condition "!mem" is true. Returned: nullptr

and

ERROR: Condition "status != 0x8CD5" is true.
   at: RasterizerStorageGLES3::_render_target_allocate (drivers\gles3\rasterizer_storage_gles3.cpp:7122) - Condition "status != 0x8CD5" is true.
ERROR: Condition "status != 0x8CD5" is true.
   at: RasterizerStorageGLES3::_render_target_allocate (drivers\gles3\rasterizer_storage_gles3.cpp:7122) - Condition "status != 0x8CD5" is true.

both of which means "game asked OS for memory and OS didn't give it that memory".

If you are positive that your system has sufficient memory to run, you might be hitting an OpenGL driver bug. Please take a look at https://delta-v.kodera.pl/index.php/Troubleshooting for some common solutions - the fist thing I suggest trying is to check for corrupted system/driver files using the windows filechecking tool with sfc /scannow

lament lagoon
#

I'll try that, thank you.

lament lagoon
raw arrow
#

I mean I see calls to "give me memory" and your system saying "no"

There might be other causes for this to happen, but that is a root cause. If the game asks for memory and doesn't get it, it can't really do anything other than crash. It can't even display nice custom message, because it doesn't get the memory to do that.

lament lagoon
#

I see. I tried the sfc command, and it did not find any integrity violations

torn adder
#

Your image does show you being low on memory.
The graph might not look it, but the numbers do.

Also, this is rare nova days, as people generally have stopped fiddling with it, but technically still a thing - is it possible for the memory issue to be related to the size (and managing) of the Windows page file?
Perhaps worth checking the settings there, to make sure it is not set too small or turned off for some reason, if everything else seems exhausted.

azure meadow
torn adder
#

Ah sorry, did a dumb.

lament lagoon
#

I am just confused, I tried everything, I can go for hours, sometimes days, and suddenly it happens, and once it happens, it keept happening till I restart my PC

#

I will continue monitoring, I believe it could be that my RAM is faulty? Although I haven't observed this happening to any of the other games I play, which is the confusing part

#

Because if it was indeed my RAM being faulty, surely it would happen elsewere as well, right?

azure meadow
#

Faulty RAM usually shows itself in form of spurious crashes, but afaik without generating explicit "Out of RAM" errors. Basically the game or any other program would write something to memory, then when it later wants to retrieve it, one or more bits have been flipped. This can cause all sorts of strange issues, usually the kind that brings a program into an unrecoverable state.

A way to check the RAM is to run memtest86+ (https://en.wikipedia.org/wiki/MemTest86). Leave it running for as long as possible, ideally hours or a full day. The longer it runs without errors, the more confident you can be that your RAM is error free.