Article ID: 907544
Article Last Modified on 12/3/2007
APPLIES TO
- Microsoft .NET Framework 1.1
- Microsoft .NET Framework 1.1 Service Pack 1
SYMPTOMS
Microsoft .NET Framework 1.1 applications may crash on some computers when the computers set a bit in a processor MSR to disable LOCK# signal generation. This signal tells the memory subsystem to handle the associated memory requests as one operation and not let other processors access the shared memory location until the LOCK# signal is released. The BIOS does this because the memory subsystem is configured to stop the system if it receives a LOCK# signal.
CAUSE
This problem occurs because of behavior that occurs when this bit is set. A .NET Framework 1.1 application can issue a request that the application assumes is atomic. However, the request is not atomic. This behavior can lead to memory corruption if two or more processors issue a command to access the same misaligned data structure at the same time.
Note A convention exists between hardware and software vendors that software will only use LOCK# signals for data that is aligned to a memory address that is a multiple of the size of the memory address. This convention prevents LOCK# signals from being asserted outside the processor and having performance and functionality implications.
RESOLUTION
Hotfix information
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 Microsoft .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.
Prerequisites
There are no prerequisites for applying this hotfix.
Restart requirement
You must restart the computer after you apply this hotfix.
File Information
The English version of this hotfix has the file attributes (or later file attributes) 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.
| File name | File version | File size | Date | Time | Platform |
|---|---|---|---|---|---|
| Corperfmonext.dll | 1.1.4322.2349 | 81,920 | 23-Sep-2005 | 08:05 | x86 |
| Mscorlib.dll | 1.1.4322.2349 | 2,142,208 | 23-Sep-2005 | 01:43 | x86 |
| Mscorsvr.dll | 1.1.4322.2349 | 2,519,040 | 23-Sep-2005 | 08:05 | x86 |
| Mscorwks.dll | 1.1.4322.2349 | 2,506,752 | 23-Sep-2005 | 08:05 | x86 |
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
MORE INFORMATION
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Keywords: kbwinserv2003sp2fix kbfix kbbug kbnetframe110presp2fix kbqfe kbhotfixserver KB907544
