Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Access violation when a Visual C++ application tries to create a processor component in Windows 8 or Windows Server 2012

Access violation when a Visual C++ application tries to create a processor component in Windows 8 or Windows Server 2012

View products that this article applies to.

Symptoms

Consider the following scenario:
  • You run a Visual C++ application on a computer that is running Windows 8 or Windows Server 2012.
  • The application uses Microsoft XML Core Services 6.0 (MSXML 6.0) to cache complied XSLT style sheets multiple times into an IXSLTemplate object.
  • The application tries to create a processor component by using the IXSLTemplate object.
In this scenario, the application crashes and throws an access violation exception that resembles the following:
c0000005 (Access violation)

↑ Back to the top

Cause

This issue occurs because a certain document object in an old StyleSheet object in the cache loses the last reference from the IXSLTemplate object. A new StyleSheet object obtains a reference from the IXSLTemplate object. Therefore, the access violation occurs.

↑ Back to the top

Resolution

This hotfix is also available at Microsoft Update Catalog.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:
http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must be running Windows 8 or Windows Server 2012.

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.
File information
The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.





Windows 8 and Windows Server 2012 file information notes
Important Windows 8 hotfixes and Windows Server 2012 hotfixes are included in the same packages. However, only "Windows 8" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:

    VersionProductMilestoneService branch
    6.2.920 0.20 xxxWindows 8 and Windows Server 2012RTMLDR
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows 8 and Windows Server 2012" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows 8
File nameFile versionFile sizeDateTimePlatform
Msxml6.dll6.30.9200.207271,802,24023-May-201323:35x86
Msxml6r.dll6.30.9200.205512,04801-Nov-201204:21x86
For all supported x64-based versions of Windows 8 and of Windows Server 2012
File nameFile versionFile sizeDateTimePlatform
Msxml6.dll6.30.9200.207272,361,85624-May-201301:45x64
Msxml6r.dll6.30.9200.205512,04801-Nov-201204:21x64
Msxml6.dll6.30.9200.207271,802,24023-May-201323:35x86
Msxml6r.dll6.30.9200.205512,04801-Nov-201204:21x86

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

More Information

For more information about the IXSLTemplate object, go to the following Microsoft website:
General information about the IXSLTemplate object
For more information about software update terminology, 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
Additional file information

Additional file information for Windows 8 and Windows Server 2012

Additional files for all supported x86-based versions of Windows 8
File nameX86_53082ca14fb1c92d2650ca59ff5fc23f_31bf3856ad364e35_6.2.9200.20727_none_76c201a4693c4628.manifest
File versionNot applicable
File size695
Date (UTC)24-May-2013
Time (UTC)15:15
PlatformNot applicable
File nameX86_microsoft-windows-msxml60_31bf3856ad364e35_6.2.9200.20727_none_85e68b0681276f7e.manifest
File versionNot applicable
File size113,272
Date (UTC)24-May-2013
Time (UTC)15:15
PlatformNot applicable
Additional files for all supported x64-based versions of Windows 8 and of Windows Server 2012
File nameAmd64_5844d8b64734a668c3a7e32a3b4807c4_31bf3856ad364e35_6.2.9200.20727_none_fc096436629dcbb4.manifest
File versionNot applicable
File size699
Date (UTC)24-May-2013
Time (UTC)15:15
PlatformNot applicable
File nameAmd64_c636c7d27f16caf647ab4915ec2999ee_31bf3856ad364e35_6.2.9200.20727_none_8546e88480a2552e.manifest
File versionNot applicable
File size1,040
Date (UTC)24-May-2013
Time (UTC)15:15
PlatformNot applicable
File nameAmd64_microsoft-windows-msxml60_31bf3856ad364e35_6.2.9200.20727_none_e205268a3984e0b4.manifest
File versionNot applicable
File size113,276
Date (UTC)24-May-2013
Time (UTC)15:15
PlatformNot applicable
File nameWow64_microsoft-windows-msxml60_31bf3856ad364e35_6.2.9200.20727_none_ec59d0dc6de5a2af.manifest
File versionNot applicable
File size106,749
Date (UTC)24-May-2013
Time (UTC)15:15
PlatformNot applicable

↑ Back to the top

Keywords: kb, kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbsurveynew, kbexpertiseadvanced

↑ Back to the top

Article Info
Article ID : 2853556
Revision : 1
Created on : 1/7/2017
Published on : 7/10/2013
Exists online : False
Views : 225