Crash on startup; can't find cause in log file (attached)
Launched Iris + Distant Horizons for the first time. It launched. Then I edited a few settings and minimized. Then it crashed with error code: -1073741819. Now whenever I start Iris + Fabric, it crashes after the Mojang logo. Changing the Xmx memory size didn't help.
30 Replies
Does not contain crash information. Check the logs stored in
.minecraft\crash-report and select the file at the very bottom in the folder for the real crash log.There is no
\crash-report directory apparently. Do I need to enable it from some settings?Is it
crash-report or crashes? I forgot which one, try check if there's any folder with similar names to it.I don't see anything such...
Man I hate Discord compression...
Anyways, rerun the game to reproduce the crash. It may generate a new crash log and contain more useful information.
Well, there's no folder that says crash
Already did multiple times. Same log everytime.
Do you see a file with the name
hs_err_pid(number) in that folder?No file with those keywords
In case the crash is caused by a fabric setting, how do I reset the fabric settings? There must be a file somewhere
Fabric as in the mod loader doesn't have a setting. You likely want to delete the mods setting rather. Those can be found in the
config folder.I recheck your latest log and discovered this. I have never seen this one before.
How does it affect your game? I have no idea. If this is the cause of your crashing, fixing this will be damn near impossible without a reference somewhere.
it's OSHI related
just means some values like CPU usage may be slightly off
Okay so unrelated to crashing. Good enough.
I deleted the
config folder and it allowed the game to load. Crashed again after minimizing. But now deleting the config no longer works.Time to upload an updated log file.
I don't notice a change
Wait. This log was generated when it last crashed mid game
The last message is:
[Server thread/WARN]: Can't keep up! Is the server overloaded? Running 2837ms or 56 ticks behindIf no crash log or native crash log generated (
crash-<date>.txt and hs_err_pid<number>.txt respectively), this is very peculiar.
Push comes to shove, you have to test enabling mods one by one, starting with Fabric API, then Sodium, Iris, Indium and finally Distant Horizons in those order just to see which one will trigger the crash.Distant Horizons triggers the crash
Would like to know what system spec you have.
AMD Ryzen 5 5600X, AMD Radeon 6700XT 12GB, 32 GB RAM
I have something you can try. No guarantees it will work, but I had a similar issue of enabling this one mod causes the game to immediately crash upon loading in.
Delete the folder
.minecraft\.fabric to reset Fabric cache. Chances of this working is 50/50.Already did that yesterday
Didn't help
I am out of ideas unfortunately.
How do I report this to the devs?
Maybe it's a hardware specific bug
Unlikely. I've seen people with similar hardware with you and they run fine.
Okay, have you tried resetting the entire
.minecraft folder? It's the most nuclear option, and if that doesn't fix, I doubt anything else would.Um... okay, I'll do it. But it's the first time I'm running minecraft on this machine. I don't think it can be any fresher...
Just did it. Doesn't make a difference.
Although it did launch once. Which crashed immediately after minimizing to see the shader folder
@hardester I just found a reddit thread where another person is experiencing crashes on DH and they are not being able to find any crash logs either.
Okay, after some experimentation, I've found that the DH crash happens specifically in fullscreen mode. And also, the performance of DH is absolutely horrible for some reason.
DH axed my framerate to around 20-30 FPS from 100. Isn't it supposed to be performance friendly?
This has helped. Apparently some AMD GPUs are requiring a different iris build. https://discord.com/channels/774352792659820594/1220113399787032668/1223638820180987945
OH, that bug? Damn that's super obscure.