UOSteam Out of Memory: Add your fix

[Lowne]

This will be a long one but bear (bare?) with me.

I have read various forums that gave the following fixes for getting UOSteam to work:
Fix #1 - Set your Virtual Memory to 3x what the physical amount is, reboot and try again. (at one point I had 75gb of Virtual Mem and it didn't help)
Fix #2 - Close every program currently running and try UOSteam again.
Fix #3 - Set compatibility mode of UOSteam to WinXP SP3.
Fix #4 - Run UOSteam as Admin.
Fix #5 - Open Task Manager and close unneeded processes that are running (this one has the capability of being dangerous if you close the wrong thing)
Fix #6 - Run msconfig.exe and rid your system of unneeded Startup processes.

NONE of these worked for me as stated. #5 and #6 worked for me somewhat but I had to take it a step further.

To get UOSteam to work, I had to:
1. Run msconfig.exe
2. Select Startup tab.
3. Uncheck ALL items that are not necessary. Some items you may see are Java Auto Updater, iTunes, Google Talk; things of this nature do not need to startup when the system does. It's handy that they do so, but not necessary.
4. Reboot system for a fresh start.
5. Once system is back up to desktop, open Task Manager again.
6. Select the Processes Tab.
7. Click the Memory heading to sort highest to lowest memory usage, at the top (on my system anyway) was svchost.exe as using the most memory. (I won't go into it all but you can drill further down with Procmon and other tools to find exactly what is being called into memory from each process but I was impatient and just went on with....)
8. Select the top process of svchost.exe and clicked End Process. (if svchost.exe isn't the process using the most Memory, find the svchost.exe (there are several) that is using the most and End Process on it)

You are shooting for the lowest amount of Memory in use prior to starting up UOSteam. This got my memory below 19% usage and UOSteam fires up everytime for me following my "Kill the svchost.exe after a Fresh Reboot" Plan.

Now when I want to fire up UOSteam I only need to do the following: (this is where the fixes listed at the top start to coincide with reality for me and my computer)
1. Close all programs.
2. Open Task Manager and kill highest svchost.exe
3. Fire up UOSteam.
4. Bask in the glory of Excelsior.

The svchost.exe process that is using the most memory generally doesn't contain anything critical to the running of your system but the best way is to use a tool to see what it's calling and make sure. Not all svchost.exe's are the same and End Process on the wrong one can cause a system crash.

Ultimately, my system is messy internally and it is my own fault that I had the UOSteam issues that I've had. If I were a good Tech I would reformat my home system more often but I do this crap all day long at work, when I get home I really don't have the desire to muck about with OS's, hardware and etc.; I just want to have some fun playing a game and relax.

Anyway, I've posted this in case it might help someone. Please use your own discretion if you choose to use what I've done. I don't remember everyone's name, but there are several folks at Excelsior that I've talked to in game that have a lot of good info as well. Hopefully they will reply to this thread with their ideas also.

(if more detail is needed, just holler. I've only given a general overview of things here.)

[Asmodean]

"Out of Memory" Error
Occasionally when opening the patched client via Razor, you may receive an "Out of Memory" error. There is no known resolution to this issue, though I have spent dozens of hours researching and fiddling with it. Basically, the version of the UO client our shard runs on was not meant to accept files quite as large as we are now going to be using, so sometimes the client and razor get a little insecure and throw an error. If this happens for you, simply close all other programs running on your system, start your client with razor, and then open your programs again. I have been running the patched client for over 6 months now, and have only received this error 4-5 times, almost always after a fresh reboot. This is the only known issue with the functionality of the patch.
UPDATE: I have modified the patch to decrease some file sizes. Please download the new version. If you are still having trouble after installing the updated patch files, you may try this microsoft fixit: http://support.microsoft.com/kb/947246
Some players have had success with this method, but others have not. Further suggestions are to close the system process "Lcore.exe" if you are using logitech products. This is a rather memory-heavy process that is not necessary to the functionality of your devices.

Improper installation errors:
These are usually evident when you log in after installing the patch and you can no longer see your character or other mobiles. This is a result of partially corrupt files and it can happen in the following ways:
- If you try to install the patch before the files are completely finished downloading
- If your game window is open while you're installing the patch.
- If you have any sort of system error while copying (Ie: a program crashes, your computer locks up, windows updates reboots your computer, etc etc etc.)

If this happens, just reinstall the patch making certain you have no UO windows or utility programs open at the time you begin the copy. Reboot your computer, and you should be good to go.

I use uosteam, and this fix works for that as well.
http://uoex.net/forum/viewtopic.php?f=6&t=7360

[Lowne]

Nice one, forgot about it.

I did the "Lcore.exe" and MSKB thing as well and they also didn't solve my issue but it obviously works for others.

[Neville Folliot]

• check for and clean malware off your system.
• close chrome browser before starting UO.
• Otherwise yeah limit your startup items as mentioned above.

[DrussRob]

I would rather have a fix for uosteam than have to "fix" my non broken computer.
The problem lies with the program not the system.

System type 64-bit operating system
Number of processor cores: 4
Intel(R) Core(TM) i5-2320 CPU @ 3.00GHz
12.0 GB RAM
1696 MB Total available graphics memory
587GB Free (745GB Total) HD

No Malware or extra crap, this system runs clean.
I should have no problems.

[scuba]

i don't use UOSteam but i have a huge out of virtual memory and even after trying all these methods i still have to restart my computer multiple times and i have set a rule for my self i wont try more than 5 restarts then i just give up and play a different game it really sucks because i love this shard and community but i find my actual play time is about 2-3 hours a month now due to the hassle of trying to log on but my method like i said was repeated restarts after doing all other steps such as closing all apps i almost feel like this could be a Samsung laptop problem as i seem to have manufacture software that crashes when i try to launch the game to soon after restarts. the name of the app is S agent and it is for updating Samsung apps that come with the comp..

Ps. glad to see this problem getting some light as i would love to play again but its not gonna happen if it takes me 30 mins to log every time i want to play ( lol if i m lucky enough to get on in 30 mins )

[Pariah]

I would rather have a fix for uosteam than have to "fix" my non broken computer.
The problem lies with the program not the system.

System type 64-bit operating system
Number of processor cores: 4
Intel(R) Core(TM) i5-2320 CPU @ 3.00GHz
12.0 GB RAM
1696 MB Total available graphics memory
587GB Free (745GB Total) HD

No Malware or extra crap, this system runs clean.
I should have no problems.

While you are correct in essence, these are ancient programs that are no longer supported by today's standards. Everything is a workaround. You could go code a fix for it yourself. Hijacking the thread to post specs of your system to prove how superior you are to everyone in a thread where people are actually trying to help is like offering a drowning man a VCR...

P.S. I don't have half the setup you have and I can run UO, Razor, EUOX, etc. just fine on a 64 bit OS. Just takes a little bit of leg work, which I don't mind as I really enjoy playing here. In fact, I enjoy it enough to setup on my Mac as well running through Wine. Makes me grateful for my Vaio laptop...

[Versales]

Ok, so I broke down and downloaded UOSteam on my computer. I am on a Mac, I have WINE, and can use that to log into the shard. However, now that I have downloaded steam I would (ideally) like to use it so I can run scripts and macros and what not. I am not very computer savvy. I **think** I have set up steam to run UO properly...though really...who knows. When I open steam up it says I'm out of virtual memory/not using it ect. and then closes out steam. So I'm wondering how to get it going.
I don't really know how to even do the fixes people suggest, like running task manager. I don't think I even have that.

P.S.
Yelling at the computer did not work. Nor did slamming the screen closed and inhaling sharply with my fists clenched.

Any help from you computer guru's would be greatly appreciated.
I mean like I need it explain so a 5 year old can do it.

[Iltar]

Can try this program: http://www.techpowerup.com/forums/threa ... re.112556/ that helps to run uo under Windows 10. Also can try rebooting and running uo earlier then all other applications.
Other then this, I doubt it is easy to find solution of this problem for MacOS. If the program doesn't help, I can suggest is to run Windows in virtual machine.
http://www.macworld.com/article/1164817 ... r-mac.html

[beanerman]

I also get that error as well on my win 7 laptop and I just have to close out of most running programs like team viewer and steam

[flakjakkit]

This fix worked for me, and i've never had a problem since using it. It's a tiny program that sets the Large Address Aware flag to "on" for your UO client.exe.

http://pandorauo.com/traffic/virtualmemory.html

Full instructions, and the program download are there.

[heyyo]

flakjakkit's fix worked for me.

I turned off my PC because a big thunderstorm was coming through. I had some virtual memory problems prior, but usually closing everything down and I could launch UOSteam no problem. For some reason, after the restart I absolutely could not get it started. Weird.

[fixxer1963]

In most cases, this error is because of some program that accesses the internet running before UO Steam starts.
This includes update software, browsers, sometimes even widgets or apps.
For me it is usually Chrome. But I don't have any update software running.