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. "0x0000003B" or "0x0000007E" Stop error on a Windows-based computer that has 4K sector disks

"0x0000003B" or "0x0000007E" Stop error on a Windows-based computer that has 4K sector disks

View products that this article applies to.

This article describes various known issues that occur when system files or device drivers are compressed in Windows 8.1, Windows RT 8.1, or Windows Server 2012 R2. A hotfix is available to resolve this issue. The hotfix has a prerequisite.

↑ Back to the top

Symptoms

Assume that you have a computer that is running Windows 8.1, Windows RT 8.1, or Windows Server 2012 R2 and has Advanced Format disks that have a 4,096 bytes (4K) physical sector size.

The servicing stack in Windows 8.1, Windows RT 8.1, and Windows Server 2012 R2 may enable NTFS compression on some device drivers and other system files in order to save disk space. For example, this may occur after you install a Windows Update.

Because of a problem in the Ntfs.sys file, when the compressed files are loaded from a 4K sector disk, various drivers may encounter failures because of random access memory (RAM) that is expected to be initialized to zero contains random data instead.

Known Issues that are fixed in this hotfix

  • You try to mount a virtual hard disk (VHD or VHDX) on the computer. In this situation, you receive a Stop error that resembles the following:

    SYSTEM_SERVICE_EXCEPTION
    STOP: 0x0000003B (parameter1, parameter2, parameter3, parameter4)
  • During the start of the computer, you receive a Stop error that resembles the following:

    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
    STOP: 0x0000007E (parameter1, parameter2, parameter3, parameter4)
If you analyze the memory dump file by using a debugger, you may notice that intelppm.sys has tried to execute some code at an invalid address. Or, you may see a failure occurred when the wpprecorder.sys was loaded during the initialization of another driver, such as cdrom.sys.

Notes
  • The parameters in the Stop error messages vary, depending on the configuration of the computer.
  • Not all "0x0000003B" or "0x0000007E" Stop errors are caused by this issue.
  • Sometimes system files are compressed after you install a Windows update.

↑ Back to the top

Cause

This issue occurs because the read of the compressed file has to be double-buffered. When the compressed binaries on 4K sector disks are read into memory, some memory may be copied beyond the original buffer length.

↑ Back to the top

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 have

update 2919355 installed in Windows 8.1 or Windows Server 2012 R2.

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

Important Windows 8.1 hotfixes and Windows Server 2012 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8.1/Windows Server 2012 R2" 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.17xxxWindows 8.1, Windows RT 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" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very 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
Ntfs.sys6.3.9600.176311,687,87214-Jan-201520:06x86
For all supported x64-based versions of Windows 8.1 and of Windows Server 2012 R2
File nameFile versionFile sizeDateTimePlatform
Ntfs.sys6.3.9600.176312,022,72014-Jan-201520:12x64
For all supported ARM-based versions of Windows 8.1
File nameFile versionFile sizeDateTimePlatform
Ntfs.sys6.3.9600.176311,495,88814-Jan-201520:18Not applicable

Additional file information

Additional file information for Windows 8.1 and for Windows Server 2012 R2
Additional files for all supported x86-based versions of Windows 8.1
File propertyValue
File nameX86_a5d431249bef2b5984ca7827a947e986_31bf3856ad364e35_6.3.9600.17633_none_b0057fc0d2074ef4.manifest
File versionNot applicable
File size692
Date (UTC)14-Jan-2015
Time (UTC)20:30
PlatformNot applicable
File nameX86_microsoft-windows-ntfs_31bf3856ad364e35_6.3.9600.17633_none_3b45ec80385d9adb.manifest
File versionNot applicable
File size16,008
Date (UTC)14-Jan-2015
Time (UTC)20:34
PlatformNot applicable
Additional files for all supported x64-based versions of Windows 8.1 and of Windows Server 2012 R2
File propertyValue
File nameAmd64_c6023eb259ca802b99b3e661e37dc48b_31bf3856ad364e35_6.3.9600.17633_none_bd094807436c299f.manifest
File versionNot applicable
File size696
Date (UTC)14-Jan-2015
Time (UTC)20:30
PlatformNot applicable
File nameAmd64_microsoft-windows-ntfs_31bf3856ad364e35_6.3.9600.17633_none_97648803f0bb0c11.manifest
File versionNot applicable
File size16,014
Date (UTC)14-Jan-2015
Time (UTC)20:38
PlatformNot applicable
Additional files for all supported ARM-based versions of Windows 8.1
File propertyValue
File nameArm_bc13181ffa3e7154af502f1530c9b6f8_31bf3856ad364e35_6.3.9600.17633_none_2efec30083ff7f01.manifest
File versionNot applicable
File size692
Date (UTC)14-Jan-2015
Time (UTC)20:30
PlatformNot applicable
File nameArm_microsoft-windows-ntfs_31bf3856ad364e35_6.3.9600.17633_none_3b485ed8385ab9a1.manifest
File versionNot applicable
File size16,008
Date (UTC)14-Jan-2015
Time (UTC)20:30
PlatformNot 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

See the terminology that Microsoft uses to describe software updates.

↑ Back to the top

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

↑ Back to the top

Article Info
Article ID : 3027108
Revision : 1
Created on : 1/7/2017
Published on : 7/17/2015
Exists online : False
Views : 192