A memory leak occurs in Windows XP when you play a Digital Rights Management-enabled video for a long time


A memory leak occurs when you play a Digital Rights Management (DRM)-enabled video in Windows XP. Therefore, system performance gradually decreases when you play DRM-enabled videos for a long time. After an extended time, the system may stop responding (hang) or crash.


When you play DRM-enabled video in Windows XP, the Cryptographic service is used to decrypt the DRM content by using the Microsoft Jet database. The Cryptographic service allocates memory to cache the state of the open database sessions, tables, and other related data. Additionally, a thread checks whether the cache is stale or not. If the thread is not accessed within the time-out limit, it clears the cache on the side of the Cryptographic service. However, the thread does not clear the session state on the side of the Jet database. Because there is an error in the database memory and the resource requirement calculation logic, the JET database goes on committing more and more memory and does not free it.


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 Web site: 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.


To apply this hotfix, you must be running Windows XP Service Pack 2 (SP2) or Windows XP Service Pack 3 (SP3).For more information about how to obtain a Windows XP service pack, click the following article number to view the article in the Microsoft Knowledge Base:

322389 How to obtain the latest Windows XP service pack

Registry information

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

Restart requirement

You may have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The English (United States) 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 XP file information notes
  • In addition to the files that are listed in these tables, this hotfix also installs an associated security catalog file (KBnumber.cat) that is signed with a Microsoft digital signature.
For all supported x86-based versions of Windows XP SP2
File nameFile versionFile sizeDateTimePlatform
For all supported x86-based versions of Windows XP SP3
File nameFile versionFile sizeDateTimePlatform


To work around this issue, set the following two time-out settings to very large values. The value that you set depends on the situation that you are encountering.
Location: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\CatalogDB
Name: CallbackTime
Location: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\CatalogDB
Name: DatabaseTimeout


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