Ever since 1.8.1 and still here at 1.0.0, my minecraft has started rapidly crashing, well it's never actually crashed but it freezes and never goes back to a playable frame rate until I restart Minecraft.
It is not my hardware that is causing this issue.
CPU: i7 2600K @ 4.0GHz
GPU: GTX 550 Ti @ 1000MHz
RAM: 16GB @ 1600MHz
OS: 32-Bit Windows XP
I've been playing this game since 2/4/11 and I've been playing on maximum settings ever since, with a reliable 100-400 FPS.
Why is it that now, out of nowhere, since 1.8 was released my minecraft crashes randomly while the render distance is set to Far? Even on Far, I get well over 100 FPS but at times when I move a few blocks, it will crash.
I've tried all the stuff most people will suggest I do, like updating and downgrading GPU Drivers, testing the RAM, GPU and CPU for stability, setting the affinity for minecraft to run on one CPU core, trying different types of Java.. custom .bats to launch minecraft with more and less RAM, but nothing has worked.
in the options menu, when you switch to render distance far it now tells you that you need 64bit Java to run without crashing... Noticed the warning for the first time when i updated to 1.0 .I used to play with my distance on far also, but have had to get used to playing on normal... unless you upgrade to a 64bit java, looks like you just gonna have to get used to it too.
By the way an other tip, you can only use 3Gs of that Ram with a 32bit system, a complete waste. With a rig like yours you really should get a 64bit system just so you can use that wonderful ram of yours. I wouldn't recommend XP64 bit as it's actually Windows Server 2008 and is ultimately unstable anyways, from what I've heard. Windows 7 is where it's at, and with that rig you have no excuse really other then not affording it, which is understandable but it really doesn't do your system justice without it.
The problem is with the Java VM. you can't "fix" the Java VM. They also have good reasons (Sun-Microsystems and now Oracle side) to restrict the size of the Java Heap. That said, there are some command line parameters you can use to force it larger, but things could get messy. I don't know, myself, being that I actually use an Operating System version that makes use of my CPU, rather than having it run the CPU in 32-bit mode.
lastly, LOVE the fact that you have 16GB of RAM, of which 13 are sitting completely unused because you are one of those die-hards who thinks that a 10 year old Operating System on a new machine is somehow more performant.
Lastly, LOVE the fact that you have 16GB of RAM, of which 13 are sitting completely unused because you are one of those die-hards who thinks that a 10 year old Operating System on a new machine is somehow more performant.
The frustrating part is that prior to 1.8 I could run the game on Far distance with little to no problems. Occasionally the terrain would "disappear" in 1.7.3 (maybe once every 10-30 minutes) and a DC/RC fixed it. Prior to 1.7, I had zero such issues.
So here's my personal timeline:
1.6 and lower: Minecraft runs great.
1.7: Occasionally, the game would make terrain "disappear" on Far. A disconnect/reconnect would fix this.
1.8: The terrain disappears on Far (if not outright crashing the game). The only thing that fixes this is to restart the Minecraft client.
1.0: Same as 1.8 - pretty much unplayable on Far setting.
Aren't games supposed to get better as they are developed? Loads of new features, rendering, lighting, etc. were put in with very little QA testing and/or efficiency IMO. :dry.gif:
@ Shadow11377 : Go get Win 7 64 bit as fast as you can ! Seriously !
You are wasting 13 Gb (at least) of Ram without it !
Oh... And you might want to make a before after test with some performance tools :laugh.gif: If you can afford Win7 in any way, do it ! You will cry about why you didn't do that sooner :wink.gif:
The problem is you are looking at is as a Minecraft issue. It's a Java issue. You are using a feature that is optimized for 64-bit Java, with a 32-bit OS. And I fail to see how updating your OS to a recent release is not necessary. The only reason to ever have XP is if it's a computer linked up to a server, like at work. And even then, why would a server based computer have 16gigs of RAM. Just need to stop sticking with a "if it ain't broke why fix it" mentality. Improve your experience and upgrade. Not just for Minecraft. Otherwise, you may as well just sell your rig, and buy a bargain bin PoS for 300-500$.
Rollback Post to RevisionRollBack
Quote from GretchenMC »
"I'm an underaged girl on the internets, come play with me and we can video chat!"
There is no excuse for running a 32-bit OS with 16 GB RAM that you cannot even use. Somebody didn't sell it to you that way did they (or did you build it yourself)?
You could always dual boot 64-bit Linux. That is what I use for minecraft on i5 650 3.2 GHz, 8 GB, GT 430, far and fancy and everything else in normal survival (balanced speed). OpenGL in 1.0.0 @ 1080p (32") is usually well over 100 fps (less with OpenGL off). It does not need Oracle (formerly Sun) Java, it works fine with openjdk.
Far and fancy also worked fine in 64-bit Win7, but 1.8 beta was current MC version last time I booted Win7. Not sure if that used 32 or 64-bit Java (both are installed).
You shouldn't use Win7 64bit for Minecraft but for everything else :laugh.gif:
Could you post some benchmarks ? I really tend to doubt it performs the same ... ( At least with Crysis 1/2 or other DX11 games or other hardware-hungry games)
lastly, LOVE the fact that you have 16GB of RAM, of which 13 are sitting completely unused because you are one of those die-hards who thinks that a 10 year old Operating System on a new machine is somehow more performant.
I purchased this RAM when I got Windows 7 64-bit, I knew what I was doing, but I didn't like the interface of Windows 7 at all, and MS Anna annoys the hell out of me so I went back to XP. I've ran tests, and everything that I do on my computer performs the same between both operating systems. So I'm using XP and have no real reason to switch to 7, and With this great OS, I can view .gifs in the integrated picture viewer! (Windows 7 Can't, it's not all great as people make it out to be)
I know both that it's wasteful to have this much RAM, and that saying it in the OP would get people like you to bump my thread and for that, Thank you.
It is not my hardware that is causing this issue.
CPU: i7 2600K @ 4.0GHz
GPU: GTX 550 Ti @ 1000MHz
RAM: 16GB @ 1600MHz
OS: 32-Bit Windows XP
I've been playing this game since 2/4/11 and I've been playing on maximum settings ever since, with a reliable 100-400 FPS.
Why is it that now, out of nowhere, since 1.8 was released my minecraft crashes randomly while the render distance is set to Far? Even on Far, I get well over 100 FPS but at times when I move a few blocks, it will crash.
I've tried all the stuff most people will suggest I do, like updating and downgrading GPU Drivers, testing the RAM, GPU and CPU for stability, setting the affinity for minecraft to run on one CPU core, trying different types of Java.. custom .bats to launch minecraft with more and less RAM, but nothing has worked.
generation. Social experiment.
No, certainly not as it is impossible to use it with 32-Bit XP.
Please read my post a bit more.
You don't put out a "finished" game will crap like this. Only reason they did is because they were going to run out of room to put decimal points.
Then again, I'm using 7. But hey, 32 bit here!
/windows32bithighfive
Any mention about when it will be fixed?
lastly, LOVE the fact that you have 16GB of RAM, of which 13 are sitting completely unused because you are one of those die-hards who thinks that a 10 year old Operating System on a new machine is somehow more performant.
Me too! Hi-five!
So here's my personal timeline:
1.6 and lower: Minecraft runs great.
1.7: Occasionally, the game would make terrain "disappear" on Far. A disconnect/reconnect would fix this.
1.8: The terrain disappears on Far (if not outright crashing the game). The only thing that fixes this is to restart the Minecraft client.
1.0: Same as 1.8 - pretty much unplayable on Far setting.
Aren't games supposed to get better as they are developed? Loads of new features, rendering, lighting, etc. were put in with very little QA testing and/or efficiency IMO. :dry.gif:
You are wasting 13 Gb (at least) of Ram without it !
Oh... And you might want to make a before after test with some performance tools :laugh.gif: If you can afford Win7 in any way, do it ! You will cry about why you didn't do that sooner :wink.gif:
So it's not simply a 32bit issue, I see.
You could always dual boot 64-bit Linux. That is what I use for minecraft on i5 650 3.2 GHz, 8 GB, GT 430, far and fancy and everything else in normal survival (balanced speed). OpenGL in 1.0.0 @ 1080p (32") is usually well over 100 fps (less with OpenGL off). It does not need Oracle (formerly Sun) Java, it works fine with openjdk.
Far and fancy also worked fine in 64-bit Win7, but 1.8 beta was current MC version last time I booted Win7. Not sure if that used 32 or 64-bit Java (both are installed).
Could you post some benchmarks ? I really tend to doubt it performs the same ... ( At least with Crysis 1/2 or other DX11 games or other hardware-hungry games)
I purchased this RAM when I got Windows 7 64-bit, I knew what I was doing, but I didn't like the interface of Windows 7 at all, and MS Anna annoys the hell out of me so I went back to XP. I've ran tests, and everything that I do on my computer performs the same between both operating systems. So I'm using XP and have no real reason to switch to 7, and With this great OS, I can view .gifs in the integrated picture viewer! (Windows 7 Can't, it's not all great as people make it out to be)
I know both that it's wasteful to have this much RAM, and that saying it in the OP would get people like you to bump my thread and for that, Thank you.