Daniel Ortlieb
- BroOtti
- brootti
- Europe/Stockholm
- Yes
- No
Hot Fix availableMod NoticeSymptoms: Game crashes without showing a crashlog, launcher shows "Game ended with bad state (exit code -1073740791)"
Cause: The 3Dvision software bundled with the newest nvidia driver is faulty, causing Minecraft to crash. The driver in question has version 378.49 and was released on 2017-01-24.Solution 1: Uninstall the drivers and reinstall without installing the 3Dvision drivers
Solution 2: Uninstall your current nvidia driver and download an older driver from here: http://www.nvidia.com/Download/Find.aspx?lang=en-usIf you need further support, please do not reply here. Instead, go here: Community Support
To iterate, this is not caused by Minecraft.
https://twitter.com/Minecraft/status/824548998581288962
Hey! We're hearing Nvidia driver 378.49 has a few issues. Nvidia are working hard on a fix, but for now, we suggest you avoid the update.
Already tried:
Reinstalled Graphics driver
Reinstalled Java
Reinstalled MinecraftThe launcher starts but when I click on Play the game doesn't start and I get the attached log. There is no game output and no other log.
[Hot Fix] Game ended with bad state (exit code -1073740791) - Faulty nVidia driver
[Hot Fix] Game ended with bad state (exit code -1073740791) - Faulty nVidia driver 378.49
Like I said before there is no other log. So no crash report.
The exit code should tell where the program exits. More information I can't deliver.
I searched my whole disk for a crash-reports folder but nothing found.
Is Minecraft or Java creating the crash-reports?
Restart your computer and look if the problem is solved. For me a restart is the solution.
Restart your computer and look if the problem is solved. For me a restart is the solution.
If someone experiences the problem described in this bug report they should really update their system. The bug report is related to an old driver and was fixed in newer driver. If you encounter the same error message on a newer driver version you need to create a new bug report as the cause could be something different.
Don't comment on this old bug report as it is already solved years ago.
Well, then someone maybe should open a ticket at nvidia support. This bug report states that it's not an error with minecraft. It helps nobody if more people comment here.
Does nvidia has an open tracking system? So sharing a tracking number would be useful.
Not sure if I found the right tool from nvidia but it is something like a forum? If you haven't found a thread about the error, you created a topic yourself? Maybe you can share the URL so others can find it easier?
I looked up some other reports with this error code. The answer is always the same. They can't provide technical support and so you should go for community support.
This bug report here indicates the error is caused by a faulty driver by NVIDIA. Minecraft is not the cause of this error, and so Mojang can't resolve the problem.
In fact TNT9182 already mentioned this is a problem with all OpenGL applications. So do they contact each software developer for support? Would be a lot easier to contact NVIDIA directly. And if needed, NVIDIA can get in contact with the software developers.
Also, it seems this time it doesn't affect that many people. Saying that, I don't think it is directly caused by a faulty driver. Maybe a special combination of hardware or software used. In fact, some people mentioned they switched to an older version of the NVIDIA driver and still experienced the problem. So they first need to identify the root cause of the problem, which is general technical support. You can't blame Mojang if your system doesn't work accordingly. It's like you try to get support from a supermarket because you can't transfer your shopping bags with your bicycle home.
Also, 5 years back the problem was found by another user and afterwards Mojang already noticed further support can only be get by community support. I was the first one reporting a crash with this exit code, which means it's an unexpected exit code for Mojang. So if you can't provide at least a crash log, they can't help you further. If you have a crash log with additional info, create a new bug report. Well, properly it won't be a bug at all and keeps being a technical support case.
Imho this bug report should be closed for new comments.