After this update, I once again cannot enter the game. It’s the same issue as before—it only shows “Moon Studios,” then the screen goes black and the game exits without any other error messages.
*After the recent update, I’m once again unable to launch the game—the same issue as before. It only shows the ‘Moon Studios’ logo, then crashes to a black screen without any error messages. This problem had been fixed in a previous update, but now it’s recurring. Please refer to this thread for context:
I can not enter the game - Wicked Bug Reporting - No Rest For The Wicked
Previously, I had already updated my drivers, verified the integrity of game files through Steam, and confirmed that the DLL and VC++ runtime files were all functioning properly. Moreover, I was able to run this game without issues back in February.
Below is the .dmp file analysis from WinDbg Preview:
-
* -
Exception Analysis * -
*
*** WARNING: Unable to verify checksum for GameAssembly.dll
*** WARNING: Unable to verify checksum for NoRestForTheWicked.exe
*** WARNING: Unable to verify checksum for KERNEL32.DLL
*** WARNING: Unable to verify checksum for USER32.dll
*** WARNING: Unable to verify checksum for ole32.dll
*** WARNING: Unable to verify checksum for KERNELBASE.dll
*** WARNING: Unable to verify checksum for BacktraceCrashpadWindows.dll
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 15
Key : Analysis.Elapsed.mSec
Value: 417804
Key : Analysis.IO.Other.Mb
Value: 27
Key : Analysis.IO.Read.Mb
Value: 1
Key : Analysis.IO.Write.Mb
Value: 47
Key : Analysis.Init.CPU.mSec
Value: 15
Key : Analysis.Init.Elapsed.mSec
Value: 252018
Key : Analysis.Memory.CommitPeak.Mb
Value: 444
Key : Analysis.Version.DbgEng
Value: 10.0.27829.1001
Key : Analysis.Version.Description
Value: 10.2503.24.01 amd64fre
Key : Analysis.Version.Ext
Value: 1.2503.24.1
Key : Failure.Bucket
Value: ILLEGAL_INSTRUCTION_c000001d_UnityPlayer.dll!Unknown
Key : Failure.Exception.Code
Value: 0xc000001d
Key : Failure.Exception.IP.Address
Value: 0x7ffcb716e110
Key : Failure.Exception.IP.Module
Value: UnityPlayer
Key : Failure.Exception.IP.Offset
Value: 0x54e110
Key : Failure.Hash
Value: {7cd781bd-17c8-0ea0-167d-fdc8bdb44ad2}
Key : Failure.ProblemClass.Primary
Value: ILLEGAL_INSTRUCTION
Key : Timeline.Process.Start.DeltaSec
Value: 18
Key : WER.Process.Version
Value: 2022.3.31.0
FILE_IN_CAB: 0ca3a7d9-2156-4397-aed2-ac4d8e120f63.dmp
NTGLOBALFLAG: 0
CONTEXT: (.ecxr)
rax=0000025c81fbf580 rbx=0000025bd000002c rcx=0000025c81fbf580
rdx=0000025c81fbf6c0 rsi=0000000000000001 rdi=0000025b201f4be0
rip=00007ffcb716e110 rsp=000000b6542edc90 rbp=00000000000006c5
r8=0000025c81fbf680 r9=0000025b7111c850 r10=0000025c81fbf580
r11=000000b6542edc88 r12=0000000000000000 r13=000000000000002d
r14=0000025b7111c850 r15=0000025c81fbf580
iopl=0 nv up ei pl nz na pe nc
cs=0033 ss=0000 ds=0000 es=0000 fs=0053 gs=002b efl=00010202
UnityPlayer+0x54e110:
00007ffc`b716e110 c4627913d8 vcvtph2ps xmm11,xmm0
Resetting default scope
EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 00007ffcb716e110 (UnityPlayer+0x000000000054e110)
ExceptionCode: c000001d (Illegal instruction)
ExceptionFlags: 00000000
NumberParameters: 0
PROCESS_NAME: NoRestForTheWicked.exe
ERROR_CODE: (NTSTATUS) 0xc000001d - { }
EXCEPTION_CODE_STR: c000001d
Here are the relevant files you requested. Please review them.
I genuinely love this game and I’m eager to play it as soon as possible. However, this is already the second time during Early Access that I’ve been unable to launch the game after an update. I don’t know if you can permanently resolve this issue, but it’s extremely frustrating. I have to say this has significantly diminished my excitement for the game. While I truly enjoy it, But, if this problem persists, I may have to seriously consider requesting a refund
Greetings.
I am here on behalf of friends because I still do not download the Breach update out of fear or instability or potential bugs.
There are people reporting about crashing to desktop after the Moon Studio logo opening and black loading screen with spinning red orb with the new Breach update. They mentioned about access violation related to UnityPlayer.dll in their Player.log and there was nothing else. The access violation related to UnityPlayer.dll was the only error logged by the game before it crashed to desktop. According to them, verifying the game files did not help because Steam did not download or replace anything. Removing the game by uninstalling it and then reinstalling the game did not help either.
I cannot mention anything else other than what my friends have mentioned to me because I still do not update my game yet. And judging by many posts in Steam forums, I think I better keep my game as is and prevent Steam from updating it. I am still with the previous version and I can run my game normally and there was no error recorded in the log or crash to desktop.
Examples from Steam forums:
Game crashing when loading main menu – RX 580 + Media Foundation
As I have mentioned, I do not have the Breach update so I cannot test the issue myself, but please take a look at the issue those people are having after they installed the Breach update.
Thank you very much for the help.
1 Like
i moved your report and files here, where we have all the others collected already 
After a day of working with AI, I finally identified the issue: the game requires the AVX instruction set, but my BIOS had AVX disabled. As a result, when the game launched and detected no AVX support, it immediately crashed. I entered the BIOS, enabled AVX, and now the game launches normally. I hope this solution helps others facing the same problem!
2 Likes
Still no luck here running the game, with today’s hotfix.
And i have AVX enabled
1 Like
You were wrong. My post had nothing to do with this thread because this thread is for people who were suffering crashes to desktop after Moon Studio logo since long before the Breach update and they are still suffering from the same crashes today.
My post is about users or players (my friends) who cannot open the main menu anymore after they downloaded and installed the Breach update, which means none of my friends whom my post was made on behalf of suffered any crash to desktop before they have the Breach update which was released recently. Their logs showing errors with exception and memory violation related to UnityPlayer.dll also occurred after they installed the problematic Breach update, not before like all people in this thread.
The crashes is tied exclusively to the Breach update because after I gave my copy of the game, which is the version before the Breach update (I did not download or install the update because it is problematic) to them they could run the game again without any crash or error related to any of the game files or data. The only thing they always need to do now is to open or run Steam first and then run the game by opening the game .exe file because if they run the game through Steam, Steam will ask them to update their game first before they can play.
I was also going to post to ask the developers about why the crucible legacy version of the game is not available to download on Steam despite the claims from some people that the crucible legacy version is made available for people who still want to play the version of the game without or before the Breach update. This is the reason why I offered my copy of the game to my friends so they can continue playing the game now without have to worry about the problematic Breach update because now is holiday period for us Japanese. Yet my thread was locked.
My apologies, I mean no offense, but my post which was incorrectly moved to this thread had nothing to do with AVX instruction set. I am here on behalf of my friends who do not have an account in this forum to report about issues. They did not have any problem with AVX instruction set because otherwise they would not be able to play Clair Obscur: Expedition 33 with the same PC now or played No Rest for the Wicked often with the Crucible update before the problematic Breach update was released and they installed it.
My friends could play No Rest for the Wicked without any crash to desktop before they installed the Breach update, and they played very often and only suffered constant crash to desktop after the Moon Studio logo recently after they installed the problematic update, so unfortunately whatever the issue that people have in this thread may not have anything to do with my friends.
1 Like
there are a lot of reports here with different setups, but all have the same issue, the crash after the moon logo, so they can not enter the main menu. the bio that had AVX disabled was 1 person out of multiple. And all of them were quite helpful with sharing logfiles, etc.
i just try to keep things together. we collect them by how the bug or error presents.
when we have 1 thread for each individual “after moon logo crash”, then each of them gets burried somewhere within the 160 new posts and thread per day. i am pretty sure it is NOT in the interest of your friend, to have a separate post somewhere beneath all those new reports. that does not help anyone.
and it does not help the team either. when we keep all in one place to collect logfiles etc, they do not have to click though 50 threads but can download and receive all necessary information in just one.
don’t u think that is a good thing?
A second patch of fixes has already been released. And we are still waiting for the departure to be fixed after the logo.
1 Like
No, it is not a good thing. My apologies if this sounds impolite but you do not know my friends. You were only assuming or thinking that you are pretty sure about my friends’ interest while in fact, you were completely wrong about my friends and their interests.
It was them who asked me to create a new thread in either the Bug Report section or Feedback section about the crash to desktop after Moon Studio logo because this issue occurrs only and only after the Breach update, not before.
My friends and I, all of us were already knew the existence of this thread, and none of them had any crash to desktop after the Moon Studio logo before they installed the Breach update. None of the issues or solutions posted here worked for any of us with the issue of crashing to desktop caused by the Breach update. That was why I did not post a feedback in this thread. Like I mentioned, you were only assuming. Please read again all my posts before assuming you know or sure about something, because the more you claim, the more you prove you are wrong.
My thread about the crash to desktop after the Moon Studio logo issue is occurred only and only after the Breach update, and that is why my thread or post is a feedback exclusive to the Breach update to raise the awareness to the developers about the crash to desktop issue that my friends are experiencing after they installed the Breach update. I mention this again, none of my friends had any crash to desktop before the main menu appears prior to installing the Breach update.
My thread was and is still a feedback exclusive to the Breach update directed to the developers, and it was requested specifically by my friends, who do not have accounts here. That was why it was posted in Feedback section and not the Bug Report section and not in this thread either, even though the exception or access violation related to UnityPlayer.dll may be a bug or a mistake on the developers’ end. I repeat this again, none of my friends had any crash to desktop, related to UnityPlayer.dll or anything else, prior to installing the Breach update.
Hi! Throws it out of the game after the update, I have not seen such problems before.
If you are in the main menu game, nothing happens. As soon as you enter the game mode directly, either immediately or after 5-10 minutes it throws it on the desktop without any messages. According to the dumps, he seemed to swear at the beginning on BacktraceCrashpadWindows.dll , i update Windows . Now he swears at fsr2-unity-plugin.dll . On the video card, the RSR turned it off and on. The result is the same.
I am attaching files for analysis.
Hello. Could you tell me if any of the developers have seen our dmp files? Is there any way to solve these problems? Will there be an attempt to help me and people like me in the near future?
3 Likes
A new patch, but the problem is the same.
Will there be a decision?
At the very beginning, when the game came out, everything worked fine.
Then the update and everything broke…
1 Like
As of the most recent (Breach) update, the game no longer runs on my computer; the Moon Studios logo comes up, and then the game crashes to desktop. I was previously able to play on an old AMD graphics card, without issue, but took a break to wait for the next update. In the interim, I swapped out the graphics card for a NVIDIA 4060, so I suspect the crash is related to that.
I can confirm I updated to latest graphics drivers, reinstalled, and verified the integrity of the files. I’ve modified V-sync to fast/off, to no avail. I also had the same crash when I switched to use the legacy version.
I took a quick look at the .dmp file and can confirm there’s an exception there:
FAILED_INSTRUCTION_ADDRESS:
UnityPlayer+54e110
00007ffc`1c0ae110 c4627913d8 vcvtph2ps xmm11,xmm0
SYMBOL_NAME: UnityPlayer+54e110
MODULE_NAME: UnityPlayer
IMAGE_NAME: UnityPlayer.dll
FAILURE_BUCKET_ID: ILLEGAL_INSTRUCTION_c000001d_UnityPlayer.dll!Unknown
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
IMAGE_VERSION: 2022.3.31.0
FAILURE_ID_HASH: {7cd781bd-17c8-0ea0-167d-fdc8bdb44ad2}
Followup: MachineOwner
All requested data is here:
https://drive.google.com/drive/folders/1Huy2kbmlfd5g15hCUPscPeXGC3PjPHK4?usp=sharing
1 Like
Возможные причины
- Проблема с Crashpad:
- Система создания дампов аварийных завершений сама дала сбой.
- Возможно, повреждены файлы
BacktraceCrashpadWindows.dll.
- Ошибка в игре/приложении:
- Сбой в управлении памятью (например, сборщик мусора IL2CPP).
- Проблема с загрузкой зависимостей (DLL).
- Повреждение системных библиотек:
- Ошибки в
ntdll.dll,KERNEL32.dll(редко, но возможно).
Что можно сделать?
1. Для пользователя (если это игра/программа):
- Проверить целостность файлов (через Steam, Epic Games или установщик).
- Обновить драйверы (особенно графические, если это игра).
- Отключить наложения (Discord Overlay, GeForce Experience и т.д.).
- Попробовать запустить от имени администратора.
2. Для разработчика (если это ваше приложение):
- Проверить логи Crashpad (обычно в
%LOCALAPPDATA%\Crashpad). - Проанализировать минидамп (используя WinDbg или IDA Pro).
- Проверить целостность IL2CPP-сборки (возможно, ошибка линковки).
Вывод
Этот краш, скорее всего, связан с ошибкой в системе Crashpad или повреждением данных в памяти игры. Если проблема возникает у многих пользователей – стоит ждать обновления от разработчиков. Если это единичный случай – попробуйте переустановить приложение.
1 Like
гениальные советы! ждать обновления или переустановить.
могу добавить: подудь на диск и протереть майкой
1 Like
please try to use english. if u are already using chatGPT, which your text suggests, ask it to give u the info in english. here is the translation:
Possible Causes
Crashpad Issue:
The crash dump generation system (Crashpad) itself has failed.
Files like BacktraceCrashpadWindows.dll may be corrupted.
Game/Application Error:
- Memory management failure (e.g., IL2CPP garbage collector).
- Failure to load dependencies (DLLs).
System Library Corruption:
- Errors in
ntdll.dll,KERNEL32.dll(rare, but possible).
What Can Be Done?
1. For Users (if it’s a game/program):
- Verify file integrity (via Steam, Epic Games, or installer).
- Update drivers (especially graphics drivers if it’s a game).
- Disable overlays (Discord Overlay, GeForce Experience, etc.).
- Try running the app as administrator.
2. For Developers (if it’s your application):
- Check Crashpad logs (usually in
%LOCALAPPDATA%\Crashpad). - Analyze the minidump (using WinDbg or IDA Pro).
- Verify IL2CPP build integrity (might be a linking error).
Conclusion
This crash is most likely related to an issue in the Crashpad system or memory corruption within the game. If many users are experiencing it – wait for an update from the developers. If it’s an isolated case – try reinstalling the application.
Thanks for the advice! But it won’t help me personally, even if it’s in Portuguese. As the game did not work after the update, it still does not work.