[Combined] Game is freezing on Moon Studios startup logo animation, and closes

Coming back after the wicked together update today. Using -force-d3d12 allows me to play the game smoothly now!

Without forcing d3d12, I was crashing with the error below. I’m not sure what’s causing it but maybe the team could look into;

2026-01-22T19:07:35.058|W|15220||D3D11: Failed to create RenderTexture (1919 x 800 fmt 26 aa 1), error 0x887a0005
2026-01-22T19:07:35.058|W|15220||D3D11: Failed to create RenderTexture (1919 x 800 fmt 19 aa 1), error 0x887a0005
2026-01-22T19:07:35.058|W|15220||D3D11: Failed to create RenderTexture (1919 x 800 fmt 26 aa 1), error 0x887a0005
2026-01-22T19:07:35.058|?|15220||d3d11: failed to create staging 2D texture w=128 h=1 d3dfmt=28 [887a0005]
2026-01-22T19:07:35.058|?|15220||d3d11: failed to create staging 2D texture w=64 h=1 d3dfmt=28 [887a0005]
2026-01-22T19:07:35.058|?|15220||d3d11: failed to create staging 2D texture w=32 h=1 d3dfmt=28 [887a0005]
2026-01-22T19:07:35.058|?|15220||d3d11: failed to create staging 2D texture w=16 h=1 d3dfmt=28 [887a0005]
2026-01-22T19:07:35.058|?|15220||d3d11: failed to create staging 2D texture w=8 h=1 d3dfmt=28 [887a0005]
2026-01-22T19:07:35.058|?|15220||d3d11: failed to create staging 2D texture w=4 h=1 d3dfmt=28 [887a0005]
2026-01-22T19:07:35.058|?|15220||d3d11: failed to create staging 2D texture w=2 h=1 d3dfmt=28 [887a0005]
2026-01-22T19:07:35.058|?|15220||d3d11: failed to create staging 2D texture w=1 h=1 d3dfmt=28 [887a0005]
2026-01-22T19:07:35.060|W|29416||D3D11: Failed to create RenderTexture (3840 x 1600 fmt 27 aa 1), error 0x887a0005
2026-01-22T19:07:35.060|W|29416||D3D11: Failed to create RenderTexture (3840 x 1600 fmt 19 aa 1), error 0x887a0005

Hi, I have bought this game recently and I when I try to start the game it crashes before getting to the main menu as shown in the video in the link below.
I have also uploaded all the files you’ve asked for but there is some files such as (%USERPROFILE%\AppData\LocalLow\Moon Studios\NoRestForTheWicked\backtrace\crashpad\reports) because there is no error message when it crashes.
I have tried many solutions but nothing seems to work.
Thanks.
Link: crash - Google Drive

1 Like

Hi iu.g3,

I’m so sorry you are experiencing this incredible nasty bug.

Could you try the different fixes in this topc?

Please try the launch parameter for Steam first! (click to the link, it goes to the post) [Combined] Game is freezing on Moon Studios startup logo animation, and closes - #175 by ThomTom

Silas

I have tried all of these solution right now:
NVIDIA V-sync settings (Off / Fast).

Clean install and rollback of GPU drivers.
Uninstalling recent Windows Updates.
Deleting the DataStore / AppData folder.
Steam launch options (-skipintro, -force-d3d12, etc.)

and unfortunately, none of them worked. I need the help please.

1 Like

The most recent moon logo crash is being investigated!

Thank you everyone who provided help in the investigation!

1 Like

Hi everyone,
I’m having an issue where the game keeps crashing before it even finishes loading. As soon as I launch it, the game closes or crashes on the loading screen, and I can’t get into the main menu at all.

I’ve already tried restarting my device and relaunching the game, but the problem keeps happening. If anyone has experienced this before or knows a fix, please let me know. Any help would be appreciated!

the major problem is cant pass the moon logo it freezing on the thing on the right corner keep freezing there and i tried the solutions with xinput9_1_0 and reset my controller.

files

Thanks in advance.

1 Like

I need everyone to try something for us…This is gonna sound weird.

But please try changing your calendar to Gregorian until we work this fix in.

edit: setting it to Recommended can work as well, as has been reported by user Knz.

To do so,


1 Like

The game crashes as soon as it opens.

I leave here the files asked for bug reporting:

1 Like

Please see my post right above yours

1 Like

I’m having an issue where the game crashes or freezes before it fully loads. Every time I launch it, the game closes or gets stuck on the loading screen, and I can’t reach the main menu. I’ve already tried Steam launch options (-skipintro, -force-d3d12, etc.)and restarting my device and relaunching the game, but the issue keeps happening. The main problem is that it won’t get past the moon logo — it freezes there, with the loading icon in the bottom-right corner stuck. Also, i tried changing the calendar to Gregorian and didnt work. I really want to play the game as soon as possible and I need help.

1 Like

I have a problem: every time I launch the game, it automatically closes within the first 5 seconds of loading.

Hello everyone,

For those of you who still face the logo crash issue after the together update, I tried changing the calendar and didn’t work. I checked my player log file and it seems that the calendar is indeed the one causing the crash. I changed the regional format to recommended and now it works like magic.

I just wanted everyone facing the issue to know, maybe it could work for them as well.
Also, you can get to this screen by going to Settings → Time & Language → Language & Region and you will find it underneath the Region section.

3 Likes

it was crashing when in character creator screen. after i updated drivers/reinstalled/verified files it now crashes on startup.
reports
datastore.zip

dxdiag.txt

player.log

player-prev.log

folder has all the files.
not sure if i did the dxdiag thing correctly. let me know if i need to upload anything else

Answer:

  • Were you able to reproduce the bug? Yes, every time i start game

  • Where did it occur? During startup loading

  • Has it been reported before? i don’t know. probably. you had one about the calender recently but its not that because i use gregorian calender.

its forcing me to upload a video/screenshot but its crashing on startup so thats not helpful.

1 Like

Hi Crowned,

Can you please try the various fixes in this topic?

Silas


A user on Discord had the same problem. The -skipintro and -force-d3d12 launch options fixed it for him.

Source

1 Like

Hi team, sadly this did not work for me. it definitely affected the startup as i don’t see the logo during startup anymore but i still get the same crash on startup sadly.

1 Like

Hey everyone, can you check today and see if the latest hotfix solved the issue? We may have found and fixed the potential fault.

1 Like

hi, just tested and made sure to try all the previous solutions but still nothing sadly

1 Like

Can confirm it’s still happening, but I am using Bazzite with Proton Experimental. Tried the solution with the skip intro and d3d12 but to no avail. Removed the pfx folder for the game and the game still crashes.

2026-01-26T20:11:46.871|?|328||Input System module state changed to: Initialized.
2026-01-26T20:11:46.875|?|328||[Physics::Module] Initialized fallback backend.
2026-01-26T20:11:46.875|?|328||[Physics::Module] Id: 0xdecafbad
2026-01-26T20:11:46.877|?|328||Initialize engine version: 6000.1.15f1m1 (0)
2026-01-26T20:11:46.877|?|328||[Subsystems] Discovering subsystems at path Z:/var/mnt/g/SteamLibrary/steamapps/common/NoRestForTheWicked/NoRestForTheWicked_Data/UnitySubsystems
2026-01-26T20:11:46.877|?|328||Forcing GfxDevice: Direct3D 12
2026-01-26T20:11:46.877|?|328||GfxDevice: creating device client; kGfxThreadingModeSplitJobs
2026-01-26T20:11:47.451|?|328||d3d12: supports Tighter Alignment.
2026-01-26T20:11:47.452|?|328||d3d12: could not load DirectML.dll.
2026-01-26T20:11:47.475|?|328||Direct3D:
2026-01-26T20:11:47.475|?|328||    Version:         Direct3D 12 [level 12.1]
2026-01-26T20:11:47.475|?|328||    Renderer:        NVIDIA GeForce RTX 4090 (ID=0x2684)
2026-01-26T20:11:47.475|?|328||    Vendor:          NVIDIA
2026-01-26T20:11:47.475|?|328||    VRAM:            24564 MB
2026-01-26T20:11:47.475|?|328||    App VRAM Budget: 21819 MB
2026-01-26T20:11:47.475|?|328||    Driver:          32.0.65535.65535
2026-01-26T20:11:47.484|?|328||D3D12 MachineLearning context creation failure : null DML device.2026-01-26T20:11:47.512|?|328||[Physics::Module] Selected backend.
2026-01-26T20:11:47.512|?|328||[Physics::Module] Name: PhysX
2026-01-26T20:11:47.512|?|328||[Physics::Module] Id: 0xf2b8ea05
2026-01-26T20:11:47.512|?|328||[Physics::Module] SDK Version: 4.1.2
2026-01-26T20:11:47.512|?|328||[Physics::Module] Integration Version: 1.0.0
2026-01-26T20:11:47.512|?|328||[Physics::Module] Threading Mode: Multi-Threaded
2026-01-26T20:11:47.728|?|328||<RI> Initializing input.

2026-01-26T20:11:47.734|?|328||<RI> Input initialized.

2026-01-26T20:11:47.773|?|328||<RI> Initialized touch support.

2026-01-26T20:11:47.894|?|328||UnloadTime: 0.022700 ms
2026-01-26T20:11:48.443|I|328||

No Rest for the Wicked

  > Build Id:               26807
  > Project Revision:       144647
  > Engine Version:         Unity_6000.1.15f1_upd1017
  > Graphics API(s):        Direct3D11, Direct3D12
  > Final Build:            True
  > Development Build:      False
System Information:
  > System RAM:             31025 MB
  > CPU:                    AMD Ryzen 9 7900X 12-Core Processor, 24 cores, 4690 MHz
  > Resolution:             1920x1080
  > Graphics API:			 Direct3D12
  > Controller:             


2026-01-26T20:11:48.513|I|328||MoonDebug Initialized... Debug Allowed: False. Hidden on Boot: True
2026-01-26T20:11:48.965|I|328||WwiseUnity: Wwise(R) SDK Version 2022.1.19 Build 8584.
2026-01-26T20:11:48.966|I|328||WwiseUnity: Setting Plugin DLL path to: Z:/var/mnt/g/SteamLibrary/steamapps/common/NoRestForTheWicked/NoRestForTheWicked_Data\Plugins\x86_64
2026-01-26T20:11:51.291|I|564||First video frame not zero: 1 (0.021333s). Result may be out of sync. Please make sure tracks all start at 0 in Z:/var/mnt/g/SteamLibrary/steamapps/common/NoRestForTheWicked/NoRestForTheWicked_Data/resources.resource
2026-01-26T20:11:51.291|W|564||Color primaries 0 is unknown or unsupported by WindowsMediaFoundation. Falling back to default may result in color shift. Z:/var/mnt/g/SteamLibrary/steamapps/common/NoRestForTheWicked/NoRestForTheWicked_Data/resources.resource
2026-01-26T20:11:52.008|I|328||[SteamLogin] Gatekeeper resolved: auth=https://prod.auth.norestforthewickedbackend.net, base=https://prod.main.norestforthewickedbackend.net/, queue=https://prod.queue.norestforthewickedbackend.net
2026-01-26T20:11:52.645|I|328||[SteamLogin] Login successful: accountId=167fbe4e-8c95-4854-ac7c-67d04300cfeb
2026-01-26T20:11:53.247|E|740||Unknown error occurred while loading 'archive:/CAB-90bb0bb6feddd71d6635c161937ccdf1/CAB-18d1f016fb529ce882f9e6dc1e5f4209'.
2026-01-26T20:11:53.260|E|328||The AssetBundle 'aa\StandaloneWindows64\world_scenes_all_bde6b3d59710f75c996d636909aba81b.bundle' can't be loaded because it was not built with the right version or build target.
2026-01-26T20:11:59.696|I|328||[ViewFrame Initialization] Executing: IntroSequence.WaitForIntroSequence
2026-01-26T20:12:01.069|E|740||Unknown error occurred while loading 'archive:/CAB-90bb0bb6feddd71d6635c161937ccdf1/CAB-18d1f016fb529ce882f9e6dc1e5f4209'.
2026-01-26T20:12:01.083|E|328||The AssetBundle 'aa\StandaloneWindows64\world_scenes_all_bde6b3d59710f75c996d636909aba81b.bundle' can't be loaded because it was not built with the right version or build target.
2026-01-26T20:12:01.084|X|328||NullReferenceException: Object reference not set to an instance of an object.
  at Moon.GameSession.MainMenuFlowStage.InitializeMainMenu () [0x00000] in <00000000000000000000000000000000>:0 
  at Moon.GameSession.LoadingMainMenuFlowStage.Tick (Moon.TheLoop.ViewFrame vf) [0x00000] in <00000000000000000000000000000000>:0 
  at Moon.GameSession.UpdateClientFlow.Tick (Moon.TheLoop.ViewFrame vf) [0x00000] in <00000000000000000000000000000000>:0 
  at Sini.PlayerLoopExtensions.PlayerLoopExtensions+<>c__DisplayClass16_0.<WrapWithProfilerMarkerIfPossible>b__0 () [0x00000] in <00000000000000000000000000000000>:0 

It just flooded the logs with this displayclass exceptions and then crashed the game on startup.

[EDIT] Upon repairing the game it downloaded some additional data and now it runs without issues!

1 Like

i’ve since realised that the gpu usage spikes to 99% during the loading screen so i assume the OS is killing the application. any tips on how to solve that?