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.

Stop error message in Windows Server 2008 R2 SP1 or in Windows 7 SP1: "STOP: 0x0000007F"


View products that this article applies to.

Not sure if this is the right fix? We've added this issue to our memory dump diagnostic which can confirm.

↑ Back to the top


Symptoms

Consider the following scenario:
  • You have a computer that is running Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 SP1.
  • You perform one of the following operations:
    • You configure the computer to automatically connect to a wireless network. Then, you restart the computer or resume the computer from sleep mode or from hibernation.
    • You start data transfer with another computer through a wired or wireless network connection.
In this scenario, you may receive an error message that resembles the following under rare circumstances:
STOP: 0x0000007F (parameter1, parameter2, parameter3, parameter4) UNEXPECTED_KERNEL_MODE_TRAP

Note This issue may also occur on a computer that is running Windows 7 or Windows Server 2008 R2 and that has hotfix 979612 installed. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
979612 A hotfix is available that improves TCP loopback latency and UDP latency in Windows Server 2008, Windows Server 2008 R2, Windows Vista, and Windows 7

↑ Back to the top


Cause

This issue occurs because the operating system does not allocate enough stack space.

↑ Back to the top


Resolution

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

Prerequisites

To apply this hotfix, you must be running one of the following operating systems:
  • Windows 7 Service Pack 1 (SP1)
  • Windows Server 2008 R2 Service Pack 1 (SP1)
For more information about how to obtain a Windows 7 or a Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

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 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 7 and Windows Server 2008 R2 file information notes
Important Windows 7 hotfixes and Windows Server 2008 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 7/Windows Server 2008 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, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
    VersionProductSR_LevelService branch
    6.1.760
    1.
    17xxx
    Windows 7 and Windows Server 2008 R2SP1GDR
    6.1.760
    1.
    21xxx
    Windows 7 and Windows Server 2008 R2SP1LDR
  • GDR service branches contain only those fixes that are widely released to address widespread, very important issues. LDR service branches contain hotfixes in addition to widely released fixes.
  • 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 Server 2008 R2 and for Windows 7" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are very important for maintaining 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 7
File nameFile versionFile sizeDateTimePlatform
Fwpkclnt.sys6.1.7601.17514187,77620-Nov-201012:29x86
Tcpip.sys6.1.7601.175821,290,62419-Mar-201106:28x86
Fwpkclnt.sys6.1.7601.21687187,77619-Mar-201106:58x86
Tcpip.sys6.1.7601.216871,300,86419-Mar-201106:58x86
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Fwpkclnt.sys6.1.7601.17514288,64020-Nov-201013:33x64
Tcpip.sys6.1.7601.175821,924,48019-Mar-201107:39x64
Fwpkclnt.sys6.1.7601.21687288,64019-Mar-201107:45x64
Tcpip.sys6.1.7601.216871,927,55219-Mar-201107:45x64
For all supported IA-64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Fwpkclnt.sys6.1.7601.17514483,20020-Nov-201010:33IA-64
Tcpip.sys6.1.7601.175823,782,01619-Mar-201106:10IA-64
Fwpkclnt.sys6.1.7601.21687483,20019-Mar-201106:50IA-64
Tcpip.sys6.1.7601.216873,807,61619-Mar-201106:50IA-64

↑ 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 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 7 and for Windows Server 2008 R2

Additional files for all supported x86-based versions of Windows 7
File nameUpdate-bf.mum
File versionNot applicable
File size2,094
Date (UTC)22-Mar-2011
Time (UTC)01:35
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size2,138
Date (UTC)22-Mar-2011
Time (UTC)01:35
PlatformNot applicable
File nameX86_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7601.17582_none_b4d7cc35c4e2eaea.manifest
File versionNot applicable
File size3,780
Date (UTC)22-Mar-2011
Time (UTC)01:39
PlatformNot applicable
File nameX86_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7601.21687_none_b5666a72ddfc0967.manifest
File versionNot applicable
File size3,834
Date (UTC)19-Mar-2011
Time (UTC)07:23
PlatformNot applicable
Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameAmd64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7601.17582_none_10f667b97d405c20.manifest
File versionNot applicable
File size3,784
Date (UTC)22-Mar-2011
Time (UTC)01:43
PlatformNot applicable
File nameAmd64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7601.21687_none_118505f696597a9d.manifest
File versionNot applicable
File size3,838
Date (UTC)19-Mar-2011
Time (UTC)08:17
PlatformNot applicable
File nameUpdate-bf.mum
File versionNot applicable
File size2,304
Date (UTC)22-Mar-2011
Time (UTC)01:35
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size2,352
Date (UTC)22-Mar-2011
Time (UTC)01:35
PlatformNot applicable
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
File nameIa64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7601.17582_none_b4d9702bc4e0f3e6.manifest
File versionNot applicable
File size3,782
Date (UTC)22-Mar-2011
Time (UTC)01:35
PlatformNot applicable
File nameIa64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7601.21687_none_b5680e68ddfa1263.manifest
File versionNot applicable
File size3,836
Date (UTC)19-Mar-2011
Time (UTC)08:19
PlatformNot applicable
File nameUpdate-bf.mum
File versionNot applicable
File size1,425
Date (UTC)22-Mar-2011
Time (UTC)01:35
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size1,447
Date (UTC)22-Mar-2011
Time (UTC)01:35
PlatformNot applicable

↑ Back to the top


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

↑ Back to the top

Article Info
Article ID : 2519736
Revision : 3
Created on : 4/18/2018
Published on : 4/19/2018
Exists online : False
Views : 355