Registrations are now open. Join us today!
There is still a lot of work to do on the wiki yet! More information about editing can be found here.
Already have an account?

Microsoft KB Archive/925793

From BetaArchive Wiki

Article ID: 925793

Article Last Modified on 8/29/2007


  • Microsoft Windows XP Embedded


Consider the following scenario:

  • You have a Microsoft Windows XP Embedded-based computer that uses a disk that is part of a Storage Area Network (SAN) array.
  • You use the /maxmem switch to specify the maximum amount of random access memory (RAM) memory that Windows may use.
  • You use drivers that use the MmMapIoSpace and the MmUnmapIoSpace functions. These functions record a log of mapping and of unmapping of memory that is larger than the maximum memory value.

In this scenario, you may receive a Stop error message that resembles the following:



This problem can occur because of stale Translation Look-aside Buffer (TLB) entries in which the virtual-to-physical mapping does not match the Page Table Entry (PTE). The error occurs when the MmMapIoSpace function is called by using either MmCached or MmNoncached memory, and the stale TLB entries are not correctly invalidated. When the MmMapIoSpace function is called by using MmUncached memory, the TLB entries are correctly invalidated. The problem does not occur if the drivers use the MmMapIoSpace or the MmUnmapIoSpace functions only at load and unload time.


To resolve this problem, install Windows XP Embedded Service Pack 2 (SP2). For more information, click the following article number to view the article in the Microsoft Knowledge Base:

322389 How to obtain the latest Windows XP service pack

Hotfix information

A supported hotfix is now 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. This hotfix might 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, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:

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.

File name File version File size Date Time Platform SP requirement
Ntkrnlpa.exe 5.1.2600.3044 2,059,264 30-Nov-2006 11:37 x86 SP2
Ntoskrnl.exe 5.1.2600.3044 2,182,016 30-Nov-2006 12:49 x86 SP2
Updspapi.dll 371,424 12-Oct-2005 23:12 x86 SP2


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


For more information about how hotfix packages are named, click the following article number to view the article in the Microsoft Knowledge Base:

816915 New file naming schema for Microsoft Windows software update packages

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

Additional query words: stale TLB TB flush PTE STOP BugCheck BSOD blue screen of death

Keywords: kbfix kbbug kbhotfixserver kbqfe kberrmsg kbexpertiseadvanced KB925793