Message from Mojang
Fix for this has been found and will be coming soon. Recent Store update is to fix a related but distinct issue. An Official update to fix this problem is scheduled for later this week.
The bug
I faced a bug when I have installed the new version from MS Store. Installation process was ok. After I had opened and closed it about 5 times my PC started crashing. I just open launcher, wait 3 seconds and my pc crash with BSOD (wcifs.sys). I fixed it by installing older version of launcher.
Steps to reproduce
Repeated or double open game version 1.17.1.
Linked issues
is duplicated by 114
Attachments
Comments 76
The BSOD error code is always SYSTEM_SERVICE_EXCEPTION.
The kernel memory dump is over 1GB, not an issue with the launcher.
[media][media]
[media]
It might be a problem with Windows 11 optimization. Does anyone has this problem on Windows 10?
i have a similar problem with Windows 10.
when i try to log in with microsoft account the application crashes.
If it's a windows 11 problem, we need to know what failed.
For me it was wcifs.sys which is apperantly Windows Container Isolation FS Filter Driver
I have no idea what it does.
I have found an article about wcifs.sys. Now I understand that the issue is very deep inside of OS. To clarify it is something to do with the storage management. It might be cause of reading and writing file data or setting file, directory or volume info or even by opening, creating files and directories. Therefore, when you open the launcher something happens with data and it is crashing with BSOD. Now I appeal to MODS if they are having the same issue on Windows 10. The article itself: https://docs.microsoft.com/en-us/windows-hardware/drivers/ifs/about-file-system-filter-drivers
Same here on windows 11, but only since snapshot 21w44a. Used the new launcher yesterday with no issues on previous snapshot 21w43a
I have exactly the same issue. One thing that I found while using WhoCrashed was this following line:
"This was probably caused by the following module: fltmgr.sys (FLTMGR!FltGetFileNameInformation+0x14FD)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8078E215C36, 0xFFFFBB85EF65D710, 0x0)"
This was in the second crash I experienced, and wcifs.sys was also implicated.
(Also, I have a Samsung EVO SSD (860) as well, but chkdsk did not find any issues.)
[FIXED] Click on this (download BTW) https://launcher.mojang.com/download/MinecraftInstaller.msi and that will download the old Minecraft Launcher. Delete the new MC Launcher by clicking on "Windows Key", typing Minecraft, and right clicking on the one with the black background. Then go to the old Minecraft Launcher and play from there. Took me about 3 hours to finally get this lol, hopefully they fix this.
I can use the new launcher with the java version if I select java from Oracle in the advanced settings.
Many of you didn't read my post. I have already written how to fix it (3rd comment). And we are not discussing whether should we upgrade to Windows 11 or not. Except XnossisX who has just confirmed my thoughts about the depth of this issue. Read this article: https://docs.microsoft.com/en-us/windows-hardware/drivers/ifs/filter-manager-concepts
Tom Kitz, that probably means that the issue lies in the filesystem filter driver for the custom Java type Mojang uses.
Download old minecraft launcher gabriel https://launcher.mojang.com/download/MinecraftInstaller.msi
I have this problem, but it only happens when I actually launch the game, only with a custom profile directory, and only for OptiFine 1.16.5. I am using Windows 11 on the beta channel.
Hey guys!
Please refrain from commenting if you don't have any additional information to add to the report. Commenting saying 'I hope it gets fixed soon' makes it harder to find the helpful information that may be posted!
FYI Launcher team is working on this. Seems a bug in Win11 interaction that we will correct.
I found a fix from Reddit that will help our access problems for the new Minecraft Launcher. This is tentative though while we wait for the official fix. May this guide help everyone who is having issues in launching the game.
I did it, and BSoD is still there. We need to be more patient and give Mojang the chance to fix it.
Ok... we will wait for the official fix. hmmm. weird as the solution launched the game at my end but it is a bit unstable as it has graphical issues observed [like particles won't show]. anyways, it's ok, I will still wait for the official update.
I also have the same issue, I did find a work around that kinda works where you reinstall the new launcher each time it crashes and it temporarily solved the issue but after closing mc it can happen again so you'd have to reinstall. Bit of a hassle and i'll be going back to the old launcher till this is fixed but if you want you can do this.
what we can do for now is go to minecraft net and install the minecraft launcher for windows 7/8
[media]
(and not update it to the new version)
YEP I have the same problem althougt I have minecraft from xbox app gamepass and Iam unable to install it from somewhere else, also I have the problem which don't install on my second 2TB Hdd and only installs minecraft Launcher on my main drivedmp files
Message from Mojang
FYI Launcher team is working on this. Seems a bug in Win11 interaction that we will correct.
The PC will not crash when trying to open up another instance after closing the initial one if you:
1. Close the original instance of the game
2. Open the Launcher
3. Go to Task Manager and terminate the Launcher task.
4. Reopen the Launcher and start a new instance
Another method to prevent a crash is to:
1. Close the original instance of the game
2. Uninstall the MInecraft Launcher from the "Apps and Programs" section of the Settings app.
3. Go to the Xbox app and redownload the Minecraft Launcher.
4. Reopen the Launcher and start a new instance
It's exactly the same problem, especially when I try to play with Optfine.
Now WIN7/8 Launcher can't install on Windows 11, it doesn't do anything, the file won't start.
For now I'm solving it as follows: There was a problem, the blue screen appeared, it restarted.
I uninstall the launcher and reinstall and play.
Even so, Optifine doesn't work at all.
When I first downloaded the new launcher, I could play it just fine (I was using 1.17.1 with OptiFine) before I started getting the BSoD upon launching the game.
If OptiFine is a cause for this happening (along with the issue with Windows 11), I hope that could be fixed also.
A temporary fix I have found to the BSOD, still, not resolving the game crash though; When creating a new version on Windows 11.
Step 1: Download and install jdk-17_windows-x64_bin.exe from the original website.
Step 2: Upon Creating/ Editting a version in the "Installs" tab in the launcher, click on more settings and set the java executable to C:\Program Files (x86)\Java\jre1.8.0_301\bin and select the "javaw.exe" file.
Step 3: Save or create the new instalation, click play and it will just crash the game when it tries to load instead of BSOD.
Credit: https://www.youtube.com/watch?v=juiwBb251To&t=1s
Another fix that works is just using the old launcher, I think you should be able to still download it from the official site, I happened to still have the msi file which was great. one downside is that you'll get a pop-up everytime you open the launcher telling you to update to the newest version; we'll just have to deal with it until the issue is fixed.
Previously in the new launcher it gave me the BSOD only when launching the game (while loading the game around the 30% load completion), not the launcher itself. The pc is just frozen not even being able to try to collect any data when it happens, regardless of how much time I wait, it could be just the pc's fault.
Edit: Alex's (https://bugs.mojang.com/browse/MCL-19992?focusedCommentId=1104283&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-1104283 ) version solved the crashing when opening an instalation with optifine and also with the 1.17.1 one (making them playable, nice), I'll assume that it works with other non-modded instalations as well. It still seems to not make it work for the Forge instalations though; modifying/ removing any amount of mods doesn't produce different results; changing the JVM arguments to allocate more ram also doesn't lead to a fix.
I believe so, as I did several tests with the same result. I can't play with OptiFine, it's always blue screen.
I did exactly what this tutorial taught and it didn't work.
The old launcher, with extensive MSI, does not install itself, I have already excluded all launchers and versions that it had, it does not install.
The temp fix listed by Sandel worked for me. able to play again. thanks. Looks to be bad coupling of the jdk is at fault here. Worked with Optifine and Fabric Mods as well. have to set link on each install.
Workaround by Sandel with jdk-17 "worked". No BSOD but the game is crashing. With jdk-18 the game is working.
Unzip JDK-18 EA build - https://jdk.java.net/18/
In "launcher > installations (optifine) > edit > more options > java executable" specify the path to "\jdk-18\bin\javaw.exe"
Play
By doing the following:
"Workaround by Sandel with jdk-17 "worked". No BSOD but the game is crashing. With jdk-18 the game is working.
Unzip JDK-18 EA build - https://jdk.java.net/18/
In "launcher > installations (optifine) > edit > more options > java executable" specify the path to "\jdk-18\bin\javaw.exe"
Play
I opened the launcher and the and it actually loaded OptiFine, but when starting it returned this error. (image)
[media]Guys, I did another test, instead of using the path "\jdk-18\bin\javaw.exe" I used the path "\jdk-17.0.1\bin\javaw.exe" and it worked.
same issue here. W11. (Insider build, 22000.282)
Related system file triggering the BSOD: wcifs.sys
Found related video on Reddit, showing the when & where
Minecraft new launcher on Windows 11 causes Green Screen : Minecraft (reddit.com)
Fix for this has been found and will be coming soon. Recent Store update is to fix a related but distinct issue.
I think I found a way to fix it. So you have to go to the Minecraft installations and then select edit for the installation that won't run and hit more options. This will open up Java executables, click browse, this should show the folder for the new launcher. Go to runtime ---->java-runtime-alpha------>windows-x64- ---->java-runtime-alpha---->bin----->then scroll down until you see javaaw.exe and the click open. This fix only works for people who haven't changed the Java executable installation, since the folder for the new launcher is hidden through windows and is hard to get through.
Just like the previous comment said, changing the executable seems to work. It did for me.
I'll leave this video made by someone else showing how to do it. Hope it helps.
https://youtu.be/juiwBb251To
@Mojang I would be very interested to know how you managed to generate a black screen with the start of Minecraft, could you please tell us after the fix where the problem was?
I've seen several updates to launcher, and I just got another today - but it still causes spontaneous reboot on Windows 11.
He said the update that fixes this problem is scheduled for later this week. The update they did today was to fix a related but distinct issue.
I think it's fixed now because I launched the launcher and it said it had a new update and then it updated and I launched it without any modifications to the java executable and it launched with no crashes. Yay! Thanks Mojang!
What's odd is I got an update from Windows store, then ran launcher and it spontaneously rebooted when i went to play. BUT... When I opened the Xbox Game App and clicked launcher there, it ran an update and its fine now.
The version in windows store didn't change.. just seemed to behave differently launching from xbox app.
@unknown Please do not tell people to download unofficial, pirated versions of the game. Your comment has been removed for this reason.
I am on Windows 10 21H2. I have done everything in my power to resolve this. Reset my PC, fix all my drivers, use tons of launchers. Nothing works
UPDATE: I regressed the current version of my ASUS STRIX RTX 3090 from Nvidia Game Ready Driver 497.09 to 472.12 and that seems to have fixed my BSOD issue on Minecraft Java 1.17 and 1.18. I will bring another update if anything happens.
Just to clarify, I was using Nvidia Game Ready Driver 497.09 on my Strix 3090, and that caused MC Java to open and communicate with Windows 10 21H2 improperly which resulted in BSOD upon every launch.
I am now using Nvidia Game Ready Driver 472.12 from the ASUS Website and it is working fine.
The issue is still remaining, my laptop stucks until I force reboot it. Windows 10 21H2 19044.1826, CPU Intel Pentium N4200 (30.0.101.1994 graphics driver), RAM Samsung 8 GB 1600MHz, SSD Kingston SA400S37120G. Launcher version: 2.3.280
Sarisan: Unless you are literally seeing the "blue screen of death" on your PC that has remained constant since December, 2021, then the issue you're having is a different issue.
If this is the issue you've been having for the last 8 months, then at this point you absolutely MUST log a support issue if you want your issue dealt with.
If your issue is even slightly different, and you are not seeing the Windows "blue screen of death" (sounds like you may not be, and instead the PC might just be hanging because of some other process causing a problem) then if you want help you should immediately:
Log a new bug in mojira, and attach your launcher logs (in %appdata%\.minecraft folder)
Also log a support issue so we can get more info directly from you.
How did you install a older version of the minecraft launcher? im facing the same issue