Microsoft KB Archive/288430

From BetaArchive Wiki

Article ID: 288430

Article Last Modified on 8/8/2006



APPLIES TO

  • Microsoft Windows Millennium Edition
  • Microsoft Windows 98 Second Edition



This article was previously published under Q288430

If this article does not describe your hardware-related issue, please see the following Microsoft Resource Center to view more articles about hardware:

SYMPTOMS

Your laptop computer may stop responding (hang) when you dock or undock it. This problem can occur when a display driver issues an interrupt (INT 10H) during cursor update operations, if the computer was initially started while in the docking station.

See the "More Information" section of this article for additional information about similar problems before you obtain and install the update that is described in this article.

CAUSE

A Windows device driver may need to execute a real-mode software interrupt within the context of a timer callback, a global event callback, or a deferred procedure call. Doing so may cause a fault to occur, depending upon which thread the interrupt happens to be executing in.

Most threads created under Microsoft Windows 95 or Windows 98 share a common virtual 8086 mode (V86-mode) stack segment (SS register). Software interrupts that are reflected to V86-mode execute by using this global V86 stack segment value.

The one case in which this is not true is for threads that are created prior to the system Virtual Machine (VM) switching into protected mode. These threads have a V86-mode stack segment value of 0. V86-mode software interrupts that execute within these types of threads run with the stack segment set to 0.

The V86-mode interrupt vector table lies in memory between 0 and 400h. A software interrupt handler that runs with SS=0 will cause corruption of the interrupt vector table when it performs a stack operation, which typically leads to a processor exception.

Under typical conditions the only threads that are created prior to the system VM switching into protected-mode are worker threads that are created by Ntkern.vxd for use by Win32 Driver Model (WDM) drivers. WDM drivers do not typically use software interrupt services, so they do not typically cause this problem to occur.

Virtual device (VxD) timer callbacks, VxD global event callbacks, and Windows timers can occur in any thread context, including those created by Ntkern.vxd. If these timer/event callback functions happen to execute a software interrupt, they cause this problem to occur.

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:

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 English version of this fix should have the following file attributes or later:

   Date        Time     Version    Size     File name   Operating system
   ---------------------------------------------------------------------
   02/21/2001  10:27pm  4.10.2224  195,262  Ntkern.vxd  Windows 98 
                                                        Second Edition
   03/05/2001  02:26pm  4.10.2226  472,564  Vmm.vxd     Windows 98 
                                                        Second Edition
   02/21/2001  10:27pm  4.90.3004  203,994  Ntkern.vxd  Windows Me
   03/05/2001  02:34pm  4.90.3002  471,048  Vmm.vxd     Windows Me
                



STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

MORE INFORMATION

The update that is described in this article has been verified to also fix the problem that is described in the following article, as it applies to Windows 98 Second Edition:

246817 APM Computer with Battery May Stop Responding During Shutdown


For additional information about Windows Me hotfixes, click the article number below to view the article in the Microsoft Knowledge Base:

295413 General Information About Windows Millennium Edition Hotfixes


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:

206071 General Information About Windows 98 and Windows 98 Second Edition Hotfixes


Microsoft recommends that you inspect the following articles to see if they apply to your situation before obtaining and installing the update that is described in this article.

Windows 98 Second Edition Only

232729 Computer Hangs After Hot Dock, Suspend and Resume


238781 Computer Does Not Resume After Warm Undock with USB Controller


247177 Resuming While Docked Hangs During Dock Change Notification


263126 ACPI Laptop Computer Hangs When Docked with Display Blanked


Windows Millennium Edition Only

261307 Acer TravelMate 720 Stops Responding After Hot Docking/Undocking


263778 Problems Docking or Undocking When Computer Is in Hibernation Mode


267393 Acer TravelMate 720 Notebook Hangs After Hot Docking/Undocking



Additional query words: hang freeze sleep hibernate HWDISHHS

Keywords: kbhotfixserver kbqfe kbfix kboswin98fix kbprb kbqfe KB288430