I think I know which of your old posts you are referring here, and I think it's this one:
Originally Posted by Missing_Minds
and yes, I had that copied to a notepad for future references, though that was against zoning issues if I recall.
A Possible Solution to the Zone in and Crash issue. (32 bit OS only)
Posted On: May 29th, 2012
Posted By: Missing_Minds
Posted in: Uncategorized
Several players have the issue of zoning into Gianhold, Desert, or what have you for an adventure region, and then crash. What is the cause of this is still unknown, but could very well relate to memory management (among a large list of possibilities).
The reason why it could be memory management is because by default, most all 32 bit OS are rigged to allow 2 gig of memory for system/kernal usage and 2 gig for user memory. If a program tries to go beyond that, it goes out of range and most programs crash at that point. DDO is compiled to be able to handle larger than 2 gig of address space. (confirmed by SisAmethyst. http://forums.ddo.com/showpost.php?p=4485144&postcount=30)
The person that I first saw suggest this fix was SilentAssassin82 as he used the fix for Battlefield 3. This fix is only for 32 bit OS versions of XP,Vista, and Win7.
The following comes directly from the link below.
What does it help with?
This is not the solution for all crashes. It deals primarily with the crash to desktop that is caused by lack of virtual address space. Due to the unique nature of how addresses are mapped differently on each machine this crash may happen at different places and times of the game, even loading a map, menu or waiting on an AI turn. If you try this fix, and you follow directions properly, and it doesn’t help you then your crash is due to something else.
How do I do it?
Follow directions explicitly. I have seen people consistently skip steps or not read the directions properly so it doesn’t work for them when they don’t do what it says. it’s not as complicated as it sounds, I’m just being thorough.
APPLY THE WORKAROUND (juicy caramel center)
Only real requirements is that you have at least 2GB RAM. You don’t need beyond that even though we are allowing addressing up to 2.5 GB. Also following instructions and being somewhat familiar with working with files in windows is required. Make sure you are using Vista SP1 or later. If not then you need this hotfix that fixes a major blunder with Vista address space - http://support.microsoft.com/kb/940105 “Virtual address space usage in Windows Vista game development”
That’s all, follow the 3 steps.
1) Prepare the operating system to be able to use beyond 2GB address space with a userva of 2.5GB (only 32 bit OS’s need to do this): I am purposely using only 2500 for userva for specific reasons and any more will likely not be needed, as a result the kernel will have plenty of space to play in.
Windows 7/Windows Vista
* In Windows 7/Vista go to Start menu. Go to Accessories. Locate the command prompt shortcut and hover mouse over it. Right Click on the shortcut then select Run as Administrator.
* In the command prompt type this exactly: bcdedit /set increaseuserva 2500. Then hit enter.
* Make sure you get a message back confirming the change was made. To verify the entry is there you can type just bcdedit, hit enter, and you should see the entry now listed.
* Then close the command prompt. You just told Vista to increase user virtual address (userva) space to 2500MB.
* Changes take effect on reboot but don’t reboot yet.
We extended the user virtual address space in XP, Vista and 7 to 2500MB, so now applications can utilize up to that much if they are set to be Large Address Aware. While some 32 bit games/applications are set, Empire is not.
2) Now reboot the PC because Windows needs to set the userva at 2500 which only happens after startup.
If you skip any step it will not work. When you have rebooted you should be good to go. Run the game as normal with the original game shortcut.
TO UNDO THE CHANGES
For Vista 32 Open command prompt as administrator and type: bcdedit /deletevalue increaseuserva. That deletes the entry.
Reboot and you are back to normal.
It should be noted that you may get Out of Memory (OOS) issues depending on your graphic card memory size (notably if your GPU has more than 640 MB of RAM). From what I’ve read on different sites, reduce the value of 2500 by 64 each time until your system becomes stable.
XP 32 bit
Note: for whatever reason, this blog system is very dumb and will not allow boot_ini to use a “.” for the actual file name. So just remember it is looking for your boot . ini file.
* Find your Boot_ini located usually on the C:.
If you cannot see it, you probably have system files hidden, then follow these instructions at microsoft (also uncheck “hide protected operating system files”)
* Right click on the boot_ini and choose properties. Uncheck “read only”
* Open the boot_ini by double clicking it.
* Under the section called find the line that says “multi(0)disk(0)rdisk(0)partition(1)\WINDOWS=”Windows XP Professional…”. Yours may look a bit different. We are going to make a duplicate, so that if you make a mistake you will not harm yourself from booting into your computer. Drag you’re mouse across the entire line, right click and choose copy. Then right below the line you just copied right click your mouse and choose paste. You should now have two lines one after another that are exact duplicates.
* Change the bottom line that you just copied with the following addition on the end. Add a space at the end of the line and then this without the quotes “/3GB /USERVA=2500?
* In that lower boot entry you just made, find the name of the operating system in quotes and change it to something like “Windows XP 3GB”, so you can differentiate at boot up.
* Close and save the boot_ini.
* Right click on the boot_ini, hit properties, check read only.
NOTE: I have never really ever suffered this on my machines (plural) but I wanted to record this for those who do so it would not be lost.
Edit: This was edited to include XP instructions.
(4 votes, average: 5 out of 5)
Click the emblems to rate this post.
Report this post