Constant crashes

[Amenoso]

Is it only me or the game constantly crashes? Especially during the day-time IRL. In the evening I can get like 1 crash. But 12pm till 4pm are constant crashes (alot at my base camp)... Sometimes it's a crash with message. But in most cases it's just a screen-freeze. Where I can move and hear everything, but can't see (as the last image froze and nothing moves on the screen)

And this is only in NMS. Besides sometimes it doesn't happen at all...
I7, gtx1080,16RAM

[Azrak]

Huh. Given that it's more often during daytime it might be due to heat or (in case of a very fragile infrastructure) electricity issues?

[Amenoso]

Crashes only in NMS. No internet connection problem nor electicity issues.

If it was everywhere - I wouldn't say a thing. But this is only in NMS.

[Azrak]

Do your other games tax GPU/CPU as heavily as NMS does? Do you keep an eye on your temperatures (GPU, CPU, PSU)?

[Amenoso]

If the problem was in hardware it would crash all the time. Sometimes I play for hours without a single crash. Besides there are some threads here with the same problem and different PCs (as I found just now).

And yes - temperatures are fine. And Pc is not too stressed when I play it.

[Azrak]

Hardware problems aren't as consistent as you make them out to be, especially e.g. RAM issues. And what makes it less likely to be a NMS-related issues is the statement that it occurs mostly during the RL-day and less so in the evening/night.

Anyway, I'm out of ideas. Good luck finding a solution and if you do, post it here, please!

[Musashi]

Originally posted by Amenoso:

Is it only me or the game constantly crashes? Especially during the day-time IRL. In the evening I can get like 1 crash. But 12pm till 4pm are constant crashes (alot at my base camp)... Sometimes it's a crash with message. But in most cases it's just a screen-freeze. Where I can move and hear everything, but can't see (as the last image froze and nothing moves on the screen)

And this is only in NMS. Besides sometimes it doesn't happen at all...
I7, gtx1080,16RAM

Error codes would be helpful

You may have a look into your windows Event Viewer for more Info about that crash.
WIN+X will open that windows list, there start the Event Viewer and
expand Windows Logs and look under Application for warnings with a timestamp of that crash.

If this one shows only AppHang with unknown Reason, check the Events below of this one

[Amenoso]

Originally posted by Musashi:

Originally posted by Amenoso:

Is it only me or the game constantly crashes? Especially during the day-time IRL. In the evening I can get like 1 crash. But 12pm till 4pm are constant crashes (alot at my base camp)... Sometimes it's a crash with message. But in most cases it's just a screen-freeze. Where I can move and hear everything, but can't see (as the last image froze and nothing moves on the screen)

And this is only in NMS. Besides sometimes it doesn't happen at all...
I7, gtx1080,16RAM

Error codes would be helpful

You may have a look into your windows Event Viewer for more Info about that crash.
WIN+X will open that windows list, there start the Event Viewer and
expand Windows Logs and look under Application for warnings with a timestamp of that crash.

If this one shows only AppHang with unknown Reason, check the Events below of this one

Thnx for advice. I checked it. Every crash has got 2 Windows Error Reporting prior to it. the code is 1001 and the only common position is P1: 141.
I've checked google on this account and didn't find any usefull information. Only general: "Check this, install this, delete temp" and etc....
There was one thread in windows support with P1: 141. And they adviced uninstall all Graphics drivers with DDU and reinstall them... I'll try this one... I have already installed all the windows updates, newest graphics drivers, cleaned register and temp files... Everything i could XD Maybe there would be some temp files deleted with DDU which couldn't with WM...

Will report tommorow XD

[Amenoso]

Oh, and I also found some Errors during "sfc /scannow". They concerned update "KB3025096". It could be part of the problem, who knows.

[Ductape42]

I have the same issue. The screen will freeze, then I'll have to go to Task Manager to end the process. Also running a GTX 1080 with 16 GB RAM

[Amenoso]

Nah, all the same....

P1: 141
P2: ffffa10abb6b7050
P3: fffff8075e0260c8
P4: 0
P5: 2d08
P6: 10_0_19044
P7: 0_0
P8: 256_1
P9:
P10:

Now I will try to install windows updates for Intel which are not mandatory....

[Amenoso]

As I've read at multiple websites and threads: this is very complicated problem that concerns optimisation. But not the one we all mostly know "game <-> PC" but "game <-> windows <-> Pc". In most cases of bad optimisation - the game doesn't like PC (if we speak in children's language). But as far as "Error code 1001" is concerned, it's: The game likes PC but Windows doesn't. And Windows causes game crashes because of "who-knows-why" reasons....

I wasn't able to find any way to solve this problem.... I tried:
-checking game files for errors
-tried all tips from hellogames supprt advices
-clean drivers reinstall
-cleaning memory
- cleaning register
- checking sys and memory for errors
- updating windows.

Other people tried:
- moving to another SSD/HDD
- checking them for errors

Everywhere it says: The cause is unknown and it happens for different users and for different games.... I'll try something else but..... I don't think that it will help XD

[sstooney]

Yesterday I've updated nvidia driver for 1060(latest avaliable) and then the game has been crashing every 5 minutes, even a bluescreen occured. Rolling back to 465 version helps, but NMS suddenly crashes once an hour approx. No such problems in any other game. It looks that it's not an overheating - but only a NMS problem.

[Rexxer]

See my discussion post too. It is indeed base related. I get crashes constantly but mostly while building the base since I push walkways out to distant resources sites, then string up teleporter chains along the walkways. Always happens when I have the long but temporary walkways up, so I carry around a save point or beacon to save every few steps. Once I remove the walkways however (just using the short-range teleporters), the crashing stops.

Sudden movements, or changing zones (like entering a cuboid), seem to trigger the freeze then crash. I usually can push through the BS with constant saving an walking cables rather than running them. And I never turn sharply or jetpack while it is in this crash phase.

As mentioned....after the walkways are pulled up, relying just on the short-range teleporters, I no longer have the crashes, so it happens most right at the start of building a base for me. If you are connecting all 5 planetary resources to a base, long pathways are inevitable. Outside of that it seems nonexistant.

[Musashi]

@Amenoso

Originally posted by Amenoso:

----Sometimes it's a crash with message....

Than there may be a crashdump file, which should be in :
C:\Users\YOUR_ID\AppData\Local\Temp
(it will be called something like NMS_crashcode_xxxxxxxx.dmp)

Which you can analyze with WinDbg (Google it and download it from the Microsoft site)

But, as Rexxer did mention... if you are nearby a complex Base, it can also be the reason for a crash, also if Multiplayer is enabled can make problems.

I wonder what happens if you run NMS with Steam offline

[Amenoso]

At certain point of playing Gpu is greatly stressed for a msec and them crash.... According to logs:
STACK_TEXT:
00000067`9c4ffb90 00007ff6`3e23da01 : 00000000`00018db5 00000000`00018db5 00000067`9c4ffbf0 00000067`9c4ffbf3 : nvoglv64!vk_icdNegotiateLoaderICDInterfaceVersion+0xf6ad
00000067`9c4ffbc0 00007ff6`3e29cbcd : 00007ff6`3ebf4780 000001a7`0610a000 00000000`00000000 00000000`00000000 : NMS!AK::WriteBytesCount::SetCount+0x352861
00000067`9c4ffc10 00007ff6`3c84e556 : 00000089`9c27189b 00000000`00000000 000001a7`0610a000 00000000`00000000 : NMS!AK::WriteBytesCount::SetCount+0x3b1a2d
00000067`9c4ffcc0 00007ff6`3c84bd46 : 00007ff6`3f78f148 000001a7`0610a000 00007ff6`3ebf4780 00000000`00000000 : NMS!AK::SoundEngine::RegisterResourceMonitorCallback+0x28b6
00000067`9c4ffd00 00007ff6`3c849760 : 00000067`9c4ffda0 00000000`00000000 00000000`00000000 00007ff6`3e7d99b1 : NMS!AK::SoundEngine::RegisterResourceMonitorCallback+0xa6
00000067`9c4ffd40 00007ff6`3c850738 : 00000000`00003e19 00007ff6`3e7d9915 00007ff6`3ebee660 00000000`00003de6 : NMS!AK::WriteBytesCount::Bytes+0x14840
00000067`9c4ffd80 00007ff6`3e7d91cc : 00000000`00000001 000001a7`0610a0e0 00000000`00000000 00000067`9c211000 : NMS!AK::SoundEngine::RegisterResourceMonitorCallback+0x4a98
00000067`9c4ffdc0 00007ffc`154a7034 : 00000000`00000000 00000000`00000000 00000000`00000000 00007ffb`d8b20000 : NMS!NVSDK_NGX_VULKAN_Shutdown1+0x16093c
00000067`9c4ffe00 00007ffc`16682651 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x14
00000067`9c4ffe30 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x21


SYMBOL_NAME: nvoglv64!vk_icdNegotiateLoaderICDInterfaceVersion+f6ad

MODULE_NAME: nvoglv64

IMAGE_NAME: nvoglv64.dll

STACK_COMMAND: ~0s ; .ecxr ; kb

FAILURE_BUCKET_ID: NULL_POINTER_READ_c0000005_nvoglv64.dll!vk_icdNegotiateLoaderICDInterfaceVersion

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

IMAGE_VERSION: 30.0.14.9709

FAILURE_ID_HASH: {10654cf2-b90b-116d-e31d-c447a9202445}


As I understand the "problematic" file is "nvoglv64".... I will try to find the solution with this file in mind.....