NMS Crashes on Start up, no error code

[Mexipally]

Hey all, I just bought this game thinking it would be a cool VR experience, but I've run into this glaring issue after downloading: The game instantly crashes with no error codes. Here is what Windows Event Viewer is telling me:

Faulting application name: NMS.exe, version: 37714.0.0.0, time stamp: 0x6439a15f
Faulting module name: nvcuda64.dll, version: 31.0.15.3161, time stamp: 0x64311106
Exception code: 0xc0000409
Fault offset: 0x000000000053cfc4
Faulting process id: 0x2c8c
Faulting application start time: 0x01d971524a44f602
Faulting application path: S:\SteamLibrary\steamapps\common\No Man's Sky\Binaries\NMS.exe
Faulting module path: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_fa77e19594721328\nvcuda64.dll
Report Id: 3f9524a2-263d-4a14-9b66-f6d602fbd81e
Faulting package full name:
Faulting package-relative application ID:

I've also tried redownloading the game, running it as administrator, changing it to windowless/borderless in the graphics settings, and I've updated my GPU. Any help is appreciated!

[Musashi]

that Exception code: 0xc0000409 is known because of Overwolf and Reshade
and if you have NMS not excluded in SentinelOne (Antivir)
But there is still that <Data>nvcuda64.dll</Data> .. which is not normal...
I dont know what CUDA is .. you wrote you did have it installed .. maybe its not fully uninstalled .. maybe there is still a folder ..

I have no Idea and my Pillow is calling .. be back tomorrow

[Mexipally]

Originally posted by Musashi:

that Exception code: 0xc0000409 is known because of Overwolf and Reshade
and if you have NMS not excluded in SentinelOne (Antivir)
But there is still that <Data>nvcuda64.dll</Data> .. which is not normal...
I dont know what CUDA is .. you wrote you did have it installed .. maybe its not fully uninstalled .. maybe there is still a folder ..

I have no Idea and my Pillow is calling .. be back tomorrow

Thanks a bunch for your help! I'll get to scouring my C drive for any missing overlay programs. You've been a great help!

[voidCaster]

Originally posted by tekmunkey:

Originally posted by Mexipally:

Well, something different DID happen: Before, it would load up a bordered window that was white and said "No Man's Sky". NOW, it's a black screen that says nothing, is in full screen mode, and crashes with no errors (this is with and without running it in admin mode).

Did you ever try running sfc /scannow from an elevated command prompt?

@Mexipally: I don't know if you saw this or not while working with Musashi.

0xc0000409 is a STACK OVERFLOW EXCEPTION (unrelated to Google's crappy webforums). Stack overflow means an attempt was made to access memory addresses which the application does not have permissions to access.

If you websearch that exception code, the first 20 hits all suggest SFC /SCANNOW. The reason has to do with corrupted files in the operating system.

I originally assumed you had already done this before coming to the forum, but then I noticed your thread title is "no error code" so I figured you didn't know there actually is one.

[DEDloc_©]

Originally posted by tekmunkey:

Originally posted by tekmunkey:

Did you ever try running sfc /scannow from an elevated command prompt?

@Mexipally: I don't know if you saw this or not while working with Musashi.

0xc0000409 is a STACK OVERFLOW EXCEPTION (unrelated to Google's crappy webforums). Stack overflow means an attempt was made to access memory addresses which the application does not have permissions to access.

If you websearch that exception code, the first 20 hits all suggest SFC /SCANNOW. The reason has to do with corrupted files in the operating system.

I originally assumed you had already done this before coming to the forum, but then I noticed your thread title is "no error code" so I figured you didn't know there actually is one.

I have to agree. The only person I can find on google who actually fixed this... he just reloaded windows, so yeah, the sfc/scannow thing might be the ticket.

I KNOW that nvcuda64 entry isn't what it's supposed to be doing. Should be using nvogl64. As I understand the cuda file is related mostly to PhysX which NMS doesn't even use, so....

[voidCaster]

Originally posted by DEDloc_©:

I KNOW that nvcuda64 entry isn't what it's supposed to be doing. Should be using nvogl64. As I understand the cuda file is related mostly to PhysX which NMS doesn't even use, so....

CUDA is an acronym identifying the architecture of the processing units embedded in the GFX card. OP has an nVidia card and so far as I know only Intel and nVidia use CUDA processors, so it makes sense. Every bit of data processed by that GFX card is processed by a CUDA core, the same way that every bit of data on an Intel Pentium Core i5 or i7 is processed by a Nehalem core (or was in the first generation of Core i<whatever>).

Any game makes calls to Direct-X or OpenGL or whatever library which interacts with WIndows which interacts with the hardware driver.

I don't know what filename you're thinking of, but I doubt it's the same one mentioned by the OP.

[DEDloc_©]

Originally posted by tekmunkey:

Originally posted by DEDloc_©:

I KNOW that nvcuda64 entry isn't what it's supposed to be doing. Should be using nvogl64. As I understand the cuda file is related mostly to PhysX which NMS doesn't even use, so....

CUDA is an acronym identifying the architecture of the processing units embedded in the GFX card. OP has an nVidia card and so far as I know only Intel and nVidia use CUDA processors, so it makes sense. Every bit of data processed by that GFX card is processed by a CUDA core, the same way that every bit of data on an Intel Pentium Core i5 or i7 is processed by a Nehalem core (or was in the first generation of Core i<whatever>).

Any game makes calls to Direct-X or OpenGL or whatever library which interacts with WIndows which interacts with the hardware driver.

I don't know what filename you're thinking of, but I doubt it's the same one mentioned by the OP.

I know all that. I'm talking about the .dll file it's using. Every single installation I have seen uses nvogl64.dll...... NOT nvcuda64.dll. I am definitely guessing when I say it is probably used more for stream computing and such and apparently in games it is used for PhysX, but primarily speaking, NMS shouldn't be using it AT ALL.
I hope that's more clear for you.

Also if you read his error report, it in fact does name nvcuda.dll as the offending package.

[voidCaster]

Originally posted by DEDloc_©:

Originally posted by tekmunkey:

Any game makes calls to Direct-X or OpenGL or whatever library which interacts with WIndows which interacts with the hardware driver.

I know all that. I'm talking about the .dll file it's using. Every single installation I have seen uses nvogl64.dll...... NOT nvcuda64.dll. I am definitely guessing when I say it is probably used more for stream computing and such and apparently in games it is used for PhysX, but primarily speaking, NMS shouldn't be using it AT ALL.
I hope that's more clear for you.

Also if you read his error report, it in fact does name nvcuda.dll as the offending package.

OpenGL or DirectX to CUDA interface... nvCUDA64.dll or nvOGL64.dll... hmmmm. What a massive, quivering mystery!!!

[voidCaster]

@Mexipally: Since this spilled over onto a 2nd page and I have no idea how much of the drivel you'll read back through: Try SFC /SCANNOW from an elevated command prompt before you do anything drastic, like somebody mentioned reinstalling Windows.

[Musashi]

Did read again your crash_dump_file
Looks like its trying to load
Image path: S:\SteamLibrary\steamapps\common\No Man's Sky\Binaries\vulkan-1.dll
Actually you can delete that dll in that folder...
should be normally in C:\Windows\System32\vulkan-1.dll
you may search on C drive for vulkan-1.dll .. if it is in C:\Windows\System32 it should be ok

[Mexipally]

Originally posted by tekmunkey:

Originally posted by tekmunkey:

Did you ever try running sfc /scannow from an elevated command prompt?

@Mexipally: I don't know if you saw this or not while working with Musashi.

0xc0000409 is a STACK OVERFLOW EXCEPTION (unrelated to Google's crappy webforums). Stack overflow means an attempt was made to access memory addresses which the application does not have permissions to access.

If you websearch that exception code, the first 20 hits all suggest SFC /SCANNOW. The reason has to do with corrupted files in the operating system.

I originally assumed you had already done this before coming to the forum, but then I noticed your thread title is "no error code" so I figured you didn't know there actually is one.

I did actually miss this, so I ran the sfc /scannow in cmd prompt as an admin also ran a memory test last night. Both came back with no errors. I'm back to this error coming back every time I run NMS (as admin and non-admin) so atleast that's neat! I feel like I borked my computer somehow.

https://imgur.com/a/6zYly9L

I also had AutoCAD by AutoDesk installed. I went through and cleanly uninstalled this as it had a background process that would check if you had registered software. It's uninstalled, I removed all files, even went into the registry and deleted files there just to be sure. From doing that whole process, I found files lingering from Overwolf, OBS, Twitch, Riva Statistics, and MSI Afterburner in my C:Program Files, C:Programfiles(x86), C:AppData, C:ProgramData, %localdata% , %tempdata% folders, and lastly the registry. Those are all gone now

Now I'm not getting a screen or anything when I boot NMS, the game just freezes and doesn't do anything.

[voidCaster]

Originally posted by Mexipally:

Now I'm not getting a screen or anything when I boot NMS, the game just freezes and doesn't do anything.

When you check your event viewer after a game crash, is there a new Exception Code or is it still 0xc0000409?

[voidCaster]

Originally posted by Musashi:

Did read again your crash_dump_file
Looks like its trying to load
Image path: S:\SteamLibrary\steamapps\common\No Man's Sky\Binaries\vulkan-1.dll
Actually you can delete that dll in that folder...
should be normally in C:\Windows\System32\vulkan-1.dll
you may search on C drive for vulkan-1.dll .. if it is in C:\Windows\System32 it should be ok

Well that is weird, isn't it? OP has an nVidia Card but Vulkan is a Radeon feature.

[DEDloc_©]

Vulkan is definitely NOT a radeon feature.
Anyway, Now that you have your system better sorted, I would think trying one more clean install of drivers might be the ticket. Consider reinstalling NMS too if you have the bandwidth (backup your game files first). It sounds like you really got it cleaned, so hopefully it will have better results. You can also try reinstalling Vulkan from https://vulkan.lunarg.com/sdk/home ....just get the runtime and install it though you shouldn't need it since it should be included with the NV drivers.
Oh, and I wasn't suggesting you just reinstall windows, sorry if it came across that way.

[Musashi]

No Vulkan drivers are available for NVIDIA and AMD graphics products

[Musashi]

@Mexipally
Did you delete that vulkan-1.dll in

You may upload your crashdump file , so I can download it and check it
S:\SteamLibrary\steamapps\common\No Man's Sky\Binaries\
For Registrie Cleaning I use CCleaner ... the free Version... you need to run it several times in a row until it does not found anything more...
https://www.ccleaner.com/ccleaner/download