Intermittent Exit code -1073741819 while using 2 core cpus on 1.13.2 and above, runs fine on 1.13.1

Thank you for your report!
However, this issue has been temporarily closed as Awaiting Response.

We do not have enough information to find the cause of this issue.
Please attach the launcher log (.minecraft/launcher_log.txt) here.

Once attached, the report will be reopened automatically.

Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki

See -1073741819.

Thank you for the reply, Neko.   These are not the solutions.  I am testing with both the bundled Java and a clean install of jre1.8.0_181.  Both produce the same error.  I do not have D3Dgear installed.  I have tested with several versions of Nvidia drivers, including 398.82 and 416.34 (latest version, clean install)  for my 660Ti, all with the same result.

Again, 1.13.1 runs without any error.  Only 1.13.2 and 18w43b produce the error.

This should not be marked as resolved or a duplicate. All known causes as well as other unrelated fixes were attempted in the #minecrafthelp IRC. With other instances of that exit code, it is a problem on the PC that effects all installed versions. This user only experienced the problem on the latest release version and further snapshots. 

Reopening.

Crash is in lwjgl.dll, attaching dxdiag with old version of driver https://paste.ubuntu.com/p/SNBPQGxHZP/

and latest from 3 users https://paste.ubuntu.com/p/r8rh5VYmBj/ https://paste.ubuntu.com/p/5kf2dDrrfh/ https://paste.ubuntu.com/p/HMThSv8zmq/

All of them with weak 2 core cpus

Doesnt affect 1.13.2-pre1 but it affects 1.13.2-pre2

After doing my own testing, this is what I have concluded about this issue:

It only occurs on old 2 core processors which do not fully load the game during the LWJGL startup process and just terminates. Any  2c/4t processor should not have this issue. It can only be replicated on 2c/2t processors which are either very old or have very low clock speeds.

If you cripple an FX-8350 to run at 2GHz and only 2 cores (2 threads) then you can occasionally get the error. Same with a Ryzen 1500. However, it is inconsistent at best, and not constantly going to produce the issue. 

As the minimum requirements for the game specifically reference 2 core/4 thread processors released within even the last 5 years should not have this issue.

Essentially: your machines have not met the minimum requirements for some time and use 10 year old hardware. The hardware requirements have been this way for over a year now, so it's fair to say it's just too old to support.

https://help.mojang.com/customer/portal/articles/325948-what-are-the-system-requirements-

From @marcono1234

It is not documented, but `commonPool()` has available processors -1 (http://hg.openjdk.java.net/jdk8u/jdk8u/jdk/file/478a4add975b/src/share/classes/java/util/concurrent/ForkJoinPool.java#l3435)

And https://docs.oracle.com/javase/8/docs/api/java/util/concurrent/CompletableFuture.html says
> All async methods without an explicit Executor argument are performed using the ForkJoinPool.commonPool() (unless it does not support a parallelism level of at least two, in which case, a new Thread is created to run each task)
And also https://bugs.openjdk.java.net/browse/JDK-8213114, so explicit usage of the `commonPool()` can cause use of thread per task as well

DataFixerUpper uses number of cores - 1, so in 2 core processors the parallelism ends up being 1, so a thread is created for each thread

This makes the OS run out of native threads while running in 32 bits(MC-137353), and seems to trigger this bug in 64 bit

@Lord_kalex apparently it doesn't only happen for pcs and laptops that are "too old", it seems like it happens to any new or old PC as long as it has low enough specs, I would know since I am having this exact issue on this laptop that I bought a couple of months ago so it is new https://support.hp.com/us-en/document/c05987723, I didn't have much money at the time so its all I could buy but I figured it would at LEAST run lower end games like MC, but nope, I am getting the exact same OutOfMempry error about not being able to create enough native threads on 18w50a. It is 64 bit but has a dual core CPU so I assume that is the issue. I didn't know MC would require a 4 core cpu, guess I am stuck playing 1.13 for a while ;~;

@therektafire This happens on 2 core 2 threads machines, so any 2 core PC without hyperthreading, which are usually really old PCs as even cellphones nowadays have 4 or more cores

Workaround - Install optifine for 1.13.2. Worked in my case.

i have this problem but on a quad core cpu. the game worked for a bit after installing before deciding to crash on launch enverytime i try to play

Fixed in the latest snapshot.

I'm having this issue since the update to 1.14.
("Process crashed with exit code -1073741819")
Win 10 on i7 w/ 16 GB RAM

BUT only at every other first start after a while; at the second start, the game runs fine….

i have tried all the suggested solutions on a i7-5820K 6 core 12 thread CPU with 32Gb of RAM and the problem persists.

My first start after installing Forge on 20w17a, and this came up after 'Setting user: PoolloverNathan', along with a good ol' launcher blackscreen.

This tracker is for Vanilla. We don't support mods and their loaders.

I have the same issue on 1.16.4... 😞

NVIDIA Quadro K2100M

Intel(R) Core(TM) i7-4810MQ CPU @ 2.80GHz

16 GB memory

Windows 10 Pro (64 bits)

Hey I might have something that would help. Uninstall Player.me from your system because it interferes with the minecraft launcher. This worked for me as I was in the same situation. Heres the video I watched,  https://www.youtube.com/watch?v=dNnJhbmX4lI

@unknown Your issue is http://hopper.minecraft.net/help/exit-code/code-1073741819/
@unknown Same thing, no player.me installed

Has someone found a solution for this problem? I kinda want my money back... I just bought Minecraft and to face this kind of problem is just so disappoiting...

Still seems to be an issue through 22w16b.

This is an issue with your setup, not an issue with Mojang.

I was experiencing this as well, but I just restarted or shut down my computer and it went smoothly after starting it back up.

@MisterZero This report has been given a Mojang Priority, meaning that Mojang consider it a valid bug.

@unknown What about this is incomplete? Which question needs to be answered to reopen this?

If you are encountering a crash with exit code -1073741819, this indicates a native access violation exception. These can have a variety of causes, but this report is likely a collection of unrelated issues without enough information to understand what went wrong unfortunately. 🙂 In the case of this error, a JVM native crash dump should be generated in your Minecraft install directory, with a name like: `hs_err_pid_xxxx.log`. Please submit a new report with this file attached. Thanks!