!! 0xc01a001d !! 36114/168718 (\Registry\Machine\COMPONENTS\DerivedData\...)

[aarque]

Is there any way to resurrect Vista (Ultimate x64) after a failed SP1 update? I have searched the problem extensively and this forum seems to be the most knowledgeable. Unfortunately, almost all the solutions I have yet encountered were achieved by a clean install. I assume the fraction in the title refers to the number of .dlls loaded versus the total detected. In my research I have not seen a larger denominator which helps to express my reluctance to format the HD. I have read that the registry keys or security permissions are changed during the update and if the process is interrupted, the repair tools on the installation CD see but do not recognize the existing installations which makes repair or restore options impossible.
I have found this repair suggestion, but hesitate to try it because I am unable to detect an installed OS to repair (for which there appears to be a work around) and also because it is directed at SP2 updaters, which is probably a moot distinction.

"To fix this issue, you will need to boot from the Windows Vista DVD. Follow these steps:

1. Boot from the Windows Vista DVD or the Windows Vista recovery disc that was supplied with your computer by inserting it into the drive then restarting (if you don’t have this disc or can’t find it, you can download a replacement here). (Note: if your system does not automatically boot from the Vista disc when it is inserted, you need to change the boot device in BIOS. To do this, boot from the installation disc, insert the disc, then restart, and while the computer is restarting, continually press the appropriate key [F12 on most systems, F1, F2, F10, the Delete (del) key or the Escape (ESC) key on others -- consult your user's manual or perform a Google search for your specific model] then select CD/DVD/CD-RW as the boot drive.)
2. Choose your language settings and hit “Next”
3. Click “Repair Your Computer” at the bottom of the screen. This will launch Windows Recovery Environment (WinRE)
4. Choose the installed OS to repair, and you will see a list of recovery tools.
5. Open the command prompt
6. Enter the following commands, pressing enter after each, to create a Manual System Restore (as discovered by Arun Kumar on the TechNet discussion boards):
   • cd windows\system32\config
   • ren default default.old
   • ren sam sam.old
   • ren security security.old
   • ren software software.old
   • ren system system.old
   • cd regback
   • copy default c:\windows\system32\config
   • copy sam c:\windows\system32\config
   • copy security c:\windows\system32\config
   • copy software c:\windows\system32\config
   • copy system c:\windows\system32\config
7. Restart your computer, this time booting from the hard disk.If the problem recurs, repeat the process."

and this, the work around:

"try placing cd with cd /d c:\windows\system32\config"

which unfortunately seems a little cryptic. Both entries from this page:
Windows Vista SP2 Won’t Boot; Error 0xc0000034: Fix

So, to sum up, I assembled this system about 1 month ago after a previous MB failed. I have already filled 378 of the 500 available gigabytes on C drive. I have edited and added system specs. *Homebuilt, CPU AMD Phenom 9600 AM2+, Motherboard Asus Crosshair, Memory 8gb OCZ Platinum PC6400, Graphics (2) BFG 8800 GTS OC wc.*

I started with a blank HD, used a retail Vista upgrade DVD and inserted a XP disk when prompted to enable the installation. A week ago, automatic update started the SP1 installation, which I allowed. At some point the computer froze so I manually re-started. The system boots to the Windows progress bar, then changes to a black screen with a text string similar to the one in the title. The numerator rapidly increases and characters change on the other side of the denominator. They appear to represent .dll's, .exe's, .js's and .mui's. Everything freezes when the numerator reaches 36114 and will never progress. Booting in safe mode stops at "crc.dsk" and will never progress.

Any help would be greatly appreciated.

 

[usasma]

When Startup Repair can't find the OS, have you pointed it (with the Load Drivers button) to the drivers for your motherboard's hard drive controller? It's most likely available from the Asus support website. You may have to extract the files from the installer and place them on a USB stick in order to get them to load.

Have you tried to uninstall SP1 using this link (using Method 3): How to uninstall Windows Vista service packs as a troubleshooting step You can get to the Command Prompt by using the Startup Repair disk.

The detailed repair suggestion that you posted is essentially a "manual" system restore of the registry - using the data stored in C:\Windows\System32\config\RegBack Please check to ensure that that directory exists and that it has copies of the registry hives in it (they're the filenames without any file extension).

Also, have you run any free diagnostics? If not, please try these:

I suggest starting all troubleshooting with the following diagnostic tests. They'll save you a lot of time and heartache if there is a hardware failure, and you'll have the disks on hand in case you need them in the future:

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

 

[aarque]

When Startup Repair can't find the OS, have you pointed it (with the Load Drivers button) to the drivers for your motherboard's hard drive controller? It's most likely available from the Asus support website. You may have to extract the files from the installer and place them on a USB stick in order to get them to load.

I have loaded each driver available on the original driver CD that came with the board. It was easy to find since this system is only about a month old. No loaded driver allowed the repair tool to recognize the installed operating systems.

Have you tried to uninstall SP1 using this link (using Method 3): How to uninstall Windows Vista service packs as a troubleshooting step You can get to the Command Prompt by using the Startup Repair disk.

Method 3 describes opening an elevated Command Prompt from within the Windows environment. Is this the same procedure to be performed in Command Prompt from within the DVD loaded operating system?

The detailed repair suggestion that you posted is essentially a "manual" system restore of the registry - using the data stored in C:\Windows\System32\config\RegBack Please check to ensure that that directory exists and that it has copies of the registry hives in it (they're the filenames without any file extension).

I can follow directions to a "T," but I am not versed in DOS well enough to peruse and evaluate directories...

Also, have you run any free diagnostics? If not, please try these:

I suggest starting all troubleshooting with the following diagnostic tests. They'll save you a lot of time and heartache if there is a hardware failure, and you'll have the disks on hand in case you need them in the future:

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

I have run all diagnostics. Additionally, the hard drive was a new Seagate SATA drive one month ago when this system was installed. Also I replaced the BIOS chip because I'd read in one thread where that was a possible solution.

 

[aarque]

This is a status update. I am able to install this hard drive and another bootable Vista drive into another computer. The repair tool recognizes both volumes which leads me to believe it is a hardware compatibility issue, as if Vista might not work with some motherboards, especially an Asus one. Anyway, the repair tool offers to restore the system but takes several hours with no change. If I restart and select "no" for the restore, the repair tool claims to have rooled back or reverted the registry. The volume will boot to the Vista progress bar on either computer but the briefly blue screens before restarting. The other volume will not boot in the problem computer, again pointing to HW issues, but boots fine in this chassis and can see and open files in the hard drive that contains the copy of Vista that worked before the SP1 update.
Any ideas besides a new motherboard?

 

[usasma]

The mobo is the most likely culprit here - but it's your money, so you'll have to choose.

Try removing everything from the mobo except for 1 stick of RAM, the CPU and cooler, the PSU, mouse/keyboard and video card (no hard drive, no CD/DVD drive, no other add-on cards, no loose cables). Then try to boot. Do you get the POST screen?

Then put the hard drive in and try to boot from it. Does it attempt to boot to Windows?
Remove the hard drive and try just the CD/DVD drive - can you boot from it (try the memory test CD).
If none of this works, then I'd strongly suspect the mobo.

And, if everything but the hard drive works - and the hard drive works on another system - then I'd suspsect the mobo also.

 

[aarque]

Yes, I have concluded it is a hardware issue. Especially since by using a fresh BIOS, I was able to return the board to the software state that existed before the crash and still not boot, likely some pesky IDE drive or USB dongle. However the point is moot since the operating environment of that installation appears to be destroyed. While the volume was mounted in another Vista booted system, I did this procedure manually:

• cd windows\system32\config
• ren default default.old
• ren sam sam.old
• ren security security.old
• ren software software.old
• ren system system.old
• cd regback
• copy default c:\windows\system32\config
• copy sam c:\windows\system32\config
• copy security c:\windows\system32\config
• copy software c:\windows\system32\config
• copy system c:\windows\system32\config

I found a folder called "regback," dated the day before I updated. In it I found the five files: default, sam, security, software and system, all with ".old" extensions. I renamed the same files in the config folder with extension ".rk" (my initials). Then I copied the originals into config and removed the extensions. The volume still refuses to boot. Disk tools can see and address the volume, it says the volume can't be repaired because the registry is corrupt. I can choose the restore option, select the save point from before the update, but the restore operation never completes and when I check the volume I again get a corrupt registry message. Is there any to manually rebuild or copy/paste a good registry?

 

[usasma]

You rebuilt the registry when you did those commands.
You can search the system for other copies of the registry files (those files that don't have extensions are what comprises the registry) and see if you can rename those to make it work (but keep careful track of what you're doing)

But, if it's a hardware issue, then the system won't boot no matter how much that you massage the registry.
What's probably happening is that a certain portion of the registry has to pass through the bad hardware and that's what corrupts it (in memory, not in the file itself).

Good luck!

 

[aarque]

Thank you so much. The main thing I wanted to salvage was the file structure, which remains intact. I will most likely be able to duplicate this build using what I have as a guide. In the meantime, I will keep experimenting with registry permutations to develop a bootable volume. Pattern cyphering is among my skills.
When I started this thread, one of the things I wanted to do was to help answer the Vista SP1 issue so many seem to post inconclusively about, hence the title. I tried to gather or describe everything relevant and perhaps that can continue. Thank you again.