This is a Guide for those who want to use Minecraft with Texture Packs and how to optimize Java, specifically Javaw (Javaw for Windows) so you don't get the Black Screen.
The Black Screen crash usually happens when Javaw runs out of memory. Texture Packs larger than 32x start using up a lot more memory, the higher the definition of the texture pack, the more memory Javaw needs to run. Technically Texture Packs, if installed correctly, don't crash Minecraft, it is the lack of available system memory to run the pack that causes the crash.
Pro Tip: Windows 32bit, use Javaw 32bit, Windows 64bit use Javaw 64bit. NEVER mix and match 32bit and 64bit versions.
I Suggest using 64 bit windows with at least 4gb of memory and 64bit Javaw on all packs above 64x. You may get some success on 64x packs with 32bit Windows with 3gb of memory, but it may crash to black occasionally as you max your memory. 128x packs crash a lot faster and don't even try 256x packs on anything but Windows 64bit with a minimum of 4gb of memory, 64bit Javaw. A little more info on this later for you doubters.
First a general TP Installation Guide:
1. Download the "Texture Pack.zip" that you want.
2. Download the MCPatcher HD Fix (currently 2.1) always check for a more current version.
Download here. viewtopic.php?f=1021&t=252531
Follow the instructions there on how to install the HD patcher.
3. Next put your downloaded "texture pack.zip" into the texturepacks folder under the .minecraft folder where Minecraft is installed. Do Not Unzip it anywhere.
4. Start Minecraft, Click on the "Mods and Texture Packs" button
5. Click ONCE on the Icon of the Pack you wish to run (doesn't matter if it is grayed out, this is normal for some packs). Now wait, be patient, it takes time to load. You can tell it is loaded when it is outlined in grey. Also the buttons may change to the Packs style. When loaded, click on Done.
6. Chose which mode, Singleplayer, or Multi.
7. The Game may or may not run, don't panic if it doesn't, you may have a conflict on installation, it is easy to mess up a step. Deleting the bin folder under .minecraft and starting Minecraft up to re load will clear the way to start at step two again. Do not delete the complete .minecraft folder if you have started a world. Your saved games are in there.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Edit: upon further testing on different settings to the xmx, xms string, I can find no difference to the way Minecraft runs what so ever on a computer that has adequate memory, Javaw will load its Maximum allowed memory no matter what numbers I type into the below string. But If you try to force it to load more that it can, as -xmx2048 on a 32bit system, it won't load. If I set it to 512/512, Javaw 32bit still loads 1gb. It seems 64bit systems with enough memory act the same, only it loads more memory. Since my systems all have 2 sticks of memory, i can't test Minecraft running with low memory. Maybe this string only resolves some conflicts between settings, I don't know. As of this time I don't see much use for this string. Minecraft seems to default to a max of 1024 Javaw load, maybe because of MCPatcher has that setting, so the only real fix may be to upgrade to max memory for 32bit and only run 64x Packs and then you may still get occasional Black Screens. Upgrade to 64bit Windows and 64bit Javaw and solve all your problems. This post along with every thing else in Minecraft is a WIP.
=====================================Skip 8 & 9 unless Minecraft doesn't start
8. Make a shortcut of the Minecraft.exe (launcher you downloaded) to your desired location. (This is not the installed .minecraft folder under appdata). Right click on the above shortcut and left click properties. In the Target box put your blinking cursor 1 space before what is typed there and paste this:
"C:\Program Files\Java\jre6\bin\javaw.exe" -Xmx1024M -Xms512M -jar
9. Make sure what you pasted is 1 space in front of what was there already and that you didn't overwrite anything. This works for 32bit(-xmx1024)and 64bit(-xmx2048) systems. 64 bit systems with more than 4gb of memory can change the -Xmx2048m to -Xmx3072m. This will also change your Minecraft icon to a Javaw icon. You can change it to another icon picture if you choose.
While adding a larger number to the -Xmx might seem helpful, Javaw cannot load any more memory than it is designed to use. I have seen in the Forums suggestions about adding all sorts of numbers here, and maybe there is a valid reason for adding a lower number as I have see "change it to 768m", to solve a problem, and maybe it does solve a particular problem, but it will only lower the amount of max memory that Javaw can use. If you have a -xmx string in 2 locations, it may confuse Javaw, so be careful.
====================================================Resume here
You need to know some basic facts on how Javaw works in order to make an accurate decision on what your problem may be depending on the x size of your Texture Pack.
Please pay attention to this next bit of information about Javaw, it's not really straight forward as in the case of Javaw, 3 minus 1 does not always equal 2.
It seems in theory at least, that 32bit Javaw can only use at the Max 1.2/1.3gb of memory on a windows 32bit system, and that is under perfect conditions. Javaw doesn't care if you have 4gb of memory installed in your system. Windows 32bit can only use 3gb of your installed memory and Javaw can only load a Max of 1.2/1.3gb of that 3gb. This is just how Java works. You need to optimize you system to get the most memory free you can on a 32 bit system. (My 3 computers all crashed Minecraft with a 64x TP when Javaw reached a 1gb load limit under Windows 32bit, usually between 10 and 30 minutes).
IMPORTANT; 32 and 64bit Javaw Needs a Contiguous chunk of memory (memory all in one chunk) for it to use its max amount of memory, let's say for arguments sake 1gb for 32bit and 3gb for 64bit systems.
BUT: Windows loads its information somewhere in the middle of your memory, so you have to be really lucky to have one blank chunk that is large enough to hold the 1 GB Javaw wants in a 32bit system. Javaw will load into your largest blank chunk of memory, and when that fills up, you get the Black Screen. Since no 2 systems are exactly identical, people's mileage varies on how long or if Minecraft will run a HD TP before Javaw runs out of memory and you get the Black Screen.
So again setting the parameters for java to use 2gb of memory in win32 doesn't change javaw's ability to run a higher texture pack. It's just a number you typed in, Javaw still maxes at 1gb.
Javaw 64 bit can handle 3GB (some say 4GB) of memory (this is where theory and arguments got over my head, a lot of theory talk). Now this 3GB is dependent on your running 64bit windows, 64bit Javaw and again, Windows puts its memory where it wants to, not where Javaw needs it to be. Javaw still needs a 3GB free chunk of Contiguous memory. Your mileage may vary depending on how much memory you have. 4GB minimum, more would certainly help if your system load is high.
My problem with Javaw and my fix for my Black Screen crash: Running a 64x TP, 32bit Windows and Javaw 32bit, 4gb (3gb usable) of memory, Minecraft crashed when Javaw hit the 1gb ceiling, every single time within 30 minutes.
After the change to Windows 64bit and Javaw 64bit and 8gb of memory, I have not crashed 1 single time. I have tested all sizes of Texture Packs up to 256x with no problems and my Javaw memory load is always over 1gb even with the 64x TP. If I run a 128x TP my Javaw memory load starts at 1.3gb and climbs to 1.46gb in 5 minutes.
So think about that, If my Javaw memory load climbs above 1.2gb with a 64x pack after a bit of time, every time I play Minecraft, and a 128x Pack starts at 1.3gb, think how stable it would be on a 32 bit system. Hd Texture Packs and Windows 32bit seem to max out at 64x and that is not without some problems.
Tip:
Minecraft's memory usage climbs the longer you're in Javaw, whether you're just standing in the game or exploring or you just go back to the join game screen. It constantly loads memory up to a certain max load. The only way to dump loaded memory from Minecraft is to totally close Javaw and restart Minecraft. So if you switch texture packs, make sure you close Minecraft completely then restart with the new texture pack otherwise your memory will continue to climb from where it was with the last texture pack, and if it was a high res pack, you will start Minecraft with a great deal of memory already loaded.
All of this info was taken from various forums on Java, Sun, Oracle, etc. A lot more is there, but so much of it is theory on interactions of memory and programs, it's hard to follow, at least for me.
I hope this information helps, it really helped me, I was about to throw my pc out of the window from all of the Black Screens.
Remember Texture Packs don't crash Minecraft. Improper installations, wrong Javaw versions, and low memory are your enemy here.
Also if you're going to run a high res pack, you may need to upgrade your cpu, my c2d 3.33ghz dropped to 20fps with the 256x pack. It wasn't fun, it wasn't pretty, I am saving for a new chip and mb!
Ps: I loaded Minecraft and my map and TP on a friends Sandy Bridge 2500k, 8gb, 64bit Win, 256x Pack, it ran at 107fps. Omg I want one!
New postby JediJennifer ยป Mon May 16, 2011 5:04 am
very good explanation, i finally understand how to write that line:
unfortunately i get this:
"C:\Program\Java\jre6\bin\javaw.exe" -Xmx2048M -Xms512M -jar C:\Users\Jennifer\AppData\Roaming\.minecraft\Minecraft.exe is invalid"
That is because you didn't precisely follow the instructions in step #8.
You made a shortcut to the installed folder of .Minecraft and not the original Launcher you downloaded to install Minecraft and which you still use to launch the program. Make a shortcut to the Launcher (Minecraft.exe), then do the copy and paste as per step #8. Depending on which version of Windows you have and which browser you have, that Launcher file could be in a couple locations, if you didn't already move it. If you have a downloads folder, look in there.
This is a very common mistake as most games launch from within their installed folders. Minecraft doesn't, it launches from that original file you first download to get the installed game.
okey i don't understand. i rightclicked on the Minecraft.exe launcher and made a shortcut. and i downloaded the .exe to my .minecraft folder. i tried downloading it to the desktop but same problem there.
could you do a video?
i must be doing something wrong but i have no idea what :/
I will re-write step 8 a bit, it seems it may be a bit confusing.
Ok, make a shortcut to the Minecraft.exe. Don't move the Minecraft.exe file, you have to leave it where it is or you will break the shortcut link. You can move the new shortcut to any place that is convenient for you to have easy access to it.
Right click on the above shortcut and left click properties. In the Target box put your blinking cursor 1 space before what is typed there and paste this:
"C:\Program Files\Java\jre6\bin\javaw.exe" -Xmx1024M -Xms512M -jar
9. Make sure what you pasted is 1 space in front of what was there already and that you didn't overwrite anything. This works for 32bit(-xmx1024)and 64bit(-xmx2048) systems. 64 bit systems with more than 4gb of memory can go up to -Xmx3072m. This will also change your Minecraft icon to a Javaw icon. You can change it to another icon picture if you choose.
You are not downloading anything, just creating a new shortcut to Minecraft.exe, modifying it and then moving the new shortcut for easy access to launch Minecraft.
i missed the " thing at the beginning (i feel like a complete idiot).
but now i get a different error: Could not create the Java virtual machine.
i tried with -Xmx1024M and the game actually started! i played for a minute or 2 and the game blackscreens.
i don't get it!!! the memory (when pressing F3) is not even over 200meg. the browser version works just fine and i can play for hours :/
(thanks to you I just found a huge conflict with those Javaw strings).
You didn't mention what size Pack you're trying to run and what your system stats are, but my guess is that you are running out of memory.
I assume from your above post that you have a 32bit system and I hope you have at least 3gb of installed memory.
Start Minecraft and keep it in a medium window so you can still see the task manager and turn on F3. Watch the stats for memory in Minecraft and watch Javaw in your task manager. When it crashes take note of the memory loads in the Task manager and Minecraft. My guess is that it is crashing way below the 1gb max load of Javaw 32bit. The 200mb memory usage you mentioned is fine, it's the allocated amount that causes the problem. When Javaw asks for 1gb, and at some point in time it will, and you don't have it, it stops running.
BTW: The Xmx, xms number that shows in Minecraft show up as a slightly lower number.
When i run 256x256 texture packs i only use more than 1 gig of RAM if i have MCE saving chunks in RAM. This guide is BS it does not require 4 gigs of RAM to run a 256x256 texture pack. Stop doomsaying. The part about raising how much memory your Java can use is helpful but you don't need 4 GB by any means lol.
Posted Yesterday, 03:46 AM
When i run 256x256 texture packs i only use more than 1 gig of RAM if i have MCE saving chunks in RAM. This guide is BS it does not require 4 gigs of RAM to run a 256x256 texture pack. Stop doomsaying. The part about raising how much memory your Java can use is helpful but you don't need 4 GB by any means lol.
I don't think you read the part of the post concerning max system memory and how Javaw uses system memory. Javaw Needs a Contiguous chunk (a blank chunk of memory all in one piece) If you have only 2gb of ram, you have no chance of running Javaw 32bit at its maximum of 1gb. Most can't do it with 3gb without getting occasional Black Screens, and this is with a 64x pack, let alone a 256x pack.
What your are saying about "only using more 1gb RAM" is the same as what I was saying. Javaw uses more than 1gb of ram for all packs 64x - 256x, and 32bit Windows is really hard pressed to give Javaw a single chunk of memory big enough for Javaw to run even 1gb of contiguous memory. While 64bit Windows and 64bit Javaw have no problem doing that as 64bit Javaw is able to use 3gb of memory.
Minecraft crashes in Windows 32bit when Javaw exceeds its 1gb memory request. But 32bit Windows needs its max 3gb of system memory for best Javaw performance, it cannot allocate more than 1gb to Javaw 32 because Javaw 32bit cannot use more than 1gb. 64bit Windows with 4gb of memory can give more memory to Javaw 64bit to run.
Giving the extreme difficulty of finding 2x512mb of ram to update your dual channel system from 2gb to 3gb, is one of the reasons so many use 4gb, also if you decide to upgrade to Windows 64bit, you're already set for memory, hence my reference to 4gbs.
Thanks for your response, Javaw and Minecraft is sort of like Witch Craft here on the forums, any discussions that can get to any truths will cut down on a whole lot of repeated questions that the makers of Texture Packs have to respond to daily.
Happy MCing
all packs i use are 16x, even when i have the default minecraft textures the game blackscreens.
i have Vista 32bit with 4 gigs installed. only 3gigs are used of course.
javaw.exe stopped working at 809meg, in minecraft it blackscreened at 129MB of 989MB, allocated 50% 495MB
i had "Far" on the distance and i used the default textures, if i use "Normal" i can play a little longer.
hope this helps somehow and that a solution can be found :S
Is seems you are just running out of memory. Have you optimized Windows to clean out unwanted processes running in the background? Run Task Manager and check the number that is running, you might get these down to 33-44 depending on what you have loaded. Run msconfig from the search box and uncheck any startups that are unnecessary. If you bought the computer new, and never ran pc decrapifier, you might google it and clean out all the crap that is loaded onto new computers. All of this just might free up enough memory to run Mc without Black Screening so much.
Be sure to google any thing you're not sure of if you stop a process or uncheck a startup file.
You can also check "Uninstall programs" and uninstall the toolbars that get loaded. Almost every download these days gives some unwanted crap that gets installed with the desired program. It all adds up to extra memory being loaded by Windows which steals the free space that Javaw needs.
This was enlightening on several details I wasn't entirely sure about. Nicely explained.
The only thing I'm still confused about is this:
I'm running a 64x texture pack on a 32-bit system with 3GB of RAM available. I don't get the black screen very often, but when I do, it seems to occur almost randomly. Sometimes, I can play Minecraft for hours on end without it having so much as a single lag spike. In the worst case, I have seen it last less than a minute before crashing. This strikes me as odd, since your tests say your game crashed within a half hour, every time. It's not like I'm closing background processes to free up memory either, since I have Fireworks (my image editor), Firefox, several folders, messenger etc. all open at the same time. Perhaps my processor is better at handling Javaw than your testing one is?
It's not that this is a problem, obviously, I'm more interested out of pure curiosity. I'd just like to know if you know of any reason my 32-bit system (Windows XP, by the way) seems to be able to handle it better than in your tests.
The Black Screen crash usually happens when Javaw runs out of memory. Texture Packs larger than 32x start using up a lot more memory, the higher the definition of the texture pack, the more memory Javaw needs to run. Technically Texture Packs, if installed correctly, don't crash Minecraft, it is the lack of available system memory to run the pack that causes the crash.
Pro Tip: Windows 32bit, use Javaw 32bit, Windows 64bit use Javaw 64bit. NEVER mix and match 32bit and 64bit versions.
I Suggest using 64 bit windows with at least 4gb of memory and 64bit Javaw on all packs above 64x. You may get some success on 64x packs with 32bit Windows with 3gb of memory, but it may crash to black occasionally as you max your memory. 128x packs crash a lot faster and don't even try 256x packs on anything but Windows 64bit with a minimum of 4gb of memory, 64bit Javaw. A little more info on this later for you doubters.
First a general TP Installation Guide:
1. Download the "Texture Pack.zip" that you want.
2. Download the MCPatcher HD Fix (currently 2.1) always check for a more current version.
Download here. viewtopic.php?f=1021&t=252531
Follow the instructions there on how to install the HD patcher.
3. Next put your downloaded "texture pack.zip" into the texturepacks folder under the .minecraft folder where Minecraft is installed. Do Not Unzip it anywhere.
4. Start Minecraft, Click on the "Mods and Texture Packs" button
5. Click ONCE on the Icon of the Pack you wish to run (doesn't matter if it is grayed out, this is normal for some packs). Now wait, be patient, it takes time to load. You can tell it is loaded when it is outlined in grey. Also the buttons may change to the Packs style. When loaded, click on Done.
6. Chose which mode, Singleplayer, or Multi.
7. The Game may or may not run, don't panic if it doesn't, you may have a conflict on installation, it is easy to mess up a step. Deleting the bin folder under .minecraft and starting Minecraft up to re load will clear the way to start at step two again. Do not delete the complete .minecraft folder if you have started a world. Your saved games are in there.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Edit: upon further testing on different settings to the xmx, xms string, I can find no difference to the way Minecraft runs what so ever on a computer that has adequate memory, Javaw will load its Maximum allowed memory no matter what numbers I type into the below string. But If you try to force it to load more that it can, as -xmx2048 on a 32bit system, it won't load. If I set it to 512/512, Javaw 32bit still loads 1gb. It seems 64bit systems with enough memory act the same, only it loads more memory. Since my systems all have 2 sticks of memory, i can't test Minecraft running with low memory. Maybe this string only resolves some conflicts between settings, I don't know. As of this time I don't see much use for this string. Minecraft seems to default to a max of 1024 Javaw load, maybe because of MCPatcher has that setting, so the only real fix may be to upgrade to max memory for 32bit and only run 64x Packs and then you may still get occasional Black Screens. Upgrade to 64bit Windows and 64bit Javaw and solve all your problems. This post along with every thing else in Minecraft is a WIP.
=====================================Skip 8 & 9 unless Minecraft doesn't start
8. Make a shortcut of the Minecraft.exe (launcher you downloaded) to your desired location. (This is not the installed .minecraft folder under appdata). Right click on the above shortcut and left click properties. In the Target box put your blinking cursor 1 space before what is typed there and paste this:
"C:\Program Files\Java\jre6\bin\javaw.exe" -Xmx1024M -Xms512M -jar
9. Make sure what you pasted is 1 space in front of what was there already and that you didn't overwrite anything. This works for 32bit(-xmx1024)and 64bit(-xmx2048) systems. 64 bit systems with more than 4gb of memory can change the -Xmx2048m to -Xmx3072m. This will also change your Minecraft icon to a Javaw icon. You can change it to another icon picture if you choose.
While adding a larger number to the -Xmx might seem helpful, Javaw cannot load any more memory than it is designed to use. I have seen in the Forums suggestions about adding all sorts of numbers here, and maybe there is a valid reason for adding a lower number as I have see "change it to 768m", to solve a problem, and maybe it does solve a particular problem, but it will only lower the amount of max memory that Javaw can use. If you have a -xmx string in 2 locations, it may confuse Javaw, so be careful.
====================================================Resume here
You need to know some basic facts on how Javaw works in order to make an accurate decision on what your problem may be depending on the x size of your Texture Pack.
Please pay attention to this next bit of information about Javaw, it's not really straight forward as in the case of Javaw, 3 minus 1 does not always equal 2.
It seems in theory at least, that 32bit Javaw can only use at the Max 1.2/1.3gb of memory on a windows 32bit system, and that is under perfect conditions. Javaw doesn't care if you have 4gb of memory installed in your system. Windows 32bit can only use 3gb of your installed memory and Javaw can only load a Max of 1.2/1.3gb of that 3gb. This is just how Java works. You need to optimize you system to get the most memory free you can on a 32 bit system. (My 3 computers all crashed Minecraft with a 64x TP when Javaw reached a 1gb load limit under Windows 32bit, usually between 10 and 30 minutes).
IMPORTANT; 32 and 64bit Javaw Needs a Contiguous chunk of memory (memory all in one chunk) for it to use its max amount of memory, let's say for arguments sake 1gb for 32bit and 3gb for 64bit systems.
BUT: Windows loads its information somewhere in the middle of your memory, so you have to be really lucky to have one blank chunk that is large enough to hold the 1 GB Javaw wants in a 32bit system. Javaw will load into your largest blank chunk of memory, and when that fills up, you get the Black Screen. Since no 2 systems are exactly identical, people's mileage varies on how long or if Minecraft will run a HD TP before Javaw runs out of memory and you get the Black Screen.
So again setting the parameters for java to use 2gb of memory in win32 doesn't change javaw's ability to run a higher texture pack. It's just a number you typed in, Javaw still maxes at 1gb.
Javaw 64 bit can handle 3GB (some say 4GB) of memory (this is where theory and arguments got over my head, a lot of theory talk). Now this 3GB is dependent on your running 64bit windows, 64bit Javaw and again, Windows puts its memory where it wants to, not where Javaw needs it to be. Javaw still needs a 3GB free chunk of Contiguous memory. Your mileage may vary depending on how much memory you have. 4GB minimum, more would certainly help if your system load is high.
My problem with Javaw and my fix for my Black Screen crash: Running a 64x TP, 32bit Windows and Javaw 32bit, 4gb (3gb usable) of memory, Minecraft crashed when Javaw hit the 1gb ceiling, every single time within 30 minutes.
After the change to Windows 64bit and Javaw 64bit and 8gb of memory, I have not crashed 1 single time. I have tested all sizes of Texture Packs up to 256x with no problems and my Javaw memory load is always over 1gb even with the 64x TP. If I run a 128x TP my Javaw memory load starts at 1.3gb and climbs to 1.46gb in 5 minutes.
So think about that, If my Javaw memory load climbs above 1.2gb with a 64x pack after a bit of time, every time I play Minecraft, and a 128x Pack starts at 1.3gb, think how stable it would be on a 32 bit system. Hd Texture Packs and Windows 32bit seem to max out at 64x and that is not without some problems.
Tip:
Minecraft's memory usage climbs the longer you're in Javaw, whether you're just standing in the game or exploring or you just go back to the join game screen. It constantly loads memory up to a certain max load. The only way to dump loaded memory from Minecraft is to totally close Javaw and restart Minecraft. So if you switch texture packs, make sure you close Minecraft completely then restart with the new texture pack otherwise your memory will continue to climb from where it was with the last texture pack, and if it was a high res pack, you will start Minecraft with a great deal of memory already loaded.
All of this info was taken from various forums on Java, Sun, Oracle, etc. A lot more is there, but so much of it is theory on interactions of memory and programs, it's hard to follow, at least for me.
I hope this information helps, it really helped me, I was about to throw my pc out of the window from all of the Black Screens.
Remember Texture Packs don't crash Minecraft. Improper installations, wrong Javaw versions, and low memory are your enemy here.
Also if you're going to run a high res pack, you may need to upgrade your cpu, my c2d 3.33ghz dropped to 20fps with the 256x pack. It wasn't fun, it wasn't pretty, I am saving for a new chip and mb!
Ps: I loaded Minecraft and my map and TP on a friends Sandy Bridge 2500k, 8gb, 64bit Win, 256x Pack, it ran at 107fps. Omg I want one!
Good Luck
That is because you didn't precisely follow the instructions in step #8.
You made a shortcut to the installed folder of .Minecraft and not the original Launcher you downloaded to install Minecraft and which you still use to launch the program. Make a shortcut to the Launcher (Minecraft.exe), then do the copy and paste as per step #8. Depending on which version of Windows you have and which browser you have, that Launcher file could be in a couple locations, if you didn't already move it. If you have a downloads folder, look in there.
This is a very common mistake as most games launch from within their installed folders. Minecraft doesn't, it launches from that original file you first download to get the installed game.
good luck
I will re-write step 8 a bit, it seems it may be a bit confusing.
Ok, make a shortcut to the Minecraft.exe. Don't move the Minecraft.exe file, you have to leave it where it is or you will break the shortcut link. You can move the new shortcut to any place that is convenient for you to have easy access to it.
Right click on the above shortcut and left click properties. In the Target box put your blinking cursor 1 space before what is typed there and paste this:
"C:\Program Files\Java\jre6\bin\javaw.exe" -Xmx1024M -Xms512M -jar
9. Make sure what you pasted is 1 space in front of what was there already and that you didn't overwrite anything. This works for 32bit(-xmx1024)and 64bit(-xmx2048) systems. 64 bit systems with more than 4gb of memory can go up to -Xmx3072m. This will also change your Minecraft icon to a Javaw icon. You can change it to another icon picture if you choose.
You are not downloading anything, just creating a new shortcut to Minecraft.exe, modifying it and then moving the new shortcut for easy access to launch Minecraft.
I hope this helps
(thanks to you I just found a huge conflict with those Javaw strings).
You didn't mention what size Pack you're trying to run and what your system stats are, but my guess is that you are running out of memory.
I assume from your above post that you have a 32bit system and I hope you have at least 3gb of installed memory.
Start Minecraft and keep it in a medium window so you can still see the task manager and turn on F3. Watch the stats for memory in Minecraft and watch Javaw in your task manager. When it crashes take note of the memory loads in the Task manager and Minecraft. My guess is that it is crashing way below the 1gb max load of Javaw 32bit. The 200mb memory usage you mentioned is fine, it's the allocated amount that causes the problem. When Javaw asks for 1gb, and at some point in time it will, and you don't have it, it stops running.
BTW: The Xmx, xms number that shows in Minecraft show up as a slightly lower number.
Good luck
I don't think you read the part of the post concerning max system memory and how Javaw uses system memory. Javaw Needs a Contiguous chunk (a blank chunk of memory all in one piece) If you have only 2gb of ram, you have no chance of running Javaw 32bit at its maximum of 1gb. Most can't do it with 3gb without getting occasional Black Screens, and this is with a 64x pack, let alone a 256x pack.
What your are saying about "only using more 1gb RAM" is the same as what I was saying. Javaw uses more than 1gb of ram for all packs 64x - 256x, and 32bit Windows is really hard pressed to give Javaw a single chunk of memory big enough for Javaw to run even 1gb of contiguous memory. While 64bit Windows and 64bit Javaw have no problem doing that as 64bit Javaw is able to use 3gb of memory.
Minecraft crashes in Windows 32bit when Javaw exceeds its 1gb memory request. But 32bit Windows needs its max 3gb of system memory for best Javaw performance, it cannot allocate more than 1gb to Javaw 32 because Javaw 32bit cannot use more than 1gb. 64bit Windows with 4gb of memory can give more memory to Javaw 64bit to run.
Giving the extreme difficulty of finding 2x512mb of ram to update your dual channel system from 2gb to 3gb, is one of the reasons so many use 4gb, also if you decide to upgrade to Windows 64bit, you're already set for memory, hence my reference to 4gbs.
Thanks for your response, Javaw and Minecraft is sort of like Witch Craft here on the forums, any discussions that can get to any truths will cut down on a whole lot of repeated questions that the makers of Texture Packs have to respond to daily.
Happy MCing
Is seems you are just running out of memory. Have you optimized Windows to clean out unwanted processes running in the background? Run Task Manager and check the number that is running, you might get these down to 33-44 depending on what you have loaded. Run msconfig from the search box and uncheck any startups that are unnecessary. If you bought the computer new, and never ran pc decrapifier, you might google it and clean out all the crap that is loaded onto new computers. All of this just might free up enough memory to run Mc without Black Screening so much.
Be sure to google any thing you're not sure of if you stop a process or uncheck a startup file.
You can also check "Uninstall programs" and uninstall the toolbars that get loaded. Almost every download these days gives some unwanted crap that gets installed with the desired program. It all adds up to extra memory being loaded by Windows which steals the free space that Javaw needs.
Good Luck
I wish I was in this :C
The only thing I'm still confused about is this:
I'm running a 64x texture pack on a 32-bit system with 3GB of RAM available. I don't get the black screen very often, but when I do, it seems to occur almost randomly. Sometimes, I can play Minecraft for hours on end without it having so much as a single lag spike. In the worst case, I have seen it last less than a minute before crashing. This strikes me as odd, since your tests say your game crashed within a half hour, every time. It's not like I'm closing background processes to free up memory either, since I have Fireworks (my image editor), Firefox, several folders, messenger etc. all open at the same time. Perhaps my processor is better at handling Javaw than your testing one is?
It's not that this is a problem, obviously, I'm more interested out of pure curiosity. I'd just like to know if you know of any reason my 32-bit system (Windows XP, by the way) seems to be able to handle it better than in your tests.
This is wrong, as I can run 128x packs without doing anything special, in fact, my laptop only has 3.5GB of ram, on 32 bit Vista.