Power! Power! Power!
A couple of days ago I bought a brand new ATI Radeon X800 Pro and decided to install it in my computer. Of course, I still had the cheap power supply that came with my case (300W Codegen) and it just wouldn't supply enough power, the computer would crash as soon as I tried to do anything graphics intensive. So I replaced my power supply with a 400W Antec TruePower and restarted the computer. Guess what happened? The computer would get half way through the loading Windows XP screen and then restart. It kept doing this in a continuous loop. So I went into Advanced Startup (F8) and found a cool boot mode (Disable Auto Restart) that keeps the BSOD up if the computer crashes. Sure enough the computer crashed but this time I was able to get the following error code: STOP 0x000000ED and after a quick Google search came across the following:
"RESOLUTION To resolve this behavior, use the appropriate method. UDMA ControllerIf your computer uses a UDMA hard disk controller, use the following procedures: Replace the 40-wire cable with an 80-wire UDMA cable.In the BIOS settings for your computer, load the 'Fail-Safe' default settings, and then reactivate the most frequently used options such as USB Support.Damaged File SystemIf the second parameter (0xbbbbbbbb) of the Stop error is 0xC0000032, then the file system is damaged. If this is the case, restart the computer to the Recovery Console, and then use the chkdsk /r command to repair the volume. After you repair the volume, check your hardware to isolate the cause of the file system damage. To do this, use the following steps: Start your computer with the Windows startup disks, or with the Windows CD-ROM if your computer can start from the CD-ROM drive.When the Welcome to Setup screen appears, press R to select the repair option.If you have a dual-boot or multiple-boot computer, select the Windows installation that you want to access from the Recovery Console.Type the administrator password when you are prompted to do so.NOTE: If no administrator password exists, press ENTER.At the command prompt, on the drive where Windows is installed, type chkdsk /r, and then press ENTER.At the command prompt, type exit, and then press ENTER to restart your computer.For additional information about how to use the Recovery Console in Windows XP, click the article number below to view the article in the Microsoft Knowledge Base: 314058 Description of the Windows XP Recovery Console If this procedure does not work, repeat it and use the fixboot command in step 5 instead of the chkdsk /r command."
To my great luck it worked and my computer rebooted flawlessly after the somewhat endless 2 hour repair process. Note that I didn't need to run fixboot and my computer began booting again just after running chkdsk /r I later also realized that I was using a 40 conducter IDE cable and as soon as I replaced it with an 80 conductor cable my boot time was quartered. I believe that the entire problem resulted from data corruption due to using an underspeced IDE cable, but now that I've repaired the disk and replaced the cable I have a much faster and working computer.
"RESOLUTION To resolve this behavior, use the appropriate method. UDMA ControllerIf your computer uses a UDMA hard disk controller, use the following procedures: Replace the 40-wire cable with an 80-wire UDMA cable.In the BIOS settings for your computer, load the 'Fail-Safe' default settings, and then reactivate the most frequently used options such as USB Support.Damaged File SystemIf the second parameter (0xbbbbbbbb) of the Stop error is 0xC0000032, then the file system is damaged. If this is the case, restart the computer to the Recovery Console, and then use the chkdsk /r command to repair the volume. After you repair the volume, check your hardware to isolate the cause of the file system damage. To do this, use the following steps: Start your computer with the Windows startup disks, or with the Windows CD-ROM if your computer can start from the CD-ROM drive.When the Welcome to Setup screen appears, press R to select the repair option.If you have a dual-boot or multiple-boot computer, select the Windows installation that you want to access from the Recovery Console.Type the administrator password when you are prompted to do so.NOTE: If no administrator password exists, press ENTER.At the command prompt, on the drive where Windows is installed, type chkdsk /r, and then press ENTER.At the command prompt, type exit, and then press ENTER to restart your computer.For additional information about how to use the Recovery Console in Windows XP, click the article number below to view the article in the Microsoft Knowledge Base: 314058 Description of the Windows XP Recovery Console If this procedure does not work, repeat it and use the fixboot command in step 5 instead of the chkdsk /r command."
To my great luck it worked and my computer rebooted flawlessly after the somewhat endless 2 hour repair process. Note that I didn't need to run fixboot and my computer began booting again just after running chkdsk /r I later also realized that I was using a 40 conducter IDE cable and as soon as I replaced it with an 80 conductor cable my boot time was quartered. I believe that the entire problem resulted from data corruption due to using an underspeced IDE cable, but now that I've repaired the disk and replaced the cable I have a much faster and working computer.
0 Comments:
Post a Comment
<< Home