Freezing then crashing Subnautica
EmmettTheDestroyer
Join Date: 2017-01-07 Member: 226306Members
Join Date: 2017-01-07 Member: 226306Members
When I first started playing Subnautica everything was fine... Then I got the seaglide and the game would crash at random without warning. I would just be strolling around then suddenly everything freezes, the audio keeps playing and then after a bit it would crash. It was bearable. Now I have the seamoth and I'll be going full speed but then it freezes with the audio still playing, and then the game crashes and says this:
Oops!
The game crashed.
The crash report folder named "2017-01-07_102850" next to game
executable.
It would be great if you'd send it to the developer of the game!
What can I do to stop this from happening?
Edit: Here is part of the crash file: Unity Player [version: Unity 5.4.3f1_01f4c123905a]
Subnautica.exe caused an Access Violation (0xc0000005)
in module Subnautica.exe at 0033:32cab41a.
Error occurred at 2017-01-07_103410.
\SteamLibrary\steamapps\common\Subnautica\Subnautica.exe, run by ***********.
64% memory in use.
8045 MB physical memory [2885 MB free].
9965 MB paging file [3136 MB free].
134217728 MB user address space [134214513 MB free].
Read from location a657b378 caused an access violation.
Context:
RDI: 0xc48fabc0 RSI: 0x00002a4c RAX: 0xa657b330
RBX: 0x00000014 RCX: 0x2ce881d0 RDX: 0xc48fabc0
RIP: 0x32cab41a RBP: 0x886440b0 SegCs: 0x00000033
EFlags: 0x00010246 RSP: 0x0035ee10 SegSs: 0x0000002b
R8: 0x00000000 R9: 0x00000000 R10: 0x00000000
R11: 0x0035ee08 R12: 0xad7b20b0 R13: 0x2ce881d0
R14: 0xc48fabc0 R15: 0x00000000
Oops!
The game crashed.
The crash report folder named "2017-01-07_102850" next to game
executable.
It would be great if you'd send it to the developer of the game!
What can I do to stop this from happening?
Edit: Here is part of the crash file: Unity Player [version: Unity 5.4.3f1_01f4c123905a]
Subnautica.exe caused an Access Violation (0xc0000005)
in module Subnautica.exe at 0033:32cab41a.
Error occurred at 2017-01-07_103410.
\SteamLibrary\steamapps\common\Subnautica\Subnautica.exe, run by ***********.64% memory in use.
8045 MB physical memory [2885 MB free].
9965 MB paging file [3136 MB free].
134217728 MB user address space [134214513 MB free].
Read from location a657b378 caused an access violation.
Context:
RDI: 0xc48fabc0 RSI: 0x00002a4c RAX: 0xa657b330
RBX: 0x00000014 RCX: 0x2ce881d0 RDX: 0xc48fabc0
RIP: 0x32cab41a RBP: 0x886440b0 SegCs: 0x00000033
EFlags: 0x00010246 RSP: 0x0035ee10 SegSs: 0x0000002b
R8: 0x00000000 R9: 0x00000000 R10: 0x00000000
R11: 0x0035ee08 R12: 0xad7b20b0 R13: 0x2ce881d0
R14: 0xc48fabc0 R15: 0x00000000
Comments
How do I clean my cache? I couldn't get all of that sorry
http://forums.unknownworlds.com/discussion/147508/bug-wrecks-stacking-in-the-same-location-version-42313#latest
Short: When saving wrecks and vines spawn multiple times in the same location. When changing biome it can crash your game.
This is also a main reason for fps drops.
This way I also get a ton of lag with my GTX 1060 after around 2 hours of gameplay.
But I get lags when I am nowhere near a wreck (or at least it's not in sight).
1. Open steam and go to your library
2. Right-click Subnautica then select properties
3. From there click local files and then Browse Local Files
4. Then select the folder named SNAppData
5. Go to the folder named SavedGames
6. Select the folder for the saved game that keeps crashing for example, mine was Slot000
7. Then delete the folders CompiledOctreesCache and CellsCache. These should be the top two folders
This is how you clear your cache. Keep in mind this will set all the terrain back to it's original form. So if you were doing any terraforming this will undo it. Also all quarts, titanium, anything you pick up will be reset along with fragments. So if you made t through the precursor mountain island base, you'd have to start over collecting the artifacts. After doing this my game functioned normally with the usual amount of lag, which is very little.
Hope this helps!
For those that care, the cause of this bug (terrain modification/saving) is quite stagnant right now due to the fact it is in the process of being removed from the game. Once that happens, we will hopefully not see this problem again.