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

Applies to: Windows Server 2012 R2 DatacenterWindows Server 2012 R2 EssentialsWindows Server 2012 R2 Foundation More

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.


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:

    STOP: 0x0000003B (parameter1parameter2parameter3parameter4)
  • During the start of the computer, you receive a Stop error that resembles the following:

    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.

  • 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.


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.

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:

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 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.


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


See the terminology that Microsoft uses to describe software updates.