Failfast occurs when you experience an "out of memory" condition

This article has been archived. It is offered "as is" and will no longer be updated.
When you experience an out of memory condition, the process may continue for a while in an unstable state. During the time that your computer runs in the out-of-memory condition, you may experience other problems. The out of memory condition may be difficult to troubleshoot.
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, we recommend 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 telephone numbers and information about support costs, visit the following Microsoft Web site: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.
For the .NET Framework 1.1, the following DWORD registry key causes failfast on out of memory conditions when it is set to a non-zero value:

For the .NET Framework 2.0 and later versions, the following DWORD registry key causes failfast on out of memory conditions when it is set to a non-zero value: 

If you set the value of the key to 1, an event message is logged in the application event log. If you set the value of the key to 2, you experience a break in the debugger.

If you set the value of the key to 4, an event message is logged that includes the size of the allocation that failed and the number of bytes in use:

Failed to allocate x bytes with y bytes in use. Process will be Terminated.

If you configure the registry key, one of these two events will occur:
  • The application calls the DebugBreak function, and then you experience a breakpoint exception.
  • The application creates a log event message. The log event message describes what Private Bytes are in use, and then it describes the size of the VirtualAlloc function that the application did not allocate.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Article ID: 820745 - Last Review: 12/08/2015 02:43:43 - Revision: 5.0

Microsoft .NET Framework 1.1

  • kbnosurvey kbarchive kbqfe kbhotfixserver kbnetframe110sp1fix kbnetframe110presp1fix kbfix kbbug KB820745