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. "Out of memory" error message when you run a DirectX 11 game in Windows 8.1 or Windows Server 2012 R2

"Out of memory" error message when you run a DirectX 11 game in Windows 8.1 or Windows Server 2012 R2

View products that this article applies to.

Symptoms

You run a DirectX 11 game on a computer that is running Windows 8.1 or Windows Server 2012 R2. If you run the game in full-screen mode in a non-native resolution, you eventually receive an "Out of memory" error message.

↑ Back to the top

Resolution

Hotfix information

A supported hotfix is available from Microsoft Support. 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 the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

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, contact 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, go to 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 update, you must first have update 2919355 installed in Windows 8.1 or Windows Server 2012 R2.

Restart requirement

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

Hotfix replacement information

This hotfix does not replace any previously released hotfix.

↑ Back to the top

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 8.1 and Windows Server 2012 R2 file information and notes

Important Windows 8.1 and Windows Server 2012 R2 hotfixes are included in the same packages. However, only "Windows 8.1" 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.1" 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.3.960 0.17 xxxWindows 8.1 and Windows Server 2012 R2RTMGDR
  • 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.1 and Windows Server 2012 R2" 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.1
File nameFile versionFile sizeDateTimePlatform
Microsoft-windows-desktopwindowmanager-compositor.ptxmlNot applicable4,06921-Aug-201323:39Not applicable
D3d11.dll6.3.9600.170411,779,80006-Mar-201411:13x86
Lddmcore.ptxmlNot applicable7,20806-Mar-201401:37Not applicable
For all supported x64-based versions of Windows 8.1 and Windows Server 2012 R2
File nameFile versionFile sizeDateTimePlatform
Microsoft-windows-desktopwindowmanager-compositor.ptxmlNot applicable4,06922-Aug-201306:44Not applicable
Lddmcore.ptxmlNot applicable7,20806-Mar-201401:36Not applicable
Microsoft-windows-desktopwindowmanager-compositor.ptxmlNot applicable4,06921-Aug-201323:39Not applicable
D3d11.dll6.3.9600.170411,779,80006-Mar-201411:13x86
For all supported ARM-based versions of Windows 8.1
File nameFile versionFile sizeDateTimePlatform
Microsoft-windows-desktopwindowmanager-compositor.ptxmlNot applicable4,06921-Aug-201323:33Not applicable
D3d11.dll6.3.9600.170411,648,66406-Mar-201408:16Not applicable
Lddmcore.ptxmlNot applicable7,20806-Mar-201401:34Not applicable

Additional file information for Windows 8.1 and Windows Server 2012 R2

Additional files for all supported x86-based versions of Windows 8.1
File nameX86_3fff9772b04aac379884e169e0ab0136_31bf3856ad364e35_6.3.9600.17205_none_6dce9822c8875dbf.manifest
File versionNot applicable
File size1,050
Date (UTC)12-Jun-2014
Time (UTC)21:38
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameX86_6957bf4efc751708405f0ee86c665ecf_31bf3856ad364e35_6.3.9600.17205_none_395e3a458abfc40e.manifest
File versionNot applicable
File size696
Date (UTC)12-Jun-2014
Time (UTC)21:38
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameX86_c97cd486519ed1f4398494944ef5f490_31bf3856ad364e35_6.3.9600.17205_none_1fcf56ec105f677a.manifest
File versionNot applicable
File size1,753
Date (UTC)12-Jun-2014
Time (UTC)21:38
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameX86_microsoft-windows-d..wmanager-compositor_31bf3856ad364e35_6.3.9600.17205_none_9a797e7a5ab5da04.manifest
File versionNot applicable
File size155,729
Date (UTC)12-Jun-2014
Time (UTC)21:38
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameX86_microsoft-windows-directx-direct3d11_31bf3856ad364e35_6.3.9600.17205_none_84af7a59e90402e9.manifest
File versionNot applicable
File size714,950
Date (UTC)12-Jun-2014
Time (UTC)21:38
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameX86_microsoft-windows-directx-dxgi_31bf3856ad364e35_6.3.9600.17205_none_cf75a3d639e4a54f.manifest
File versionNot applicable
File size112,634
Date (UTC)11-Jun-2014
Time (UTC)23:49
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameX86_microsoft-windows-lddmcore_31bf3856ad364e35_6.3.9600.17205_none_40bfc421fee4b103.manifest
File versionNot applicable
File size385,244
Date (UTC)12-Jun-2014
Time (UTC)21:38
SHA-1 hashNot applicable
MD5 hashNot applicable
Additional files for all supported x64-based versions of Windows 8.1 and Windows Server 2012 R2
File nameAmd64_2cb0a3f4e8d473b572b1f8c04a7c260d_31bf3856ad364e35_6.3.9600.17205_none_ac46a414d3d23289.manifest
File versionNot applicable
File size1,056
Date (UTC)13-Jun-2014
Time (UTC)06:23
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameAmd64_3742686dc906901e980ea80fa8691db1_31bf3856ad364e35_6.3.9600.17205_none_6ffae3a5fd2ff426.manifest
File versionNot applicable
File size700
Date (UTC)13-Jun-2014
Time (UTC)06:23
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameAmd64_3fff9772b04aac379884e169e0ab0136_31bf3856ad364e35_6.3.9600.17205_none_c9ed33a680e4cef5.manifest
File versionNot applicable
File size1,052
Date (UTC)13-Jun-2014
Time (UTC)06:23
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameAmd64_969abded61e818fcbc8d107aa28ac460_31bf3856ad364e35_6.3.9600.17205_none_f6510823a9f0cfef.manifest
File versionNot applicable
File size1,086
Date (UTC)13-Jun-2014
Time (UTC)06:23
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameAmd64_microsoft-windows-d..wmanager-compositor_31bf3856ad364e35_6.3.9600.17205_none_f69819fe13134b3a.manifest
File versionNot applicable
File size155,730
Date (UTC)12-Jun-2014
Time (UTC)02:00
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameAmd64_microsoft-windows-directx-direct3d11_31bf3856ad364e35_6.3.9600.17205_none_e0ce15dda161741f.manifest
File versionNot applicable
File size714,952
Date (UTC)13-Jun-2014
Time (UTC)06:23
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameAmd64_microsoft-windows-directx-dxgi_31bf3856ad364e35_6.3.9600.17205_none_2b943f59f2421685.manifest
File versionNot applicable
File size112,636
Date (UTC)12-Jun-2014
Time (UTC)02:01
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameAmd64_microsoft-windows-lddmcore_31bf3856ad364e35_6.3.9600.17205_none_9cde5fa5b7422239.manifest
File versionNot applicable
File size385,248
Date (UTC)13-Jun-2014
Time (UTC)06:23
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameX86_microsoft-windows-d..wmanager-compositor_31bf3856ad364e35_6.3.9600.17205_none_9a797e7a5ab5da04.manifest
File versionNot applicable
File size155,729
Date (UTC)13-Jun-2014
Time (UTC)06:23
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameX86_microsoft-windows-directx-direct3d11_31bf3856ad364e35_6.3.9600.17205_none_84af7a59e90402e9.manifest
File versionNot applicable
File size714,950
Date (UTC)13-Jun-2014
Time (UTC)06:23
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameX86_microsoft-windows-directx-dxgi_31bf3856ad364e35_6.3.9600.17205_none_cf75a3d639e4a54f.manifest
File versionNot applicable
File size112,634
Date (UTC)11-Jun-2014
Time (UTC)23:49
SHA-1 hashNot applicable
MD5 hashNot applicable
Additional files for all supported ARM-based versions of Windows 8.1
File nameArm_4575f998c807aa8af365bacaab2a7d8b_31bf3856ad364e35_6.3.9600.17205_none_146aafea879c9638.manifest
File versionNot applicable
File size1,753
Date (UTC)12-Jun-2014
Time (UTC)21:37
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameArm_621e26b966e80620eb390e29c410f073_31bf3856ad364e35_6.3.9600.17205_none_61b2fa5d7f4bac6b.manifest
File versionNot applicable
File size696
Date (UTC)12-Jun-2014
Time (UTC)21:37
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameArm_microsoft-windows-d..wmanager-compositor_31bf3856ad364e35_6.3.9600.17205_none_9a7bf0d25ab2f8ca.manifest
File versionNot applicable
File size155,726
Date (UTC)11-Jun-2014
Time (UTC)23:53
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameArm_microsoft-windows-directx-direct3d11_31bf3856ad364e35_6.3.9600.17205_none_84b1ecb1e90121af.manifest
File versionNot applicable
File size714,950
Date (UTC)12-Jun-2014
Time (UTC)21:37
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameArm_microsoft-windows-directx-dxgi_31bf3856ad364e35_6.3.9600.17205_none_cf78162e39e1c415.manifest
File versionNot applicable
File size112,634
Date (UTC)11-Jun-2014
Time (UTC)23:53
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameArm_microsoft-windows-lddmcore_31bf3856ad364e35_6.3.9600.17205_none_40c23679fee1cfc9.manifest
File versionNot applicable
File size385,244
Date (UTC)12-Jun-2014
Time (UTC)21:37
SHA-1 hashNot applicable
MD5 hashNot applicable

↑ 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

References

Learn about the terminology that Microsoft uses to describe software updates.

↑ Back to the top

Keywords: kb, kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbexpertiseinter, kbsurveynew, kbbug

↑ Back to the top

Article Info
Article ID : 2976943
Revision : 1
Created on : 1/7/2017
Published on : 8/12/2014
Exists online : False
Views : 211