SYMPTOMS
A complex multi-threaded program that runs for a long time under stress and that makes extensive use of the MSXML 3.0 parser may generate an access violation error. The call stack for the crash that your program experiences is as follows:
ChildEBP RetAddr Args to Child
0a4be8ac 69b5d6e1 0622483c 0caabcc0 00000001 msxml3!QueryHelper__validateContextNode+0x1f
0a4be8c4 69b5daa1 09677760 00000001 0caabcc0 msxml3!XQLSelection__setContext+0x1b
0a4be8f8 69b5dc70 00677710 00000001 0caabcc0 msxml3!XQLSelection__initSelection+0xdd
0a4be93c 69b53e3d 09677710 00000001 0caabcc0 msxml3!XQLSelection__newXQLSelection+0x63
0a4be994 7c0042f3 061bfd88 0b928ee4 0a4be9c8 msxml3!DOMNode__selectNodes+0x96
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, we recommend that you wait for the next Service Pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone 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 typical 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 fix should have the following file attributes or later:
File name Size (bytes) Date Version
--------------------------------------------------
Msxml3.dll 1,105,408 13-Dec-2001 8.20.9213.0
Msxml3a.dll 24,576 13-Dec-2001 8.20.9213.0
Msxml3r.dll 44,032 13-Dec-2001 8.20.9213.0
Xmlinst.exe 28,672 13-Dec-2001 6.0.2462.0