http://support.microsoft.com/kb/825680#kb1
FIX: Out of Memory Exception Errors May Occur When Significant Amounts of Physical Memory Are Still Available
Article ID : 825680
Last Review : October 14, 2003
Revision : 2.0
On this Page
SYMPTOMS
RESOLUTION
STATUS

SYMPTOMS
You may receive "out of memory" exception error messages, although as much as 2 gigabytes (GB) of physical memory is still available. This problem is most likely to occur when stress levels are reached and when you are using many large objects (objects that are over 85 kilobytes [KB]).
RESOLUTION
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next .NET Framework 1.1 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/default.aspx?scid=fh;[LN];CNTACTMS
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel. Date Time Version Size File name
--------------------------------------------------------------
30-Jul-2003 02:06 1.1.4322.929 77,824 Corperfmonext.dll
30-Jul-2003 02:03 1.1.4322.929 311,296 Mscorjit.dll
31-Jul-2003 06:33 1.1.4322.929 2,093,056 Mscorlib.dll
30-Jul-2003 01:57 10,748 Mscorlib.ldo
30-Jul-2003 02:05 1.1.4322.929 2,498,560 Mscorsvr.dll
30-Jul-2003 02:06 1.1.4322.929 2,486,272 Mscorwks.dll
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

je to ono nie