lo del -heapsize 128000 que no 1800 :), lo puse porque al buscar tu problema en el google encontré esa posible solución en un foro, la función supongo será decirle al HL cuanta memoria debe usar (128000 -> 128 Megas) o algo parecido, pero como ya te dije en el anterior mensaje si pegas tu error y buscas en google encuentras más opciones, pero para ser más preciso puedes ir al foro de soporte del steam en:
http://www.steampowered.com
y buscar por memory read
encuentras una respuesta amplia al problema:
http://steampowered.custhelp.com/cgi-bin/steampowered.cfg/php/enduser/std_adp.php?p_faqid=56&p_created=1092283967&p_sid=B7P7QCth&p_lva=&p_sp=cF9zcmNoPTEmcF9zb3J0X2J5PSZwX2dyaWRzb3J0PSZwX 3Jvd19jbnQ9NDkmcF9zZWFyY2hfdHlwZT1zZWFyY2hfbmwmcF9 wcm9kX2x2bDE9JnBfY2F0X2x2bDE9JnBfY2F0X2x2bDI9JnBfc GFnZT0xJnBfc2VhcmNoX3RleHQ9bWVtb3J5IHJlYWQ*&p_li=
Te la pego a continuación por si desaparece (lo dudo), pero es mejor que la veas directamente, en el foro del steam por si actualizan :)
-----------------Inicio respuesta-------------------------------------
"Memory Could Not Be Read" Error
A number of players are seeing this error, maybe just occasionally or very persistently.
NOTE: This information can help for both HL1 and HL2 / Source Games.
Please refer to this additional HL2 / Source specific FAQ for more information:
In persistent cases, re-installing Steam and the games rarely affects this problem.
There isn't one solution to fix this problem, it seems to be different for each player and his hardware.
Here is a long thread that has been looking at this problem for a couple of months now:
http://steampowered.com/forums/showthread.php?threadid=96483
This thread is full of many different reports of this error and things that may or may not affect it.
On Aug 6,2004, there were 11,400 Hits on Yahoo for +"Memory Could Not Be Read" (about 6,700 on google).
On December 17,2004 there were only 10,200 Hits on Yahoo, but there are now 19,000 hits on Google.
The Address
Note: The actual error address that failed (referenced memory at ######) might be important for diagnostic purposes, but it's a relative address and not an actual physical address.
If you enter this number in your windows calculator, use scientific mode, set to HEX first, enter the number, then switch to Decimal, it might be important if the number is around 128M, 256M, 384M, 512M.
First Things First
First off, there are a number of problems that can cause this error, Hardware, Software, Games and Operating System, Network and Routers and combinations of all of these.
NOTE: There was a recent CS update that unfortunately caused a rash of memory can't be read errors, typically symptomized by a "-model" error in the game console when certain weapons were fired. This particular problem has been fixed.
This error is generated by the operating system when an application is attempting to use memory that is inaccessible and typicallyis detected by NTDLL.DLL (part of the operating system).
Tweaks and Work Arounds
One of the reasons various "tweaks" like deleting models or cfg files and gl switch settings change a few player's memory read error symptoms is because they all affect how much memory the game is using.
Think of this read error (the long-standing one, not the CS one) in an analogy.
The Glass
If you have a glass (your computer's memory) that is partly full of water (programs), but there is a small hole in the glass about 1/2 way up (usually where one memory module ends and another starts), then when you run HL it fills up memory to just below the hole ... any little change in the game that requires more memory pushes the usage above where the hole is and makes a leak (a crash).
I'm NOT saying this is a hard memory error. What I'm saying is there is some location in memory that when HL trys to use this location that something happens.
This might be caused by the motherboard and the memory timing as it switched from one bank of memory to another. Slowing down the memory timing might fix this, overclocking might make it worse.
Skin Packs
If you have hi-res models (Fusion Pack) they take up more memory then the stock models.
Video Drivers
If you run different versions of graphics drivers, they might take up more or less memory. Using D3D or Software mode instead of OpenGL might change your symptoms in game too.
ClassMenu.res File
This file is not used by any game except TF, but for some reason the game searches for it, and the searching uses up memory space. If you see error messages about this file in your logs, it does NOT mean this file is the problem.
When you add a dummy classmenu.res file, HL finds it instead of searching for it so less memory gets used during the search.
Custom.hpk Spray File
This file contains all the sprays from other players. If you have their spray already then it won't have to be downloaded to your system. (note: only for HL1 games).
Servers also have this file and in both client and server, the file can get very large.
The more entries there are, the more memory it takes as well as the longer it takes to search for each spray.
You can safely delete this file and it will decrease your memory usage and speed up loading the game, but it will cause new sprays to download again which can cause a little lag when you first join a server.
You can set a CVAR that will keep this file from getting too large.
This CVAR is hpk_maxsize ## in either your config.cfg file or in console, the ### is the max size in megabytes. If you set this to 0, custom.hpk will not be limited in size (this is the default).
Router Firmware
If you have bad firmware in your router (Linksys/Actiotec problem) when you connect to a server the resource names for things might get scrambled (only takes one letter) and HL will search for that bogus model/sprite which ... takes more time and memory.
HL Heapsize and Zone Usage
Changing the -heapsize changes the memory usage in big chunks (MB), using -zone (for script space) changes it in KB. This is also the reason deleting some Script CFG Files might change your symptoms a little.
BOTS
There are reports that Adminmod and Realbots (Podbots too) can cause this error. As always, remove unnecessary addons when you get errors like this. Like most of these tweaks, my guess is this is just another "total memory usage" problem.
Desktop Wallpaper and Performance
Adding or removing the wallpaper on your computer changes the memory usage. Also, turning off themes and optimizing XP for performance will use less memory:
control panel > system > advanced > performance > settings > "adjust for best performance"
BIOS Caching
BIOS Caching on or off (best turned off for XP) changes how much memory in the system can get cached which can actually decrease memory demand - the work is being done in "reliable" memory L2 cache).
OPLOCK Registry
The OPLOCK registry change decreases how the operating system (XP, WIN2K) uses memory when programs use shared resources in memory as well as how it handles errors.
AGP Aperture size
Changing the AGP aperture size changes how texture memory in the graphics card maps to system memory, a smaller aperture size is actually more efficient (as long as it isn't too small). The general recommendation is to set the AGP Aperature to the same amount of memory that is on the graphics card, but not more then 1/2 your physical system memory.
Overclocking
Overclocking your computer and memory speeds might create a new hole or might make the hole bigger, slowing the clock speeds a little might close the hole up entirely.
Spyware and Unused XP Services
Removing spyware and unnecessary O/S Services decreases overall memory usage and gives you more margin below the problem memory area.
Delete old Prefetch Files
Deleting the old prefetch files will decrease your O/S baseline memory usage but only for a while (they will be re-created as you run different programs).
Clean your Registry
Cleaning your Registry can actually save many megabytes of memory, depending on how long it's been and how many programs you have installed / removed.
Direct-X Video / Sound Acceleration
Changing these features in DXDIAG will slightly change system memory usage and demand.
Virtual Memory Fix
There are two things you can try with adjusting your Virtual Memory.
If you have 512MB of memory or more then you can try disabling Virtual Memory completely, or you can increase the file size:
Left click on My Computer - select Properties - Go to the Advanced Tab to the right and click on it - In the performance section ;
click on advanced options - In the lower box you will see Virtual Memory.
To disable - click on "No Paging File" and the "SET".
To increase the size (400 min and 2000 Max) add in 256MB steps
and click on "SET' - the size is usually not more then 2X your physical memory.
Alternately you can click "System Managed Size" then "SET".
- You will have to reboot your system for the changes to take effect.
NOTE: It has been reported that a corrupt page file can cause this error, so be sure to try disabling your virtual memory and rebooting to see if the problem goes away.
Other Things to Check (may not be useful):
Too Many System Fonts
It's been reported that having too many fonts installed can aggravate or cause this problem, again this is not the cause but rather just shifting the O/S overhead around.
Video Codec Conflict: (Reported from Warcraft III)
If you have installed any video codec packs, such as Nimo's Codec pack, for video editing or playback please uninstall them and try the game. These codec packs, especially ones with DivX codecs, may conflict with the video codecs in the game causing the game to crash or not start properly.
Some Other Things to Try
If you have a lot of custom models and other content, there is a chance you might have some offending content that is aggravating the problem.
An easy test for this is to temporarily rename the folder for your game that is having problems (counter-strike for example) and let Steam re-create a default directory and see if you have the same problem with a clean install (no custom content).
To do this, exit Steam first, then rename:
C:Program Files\Steam\SteamApps\<account>\counter-strike
to
C:Program Files\Steam\SteamApps\<account>\~counter-strike
The next time you run Steam and run CS it will create a totally default install which you can test with. If there is no difference, then just delete the new folder and rename the old one back.
Bottom Line: HL Really Uses Memory
HL uses more memory and demands more from your system then almost any program a typical player will run, so it's more likely to show this sort of existing problem.
But Why Did this Start Happening After an Update?
Over the years, as HL has been updated, it puts more and more demand on player's computers.
Players demand better looking models and maps and environment and features and action, and these all use memory.
The Operating system that the game is running under is also getting more feature rich (and using a lot more memory) - just look at the difference from Win95 to WinXP.
Where 64MB of memory used to be enough when HL first was released, now 256MB is pretty much the minimum.
For most computers, 256MB memory modules are the smallest that you can buy now, and motherboards are running very aggressive memory timing.
Each update of the game has been pushing the typical memory usage up, so where you might not have seen a problem before, another few MB of usage might push you over the line.
Remember, only a small percentage of all players ever see this error.
Something to Test
Here is a good test.
If your computer has more then one memory module installed, there is a very good chance that the memory modules are mismatched and might be causing this problem.
First, make sure you know exactly how much memory you have and what sizes the memory modules are.
You can use this little program (CPUZ):
http://www.cpuid.com/cpuz.php
Look on the second to the last tab where it shows your memory DIMMs, their size and their timing.
Next, shut your computer down and remove all but ONE memory module.
Then see if you can run the game without getting the memory error. If the game runs fine, then you know you have a timing problem with the memory on your motherboard.
Here is an additional check (for multiple memory modules):
Run the task manager before you try and play HL.
Let it run for a bit and look at where your typical "PF" memory usage is (Page File). Look at the graph and see exactly where your memory DIMMs are, especially where one stops and another starts.
Then run HL to the splash screen (don't connect to a server).
Let it just sit there for a bit, then alt-tab to the taskmon and look at how much memory is being used.
Specifically look and see where this usage is relative to where your DIMMs are ending and starting.
If running HL takes you right to a crossover, then all of the changes listed above might affect if you see this problem or not.
Trojans Can Cause this Error
Virus' and Trojans are known to cause this error, the Sasser is well known for causing it as well as MSBlaster. Null memory references in random programs (accessing address 0x0000000) is a classic symptom.
Memory Tests
It's always good to run a memory test or two if you get memory errors of any kind just to make sure it isn't something easy to find. Typically, memory test will not find this problem though.
Here are a few you can get for free:
Windows Memory Diagnostic Download Page
Memtest86
Simmtester DocMeM Memory Test Program
Just to be complete, here are some specific coding problems and symptoms that can cause this sort of error:
1. trying to access memory beyond an array boundary
2. trying to access an object through a NULL pointer
3. Null memory references in random programs (accessing address 0x0000000)
4. passing a NULL pointer to a Win32 function that expected a valid structure pointer
5. de-referencing a NULL pointer
Some Additional Web Threads on this Problem
http://www.annoyances.org/exec/forum/win2000/t1036959048
Here are three more additional things to make sure are off:
1. uncheck EAX and A3D in the Game Audio Options
2. Don't run BOTs (if you get this error)
3. delete custom.hpk and tempdecal.wad
#3 has to do with custom spray wad files (perhaps bad ones) have been reported to cause this to start happening. Both of these files are in your game directory, delete them and see if your problem still happens.
-----------------Fin respuesta---------------------
Bueno y si tienes más dudas ponte en contacto con valve a través de su página o de la página de soporte de steam.
Saludos.