Windows won't boot. Getting rdisk partition\windows message.

Anonymous
2011-05-23T14:57:00+00:00

Original Title: Can't Boot Windows XP

Hi there everyone,

The other day I un-installed some items that were clogging up my old Dell Inspiron 6000 (Norton, Nero etc).

When I restarted the computer it brings me to a screen that provides some options

-Safe Mode

-Safe Mode w/ Command Prompt

-Safe Mode w/ Networking

-Last Known Good Config

-Start Windows Normally

No matter which one I pick, the computer hangs.

If I pick any of the Safe Mode options some text appears at the bottom in relation to multi disk rdisk partition\windows... and then some .dll, .nls and .sys files.

I've tried booting from a backup disc but to no avail (I changed the BIOS settings to boot from the disc) but it still brings me to command prompt and nothing runs from there. I'm wondering if the Boot disc is funked up? I have XP on a home desktop so perhaps I should make another boot disk and try again?

I've tried working my way through some of KB articles on the site (sys restore through command prompt didn't work).

I hope I've provided enough information and I'd be very appreciative of any help.

Thanks

GM

Windows for home | Previous Windows versions | Install and upgrade

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
{count} votes
Answer accepted by question author
  1. Anonymous
    2011-05-30T21:15:24+00:00

    That sounds good so far.

    Now do this:

    Once you are booted on the CD of your choice, navigate to the following folder (assuming XP is installed on your C volume):

    c:\windows\system32\drivers

    From the Recovery Console you would enter this command:

    cd system32\drivers

    Look for a file that ends with a .sys extension and is zero bytes in length.  The file may also have a curious name since it may have been generated at random.

    If you are in the XP Recovery Console, issue the following command while in the c:\windows\system32\drivers folder:

    dir  *.sys

    The files will scroll by one screen at a time.  Look at the list of files with the .sys extensions and their lengths.  You don't need to worry about the Directories...  If you see a file(s) with a .sys extension that is zero bytes, that is the one to suspect.

    If you are using the Mini XP Mode of a Hiren's boot CD (which operates just like the XP desktop), just navigate to the folder from the My Computer desktop icon and locates the suspicious file(s).

    You will want to actually delete the suspicious file once you get running and have run some scans for malicious software, but if you are not sure what the suspicious file is or if it might be needed, just rename the suspicious file for the time being in case you are not sure.

    For example, if you found that the zigxrtml.sys file had a length of zero bytes, rename it:

    rename zigxrtml.sys   zigxrtml.bad

    Renaming or deleting the suspicious file to get the system running is not fixing the problem.  It is fixing the symptom of the problem.

    The problem is your system is infected with malicious software and you must still follow up with some scans to remove the infection.

    Once your system is running, follow up with MBAM and SAS to be sure the affliction has really been removed.

    Reduce the chances of malicious software by running some scans.

    Download, install, update and do a full scan with these free malware detection programs then resolve any remaining issues:

    Malwarebytes (MBAM):  http://malwarebytes.org/

    SUPERAntiSpyware: (SAS):  http://www.superantispyware.com/

    These can be uninstalled later if desired.

    0 comments No comments
Answer accepted by question author
  1. Anonymous
    2011-05-24T01:00:48+00:00

    If you have no bootable XP media (or are not sure what you have) create a bootable XP Recovery Console CD and be sure.

    This is not the same as any recovery disks that might have come with a store bought system.  

    You can make a bootable Recovery Console CD by downloading an ISO file and burning it to a CD.

    The bootable ISO image file you need to download is called:

    xp_rec_con.iso 

    Download the ISO file from here:

    http://www.mediafire.com/?ueyyzfymmig

    Use a new CD and this free and easy program to burn your ISO file and create your bootable CD:

    http://www.imgburn.com/

    Here are some instructions for ImgBurn:

    http://forum.imgburn.com/index.php?showtopic=61

    It would be a good idea to test your bootable CD on a computer that is working.

    You may need to adjust the computer BIOS settings to use the CD ROM drive as the first boot device instead of the hard disk.  These adjustments are made before Windows tries to load.  If you miss it, you will have to reboot the system again.

    When you boot on the CD, follow the prompts:

    Press any key to boot from CD...

    The Windows Setup... will proceed.

    Press 'R' to enter the Recovery Console.

    Select the installation you want to access (usually  1: C:\WINDOWS)

    You may be asked to enter the Administrator password (usually empty).

    You should be in the C:\WINDOWS folder.  This is the same as the 

    C:\WINDOWS folder you see in explorer.

    The Recovery Console allows basic file commands like: copy, rename, replace, delete, cd, chkdsk, fixboot, fixmbr, etc.

    For a list of Recovery Console commands, enter help at the prompt or read about the XP Recovery Console here:

    http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/recovery_console_cmds.mspx?mfr=true

    A good idea before starting things is to first verify the integrity of your file system using the chkdsk command.

    From the command prompt window run the chkdsk command on the drive where Windows is installed to try to repair any problems on the afflicted drive.

    Running chkdsk is fine even if it doesn't find any problems.  It will not hurt anything to run it.

    Assuming your boot drive is C, run the following command:

    chkdsk C: /r

    Let chkdsk finish and correct any problems it might find.  

    It may take a long time for chkdsk to complete or it may appear to be 'stuck'.  Be patient.  If the HDD light is still flashing, chkdsk is doing something.  Keep an eye on the percentage amount to be sure it is still making progress.  It may even appear to go backwards sometimes.

    You should run chkdsk /r again until it finds no errors to correct.

    0 comments No comments

10 additional answers

Sort by: Most helpful
  1. Anonymous
    2011-05-23T19:11:15+00:00

    @joselbarra > I really appreciate the quick response and help.

    If I click run in Safe Mode then a list of text is displayed underneath that options menu. The final line reads:

    multi(0)disk(0)rdisk(0)partition(2)\WINDOWS\system32\DRIVERS\isapnp.sys

    I have just restarted the computer (hitting F8) to load the Advanced Options Menu and have disables the automatic restart following a system failure.

    It then went to a blank screen and remained there until I power cycled the unit.

    I haven't gotten any BSoD

    0 comments No comments
  2. Anonymous
    2011-05-24T00:58:41+00:00

    That sounds familiar, but you are going to have to boot on something in order to fix it (if it is what I think it is).

    You can fix it from the XP Recovery Console using a genuine bootable XP installation CD, or if you don't have a genuine bootable XP installation CD, you can make a bootable Recovery Console CD, or you could make a Hiren's boot CD.

    If the MS Answers forums would prompt for this kind of information when a new question is asked, you would be done by now.

    Tell us what you have for bootable media or if you need to make a bootable CD and I will give you instructions (see next post).

    Then when you are booted on the CD, do this:

    That symptom often means your system is afflicted with malicious software.

    If you choose to boot in Safe Mode, and the last thing you see on the screen looks something like this:

    multi(0)disk(0)rdisk(0)partition(1)\WINDOWS\system32\DRIVERS\isapnp.sys

    If your system hangs in Safe Mode on the isapnp.sys file, you need to look for a driver file of zero bytes in length in the following folder:

    c:\windows\system32\drivers

    Of course you are going to have to boot the system on something in order to access the hard disk to check for the suspicious file and get rid of it.

    If you have no genuine bootable XP installation CD from which to boot into the XP Recovery Console or are not sure what kind of bootable CDs you have, make a bootable XP Recovery Console CD or a Hiren's Boot CD and be sure.

    There is no XP media required to make either a bootable XP Recovery Console or a Hiren's Boot CD.  Then you can access the folder and check to see if there is such a suspicious file and take action.

    Once you are booted on the CD of your choice, navigate to the following folder (assuming XP is installed on your C volume):

    c:\windows\system32\drivers

    Look for a file that ends with a .sys extension and is zero bytes in length.  The file may also have a curious name since it may have been generated at random.

    If you are in the XP Recovery Console, issue the following command while in the c:\windows\system32\drivers folder:

    dir  *.sys

    The files will scroll by one screen at a time.  Look at the list of files with the .sys extensions and their lengths.  You don't need to worry about the Directories...  If you see a file(s) with a .sys extension that is zero bytes, that is the one to suspect.

    If you are using the Mini XP Mode of a Hiren's boot CD (which operates just like the XP desktop), just navigate to the folder from the My Computer desktop icon and locates the suspicious file(s).

    You will want to actually delete the suspicious file once you get running and have run some scans for malicious software, but if you are not sure what the suspicious file is or if it might be needed, just rename the suspicious file for the time being in case you are not sure.

    For example, if you found that the zigxrtml.sys file had a length of zero bytes, rename it:

    rename zigxrtml.sys   zigxrtml.bad

    Renaming or deleting the suspicious file to get the system running is not fixing the problem.  It is fixing the symptom of the problem.

    The problem is your system is infected with malicious software and you must still follow up with some scans to remove the infection.

    Once your system is running, follow up with MBAM and SAS to be sure the affliction has really been removed.

    Reduce the chances of malicious software by running some scans.

    Download, install, update and do a full scan with these free malware detection programs then resolve any remaining issues:

    Malwarebytes (MBAM):  http://malwarebytes.org/

    SUPERAntiSpyware: (SAS):  http://www.superantispyware.com/

    These can be uninstalled later if desired.

    0 comments No comments
  3. Anonymous
    2011-05-23T15:27:57+00:00

    Sounds like bad ideas.

    If you choose to boot in Safe Mode what is the last thing you see on your screen?

    If there is a problem booting, XP is configured to automatically try to boot again and you can get stuck in a loop of just being unable to get past the boot options screen or none of the boot options you choose will work.

    Sometimes when XP has a problem starting or crashes and tries to start again, it will give you a "short" menu of boot options and none of them will seem to be the right ones to get your system going again.  You've tried them all!

    The options resemble the XP Advanced Boot Options menu, but the one option you need (Disable automatic restart on system failure) is not offered because XP has gone too far along in the boot process and offers you a limited number of boot options.

    If that is the case, you must invoke the Advanced Boot Options menu yourself until you do see the option:

    Disable automatic restart on system failure

    When you do get to the correct XP Advanced Options Boot menu you want to see, it has options on it like these:

    Safe Mode

    Safe Mode with Networking

    Safe Mode with Command Prompt

    Enable Boot Logging

    Enable VGA mode

    Last Known Good Configuration (your most recent settings that worked)

    Directory Services Restore Mode (Windows domain controllers only)

    Debugging Mode

    Disable automatic restart on system failure

    Start Windows Normally

    Reboot

    Return to OS Choices Menu

    What you need to choose from that menu is the option:

    Disable automatic restart on system failure

    Then if XP fails to boot normally, you will see an error screen with information and clues regarding the problem and then you can decide what to do next.

    If you do not see the Disable automatic restart on system failure option, you need to reset your system and start tapping the F8 key on the keyboard until you do see the Disable automatic restart on system failure option. 

    If you miss the F8 window of opportunity, you need to try again and start tapping the F8 key with more urgency (sooner and more frequently) until you do see Disable automatic restart on system failure, then select it.

    You need to keep trying the F8 menu until you do see Disable automatic restart on system failure option, and select it.

    If your system is experiencing a Blue Screen of Death (BSOD), we need to know what the screen says:

    Here is a BSOD example showing information you need to provide:

    http://techrepublic.com.com/i/tr/downloads/images/bsod_a.jpg

    Send the information pointed to with the red arrows (3-4 lines total).  

    Send the entire *** STOP message line since there are clues in the 4 parameters.

    If it looks like there is some kind of file name listed under the STOP message, send that line too.

    Skip the boring text unless it looks important to you.  We know what a BSOD looks like, we need to know what your BSOD looks like.

    Respond to the queries and report back the results from the Disable automatic restart on system failure screen and you can decide what to do next.

    0 comments No comments