A "0x000000D1" Stop error occurs when you run a telephony application that uses the RAS PPPoE driver in Windows 7

Applies to: Windows 7 EnterpriseWindows 7 Home BasicWindows 7 Home Premium

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


Consider the following scenario:

  • You have a computer that is running a 32-bit version of Windows 7.
  • You run a telephony application that uses the Remote Access Service (RAS) Point-to-Point Protocol over Ethernet (PPPoE) driver on the computer.
In this scenario, you receive a Stop error that resembles the following:

0x000000D1 ( parameter1 , parameter2 , parameter3 , parameter4 )

  • The parameters in this error message vary, depending on the configuration of the computer.
  • Not all "0x000000D1" Stop errors are caused by this issue.


This issue occurs because the RAS PPPoE driver (Rasppoe.sys) tries to perform an operation that is not permitted during the Deferred Procedure Call (DPC) processing.


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.


To apply this hotfix, you must be running one of the following operating systems:
  • Windows 7
  • Windows 7 Service Pack 1 (SP1)

Registry information

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

Restart requirement

You 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 7 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  0.
    Windows 7RTMLDR
    6.1.760  1.
    Windows 7SP1LDR
  • 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 7" 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 7
File nameFile versionFile sizeDateTimePlatformService branch


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

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

Additional files for all supported x86-based versions of Windows 7
File nameUpdate.mum
File versionNot applicable
File size2,731
Date (UTC)13-Jan-2011
Time (UTC)15:55
PlatformNot applicable
File nameX86_1e96add1a62ca642e72da4558ddc7f5f_31bf3856ad364e35_6.1.7600.20879_none_93d2251428def47d.manifest
File versionNot applicable
File size704
Date (UTC)13-Jan-2011
Time (UTC)15:55
PlatformNot applicable
File nameX86_5ecef0eeb45383a43b64acab01284a23_31bf3856ad364e35_6.1.7601.21640_none_2916b2835a02000a.manifest
File versionNot applicable
File size704
Date (UTC)13-Jan-2011
Time (UTC)15:55
PlatformNot applicable
File nameX86_microsoft-windows-rasbase-raspppoe_31bf3856ad364e35_6.1.7600.20879_none_56a24fbb14fd4c56.manifest
File versionNot applicable
File size2,904
Date (UTC)13-Jan-2011
Time (UTC)06:16
PlatformNot applicable
File nameX86_microsoft-windows-rasbase-raspppoe_31bf3856ad364e35_6.1.7601.21640_none_58a019eb12138060.manifest
File versionNot applicable
File size2,904
Date (UTC)13-Jan-2011
Time (UTC)06:09
PlatformNot applicable