Old Minecraft Versions Crashing

[Maribeth Seagers]

Minecraftkeeps crashing in 1.8.9, 1.7.10, and other versions, but 1.16.2, 1.16.3 is absolutely fine. I had Badlion client and I also use Optifine. I uninstalled and reinstalled Minecraft, Java, and the .minecraft folder. But it still keeps crashing, I just want to play 1.8.9 with no trouble at all. I don't have an AMD graphics card, I have an Nvidia card, and it's up to date.

I deleted the .minecraft folder and recycled it in the bin. And I do play in fullscreen mode, I managed once to get out of fullscreen then crashed when I switched to full screen, so that might be the problem. I don't know what you mean by the native launcher, but it crashes in any version of the Minecraft launcher

No my pc is using my nvidia card because the integrated graphics don't even show up in device manager and Minecraft says I'm using the Nvidia card, also when I followed the steps of the link you posted I clicked Javaw and it showed up in Nvidia Control panel as Badlion Client

Every time I try to play 1.20.2, eventually my game crashes to the launcher and gives the exit code -1073740791 and states that this issue is usually caused by an outdated graphics driver or a conflict with screen recording software. However, my NVIDIA driver is up to date and I don't have any screen recording software on my PC. Sometimes this crash occurs while creating a new world, other times the game is able to create the new world but will eventually crash after around 1-2 minutes of gameplay. I have tried:

I think the issue you mention concerns PCs with multiple graphics cards where Minecraft is running on the lower performance graphics card, however I only have one graphics card and so mine will always be set to "high performance" so to speak, because there's no other option available

When the issue first occurred I looked to see if my graphics driver needed an update and it did, so I updated it thinking that this was causing the problem, however Minecraft was still crashing with the same exit code even after I updated the driver, so I don't think it's the driver version causing this.

I launched vanilla 1.20.2 with the FTB launcher and again had the same issue. Not sure whether this is relevant but my GPU usage in F3 is repeatedly and seemingly randomly peaking at 100% before going back down, this could be unrelated though.

It's just weird that in most cases the game will run fine, sometimes for around 10 minutes, before it crashes. I think the only option I have left is to do a full reset of Windows and if that doesn't work then I guess maybe it's a hardware issue which would be a bit of a bummer

1. Using some screen recording or overlay program. GeForce Experience, Afterburner, OBS, etc. The exit code does also mention this so outdated drivers are unlikely to be the cause (unless you're still on seven year old nVidia drivers). If you're using any overlay or recording stuff, try without and see if that stops the issue. I was able to run these programs fine, but when I used Afterburner to record, it'd record fine, but if I recorded for too long, and then stopped, it'd trip it up.

2. Using some shaders in older (1.10/1.11 at least) Minecraft versions. Never in newer (at least 1.16+) versions. it was still pretty rare, and may have been limited to when changing from full screen to window or vice versa (I swear this is the moment when I've had so many crashes with this game). Funny thing is I moved to AMD and now in an older version (1.12), I'm just getting a loss of signal to restart crash. I had this issue on a broad scale before (RMA of the video card fixed it) so I'm not sure if it's the same issue returning, or this is simply one of many "interesting" issues with older Minecraft versions and nVidia and AMD just crash differently in response to it. Still need to test and see if my crashes extend beyond this situation, but I digress.

If it's instead happening frequently and soon after starting to play, and in recent versions, and if it's in more vanilla situations (no mods, no shaders, no overlay programs), then I wouldn't have many guesses left.

The first that jumps out to me (at least for the thread starter) is why are you using Windows 10 on a 12th+ generation Intel? Those really want the scheduler from Windows 11 to operate more optimally due to their hybrid core nature. It may or not be the cause though.

Sort of related, but are you overclocking? If so, revert to stock/defaults (this includes setting RAM profiles like XMP to default). It might be worth investigating if your motherboard is pushing your CPU too hard, even at its default settings. I say this because some of the 13th and 14th generation upper SKU CPUs are proving to be pretty unstable in certain workloads that push them certain ways, and they need underclocked (lowering the p-core and/or e-core ratio) to be made stable. The "out of video memory trying to allocate a rendering resource" error message that even those with RTX 4090s are seeing? Or the other error messages when compiling shaders in Unreal Engine/DirectX 12 games? It's the CPU. And with an Asus motherboard I'd be more wary it's pushing the CPU hard (Asus was apparently the one brand doing it worst on AMD's side too, if you recall the situation with the 7800X3D burning up). I haven't heard of this problem with the prior 12th generation, but the point here is I'd probably rule out any overclocking (XMP included) just to be sure.

Beyond that, I'd have little if any ideas. nVidia's drivers have been on and off spotty lately and the error code does seem to be nVidia specific (though your log doesn't seem to mention the nVidia drivers as the cause, it seems to be pointing largely to Java?), so maybe trying slightly older ones to see if it is a factor in the exit code occurring or not? If not, I'd be out of guesses.

Hello, I'd like to say that I have always had trouble with this issue, more specifically, in my case the game crashes just at start loading no matter the version. Not only on modern versions, but also on older ones. I had the problem just today on 1.12.2. The code, in my experience, has always presented itself after adding a certain mod. There are some mods that inevitably cause this error. And it's not a problem with my computer, I've tried on other devices with the same mods, changed drivers many times, but the error always seems to relate to certain mods which, looking at them, have practically nothing in common. For example, I have a 1.12.2 modpack with practically zero mods, just a certainly themed modpack with no additions. Whenever I add SPECIFICALLY (I tried adding a lot of other similar mods, but only this one does so) the mod In Control (used to control mob spawns) it crashes during initial build with this code. Basically this mod has various config files in json format that can be modified to alter mob spawns or add new ones. Even if I don't even touch the config files, the game crashes. But, it doesn't happen on another modpack I have that has 156 mods on it that would have all the reasons to conflict with In Control's code.

I am more than sure it isn't an issue with that mod. Don't consider it. It's even hilarious to think that In Control is the problem, since other mods crash at absolute random with this same code, on different versions but for no apparent reason.

I myself have seen practically all of the error codes (minus the easily solvable ones, of course) and I can tell you this is a very particular issue that no one cares about but affects a modest amount of people. It's not a -1 code, where you don't know well where or what the problem is. It's a specific code happening to many people but with no evident correlation between each case and (guess what) a lot of times not for the reasons listed by the launcher for the code. It would really need some attention from someone competent.

Disclaimer: this is an updated version of a post I made a few days ago with the debug log of the official Minecraft launcher, not curse forge, also making this because my previous Pastebin was deleted for some reason. I am going to paste what I said the other day for reference. link :

Hello, I am crashing upon attempting to load Minecraft under the forge launcher. First, I should start with the paste bin. ---DELETED---. This was on the curse forge launcher as I could not find the log for the forge file installer. But I had the same issue on both so this should suffice. I have spent the past 5-6 hours on this and have tried many options, so I'll list my troubles so far.

I installed both Java 8 and 17, I then installed Minecraft from Minecraft.net, I already had the launcher apparently, so I didn't actually use that installation method until later (Minecraft dungeons on pc). I ran Minecraft on version 1.20.1 and the snapshot in advance and then closed Minecraft (I have done this all several years ago I should mention). I then attempted to run both the stable and latest release of the forge launcher, and received error code 1 on both, I reinstalled both java and Minecraft 3 times during the course of this and led to nothing. I then went and updated all of my drivers (ROG ZEPHYRUS G14 is the model, requiring ASUS drivers and already has a built-in app for driver updates. All to my knowledge correct versions of java, Minecraft, forge, and drivers alike.

Crashes are unexpected shutdowns of Minecraft, generally caused by unhandled "exceptions" while running the game. When Minecraft crashes, it typically closes immediately, though it may show an error report marking the location of the exception that caused the crash instead of closing. A sign of a server crash during gameplay is a "Saving chunks" or "Shutting down internal server" screen.

Crashes used to have an error report screen, but that feature has been removed. Yet sometimes, an error report can quickly flash right before the game closes. Minecraft occasionally does this on startup, except it stays there, not allowing the player to play the game.A tutorial exists for obtaining the report file generated by the game when it crashes so that the player can share it for diagnosis.

3a8082e126