Problems When You Swap a CD-ROM During Hibernation in Windows XP (316575)



The information in this article applies to:

  • Microsoft Windows XP Home Edition
  • Microsoft Windows XP Professional

This article was previously published under Q316575

SYMPTOMS

Under the following conditions, your CD-ROM may not work after you resume your computer, and your CD-ROM may have a Code 38 status in Device Manager:
  • Your computer was hibernating when you swapped between two ATAPI device bay CD-ROM devices.
  • You used a data CD in the original CD-ROM drive.
  • You removed the data CD from the original CD-ROM drive before your computer entered hibernation.

RESOLUTION

To resolve this problem, obtain the latest service pack for Windows XP. For additional 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

The English version of this fix has the file attributes (or later) 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 tool in Control Panel.
   Date         Time   Version      Size       File name
   --------------------------------------------------------
   10-Jul-2002  09:39  5.1.2600.49     56,064  Redbook.sys
   09-Jul-2002  19:26  5.1.2600.49  1,847,296  Ntkrnlmp.exe
   09-Jul-2002  19:28  5.1.2600.49  1,901,696  Ntkrnlpa.exe
   09-Jul-2002  19:28  5.1.2600.49  1,874,432  Ntkrpamp.exe
   09-Jul-2002  19:26  5.1.2600.49  1,879,552  Ntosknrl.exe
				

WORKAROUND

To work around this problem, use any of the following methods:
  • Use the Eject Hardware tool on the right side of the taskbar to swap drives while your computer is running.
  • Restart your computer after you swap drives.
  • Leave the CD in the drive before you eject the drive.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows XP Service Pack 1.

Modification Type:MinorLast Reviewed:9/27/2005
Keywords:kbHotfixServer kbQFE kbbug kbfix kbOSWin2000fix kbui kbWinXPsp1fix KB316575