MCLG-89Constant PC crash
Steps to Reproduce:
[Step 1]
I click to open Minecraft legends
[Step 2]
i skip through the normal opening animations
[Step 3]
i sit at the main menu or do literally anything such as open the marketplace or try to start a single player campaign
Observed Results:
after a few seconds, the screen goes dark in a very glitchy way with various colored pixels roughly showing the image of what was last on my screen. so as an example say i click on the Minecraft market place ingame after awhile parts of my screen will turn completely black while outlines of boxes will have red lines on them but the red lines will not go over all of the boxes. that image will be on the screen for 2 seconds before my pc completely crashes and sends me back to the log in screen of my pc.
Expected Results:
[Describe what should happen]
forgive me for sounding condescending here but i honestly cant figure out any other way to say this. What i expect to happen is for the game to not crash after just opening it to play it.
Because of how this bug affects my pc i am unsure i can collect a direct screenshot of it. i think i could get a picture that i take on my phone of it if you are ok with accepting that. but i dont think when my screen goes black like that i have the ability to screenshot.
Created Issue:
Constant PC crash
Steps to Reproduce:
[Step 1]
I click to open Minecraft legends
[Step 2]
i skip through the normal opening animations
[Step 3]
i sit at the main menu or do literally anything such as open the marketplace or try to start a single player campaignObserved Results:
after a few seconds, the screen goes dark in a very glitchy way with various colored pixels roughly showing the image of what was last on my screen. so as an example say i click on the Minecraft market place ingame after awhile parts of my screen will turn completely black while outlines of boxes will have red lines on them but the red lines will not go over all of the boxes. that image will be on the screen for 2 seconds before my pc completely crashes and sends me back to the log in screen of my pc.
Expected Results:
[Describe what should happen]
forgive me for sounding condescending here but i honestly cant figure out any other way to say this. What i expect to happen is for the game to not crash after just opening it to play it.Because of how this bug affects my pc i am unsure i can collect a direct screenshot of it. i think i could get a picture that i take on my phone of it if you are ok with accepting that. but i dont think when my screen goes black like that i have the ability to screenshot.
Steps to Reproduce:
[Step 1]
I click to open Minecraft legends
[Step 2]
i skip through the normal opening animations
[Step 3]
i sit at the main menu or do literally anything such as open the marketplace or try to start a single player campaignObserved Results:
after a few seconds, the screen goes dark in a very glitchy way with various colored pixels roughly showing the image of what was last on my screen. so as an example say i click on the Minecraft market place ingame after awhile parts of my screen will turn completely black while outlines of boxes will have red lines on them but the red lines will not go over all of the boxes. that image will be on the screen for 2 seconds before my pc completely crashes and sends me back to the log in screen of my pc.
Expected Results:
[Describe what should happen]
forgive me for sounding condescending here but i honestly cant figure out any other way to say this. What i expect to happen is for the game to not crash after just opening it to play it.Because of how this bug affects my pc i am unsure i can collect a direct screenshot of it. i think i could get a picture that i take on my phone of it if you are ok with accepting that. but i dont think when my screen goes black like that i have the ability to screenshot.
![[Mojang] Mega_Spud (Jay Wells)](../../../data/avatars/users/92696.png){kind=small}
I have found that trying to buy something causes my pc to break with a message popping up saying it needs to reset with the frownie face. im assuming this is a different bug but i thought i should mention it while im testing the game in windowed mode.
![[Mojang] Big Beak](../../../data/avatars/users/88062.png){kind=small}
I have tried some suggested fixes from the Minecraft Legends discord such as updating my drivers but everything i tried had no effect.
If possible, could you please include details about your system (RAM, CPU, GPU spec). Knwoing which graphics driver you have might be helpful, too.
If you like you can run dxdiag and copy the relevant information from there. (Win+R → dxdiag) - be sure to remove any personal information.
is this the correct information that you need? if not let me know what else i can provide.
Let me know if you need anything else. I can also load up the game and try to record a video of what happens with my cellphone camera if that would help.
I have the same issue. I was able to play singleplayer for a couple of hours on my first time launching the game. I then exited singleplayer and entered a mutliplayer lobby, and then my PC crashed. I have since then not been able to be in the game for more than a minute before my PC crashes. It varies when it crashes, sometimes instantly upon the game loading or sometimes after a minute. It crashes during the menus and loading screens, I´ve never been able to enter gameplay again since first launch. I pre-installed the game using the Xbox App with Gamepass, and then an update on launch day.
DxDiag.txt
Video of crash
https://drive.google.com/file/d/1mQdITj6al7x1jHjLLqNBtQlFNbiQExKy/view?usp=share_link
guazimodo's video is exactly how it happens. i just start up the game and a few moments later the screen goes exactly like how it goes in the video and the pc restarts completely.
After doing some testing i have found that putting the game in windowed mode allows it to run. the issue seems to come from me running the game in full screen. i will do some more testing. As of right now when i put the game in windowed mode it runs without crashing like in guazimodo's video.
This error no longer occurs in our testing since the August Update was released. Closing as fixed.