Game Crash on Startup - Windows Event Logs

[adamthestudly]

Hey everybody who is having this same startup problem -- can you check your Windows Event Viewer Logs (Start Menu -> type Event Viewer, then select Windows Logs, Application)

In there there are several Error messages that pop up for No Man's Sky, the main one for me is:

"Windows cannot access the file for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program No Man's Sky because of this error."

Is this the same for everybody else, or are you all having other errors? I'm not a dev, but I really want this thing to work because it looks fun. I can post my full error message info if it will help too.

[ByteRyder]

I'm getting that message as well

[Ziegenbagel]

this is what mine says: Hope Devs see and it helps...

Faulting application name: NMS.exe, version: 0.1.0.0, time stamp: 0x57ade3e9
Faulting module name: ntdll.dll, version: 10.0.10586.306, time stamp: 0x571af2eb
Exception code: 0xc0000005
Fault offset: 0x000000000001525b
Faulting process id: 0x10f8
Faulting application start time: 0x01d1f4c99fafb92a
Faulting application path: C:\SteamLibrary\steamapps\common\No Man's Sky\Binaries\NMS.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 834529b7-24c0-47e6-ac88-8068490708b7
Faulting package full name:
Faulting package-relative application ID:

[adamthestudly]

Yes, Ziegenbagel...I have that message too.

[clay408]

My screen turns black for a quarter second and then nothing.

[JizzCasso]

Same message here too

[Phoenix027]

Both the messages posted before me are showing up on my machine too. I have AMD CPU 6 core, 16GB Ripjaws ram, 760 GTX NVidia, tons of hard drive space on Western Digital 2TB Black, Windows 10, all updates. Game installed on drive D (where all my steam games are). Hope to see a hotfix soon. Crashes at "Hello Games" screen.

[MycroftCanadaNS]

adamthestudly původně napsal:

Hey everybody who is having this same startup problem -- can you check your Windows Event Viewer Logs (Start Menu -> type Event Viewer, then select Windows Logs, Application)

In there there are several Error messages that pop up for No Man's Sky, the main one for me is:

"Windows cannot access the file for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program No Man's Sky because of this error."

Is this the same for everybody else, or are you all having other errors? I'm not a dev, but I really want this thing to work because it looks fun. I can post my full error message info if it will help too.

That is the problem I am having...

Windows cannot access the file for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program No Man's Sky because of this error.

I have the game installed on my SSD, and it has crashed, I then uninstalled the game, and installed in on other drive, still crashed with the same issue.

[Riu]

Same msgs here too

[wisthler]

I have both messages too

[JUNKERPRIME]

This is what I'm getting as well.

[Nabospatos]

same

[Danny32797]

same

[VDmitry]

same

[Proxy.]

I have the same problem.

[Thumper]

Faulting application name: NMS.exe, version: 0.1.0.0, time stamp: 0x57ade3e9
Faulting module name: NMS.exe, version: 0.1.0.0, time stamp: 0x57ade3e9
Exception code: 0xc0000409
Fault offset: 0x0000000000e4a380
Faulting process id: 0x1d48
Faulting application start time: 0x01d1f4cf52a4f61d
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\No Man's Sky\Binaries\NMS.exe
Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\No Man's Sky\Binaries\NMS.exe
Report Id: b8d4bf8e-f887-4476-b740-2d20d3e1f399
Faulting package full name:
Faulting package-relative application ID: