Article ID: 174630 - View products that this article applies to.
This article was previously published under Q174630
NoticeThis article applies to Windows 2000. Support for Windows 2000 ends on July 13, 2010. The Windows 2000 End-of-Support Solution Center
(http://support.microsoft.com/?scid=http%3a%2f%2fsupport.microsoft.com%2fwin2000)is a starting point for planning your migration strategy from Windows 2000. For more information see the Microsoft Support Lifecycle Policy
When you start Windows, your computer may briefly display the blue startup screen and then continuously restart.
This behavior can occur if the following conditions exist:
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/322756/ )How to back up and restore the registry in Windows
NOTE: To work around this issue, you require a parallel installation of Windows.
To make the necessary changes, follow these steps:
Another workaround may be necessary if the minimum size of the paging file is set to a value less than the amount of physical memory. Windows requires a paging file on the system drive large enough to hold all of physical memory, plus 1 megabyte (MB), to write debugging information. You can modify the PagingFiles value of the original installation so that the dump file can be created by the STOP error message. Enough free disk space must be available on the system drive for the paging file.
Follow these steps to change the PagingFiles value in the System file in the original Windows installation location:
Windows may encounter a problem during startup that results in a STOP error message. Depending on the system configuration, the blue screen may not be displayed long enough to record the error information. Using the workarounds listed above, you can alter the startup process so that important information about the STOP error message can be gathered.
For additional information about how to troubleshoot STOP error messages, click the article numbers below to view the articles in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/123750/EN-US/ )Debugging Windows NT Setup STOP Screens
129845For additional information about a parallel install of Microsoft Small Business Server, click the article number below to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/129845/EN-US/ )Blue Screen Preparation Before Contacting Microsoft
(http://support.microsoft.com/kb/252777/EN-US/ )How to Perform a Parallel Installation on Small Business Server
Article ID: 174630 - Last Review: February 26, 2007 - Revision: 3.6