Error Message: An Exception 0D has occurred at VXD VMM(0H)+00005B01 0028:C0006B01 (256850)

SYMPTOMS

You may receive the following error message on a blue screen while Windows 98 Second Edition is starting:

An Exception 0D has occurred at VXD VMM(0H)+00005B01 0028:C0006B01

Note that this behavior occurs only on double-byte character set (DBCS) versions of Windows 98 Second Edition (this includes language versions such as Chinese [both Simplified and Traditional], Japanese [including the NEC platform], and Korean).

CAUSE

AMD K6-2 350MHz and faster processors that have a CPU ID of 0x58c (Family 5, Model 8, Stepping C) are sensitive to a particular string of instructions in the DBCS Vmm.vxd virtual device driver for Windows 98 Second Edition. This condition occurs only on a very small percentage of computers with this hardware and software combination.

RESOLUTION

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

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

http://support.microsoft.com/contactus/?ws=support

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.

The Japanese version of this fix should have the following file attributes or later:

   Date      Time    Version        Size      File name
   ----------------------------------------------------
   03/10/00  8:50pm  04.10.00.2223  477,172   Vmm.vxd

MORE INFORMATION

For additional information about Windows 98 and Windows 98 Second Edition hotfixes, click the article number below to view the article in the Microsoft Knowledge Base: