[MC-32606] JVM Crash in ig#icd64.dll (Broken Intel graphics card driver)

For 1.10+ Users

If you are experiencing this issue after upgrading to 1.10, but did not for older versions of the game, the following instructions may solve the issue:

Increase allocated RAM from 1GB to 2GB (only applicable to 64 bit users)
- In the Edit Profile menu in the Launcher, check the JVM Arguments box, and change the -Xmx1G argument to -Xmx2G
Change Video Settings in-game (Options -> Video Settings)
- Enable VSync
- Disable VBOs
  If all of these did not correct the issue, follow the remainder of the instructions on this page, or seek assistance from the Mojang Support Center.

Mod Notice

These crashes are caused by faulty display drivers which are provided by Intel or your OEM. Your best bet is to either upgrade to the latest, or if that caused it, downgrade to a version which does not cause these crashes.

This issue has also been known to occur when conflicting with other software, such as custom Windows themes, game or screen recording software (regardless if running), and Evolve.

If the crash only occurs when opening a world, it may be caused by the VBOs video setting, when used with certain intel drivers. Disabling this setting, or updating the drivers may correct the issue. You can also attempt toggling the VSync option.

Some users have reported increasing the maximum memory for the game to correct this issue. In the launcher, click Edit Profile, and check the JVM Arguments box. For 64 bit users, change the -Xmx1G argument to -Xmx2G to allocate 2GB of memory.

Information on how to update your graphics drivers can be found HERE.
The downloads for appropiate drivers can be found on THIS page. Make sure to uninstall your previous drivers, a guide for this can be found HERE.
If you require further help, try one of the community options on the Mojang Support Center.

Full List of error codes, plus download location of updated driver (if available, uninstall of previous drivers required):

ig7icd32.dll
ig7icd64.dll
ig75icd32.dll
ig75icd64.dll
ig8icd64.dll (Driver)
ig9icd64.dll (Driver)

FWIW, this is probably a duplicate of MC-24247 but there was insufficient information for me to say this for sure. I cannot find any other duplicates.

I can successfully launch Minecraft, but after a random amount of time (less than 5 minutes), the video driver crashes with the message "Display driver stopped responding and has recovered".

I can force the issue with a very arbitrary key sequence: while playing in-game, press ALT+TAB to return to the Windows desktop. Expected result: Minecraft should revert to the menu as if we had pressed Escape, and I should be task-switched to whereever I ALT+TAB'd to. I should be able to ALT+TAB back to minecraft, select "back to game", and continue playing.

Using the Profiles feature of the Launcher, the video driver crashes on Minecraft 1.6.4 and Minecraft 1.6.2 – **but does not crash on 1.5.2 nor 1.5.1. I did not try earlier versions**. It also DOES NOT crash on snapshot 13w38c .

I have recorded my trials & tribulations here:
http://www.minecraftforum.net/topic/1963062-weird-minecraft-issue/

I am logging this issue with Mojang because something must have changed between 1.5.2 and 1.6.2 to trigger this issue ('trigger', not 'cause') ... and perhaps the re-write for 1.7 has fixed it. Don't know. You're smarter than I am. 🙂

Let me know what other information I can provide. My kids love Minecraft, and their old Windows 7 laptop bit the dust, hence buying the new one, which they still can't play...

Thanks, Ted.

Linked issues

is duplicated by 1160

MC-50030 I chose a shaders mod and tried to enter my singleplayer world, and it crashed, though i am not sure is this my problem or a bug. Resolved

MC-51858 Whenever I try to enter a server the game crash's I tried single player but that crashes to Resolved

MC-61968 Bug Resolved

MC-63018 A crash while using vbs Resolved

MC-69090 Java crashes when opening a world Resolved

1155 more links

relates to 2

MC-180529 TrueType fonts crash on Intel Graphics Resolved

MC-62198 JVM crash when loaded with VBO (Vertex Buffer Object) enabled Resolved

Attachments

crash-2013-09-25_22.02.38-client.txt

crash-development-console.txt

hs_err_pid2768.log

Comments 62

Talven81 2013-09-25T20:47:13Z

I suspect the new changes may be what's causing this. I am resolving this as a duplicate of MC-297 as I suspect your graphics drivers are out of date. The following may resolve your issue... if not please include the crash report.

Please update your graphics card drivers following these instructions: Updating Graphics Card Drivers.
If you have not, please use the search function in the future, to see if your bug has already been submitted.

Do not rely on automatic searches for driver updates.
Do not use Windows Update or Device Manager - Microsoft doesn't install OpenGL, they promote DirectX.
If you know the brand and type of your graphics card, go to the links provided above and search manually for the most recent driver for your card. The automatic detection tools of the card manufacturers are not recommended.

If all that won't help, please use the Mojang Support Center.

Ted Taylor 2013-09-25T21:17:51Z

Actually, this cannot be a duplicate of MC-297 because I do not get either of the errors or crashes that are indicated in that ticket. Everything launches. Granted, the issue I am describing may be related to the issue.

Also, I cannot update the graphics drivers because
a) I have tried the latest version of Dell-supplied drivers v9.18.10.3165
b) I have tried the latest version Intel-supplied drivers v9.18.10,3257
c) I have tried the latest BETA version of Intel-supplied drivers v10.18.10.3282 (these are for Win8.1 but seems to work otherwise on my Win8.0). These drivers were released on September 18, 2013 - barely 7 days ago. They are not out of date. This is the link : https://communities.intel.com/docs/DOC-21232 .

The attached two print-screens are the bottom of the Snooper Settings page, as requested, from 1.5.2 (after downloading the mentioned Minecraft.exe which appears to be an old launcher) as well as the same page from 1.6.4, using the production launcher. I have also attached the a print-screen post-crash. All I did was play for 30 seconds on 1.6.4

You say " I suspect the new changes may be what's causing this ". I would presume that those same changes are also present in snapshot 13w38c. I can play that version without any crash. Curious.

Please "un-resolve" this issue, as it certainly is not resolved. I would like to work with you to find out how to fix the issue. Perhaps the solution is "wait until 1.7 is released". That would be a shame for the kids.

Ted.

PS: Attachments coming, once I figure out how to use this website. 🙂

Ted Taylor 2013-09-25T21:18:31Z

Attachments added as requested.

Talven81 2013-09-25T22:18:01Z

Hmm not exactly what we need... however reopened.

Please provide the crash report from ([minecraft|http://hopper.minecraft.net/help/finding-minecraft-data-folder]/crash-reports/crash-<DATE>-client.txt). Please attach it so that we can diagnose your issue.

If there is no crash report...

Please force a crash by pressing F3 + C for 10 seconds while in-game and attach the crash report ([minecraft|http://hopper.minecraft.net/help/finding-minecraft-data-folder]/crash-reports/crash-<DATE>-client.txt) here.

Ted Taylor 2013-09-26T02:09:46Z

OK, see attached crash report. I had to force it.

To be completely clean, I :
a) completely deleted my %AppData%\.minecraft folder
b) Ran MineCraft in full screen mode (MC had to re-download, as expected)
c) Pressed ALT+TAB to access the desktop. Graphics driver crashed.
d) Rebooted to reset the stage.
e) Checked for the %AppData%\.minecraft\crash-reports folder (none existed).
f) Ran MineCraft in full screen mode,
g) Pressed F3 + C for 10+ seconds.
h) The manually-triggered crash report was generated and attached!

Please let me know my next step. 🙂

Ted.

52 more comments

Ted Taylor 2013-09-27T04:26:51Z

Is there anything else I can do or provide, to help?
Ted.

Ted Taylor 2013-09-28T12:23:47Z

In fiddling with the configuration, I found more detail. To get there, I swapped out the hard disk drive, installed Windows 7 x64 (retail) on it, and just the Intel Chip Drivers, Intel HD Graphics, Java 1.7.0u25, and Minecraft 1.6.

I also changed my launcher settings to keep the launcher window open.

The issue still occurs (play game in full screen mode, press ALT+TAB to return to the desktop, bang the video drivers fail) ; BUT, I see some information in the 'Development Console' window:

Client> #
Client> # A fatal error has been detected by the Java Runtime Environment:
Client> #
Client> # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x000000000c1c1c82, pid=2768, tid=2780
Client> #
Client> # JRE version: 7.0_25-b17
Client> # Java VM: Java HotSpot(TM) 64-Bit Server VM (23.25-b01 mixed mode windows-amd64 compressed oops)
Client> # Problematic frame:
Client> # C [ig75icd64.dll+0x1c82]
Client> #
Client> # Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
Client> #
Client> # An error report file with more information is saved as:
Client> # C:\Users\Ted\AppData\Roaming\.minecraft\hs_err_pid2768.log

The full text of the Development Console, plus the quoted hs_err_pid2768.log, are now attached.

Is there any further assistance available from Mojang ?

Ted.

Ted Taylor 2013-10-02T02:03:31Z

Hmmmm. Marking this issue as "resolved" would seem to imply that Minecraft is playable, which it certainly is not.

Disappointed, (and with even more disappointed kids),
Ted.

kumasasa 2013-10-02T06:30:07Z

Sorry, but crashes in 3rd party software outside of Minecraft, don't belong here.
Did you report this to Intel ? What did they say ?

Ted Taylor 2013-10-02T12:57:49Z

Kumasasa,

I understand the position you are in, but in reality, it takes TWO parties in order to declare an incompatibility.

Minecraft 1.6.x is triggering the condition that causes the display drivers to fail. These are the two parties. "Minecraft 1.6.x" is comprised of code written directly by Mojang, and third-party libraries chosen by Mojang and included in the distribution (eg ljwgl ). I have to come back to the fact that the latest snapshot (iirc, 13w39c) , on the exact same hardware and video does NOT trigger the display drivers to fail. If there was a fault in the video drivers exclusively, it should continue to fail and fail and fail regardless of what the Mojang code was doing.

The minimum acceptable outcome to me would be all four of:
a) confirmation from Mojang that there is a problem in MC 1.6.x with this particular configuration.
b) confirmation from Mojang that a specific line of program code in MC 1.6.x (or data being used by MC 1.6.x) is triggering the condition ... ie, when running the program in debug mode, if a Mojang engineer changes that line or data, the condition is no longer triggered)
c) confirmation from Mojang that said line of program code or data no longer exists in the latest snapshot (iirc, 13w39c).
d) confirmation from Mojang that said line of program code or data will not be re-introduced into the next versions of Minecraft official releases.

A bonus would be to have an approximate date of the next versions of MC official releases ... a date that I can tell my kids that they have to wait for before they can once again play what is (and hopefully will still be) one of their favourite games.

FYI, I did report the issue to Intel here: https://communities.intel.com/thread/45162 THAT is a whole other set of disappointment.

Still not able to run MC,
Ted.

Torabi 2013-10-18T21:39:47Z

And what if the Minecraft code is correct, and it is the driver that is not? Should Mojang avoid using a specific line of code because it fails on some specific piece of hardware or driver, when it works fine on all others? If a driver claims to have some capability, but crashes when a program makes use of it, then it's the driver's fault.

Regardless, if the issue no longer occurs in the latest snapshot, then the issue should be fixed in the next release (1.7). That should be an acceptable outcome. Nobody is obligated to confirm anything about closed-source code to you. Nor do they have any obligation to promise that they will not use any particular lines of code or graphical features in the future. If they are to continue to improve the game, the code must change. If you don't like new changes, then stick to a version you like. You are not forced to update, and they are not obligated to restrict themselves to updates that please you.

Why can't your kids play 1.5.2, or the latest snapshot, if those work without problems? Why must it be 1.6.x, or the next official release?

Ted Taylor 2013-10-18T21:52:23Z

Wow. Just wow.

I thought this was a Mojang Inc official bug tracking system. Any good company would want to actually help their customers. And perhaps they would want to know what, exactly, is causing the crash and perhaps work around it, so that they could gain even more customers.

But since you asked...
Why not 1.5.2 ? I guess I could ; that is the version that I purchased. With my money. To Mojang.
Why not the snapshots? They tend to crash for other reasons not related to the Intel HD Graphics card.

Besides, they would like to be able to interact with others via multiplayer, and there are not many servers running the snapshots (if any).

I would appreciate it if a forum moderator would lock this thread. It is serving no purpose.

Torabi 2013-10-18T22:20:26Z

This is the official Mojang bug tracker. However, I am just another user, and do not represent Mojang in any capacity. Even the moderators are just unpaid volunteers.

While a good company may want to help their customers, that does not necessarily mean it is economically feasible or even logically possible to provide individualized service to each and every one of them. They have over 12 million customers, and only 36 employees. You're selfishly demanding that they take the time to explain their code to you, when they could instead take the time to work on the game, which benefits all their customers.

It would be better if Intel fixed their code, instead of Mojang working around it.

iain lewis 2015-10-25T17:49:46Z

question to the mods, how do you get some of the bugs (such as the exiting full screen) infor to mojang?

kumasasa 2015-10-25T18:00:47Z

@@unknown: Please use https://www.reddit.com/r/Mojira/ for meta questions.

iain lewis 2015-10-26T22:19:40Z

my error got sent to here too but i highly douubt that its the graphics card because i can play on stable 1.7.10 in a different environment (different folder and different set up path but same laptop with same software) and nothing crashes

Lacolus 2016-01-19T16:53:23Z

You said to turn off the VBOs setting. I saw that it was already off, so I turned on VBOs and VSync. It didn't crash when opening the world this time.

Danica Swanson 2016-03-02T00:40:11Z

I don't think my drivers are faulty, as I played 1.8 successfully less than 10 hours prior to 1.9 and the crashing. I literally played before bed, woke up, and crash.
I have updated my drivers, fresh install of java, updated my launcher, played with the VBO and Vsync options, and still just do nothing but crash. Somebody even suggested turning off clouds and shadows. That didn't help either. I guess I only get to play 1.8. Bummer.

Gothrung 2016-03-02T02:39:23Z

I also doubt it's a driver issue for a couple reasons. I had this same issue and when I open minecraft with the laucher icon in the .minecraft folder, minecraft starts and runs. I too updated my drivers and other software and it didn't allow me to start minecraft 1.9 worlds when I launched from the minecraft icon.

kumasasa 2016-03-02T07:09:21Z

@@unknown , @@unknown, @@unknown:
While in-game press F3 and look at the driver version at the top right.
When there is a driver version "8.xx.xx.xx", "10.xx.xx.xx" or "20.xx.xx.xx" then your drivers are outdated & broken.
The latest release from Intel is version "15.xx.xx.xx", download that from http://downloadcenter.intel.com

In case of doubt, contact the help chat of the Mojang Support Center.

Danica Swanson 2016-03-02T15:41:50Z

I believe I have resolved my issue. I have a 64bit operating system and a 32bit browser. So Java auto detected that I should have a 32 bit version of Java. Last night I tried downloading the 64 bit Java by selecting it from Oracle's list instead of letting them decide what I need. I played Minecraft 1.9 for about an hour without crashing. There were a couple little lags with the sand and gravel falling in the water temple I just finished draining, but that happened from time to time before the update and I can live with that.

Sammy 2016-03-02T17:46:59Z

I need help. I did the steps and fully updated my drivers, but the game still crashes.

jredfox 2016-03-03T19:40:19Z

My graphics card is 100% up to date and it still crashes. My graphics card works with all other versions of minecraft except 1.9 so I an't updating till you fix this SHIT!

Amber Dittbrenner 2016-03-03T23:01:35Z

Try increasing the memory. I had the issue with the crashes and was told my drivers were outdated also. I ended up having to increase the memory to 3g in order for minecraft to run properly on 1.9.

A Shaw 2016-03-03T23:36:27Z

I had this issue.
I found my drivers outdated (by 2 days!) and fixed them, but it didn't fixed this. Also, my java was up to date. Did the memory thing and it seems to be working fine now (or at least as well as it did before).
Specifically, I changed it from 1G to 5G on the profile. Although now the memory allocation says 4551 instead of 49xx like it used to when I did that for 1.8.9. Not sure why this is but probs worth making a note of.

GuiG4merPT 2016-03-07T19:23:46Z

Thx LY

Claudio Esposito 2016-03-07T22:02:20Z

thanks now it's ok

Nimrod Rappaport 2016-03-11T09:42:47Z

Thank you. you helped me lot

khush paliwal 2016-03-15T08:11:12Z

thank you helped me immensley i really appreciate it

Jordan Marcum 2016-03-17T00:14:58Z

Graphics seem to be a complete mess to me on any single player mode and multiplayer mode, suggestions?

kumasasa 2016-03-17T00:56:40Z

@unknown: Read the text on yellow background of the description of this ticket.

James Murray 2016-04-08T10:34:10Z

Exact problem encountered 8 April as described on Surface Pro 4 i5 with Minecraft 1.9.2.
Last time of uneventful operations 1 April.
Followed "For 1.9 Users" instructions exactly as described above.
Problem solved.
Many thanks for your diligence, and kind regards.

Walter 2016-04-16T07:45:26Z

Thanks... Now run well.-

Lucy Anderson 2016-05-01T19:55:31Z

Hi - I am having the same issue as Pamela's son. How did you fix the problem?

James Smith 2016-05-03T01:23:08Z

Thanks a lot! I can now play Minecraft again! (it was the VBOs that fixed it for me. I also changed the -Xmx1G to -Xmx2G. Maybe both of them together)

Lucy Anderson 2016-05-03T11:42:24Z

Me too James. Thanks for your help mods.

Philip Hughes 2016-05-07T08:40:59Z

This helped. I made my issue, as I didn't think it was a video issue.

Greg Lesher 2016-05-12T14:06:42Z

Tried the above bot response fix, still crash as soon as it opens

Greg Lesher 2016-05-12T14:09:11Z

This is getting crazy, why should I need to be some kind of computer tech just so my son can play the game? I need a refund!!

Noah Briggs 2016-05-26T02:45:25Z

What fixed it with me is I rolled back then re-updated my Intel(R) HD Graphics Family under Display Adapters in Device Manager. At least the error only happens for me after the game crashes when trying to exit out of full screen mode using the F11 key or ALT+TAB off the screen (less frequently though). I'm not going to test and see if the error will continue to happen by using the keys since it causes the entire display driver to stop functioning and gives me a BSOD. If it helps I think java can corrupt the .DLL files the display adapter especially if the game crashes or closes unexpectedly.

Eevee Malymeik 2016-06-09T01:06:55Z

Even after doing what the suggestions said to do, it didn't work. I'm TRYING to play 1.9+ versions but it keeps f*cking crashing, got any other ideas so this'll work? That'd be great, perhaps trying to fix it before losing money from it too would be a good idea.

Daniel Maestre 2016-06-09T23:04:23Z

I had the crash issue: every time I logged into any world it crashed almost instantly, but I solved it just by turning off the option "Use VBOs". I always played Minecraft with that option turned off, but updating to 1.10 has put that thing on without my knowledge, so I didn't know what was wrong. My Intel (R) HD Graphics is one of those graphic cards that can't stand the VBOs feature. Be aware when you update the game, because it automatically changes your video settings options very often. Hope this helps.

Cameron Padgette 2016-06-13T00:04:56Z

i disable vbo it woked

CreativeGuy2013 2016-06-14T18:25:53Z

FIX: IT USUALLY HAPPENS IF YOU HAVE OPTIFINE AND TURN UP TO 32 redner distance, then load the same options file in regular mc

Aaron Rhodes 2016-06-22T16:05:36Z

That's odd. My use vbo's option somehow got switched to true, and that was causing the problem. Did they set that option to true when updating to 1.10, because I know I have left it false ever since the use vbo's option started causing problems.

Aaron Rhodes 2016-06-22T16:20:07Z

On the official minecraft wiki, it says that vbo's are enabled by default, overriding previous settings when updating. Don't they know that vbo's have been causing a lot of trouble for a lot of people? Some people don't have the option to update their graphics cards, so will we just be forced to deal with this every time they update minecraft?

Torabi 2016-06-22T17:07:36Z

Enabling VBOs fixes issues for more people than it breaks things for, so it's been switched on by default. The options.txt file now has a version line so it can track whether you're upgrading to a new version or not, and as far as I know, automatically enabling VBOs should only happen once. If you set it to false, it won't set it back to true.

George Quilitz 2016-12-22T03:02:25Z

I tried everything there but the game still crashes:

Completely ignored arguments: [--nativeLauncherVersion, 307]
[22:00:41] [Client thread/INFO]: Setting user: UltimateDude2006
[22:00:43] [Client thread/WARN]: Skipping bad option: lastServer:
[22:00:43] [Client thread/INFO]: LWJGL Version: 2.9.4
[22:00:43] [Client thread/INFO]: Reloading ResourceManager: Default
[22:00:44] [Sound Library Loader/INFO]: Starting up SoundSystem...
[22:00:45] [Thread-5/INFO]: Initializing LWJGL OpenAL
[22:00:45] [Thread-5/INFO]: (The LWJGL binding of OpenAL.  For more information, see http://www.lwjgl.org)
[22:00:45] [Thread-5/INFO]: OpenAL initialized.
[22:00:45] [Sound Library Loader/INFO]: Sound engine started
[22:00:50] [Client thread/INFO]: Created: 1024x512 textures-atlas
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x000000006bb21580, pid=13956, tid=7340
#
# JRE version: Java(TM) SE Runtime Environment (8.0_25-b18) (build 1.8.0_25-b18)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.25-b02 mixed mode windows-amd64 compressed oops)
# Problematic frame:
# V  [jvm.dll+0xa1580]
#
# Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
#
# An error report file with more information is saved as:
# C:\Users\Robin\AppData\Roaming\.minecraft\hs_err_pid13956.log
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.sun.com/bugreport/crash.jsp
#
AL lib: (EE) alc_cleanup: 1 device not closed
Java HotSpot(TM) 64-Bit Server VM warning: Using incremental CMS is deprecated and will likely be removed in a future release

[Mod] Neko 2016-12-22T03:07:47Z

@unknown, that is not this crash. Use the community support link below.

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

Patrycja Siwkowska 2017-02-05T19:24:11Z

I have changed 1gb to 2gb,and nothing.it did not even make me go to the video settings in game to change it

Fabian Kirchdorfer 2017-03-05T11:54:07Z

Thanks! This worked!!!

spencer 2017-10-11T01:38:04Z

Nothing stil wont work

salias tee simon 2019-03-22T05:52:09Z

Refered here from report issue concerning snapshot 18w43c ... which is following 1.13 official release. so aparently this old issue is still going on. Nothing I have so far found suggested here, has worked for me in the slightest and being that vbo's can no longer be turned off, is of no help either. My integrated intel64 graphics drivers are completely up to date (as far as I currently know, anyway). my computer, an Acer Aspire, running OS 8.1 64bit, is fine with 1.12 and 1.13.2 Running no mods, or custom screensavers or other programs which could conflict (no recording software and not even sure what Evolve is.) Minecraft has only stumbled when encountering snapshot 18w44a.. (and continuing forward) which is prior to (as of the moment of posting this) the upcoming release of 1.14.

It loads in the snapshot off the launcher, no problem. Takes me to the server/actual game world option page. I choose a world, or create one. it loads, and I catch a glimpse of the world itself. (maybe a few seconds worth of time) then before I can do anything, it crashes me back to the launcher with no crash report listed on the notice. The message reads, simply, "An unexpected issue occured and the game has crashed. We're sorry for the inconvience"...and a javaw note, stating it has crashed as well. It happens everytime, without fail, no matter how many times I try.

is this really intel graphics fault? ahhk! how to fix?

Hoping this additional information is of some help in resolving this ongoing issue quickly.

salias tee simon 2019-03-25T20:45:23Z

Yes, it might just be. could try this. dxdiag-display should show year. dl assist, uninstall and reinstall to force latest driver for your computer. Don't believe the auto-update on your computer.. check the year published.

Erin Lauder 2019-04-26T09:16:28Z

I have the same problem as Salias, however my game crashes as I click play. Whether to create a world or load a previous one. I've tried every suggestion given to me that has been suggested to no luck.

I can play 1.13.2 just fine with no issues, 1.14 is giving me all the issues.

Kenneth Hook 2019-10-24T15:20:15Z

So what should I do if my JVM Argument is already allocating 2GB of RAM, uninstalled and reinstalled my graphics driver, updated the driver, repaired minecraft, deleted and reinstalled minecraft, and even tried running it under a compatability of previous windows versions? My graphics driver isn't broken because I can still play the Minecraft Windows 10 Version and Yu-Gi-Oh Duel Links. I Haven't changed the video settings because I can't get into the game to change those.

[Mod] violine1101 2019-10-24T16:39:55Z

For technical assistance, please contact Community Support, linked below.

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

Joshua 2019-10-26T18:11:53Z

I have no idea if this could fix it for everybody, but, for me Minecraft crashed on launch every time because of a texture pack. While I was playing it crashed when I tried to use the texture pack and I couldn't get Minecraft to open it until I removed it from resourcepacks in .minecraft - You can find the .minecraft folder by going to the windows search bar and typing in %appdata%. You'll find the .minecraft folder in there.

Jovanni 2019-11-24T14:49:14Z

Here I have my solution: This error happened when updating the drivers, this specific driver, Display adapters, ise with an external program, what I suggest is that if that program has a rescue center, restore that driver, restart the PC and ready.

Juan Pablo P. 2020-08-14T00:32:50Z

Hello, I have the same problem but in the future. I wanted to know if you could solve it.

finally someone who shares my problems lol 🙂

Arisa Bot 2021-03-07T15:11:09Z

An attachment with a disallowed file extension has been removed from this ticket.

Executable files and documents are not allowed as attachments.
Please attach crash reports, log files and screenshots as they are instead of pasting them into a document.
_{-- I am a bot. This action was performed automatically! Please report any issues on}_Discord_or_Reddit

Bartek Wojtaś 2021-03-09T07:12:04Z

nie działa mi jakie to jest słabe i gówniane