Microsoft KB Archive/931365

From BetaArchive Wiki

Article ID: 931365

Article Last Modified on 9/11/2007


  • Windows Vista Enterprise 64-bit Edition
  • Windows Vista Home Premium 64-bit Edition
  • Windows Vista Ultimate 64-bit Edition
  • Windows Vista Business
  • Windows Vista Business 64-bit Edition
  • Windows Vista Enterprise
  • Windows Vista Home Premium
  • Windows Vista Ultimate


When you use an Internet Protocol security (IPsec) tunnel mode connection to communicate from a Windows Vista-based computer to another computer, the Windows Vista-based computer may restart. Also, you may receive an error message that resembles the following:

STOP 0x000000D1 (parameter1, parameter2, parameter3, parameter4)

This problem occurs if you install antivirus filter drivers on the Windows Vista-based computer.


This problem occurs because of an error in the IPsec component. The IPsec component incorrectly dereferences some specific memory that is accessed as a network packet.


Hotfix information

A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.


No prerequisites are required.

Restart requirement

You must restart your computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other previously released hotfixes.

Registry information

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

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Vista, x86-based versions
File name File version File size Date Time Platform
Update.mum Not applicable 2,679 07-Mar-2007 18:37 Not applicable
X86_24bf0273fbf35bbcd0434b86e60a7e97_31bf3856ad364e35_6.0.6000.20551_none_b37733fe022d9b52.manifest Not applicable 704 07-Mar-2007 18:37 Not applicable
X86_d012dfc4c8cf16500baa86f7bafb6989_31bf3856ad364e35_6.0.6000.20551_none_298f2691411de3de.manifest Not applicable 708 07-Mar-2007 18:37 Not applicable
X86_microsoft-windows-netio-infrastructure_31bf3856ad364e35_6.0.6000.20551_none_5509b7dcd16c40f6.manifest Not applicable 4,162 07-Mar-2007 18:39 Not applicable
X86_microsoft-windows-network-security_31bf3856ad364e35_6.0.6000.20551_none_cb92baf046a991a0.manifest Not applicable 131,366 07-Mar-2007 18:39 Not applicable
Netio.sys 6.0.6000.20551 216,760 07-Mar-2007 03:06 x86
Bfe.dll 6.0.6000.20551 317,440 07-Mar-2007 02:51 x86
Fwpkclnt.sys 6.0.6000.20551 84,992 07-Mar-2007 02:08 x86
Fwpuclnt.dll 6.0.6000.20551 543,232 07-Mar-2007 02:51 x86
Ikeext.dll 6.0.6000.20551 416,768 07-Mar-2007 02:51 x86
Wfp.mof Not applicable 812 07-Jan-2007 05:32 Not applicable
Wfp.tmf Not applicable 115,173 07-Mar-2007 02:09 Not applicable
Windows Vista, x64-based versions
File name File version File size Date Time Platform
Amd64_d00a6d860e443a63cefea139bada74e1_31bf3856ad364e35_6.0.6000.20551_none_cceb70191e8dbd1f.manifest Not applicable 712 07-Mar-2007 18:37 Not applicable
Amd64_eb8e77ad6ad90193e7ef2724c467cddf_31bf3856ad364e35_6.0.6000.20551_none_1ebf89beda91ecd1.manifest Not applicable 708 07-Mar-2007 18:37 Not applicable
Amd64_microsoft-windows-netio-infrastructure_31bf3856ad364e35_6.0.6000.20551_none_b128536089c9b22c.manifest Not applicable 4,170 07-Mar-2007 19:27 Not applicable
Amd64_microsoft-windows-network-security_31bf3856ad364e35_6.0.6000.20551_none_27b15673ff0702d6.manifest Not applicable 131,410 07-Mar-2007 19:27 Not applicable
Update.mum Not applicable 2,695 07-Mar-2007 18:37 Not applicable
Netio.sys 6.0.6000.20551 324,280 07-Mar-2007 04:10 x64
Bfe.dll 6.0.6000.20551 439,808 07-Mar-2007 03:57 x64
Fwpkclnt.sys 6.0.6000.20551 147,456 07-Mar-2007 02:35 x64
Fwpuclnt.dll 6.0.6000.20551 712,192 07-Mar-2007 03:58 x64
Ikeext.dll 6.0.6000.20551 418,816 07-Mar-2007 03:58 x64
Wfp.mof Not applicable 812 07-Jan-2007 05:32 Not applicable
Wfp.tmf Not applicable 115,073 07-Mar-2007 02:35 Not applicable


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


For more information, 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

Keywords: kbfix kbqfe kbpubtypekc kbexpertiseadvanced kbhotfixserver KB931365