Greetings Mojang,
Start up information
When loading 1.13 or above the game freezes, this means game lauches for 1 second and than stops responding. i've had somebody looking at the problem if it had something to do with my options where we changed a schematica setting. this solved the problem for 1 single time. but when i minimized mc for 10 seconds to put on music the game freezed again. The issue only comes up with versions 1.13 ( all pre releases snapshopts and above). i'll provide you guys with some information with my settings/options and how my screen looks whenever i open my minecraft in this version.
What i've done to trying fixing it:
-Remove mc and all it files
-Remove Java and after it updated it to the most recent version
-Remove the mods, all non vanilla context ( only files that minecraft provided in the launcher itself. ( this includes shaders and texture packs.
-Removed all minecraft versions accept from 1.13
-Upgraded the priority that minecraft had for my cpu.
-Upgraded the ram available for launch ( it was 1 GB i upgraded it to 4 and 8
Extra information indeed needed:
The game has been opened twice where i've started a world and started playing.
I'm forced to close it. minecraft doesn't create a crash report neither does it show up a error in the logbook
i've done 24 sets of waiting for 5/10 minutes and 3 sets of 30/60 minutes of waiting.
My minecraft options at the current moment :
https://hastebin.com/ohihumalej.css
With kind regards a fellow Minecraft player,
Qutje
Related issues
Attachments
Comments

Closing Discord should fix your issue.

@neko no, when starting up the pc i only started up minecraft ( no discord ) and it still didn't went online
Are you sure Discord doesn't open automatically on startup?

From MC-124460:
... like Razer cortex's overlay, and nvidia gamecaster causes this effect.
Please attach .minecraft/latest.log

file attacked .minecraft/latest.log

"Process closed with exit code -805306369" , see MCL-6550

problem fixed, how do i change the status of the problem

Nothing to do here, this ticket is already resolved as duplicate.