The same case happened in 1.13.2, I have done some research and concluded that this is a bug and NOT a technical issue, even though your computer can run it it won't due to some sort of bug, I have tested a computer with less cores and it runs perfectly fine, the output says thisġ2:11:05.315launchermainExtracting 8 files!12:11:05.603launchermainUsing default game log configuration client-1.12.xml (outputs XML)12:11:05.603launchermainInstalling versions!12:11:09.YggdrasilAuthenticationServiceRender threadEnvironment: authHost=' ', accountsHost=' ', sessionHost=' ', servicesHost=' ', name='PROD'12:11:09.728dvoRender threadSetting user: None yo buisness12:11:12.130launchermainġ2:11:12.130monitorProcess MonitorProcess crashed with exit code -1073741819 Now you may have played 1.17 snapshots before and they worked just fine, now they won't launch, there is a work around though, if you restart your computer, it will launch for the first time, here is what makes no since though, this usually happens to computer with 2, like your computer is underpowered yet in most cases your computer passes the minimal recourses to run Minecraft. So, the reason Minecraft is crashing is due to your cpu, to demonstrate, my cpu is an intel (r) Core(TM i7-10700f cpu 2.90Hz, My GPU is a NIVADIA GeForce GTX 1660 SUPER, I actually have 8 cores, it says it on task manger, I have already updated my driver before anybody asks.
(#spoiler) = neat! (/rose) = ( full list) News Builds Gameplay Maps Tutorials Redstone Command Blocks FanArt Comment Formatting Use the wiki or community support for questions that can be answered there.Explain your suggestions with a text post.
Don't promote illegal or unethical practices.
0 kommentar(er)
