For some reason my minecraft won't load and videos in my PC are extremely choppy, and get pixelated 5 seconds in the video. YouTube and other online videos work just fine. Crash report:
---- Minecraft Crash Report ----
// But it works on my machine.
Time: 1/7/16 4:26 PM
Description: Initializing game
org.lwjgl.LWJGLException: Pixel format not accelerated
at org.lwjgl.opengl.WindowsPeerInfo.nChoosePixelFormat(Native Method)
at org.lwjgl.opengl.WindowsPeerInfo.choosePixelFormat(WindowsPeerInfo.java:52)
at org.lwjgl.opengl.WindowsDisplay.createWindow(WindowsDisplay.java:252)
at org.lwjgl.opengl.Display.createWindow(Display.java:306)
at org.lwjgl.opengl.Display.create(Display.java:848)
at org.lwjgl.opengl.Display.create(Display.java:757)
at org.lwjgl.opengl.Display.create(Display.java:739)
at bao.ag(SourceFile:340)
at bao.f(SourceFile:713)
at net.minecraft.client.main.Main.main(SourceFile:148)
A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------
-- Head --
Stacktrace:
at org.lwjgl.opengl.WindowsPeerInfo.nChoosePixelFormat(Native Method)
at org.lwjgl.opengl.WindowsPeerInfo.choosePixelFormat(WindowsPeerInfo.java:52)
at org.lwjgl.opengl.WindowsDisplay.createWindow(WindowsDisplay.java:252)
at org.lwjgl.opengl.Display.createWindow(Display.java:306)
at org.lwjgl.opengl.Display.create(Display.java:848)
at org.lwjgl.opengl.Display.create(Display.java:757)
at org.lwjgl.opengl.Display.create(Display.java:739)
at bao.ag(SourceFile:340)
-- Initialization --
Details:
Stacktrace:
at bao.f(SourceFile:713)
at net.minecraft.client.main.Main.main(SourceFile:148)
-- System Details --
Details:
Minecraft Version: 1.7.10
Operating System: Windows 8.1 (x86) version 6.3
Java Version: 1.8.0_25, Oracle Corporation
Java VM Version: Java HotSpot(TM) Client VM (mixed mode), Oracle Corporation
Memory: 42872528 bytes (40 MB) / 125042688 bytes (119 MB) up to 523501568 bytes (499 MB)
JVM Flags: 6 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx512M -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:-UseAdaptiveSizePolicy -Xmn128M
AABB Pool Size: 0 (0 bytes; 0 MB) allocated, 0 (0 bytes; 0 MB) used
IntCache: cache: 0, tcache: 0, allocated: 0, tallocated: 0
Launched Version: 1.7.10
LWJGL: 2.9.1
OpenGL: ~~ERROR~~ RuntimeException: No OpenGL context found in the current thread.
GL Caps:
Is Modded: Probably not. Jar signature remains and client brand is untouched.
Type: Client (map_client.txt)
Resource Packs: []
Current Language: ~~ERROR~~ NullPointerException: null
Profiler Position: N/A (disabled)
Vec3 Pool Size: 0 (0 bytes; 0 MB) allocated, 0 (0 bytes; 0 MB) used
Anisotropic Filtering: Off (1)
It says "We're sorry, but it seems there was an error trying to load certain aspects of the game. To solve this error, it is recommended that you update your graphic drivers. "
The latest Java works fine with the latest MC version.
When I play FTB or MC 1.7 moded or not I have to load a legacy version of Java or I get the exact results you do.
Try it out, see if it works. Before you do make a copy of your MC folder and then try it. the worst that can happen is you have to delete your copied MC and change the name of your "copy of minecraft" to "minecraft".
When Java or any software decides to drop a function or procedure in favor of something else such as an improved method, or god forbid actually use
a "reserved for future use" type of thing, that a different company utilized in it's software, said software will no longer function as intended.
Why will it not function anymore? Because the software is not forward compatible. Java has done this a few times. It's called deprecation.
You can see there is a warning that is given to everyone running current MC with current Java when the game is closed and the launcher debug window still open. The JVM issues this warning.
"Java HotSpot(TM) 64-Bit Server VM warning: Using incremental CMS is deprecated and will likely be removed in a future release"
What this means is that sometime in the future this version of minecraft will not run on a pending new version of Java.
That quite literally means that Minecraft is not a program that is to be considered as forward compatible.
However I am sure that Microsoft/Mojang will update Minecraft at that time in the future.
The original poster provided the following information.
[b]"Minecraft Version: 1.7.10[/b]
[b]Operating System: Windows 8.1 (x86) version 6.3[/b]
[b]Java Version: 1.8.0_25, Oracle Corporation[/b]
[b]...[/b]
[b]Is Modded: Probably not. Jar signature remains and client brand is untouched."[/b]
I am sure google can yield you some rather detailed examples of the error message generated in the original post.
The fix to that issue [b]if[/b] your video drivers are up to date is to reinstall an older version of java.
If you would like to replicate the problem you will need to d/l legacy versions of java and remove current versions, not just disable them.
My reference to modded versions is only because the only time I ever generated that error, unintentionally, was when using a mod launcher to launch
moded versions of MC or I was running an older version of MC with an new version of Java. If that mention for reference violates some sort of weird "never reference anything modded in an un-modded only forum" then I suggest that you ignore it as it was intended to state the only time I have ever encountered that particular error that the original poster posted. Which I felt necessary to the conversation at the time. It is not the same as saying "I only ever encountered that while eating cheese." and saying the problem is because of cheese. Nor did I state that the original poster had the problem because of mods. Nor did I state that the fix only applies when there are mods. Nor was my intent to discuss mods. Hence the phrasing "When I play FTB or MC 1.7 [b]modded or not[/b] I have to load a legacy version of Java or I get the exact results you do."
The portion of the statement containing the word "not" conveys, contextually, the idea of un-modded and strictly vanilla Minecraft, which adheres to the topic constraints that " This IS "Unmodded[/b] Client Support" ". So, if you have something to contribute that is relevant and on topic please do.
As for " And yes, I do believe you have absolutely no ideea of waht you're talking about." I suggest you take a minute and read the entirety of the posts. If you read the posts you will learn the OP is using an older version of MC, with a newer version of Java. Additionally. those versions are not the current versions of either mc or java and match the time frame of the problems of this nature that occurred then, with these versions and were fixed utilizing the method prescribed then.
For some reason my minecraft won't load and videos in my PC are extremely choppy, and get pixelated 5 seconds in the video. YouTube and other online videos work just fine. Crash report:
---- Minecraft Crash Report ----
// But it works on my machine.
Time: 1/7/16 4:26 PM
Description: Initializing game
org.lwjgl.LWJGLException: Pixel format not accelerated
at org.lwjgl.opengl.WindowsPeerInfo.nChoosePixelFormat(Native Method)
at org.lwjgl.opengl.WindowsPeerInfo.choosePixelFormat(WindowsPeerInfo.java:52)
at org.lwjgl.opengl.WindowsDisplay.createWindow(WindowsDisplay.java:252)
at org.lwjgl.opengl.Display.createWindow(Display.java:306)
at org.lwjgl.opengl.Display.create(Display.java:848)
at org.lwjgl.opengl.Display.create(Display.java:757)
at org.lwjgl.opengl.Display.create(Display.java:739)
at bao.ag(SourceFile:340)
at bao.f(SourceFile:713)
at net.minecraft.client.main.Main.main(SourceFile:148)
A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------
-- Head --
Stacktrace:
at org.lwjgl.opengl.WindowsPeerInfo.nChoosePixelFormat(Native Method)
at org.lwjgl.opengl.WindowsPeerInfo.choosePixelFormat(WindowsPeerInfo.java:52)
at org.lwjgl.opengl.WindowsDisplay.createWindow(WindowsDisplay.java:252)
at org.lwjgl.opengl.Display.createWindow(Display.java:306)
at org.lwjgl.opengl.Display.create(Display.java:848)
at org.lwjgl.opengl.Display.create(Display.java:757)
at org.lwjgl.opengl.Display.create(Display.java:739)
at bao.ag(SourceFile:340)
-- Initialization --
Details:
Stacktrace:
at bao.f(SourceFile:713)
at net.minecraft.client.main.Main.main(SourceFile:148)
-- System Details --
Details:
Minecraft Version: 1.7.10
Operating System: Windows 8.1 (x86) version 6.3
Java Version: 1.8.0_25, Oracle Corporation
Java VM Version: Java HotSpot(TM) Client VM (mixed mode), Oracle Corporation
Memory: 42872528 bytes (40 MB) / 125042688 bytes (119 MB) up to 523501568 bytes (499 MB)
JVM Flags: 6 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx512M -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:-UseAdaptiveSizePolicy -Xmn128M
AABB Pool Size: 0 (0 bytes; 0 MB) allocated, 0 (0 bytes; 0 MB) used
IntCache: cache: 0, tcache: 0, allocated: 0, tallocated: 0
Launched Version: 1.7.10
LWJGL: 2.9.1
OpenGL: ~~ERROR~~ RuntimeException: No OpenGL context found in the current thread.
GL Caps:
Is Modded: Probably not. Jar signature remains and client brand is untouched.
Type: Client (map_client.txt)
Resource Packs: []
Current Language: ~~ERROR~~ NullPointerException: null
Profiler Position: N/A (disabled)
Vec3 Pool Size: 0 (0 bytes; 0 MB) allocated, 0 (0 bytes; 0 MB) used
Anisotropic Filtering: Off (1)
Grim:
I did not make the claim that MC would not work with Java 8, that is where you misunderstand what I posted.
That was my fault for not being clear.
I agree, having a DxDiag would indicate the driver level and if it is up to date. Solving the question of the driver.
Which I alluded to in my second post.
(which was also not clearly indicated to the OP to verify the driver)
I'm not on board with the OS issue as I first encountered the error with W7x64 pro. Additionally the OP states 8.1 as the os.
So Mc_Knight would you mind posting a dxdiag and a complete launcher log? Also...when did this start happening?
A dxdiag would give us just about all we need. The "choppy video but youtube work fine" points to drivers, but could also be something else.
get us the dxdiag please.
If you are not sure how to get a dxdiag do the following:
ctrl-alt-del, select task manager, click file, click run new task, type dxdiag.exe press enter. let the program run, click save information...
(I chose this method to start dxdiag as I am unfamiliar with the nuances of win8.1 and this method is valid for windows since at least xp)
For some reason my minecraft won't load and videos in my PC are extremely choppy, and get pixelated 5 seconds in the video. YouTube and other online videos work just fine. Crash report:
---- Minecraft Crash Report ----
// But it works on my machine.
Time: 1/7/16 4:26 PM
Description: Initializing game
org.lwjgl.LWJGLException: Pixel format not accelerated
at org.lwjgl.opengl.WindowsPeerInfo.nChoosePixelFormat(Native Method)
at org.lwjgl.opengl.WindowsPeerInfo.choosePixelFormat(WindowsPeerInfo.java:52)
at org.lwjgl.opengl.WindowsDisplay.createWindow(WindowsDisplay.java:252)
at org.lwjgl.opengl.Display.createWindow(Display.java:306)
at org.lwjgl.opengl.Display.create(Display.java:848)
at org.lwjgl.opengl.Display.create(Display.java:757)
at org.lwjgl.opengl.Display.create(Display.java:739)
at bao.ag(SourceFile:340)
at bao.f(SourceFile:713)
at net.minecraft.client.main.Main.main(SourceFile:148)
A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------
-- Head --
Stacktrace:
at org.lwjgl.opengl.WindowsPeerInfo.nChoosePixelFormat(Native Method)
at org.lwjgl.opengl.WindowsPeerInfo.choosePixelFormat(WindowsPeerInfo.java:52)
at org.lwjgl.opengl.WindowsDisplay.createWindow(WindowsDisplay.java:252)
at org.lwjgl.opengl.Display.createWindow(Display.java:306)
at org.lwjgl.opengl.Display.create(Display.java:848)
at org.lwjgl.opengl.Display.create(Display.java:757)
at org.lwjgl.opengl.Display.create(Display.java:739)
at bao.ag(SourceFile:340)
-- Initialization --
Details:
Stacktrace:
at bao.f(SourceFile:713)
at net.minecraft.client.main.Main.main(SourceFile:148)
-- System Details --
Details:
Minecraft Version: 1.7.10
Operating System: Windows 8.1 (x86) version 6.3
Java Version: 1.8.0_25, Oracle Corporation
Java VM Version: Java HotSpot(TM) Client VM (mixed mode), Oracle Corporation
Memory: 42872528 bytes (40 MB) / 125042688 bytes (119 MB) up to 523501568 bytes (499 MB)
JVM Flags: 6 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx512M -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:-UseAdaptiveSizePolicy -Xmn128M
AABB Pool Size: 0 (0 bytes; 0 MB) allocated, 0 (0 bytes; 0 MB) used
IntCache: cache: 0, tcache: 0, allocated: 0, tallocated: 0
Launched Version: 1.7.10
LWJGL: 2.9.1
OpenGL: ~~ERROR~~ RuntimeException: No OpenGL context found in the current thread.
GL Caps:
Is Modded: Probably not. Jar signature remains and client brand is untouched.
Type: Client (map_client.txt)
Resource Packs: []
Current Language: ~~ERROR~~ NullPointerException: null
Profiler Position: N/A (disabled)
Vec3 Pool Size: 0 (0 bytes; 0 MB) allocated, 0 (0 bytes; 0 MB) used
Anisotropic Filtering: Off (1)
I think it is the Java version.
I seem to remember having this problem starting MC1.7 with Java 1.8.xxx
Try a legacy version of java such as Java 7. You will have to point your game launcher to the java 7 folder. I suggest a separate game profile.
Here is the link to the JAVA ARCHIVES at oracle.
Good luck.
It says "We're sorry, but it seems there was an error trying to load certain aspects of the game. To solve this error, it is recommended that you update your graphic drivers. "
Yes, and I'll wager your drivers are up to date too.
Get Java 7 ver. 1.7.60 I believe is the last version for java 7 that works properly with MC1.7, that should fix it.
What about 1.8?
The latest Java works fine with the latest MC version.
When I play FTB or MC 1.7 moded or not I have to load a legacy version of Java or I get the exact results you do.
Try it out, see if it works. Before you do make a copy of your MC folder and then try it. the worst that can happen is you have to delete your copied MC and change the name of your "copy of minecraft" to "minecraft".
Not all Java programs are forwards compatible with Java. Minecraft is one of them.
Which is one of the reasons there are different versions.
When Java or any software decides to drop a function or procedure in favor of something else such as an improved method, or god forbid actually use
a "reserved for future use" type of thing, that a different company utilized in it's software, said software will no longer function as intended.
Why will it not function anymore? Because the software is not forward compatible. Java has done this a few times. It's called deprecation.
You can see there is a warning that is given to everyone running current MC with current Java when the game is closed and the launcher debug window still open. The JVM issues this warning.
"Java HotSpot(TM) 64-Bit Server VM warning: Using incremental CMS is deprecated and will likely be removed in a future release"
What this means is that sometime in the future this version of minecraft will not run on a pending new version of Java.
That quite literally means that Minecraft is not a program that is to be considered as forward compatible.
However I am sure that Microsoft/Mojang will update Minecraft at that time in the future.
The original poster provided the following information.
[b]"Minecraft Version: 1.7.10[/b]
[b]Operating System: Windows 8.1 (x86) version 6.3[/b]
[b]Java Version: 1.8.0_25, Oracle Corporation[/b]
[b]...[/b]
[b]Is Modded: Probably not. Jar signature remains and client brand is untouched."[/b]
I am sure google can yield you some rather detailed examples of the error message generated in the original post.
The fix to that issue [b]if[/b] your video drivers are up to date is to reinstall an older version of java.
If you would like to replicate the problem you will need to d/l legacy versions of java and remove current versions, not just disable them.
My reference to modded versions is only because the only time I ever generated that error, unintentionally, was when using a mod launcher to launch
moded versions of MC or I was running an older version of MC with an new version of Java. If that mention for reference violates some sort of weird "never reference anything modded in an un-modded only forum" then I suggest that you ignore it as it was intended to state the only time I have ever encountered that particular error that the original poster posted. Which I felt necessary to the conversation at the time. It is not the same as saying "I only ever encountered that while eating cheese." and saying the problem is because of cheese. Nor did I state that the original poster had the problem because of mods. Nor did I state that the fix only applies when there are mods. Nor was my intent to discuss mods. Hence the phrasing "When I play FTB or MC 1.7 [b]modded or not[/b] I have to load a legacy version of Java or I get the exact results you do."
The portion of the statement containing the word "not" conveys, contextually, the idea of un-modded and strictly vanilla Minecraft, which adheres to the topic constraints that " This IS "Unmodded[/b] Client Support" ". So, if you have something to contribute that is relevant and on topic please do.
As for " And yes, I do believe you have absolutely no ideea of waht you're talking about." I suggest you take a minute and read the entirety of the posts. If you read the posts you will learn the OP is using an older version of MC, with a newer version of Java. Additionally. those versions are not the current versions of either mc or java and match the time frame of the problems of this nature that occurred then, with these versions and were fixed utilizing the method prescribed then.
So are we now on the same page?
Sorry, I missed this.
Version 1.8.xx MC works fine with Java 1.8xx
-
View User Profile
-
View Posts
-
Send Message
Moderatorplease post a dxdiag log
lets stay on topic for the OP's sake and fix his issue and not bicker between each other, this IS a driver issue, NOT a java issue
I agree, we should be looking to fix the issue. My second post was a nudge to confirm that his driver is up to date.
After that, the only think I can think of is the MC / Java conflict. Neither alone is a problem how ever if the version of java is the problem
It is readily fixed by installing the latest java and using the latest mc.
Mc_Knight: Is there any reason you are not using MC 1.8.9 or Java 1.8.6x
A DxDiag would help greatly.
Grim:
I did not make the claim that MC would not work with Java 8, that is where you misunderstand what I posted.
That was my fault for not being clear.
I agree, having a DxDiag would indicate the driver level and if it is up to date. Solving the question of the driver.
Which I alluded to in my second post.
(which was also not clearly indicated to the OP to verify the driver)
I'm not on board with the OS issue as I first encountered the error with W7x64 pro. Additionally the OP states 8.1 as the os.
So Mc_Knight would you mind posting a dxdiag and a complete launcher log? Also...when did this start happening?
A dxdiag would give us just about all we need. The "choppy video but youtube work fine" points to drivers, but could also be something else.
get us the dxdiag please.
If you are not sure how to get a dxdiag do the following:
ctrl-alt-del, select task manager, click file, click run new task, type dxdiag.exe press enter. let the program run, click save information...
(I chose this method to start dxdiag as I am unfamiliar with the nuances of win8.1 and this method is valid for windows since at least xp)
Updated java and to win10 it works! Sorry about leaving you guys hanging.. So yeah. Bye!