Minecraft pour window payant ne fonctionne pas sur mon pc msc
Résolu/Fermé
A voir également:
- Minecraft pour window payant ne fonctionne pas sur mon pc msc
- Mon pc s'allume mais ne démarre pas windows 10 - Guide
- Test performance pc - Guide
- Plus de son sur mon pc - Guide
- Mon pc rame que faire - Guide
- Google meet pour pc - Télécharger - Messagerie
2 réponses
Cyber-Jack
Messages postés
156
Date d'inscription
jeudi 7 avril 2016
Statut
Membre
Dernière intervention
8 juillet 2016
11
8 avril 2016 à 12:01
8 avril 2016 à 12:01
Bonjour,
Commence par nous envoyer se qu'il te dit
cordialement
Commence par nous envoyer se qu'il te dit
cordialement
8 avril 2016 à 13:32
[12:28:01] [Client thread/INFO]: Setting user: bouboule2020
[12:28:02] [Client thread/INFO]: LWJGL Version: 2.9.4
[12:28:03] [Client thread/INFO]: Reloading ResourceManager: Default
[12:28:03] [Sound Library Loader/INFO]: Starting up SoundSystem...
[12:28:03] [Thread-5/INFO]: Initializing LWJGL OpenAL
[12:28:03] [Thread-5/INFO]: (The LWJGL binding of OpenAL. For more information, see http://www.lwjgl.org)
[12:28:03] [Thread-5/INFO]: OpenAL initialized.
[12:28:03] [Sound Library Loader/INFO]: Sound engine started
[12:28:04] [Client thread/INFO]: Created: 1024x512 textures-atlas
[12:28:10] [Server thread/INFO]: Starting integrated minecraft server version 1.9.2
[12:28:10] [Server thread/INFO]: Generating keypair
[12:28:10] [Server thread/INFO]: Preparing start region for level 0
[12:28:11] [Server thread/INFO]: Preparing spawn area: 9%
[12:28:12] [Server thread/INFO]: Preparing spawn area: 20%
[12:28:13] [Server thread/INFO]: Preparing spawn area: 34%
[12:28:14] [Server thread/INFO]: Preparing spawn area: 47%
[12:28:15] [Server thread/INFO]: Preparing spawn area: 60%
[12:28:16] [Server thread/INFO]: Preparing spawn area: 73%
[12:28:17] [Server thread/INFO]: Preparing spawn area: 85%
[12:28:18] [Server thread/INFO]: Preparing spawn area: 99%
[12:28:18] [Server thread/INFO]: Changing view distance to 12, from 10
[12:28:19] [Server thread/INFO]: bouboule2020[local:E:51856b34] logged in with entity id 814 at (185.5, 65.0, 247.5)
[12:28:19] [Server thread/INFO]: bouboule2020 a rejoint la partie
#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007ff8da366c17, pid=4784, tid=7912
#
# 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:
# C [ig9icd64.dll+0x16c17]
#
# 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\clement.bernabei\AppData\Roaming\.minecraft\hs_err_pid4784.log
#
# If you would like to submit a bug report, please visit:
# http://bugreport.sun.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
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
voilà ce qu'il ne dit mais je n'arrive pas à le traduire
Super si tu peux m'aider!!!!
8 avril 2016 à 14:40
C:\Users\clement.bernabei\AppData\Roaming\.minecraft\hs_err_pid4784.log
8 avril 2016 à 17:32
Modifié par Cyber-Jack le 8/04/2016 à 22:03
puis ouve : Roaming puis ouvre hs_err_pid4784.log
et envoie moi se qui est ecrit
8 avril 2016 à 22:16
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007ff8da366c17, pid=4784, tid=7912
#
# 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:
# C [ig9icd64.dll+0x16c17]
#
# Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
#
# If you would like to submit a bug report, please visit:
# http://bugreport.sun.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
Est ce suffisant ? Merci de te pencher sur mon problème