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. A deadlock may occur when the FreePhysPage function and the HNDLCreateHandle function run at the same time in Windows Embedded CE 6.0 R3

A deadlock may occur when the FreePhysPage function and the HNDLCreateHandle function run at the same time in Windows Embedded CE 6.0 R3

Symptoms

A deadlock may occur when the following two functions run at the same time in Windows Embedded CE 6.0 R3:
  • FreePhysPage 
  • HNDLCreateHandle 
Note The FreePhysPage function is called to free physical memory and the HNDLCreateHandle function is called to create object handles.

↑ Back to the top

Cause

This issue occurs because these two functions call both the critical section and the object handle table lock. However, the functions call the critical section and the object handle table lock in a different order.

↑ Back to the top

Resolution

Software update information

A supported software update is now available from Microsoft as Windows Embedded CE 6.0 Platform Builder Monthly Update (March 2011). You can confirm this by scrolling to the "File information" section of this article. The package file name contains the product version, date, Knowledge Base article number, and processor type. The package file name format is:
Product version-yymmdd-kbnnnnnn-processor type
For example: Wincepb50-060503-kb917590-armv4i.msi is the ARMV4i Windows Embedded CE 5.0 Platform Builder fix that is documented in KB article 917590 and that is contained in the May 2006 monthly update. To resolve this problem immediately, click the following article number for information about obtaining Windows Embedded CE Platform Builder and core operating system software updates:
837392 How to locate core operating system fixes for Microsoft Windows Embedded CE Platform Builder products


Note This Windows Embedded CE 6.0 Monthly Update is also available for download from the following Microsoft Download Center website:
Windows Embedded CE 6.0 Updates

Prerequisites

To apply this software update, you must have all previously issued software updates for this product installed.

Restart requirement

After you install this software update, you must perform a clean build of the whole platform. To do this, use one of the following methods:
  • On the Build menu, click Clean Solution, and then click Build Solution.
  • On the Build menu, click Rebuild Solution.
You do not have to restart the computer after you apply this software update.

Update replacement information

This update does not replace any updates.

File information

The English version of this software update package 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.
Installer files
Wincepb60-110321-kb2514264-armv4i.msi3,502,59221-Mar-201123:12
Wincepb60-110321-kb2514264-mipsii.msi3,340,80021-Mar-201123:12
Wincepb60-110321-kb2514264-mipsii_fp.msi3,456,00021-Mar-201123:12
Wincepb60-110321-kb2514264-mipsiv.msi3,377,15221-Mar-201123:12
Wincepb60-110321-kb2514264-mipsiv_fp.msi3,500,54421-Mar-201123:12
Wincepb60-110321-kb2514264-sh4.msi3,155,96821-Mar-201123:12
Wincepb60-110321-kb2514264-x86.msi2,989,56821-Mar-201123:12
Files that are included in this hotfix package
Windows embedded ce 6.0_update_kb2514264.htm7,90321-Mar-201123:07110321_kb2514264
Physmem.c33,05615-Mar-201120:23Private\Winceos\Coreos\Nk\Kernel
Schedule.c29,26715-Mar-201120:23Private\Winceos\Coreos\Nk\Kernel
Nkmain.lib2,742,83215-Mar-201120:20Public\Common\Oak\Lib\Armv4i\Debug
Nkprmain.lib2,779,69615-Mar-201120:20Public\Common\Oak\Lib\Armv4i\Debug
Nkmain.lib1,766,11815-Mar-201120:20Public\Common\Oak\Lib\Armv4i\Retail
Nkprmain.lib1,791,54615-Mar-201120:20Public\Common\Oak\Lib\Armv4i\Retail
Nkmain.lib2,585,94815-Mar-201120:21Public\Common\Oak\Lib\Mipsii\Debug
Nkprmain.lib2,621,93415-Mar-201120:21Public\Common\Oak\Lib\Mipsii\Debug
Nkmain.lib1,675,44815-Mar-201120:21Public\Common\Oak\Lib\Mipsii\Retail
Nkprmain.lib1,705,59215-Mar-201120:21Public\Common\Oak\Lib\Mipsii\Retail
Nkmain.lib2,660,80015-Mar-201120:22Public\Common\Oak\Lib\Mipsii_fp\Debug
Nkprmain.lib2,697,06215-Mar-201120:22Public\Common\Oak\Lib\Mipsii_fp\Debug
Nkmain.lib1,735,15015-Mar-201120:21Public\Common\Oak\Lib\Mipsii_fp\Retail
Nkprmain.lib1,765,40215-Mar-201120:21Public\Common\Oak\Lib\Mipsii_fp\Retail
Nkmain.lib2,618,33815-Mar-201120:22Public\Common\Oak\Lib\Mipsiv\Debug
Nkprmain.lib2,654,45615-Mar-201120:22Public\Common\Oak\Lib\Mipsiv\Debug
Nkmain.lib1,700,49615-Mar-201120:22Public\Common\Oak\Lib\Mipsiv\Retail
Nkprmain.lib1,730,54215-Mar-201120:22Public\Common\Oak\Lib\Mipsiv\Retail
Nkmain.lib2,698,44815-Mar-201120:23Public\Common\Oak\Lib\Mipsiv_fp\Debug
Nkprmain.lib2,734,84215-Mar-201120:23Public\Common\Oak\Lib\Mipsiv_fp\Debug
Nkmain.lib1,766,65815-Mar-201120:22Public\Common\Oak\Lib\Mipsiv_fp\Retail
Nkprmain.lib1,796,80815-Mar-201120:22Public\Common\Oak\Lib\Mipsiv_fp\Retail
Nkmain.lib2,180,76415-Mar-201120:23Public\Common\Oak\Lib\Sh4\Debug
Nkprmain.lib2,205,99615-Mar-201120:23Public\Common\Oak\Lib\Sh4\Debug
Nkmain.lib1,519,02815-Mar-201120:23Public\Common\Oak\Lib\Sh4\Retail
Nkprmain.lib1,543,40415-Mar-201120:23Public\Common\Oak\Lib\Sh4\Retail
Nkmain.lib2,172,39215-Mar-201120:20Public\Common\Oak\Lib\X86\Debug
Nkprmain.lib2,200,52415-Mar-201120:20Public\Common\Oak\Lib\X86\Debug
Nkmain.lib1,531,10215-Mar-201120:20Public\Common\Oak\Lib\X86\Retail
Nkprmain.lib1,551,11415-Mar-201120:20Public\Common\Oak\Lib\X86\Retail

↑ 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

↑ Back to the top

Keywords: kb, kbexpertiseadvanced, kbsurveynew, atdownload, kbfix, kbqfe

↑ Back to the top

Article Info
Article ID : 2514264
Revision : 2
Created on : 4/9/2020
Published on : 4/9/2020
Exists online : False
Views : 92