Laptop Computer Hangs During Docking or Undocking (288430)
The information in this article 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.
RESOLUTIONA 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
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
| Modification Type: | Major | Last Reviewed: | 8/8/2006 |
|---|
| Keywords: | kbHotfixServer kbQFE kbfix kbOSWin98fix kbprb kbQFE KB288430 kbAudDeveloper kbAudOEM |
|---|
|