xp home boots normal but won't boot in safe mode

By carlswee ·
My current configuration is:

Operating System System Model
Windows XP Home Edition Service Pack 2 (build 2600) Sony Corporation PCV-RX850(UC) 28471131

Processor a Main Circuit Board b
2.40 gigahertz Intel Pentium 4
8 kilobyte primary memory cache
512 kilobyte secondary memory cache Board: ASUSTeK Computer INC. P4S533VX REV 1.xx
Bus Clock: 133 megahertz
BIOS: Award Software, Inc. ACPI BIOS Revision 1001 08/20/2002
Drives Memory Modules c,d
453.98 Gigabytes Usable Hard Drive Capacity
196.78 Gigabytes Hard Drive Free Space

DVDRW IDE1008 [CD-ROM drive]
EL3943A APL802V SCSI CdRom Device [CD-ROM drive]
3.5" format removeable media [Floppy drive]

Maxtor 6Y200P0 [Hard drive] (203.93 GB) -- drive 0, s/n Y646NFQE, rev YAR41BW0, SMART Status: Healthy
Memory Stick Slot [Hard drive] -- drive 2
ST3250823A [Hard drive] (250.06 GB) -- drive 1, s/n 3ND0BNQT, rev 3.03, SMART Status: Healthy 992 Megabytes Installed Memory

Slot 'DIMM 1' has 512 MB
Slot 'DIMM 2' has 512 MB
Slot 'DIMM 3' is Empty
Local Drive Volumes

c: (NTFS on drive 0) 81.78 GB 41.42 GB free
d: (NTFS on drive 1) 96.46 GB 53.47 GB free
e: (NTFS on drive 0) 122.14 GB 35.21 GB free
f: (NTFS on drive 1) 153.60 GB 66.69 GB free

Network Drives

My Sony Desktop boots normally but won't boot in Safe mode. It goes out of scan range with the following dialogue
multi(0)disk(0)rdisk(0)partition(1)\windows\system32\drivers, etc.

I let it continue to get to safe boot but it eventually hits the point where the computer shuts down.

Any help would be most appreciated. Anyone out there have any ideas??

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Answers

Collapse -

"Goes out of scan range ..." Huh ?

by OldER Mycroft In reply to xp home boots normal but ...

What do you mean by that?

Have you attempted to activate SafeBoot from within msconfig ?

Collapse -

Re: XP home boots normal but won't boot in safe mode

Before you try the options below please (if you can) update your memory to 2gb, this will give your computer more memory to work with.
If you are not happy going down the "Command line" route then getting another hdd would be the easy option here. Just load on your windows disk to the new drive then you will be able to access your files from your old drive.

Making Repairs from the Recovery Console
What do you do if you can?t start Windows in normal or Safe Mode? Don?t give up hope. You may be able to get back to work by using the Recovery Console, a stripped-down command-line environment that provides a limited set of tools you can use to diagnose and repair problems. The Recovery Console is not for the faint of heart. But if you?re experienced with working outside a graphical environment, it can be tremendously useful.

The chief advantage of the Recovery Console over Safe Mode is that it works even when your Windows system files are corrupted. Using the Recovery Console, you can perform any of the following tasks:

Use, copy, rename, or replace Windows system files and folders
Enable or disable services or devices (these changes take effect the next time you start Windows)
Repair the file system boot sector or the Master Boot Record (MBR)
Rebuild or repair the Windows boot menu
Create and format drives
To start the Recovery Console from the Windows CD, follow these steps:

Insert the Windows CD and restart your computer. Follow your computer?s prompts to start from the CD. (You may need to adjust settings in the computer?s BIOS to enable the option to start from a CD.)
Follow the setup prompts to load the basic Windows startup files. At the Welcome To Setup screen, press R to start the Recovery Console.
If you have multiple options on the Windows startup menu, enter the number of the Windows installation you want to access from the Recovery Console.

If you have only a single Windows installation to choose from, you might be tempted to just press Enter here. DO NOT DO IT. You must type the number of the Windows installation to start the Recovery Console. If you press Enter, Windows restarts. Also, resist the temptation to select the entry for another Windows version from this menu. Although the Recovery Console automatically detects Windows 2000 and Windows NT installations on multiboot systems, logging on to one of these operating systems is not recommended, because you risk damaging the earlier operating system?s core files if you perform any repairs. To repair installations of Windows 2000, use the Recovery Console from that operating system version. To repair a Windows NT installation, use the Windows NT Emergency Repair Disk.
When prompted, type the Administrator password. If you?re using the Recovery Console on a system running Windows XP Home Edition, this password is blank by default, so just press Enter.
At the command prompt, enter Recovery Console commands directly.
To quit the Recovery Console and restart the computer, use the Exit command.
tip - Add the Recovery Console to the startup menu

With a modest amount of advance preparation, you can add the Recovery Console to the Windows XP boot menu. In this configuration, the Recovery Console files are stored on the same drive that holds your Windows system files, and you don?t need to hassle with BIOS options or boot CDs to recover from serious problems. You?ll find step-by-step instructions for configuring this option in "Adding the Recovery Console."
Recovery Console Restrictions
Although the Recovery Console prompt looks identical to the command prompt that you?re familiar with from MS-DOS or the Windows XP command interpreter (Cmd.exe), it?s not the same. After logging on to the Recovery Console, your actions are severely limited. You may access files only in the following locations:

The root directory of any volume.
The %SystemRoot% folder and subfolders of the selected Windows XP installation. On a typical clean setup or an upgrade from Windows 98 or Windows Me, this is usually C:\Windows.
The Recovery Console Cmdcons folder and any subfolders (if you installed the Recovery Console as a startup option).
Files and folders on removable disks, including floppy disks, CDs, and Zip disks.

In addition to these security-based restrictions, technical limitations impose additional restrictions on Windows XP Professional systems that use dynamic disks. If your system is configured with one or more dynamic disks, see Knowledge Base article Q227364, "Dynamic Volumes Are Not Displayed Accurately in Text-Mode Setup or Recovery Console."
If the Recovery Console allowed unlimited access to files and folders on your hard disk, it would pose a serious security hole, especially on systems running Windows XP Home Edition, where the Administrator password is blank. To prevent unauthorized access, the Recovery Console imposes the following limits on your actions when you log on:

If you try to access folders other than those described in the previous list, you will receive an "access denied" message. Specifically, you cannot read from or write to the following folders: Program Files, Documents And Settings, and disks or folders containing other Windows installations. These restrictions apply on NTFS and FAT32 volumes alike.
Write access to removable disks is disabled. This prevents you from copying files to floppy disks and other removable media. If you try to copy a file to a removable disk, you receive an "access denied" message.
You cannot change the local Administrator account password from the Recovery Console. In fact, if you use Windows XP Home Edition you have to jump through several hoops to add a password to the local Administrator account at all, as explained in "Securing the Administrator Account."
No text editing tools are available in the Recovery Console.
Using Recovery Console Commands
After you?ve logged on to Recovery Console, you can type help to see a list of all available commands. Type help commandname or use the /? switch after a command name to learn its syntax. Although many of Recovery Console?s commands are similar to those used in the Windows XP command interpreter (Cmd.exe) and its MS-DOS predecessor (, the Recovery Console versions of each command typically offer fewer options (switches). Also, unless you tweak the Recovery Console environment as outlined in "Customizing the Recovery Console", these commands do not accept wildcard specifications.

Attrib Sets or clears attributes (Read Only, Hidden, System) for a single file or folder
Batch Executes commands from a text file
Bootcfg Automatically scans all local disks for Windows installations and configures and repairs entries in the operating system menu (Boot.ini)
Cd or Chdir Changes folders
Chkdsk Checks and, if needed, repairs or recovers a drive; marks bad sectors and recovers readable information; requires that the Autochk.exe command be located in the %SystemRoot%\System32 folder or on the Windows CD
Cls Clears the screen
Copy Copies a file
Del or Delete Deletes a single file
Dir Displays folder contents and attributes for all files in the specified folder, including hidden and system files
Disable Disables a service or driver
Diskpart Manages the partitions on basic disk volumes; note that this command is not the same as the one available at a normal command prompt and should never be used with dynamic disks
Enable Enables a service or driver
Exit Closes the Recovery Console and restarts the computer
Expand Extracts a file from a compressed (.cab) file on a local disk or removable media such as the Windows CD
Fixboot Writes a new partition boot sector onto the partition you specify
Fixmbr Repairs the Master Boot Record of the specified disk, usually the system partitionFormat Formats a primary partition, volume, or logical drive using the file system you specify
Help Displays a list of all available commands
Listsvc Lists all available services and drivers and their current start types
Logon 2000 Lists all detected installations of Windows XP, Windows, and Windows NT and allows you to choose which installation you want to log on to; if you type an incorrect password three times, the system restarts
Map Lists drive letters, file system types, partition sizes, and mappings to physical devices; intended for use with basic disks only and may return inaccurate information when used with dynamic disks
Md or Mkdir Creates a new folder or subfolder in the specified location
More Displays a text file, pausing at each screenful; use the Enter key and the spacebar to scroll through a file one line at a time and one screen at a time, respectively
Rd or Rmdir Removes folders
Ren or Rename Renames a file
Set Displays or modifies Recovery Console environment variables (for details on the usage of this command, see "Customizing the Recovery Console," below)
Systemroot Sets the current folder to the %SystemRoot% folder of the current Windows installation
Type Displays a text file

Customizing the Recovery Console
With a little advance preparation, you can overcome at least some of the Recovery Console limitations listed here when running Windows XP Professional (this technique will not work with Home Edition). Doing so requires that you use the Set command to change system variables in the Recovery Console environment. By default, the Set command is disabled. To enable it, you must change system settings using the Group Policy tool. After logging on as an administrator, follow these steps:

From any command prompt, type gpedit.msc to open the Group Policy editor.
In the console pane at the left, expand Local Computer Policy, and then expand Computer Configuration, Windows Settings, Security Settings, and Local Policies.
Select Security Options from the console pane on the left.
In the list of policies on the right, double-click the entry for Recovery Console: Allow Floppy Copy And Access To All Drives And All Folders.
Select the Enabled option and then click OK.
After enabling this policy, you can start the Recovery Console, log on with the local Administrator password, and use any of the following commands to expand your capabilities: Note that the space around the equal signs is required. (To see the current settings for all four parameters, type set and press Enter.)

Set allowwildcards = true Allows you to use the * and ? wildcards with Recovery Console commands.

Set allowallpaths = true Permits you to use the Cd command to list files and subfolders in all folders on all local disks.

Set allowremovablemedia = true Allows you to copy files from local drives to removable media.

Set nocopyprompt = true Eliminates the warning message that appears when you copy one or more files that overwrite existing files using Recovery Console commands.

Repairing Damaged Boot Files
The most common cause of problems with boot files is the improper use of third-party disk utilities or failed attempts to create a multiboot system. If the setup program for another operating system is incompatible with Windows XP, it might overwrite ordamage essential startup files. The following are repair techniques available from the Recovery Console for common problems:

The Boot.ini file is corrupt or missing From the Recovery Console, type bootcfg /scan to list all available Windows installations on all available disks. Use bootcfg /rebuild to automatically replace the existing Boot.ini file; use bootcfg /add to append a Windows installation to Boot.ini without changing existing entries.

Critical system files are damaged or missing You can restore Ntldr, Ntoskrnl.exe,, and driver files from the Recovery Console. If the file exists on the Windows CD, use the Copy command and enter the source and destination; Windows expands compressed files automatically. If the file is stored within a .cab file, such as, use the Expand command.

Another operating system replaced the Windows XP boot sector code Start Recovery Console from the Windows CD and use the Fixboot command to rewrite the boot sector code. Restart your computer.

Enabling and Disabling Services and Drivers
Because services operate at a privileged level alongside crucial operating system components, it?s possible for a poorly written third-party service to crash your system. Likewise, buggy hardware drivers can interfere with startup, in some cases so severely that you encounter Stop messages even when attempting to start in Safe Mode. If you suspect that a hardware driver or a service such as an antivirus scanner or a remote-control utility is causing your problems and you can?t start Windows even in Safe Mode, use these three Recovery Console options to identify the offending service and enable or disable it:

Listsvc Enter this command to display a complete list of all services and drivers on your system, along with their current status and any optional comments. This list is long and not exactly packed with helpful information. You might need to scroll through many screens and look carefully to identify the driver or service in question. It may help if you have documentation from the developer of the suspect driver or service that lists the names of specific driver and service files.

Disable Enter this command followed by the name of the service or driver you want to stop and press Enter. The Disable command sets the start type of the service to SERVICE_DISABLED. Before doing so, it displays the current start type value of the service: SERVICE_BOOT_START, SERVICE_SYSTEM_START, SERVICE_AUTO_START, or SERVICE_DEMAND_START. Make a note of this value so that you can re-enable the device or service properly if necessary.

Enable If after troubleshooting you determine that the device you disabled is not causing your problem, use this command, followed by the service or device name and the start type value you noted when you disabled the service or device.

I hope this helps you.

Please post back if you have anymore problems or questions.

Related Discussions

Related Forums