So i am bsod with 0x00000007a ntfs.sys when i try to backup my server with DPM so i decided to run a chkdsk and it crashes with the error. stop: c0000218 {Registry File Failure} The registry cannot load the hive (file): \SystemRoot\System32\Config\SYSTEM or its log or alternate. It is corrupt, absent, or not writeable. I am not sure how to go about fixing this. Thoughts?

So i am bsod with 0x00000007a ntfs.sys when i try to backup my server with DPM so i decided to run a chkdsk and it crashes with the error. stop: c0000218 {Registry File Failure} The registry cannot load the hive (file): \SystemRoot\System32\Config\SYSTEM or its log or alternate. It is corrupt, absent, or not writeable. I am not sure how to go about fixing this. Thoughts? It sounds like the hard drive has taken a severe hit but I could be wrong... Try updating all of the server firmware with bootable disk media. Does your BIOS report smart errors? What is the server make/model? Does the OEM provide Diagnostics with your hardware? (if Dell, goto support.dell.com - download the diagnostics iso file and burn a diagnostics cd/dvd) Try to boot Windows Server in safe mode. In Addition: Windows Recovery Environment to Repair registry problems in Vista/Windows 7. (Since Server 2008 R2 is the same build of Windows 7.) http://support.microsoft.com/kb/927525 I also very highly recommend you make a WinPE bootable disk from the WAIK kit and make an image of your server disks incase this fails!!! If you have a recent backup... save yourself some time and restore the system state and C: volume. Best Regards,Steve Kline Microsoft Certified IT Professional: Server Administrator Microsoft Certified Technology Specialist: Active Directory, Network Infrastructure, Application Platform, Windows 7 Microsoft Certified Product Specialist & Network Product Specialist Red Hat Certified System Administrator This posting is "as is" without warranties and confers no rights.

I guess i didnt give the whole story. This is a virtual machine hosted in a fail over cluster. We did had an issue with the san it was on, but that has been corrected. But when the power was basically yanked some corruption happened or dmged the VHD some how.

Hello, I think it will be better to restore your server from a backup that dates before the appearance of your problem. Once done, check that is okay and if BSODs re-appear then use Microsoft Skydrive to upload dump files that are in c:\windowd\minidumps and post a link here. You can also contact Microsoft CSS to troubleshoot BSODs. This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner Microsoft Certified Professional Microsoft Certified Systems Administrator: Security Microsoft Certified Systems Engineer: Security Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration

you can mount the vhd (or a copy of it) in the host or another w2k8 r2/w7 machine (to be safe as readonly) and check if you can access it that way, eventually if chkdsk shows up anything that way

Unfortunately those backups don't exists. This issue was actually brought to light because we were trying to get backups using DPM after the near catastrophe, Thats when we found out it was blue screening. I am not seeing the minidump folder. Making another BSOD so it hopefully creates the dumps files. What is microsoft CSS? *EDIT* For some reason the minidumps are not being created.

as a side not i did another chkdsk when i booted into the recovery off the disk(as opposed to in windows and doing it and it having me reboot and it doing it on startup) i get this error instead of the bsod Insufficient disk space to correct errors in index $SDH of file 9. Insufficient disk space to fix the security descriptors data stream. Repairing the security file record segment. 13 percent complete. (0 of 221952 file SDs/SIDS processed) An unspeecified error occurred (726173642e637878 1a1). Failed to transfer logged messages to the event log with status 50. Thoughts on this?

as a side not i did another chkdsk when i booted into the recovery off the disk(as opposed to in windows and doing it and it having me reboot and it doing it on startup) i get this error instead of the bsod Insufficient disk space to correct errors in index $SDH of file 9. Insufficient disk space to fix the security descriptors data stream. Repairing the security file record segment. 13 percent complete. (0 of 221952 file SDs/SIDS processed) An unspeecified error occurred (726173642e637878 1a1). Failed to transfer logged messages to the event log with status 50. Thoughts on this? Well you're running Chkdsk on a vhd, you might want to just mount the Server 2008 ISO, boot from DVD to startup WINRE and try to use the automated repair options available on the WINRE image. It may or may not fix the issues you're having. Also: if this is from clustered systems, shouldn't the other system have the information this one is missing? You just need to rebuilt the OS and re-cluster them, correct? That was my knowledge of the concept behind clustering... making the information available even after a system fails within the cluster. Steve Kline Microsoft Certified IT Professional: Server Administrator Microsoft Certified Technology Specialist: Active Directory, Network Infrastructure, Application Platform, Windows 7 Microsoft Certified Product Specialist & Network Product Specialist Red Hat Certified System Administrator This posting is "as is" without warranties and confers no rights.

Sorry for not being very clear. I did boot into WINRE and ran chkdsk from there. thats when i got those messages which chkdsk can not fix. As for the clustering, the server itself is in a failover cluster, and not clustered itself. So when the corruption happened it happened within the failover cluster so there is really no clean copy anywhere. At this point i am ok rebuilding the server, but if i could repair it, it would save a ton of time.

Hi, Please refer to the following Microsoft KB article and apply the hotfix to troubleshoot the issue: Stop error 0x0000007a occurs on a virtual machine that is running on a Windows Server 2008 R2-based failover cluster with a cluster shared volume, and the state of the CSV is switched to redirected access http://support.microsoft.com/kb/2494016 If the issue persists, you may contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request. To troubleshoot this kind of kernel crash issue, we need to debug the crashed system dump. Unfortunately, debugging is beyond what we can do in the forum. Please be advised that contacting phone support will be a charged call. To obtain the phone numbers for specific technology request please take a look at the web site listed below: http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607 Regards, Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Sorry for not being very clear. I did boot into WINRE and ran chkdsk from there. thats when i got those messages which chkdsk can not fix. As for the clustering, the server itself is in a failover cluster, and not clustered itself. So when the corruption happened it happened within the failover cluster so there is really no clean copy anywhere. At this point i am ok rebuilding the server, but if i could repair it, it would save a ton of time. I would mount the VHD volume to a "good" working VM and try to gather the data you can from it or run "File Recovery" software across the VHD from the working VM.Steve Kline Microsoft Certified IT Professional: Server Administrator Microsoft Certified Technology Specialist: Active Directory, Network Infrastructure, Application Platform, Windows 7 Microsoft Certified Product Specialist & Network Product Specialist Red Hat Certified System Administrator This posting is "as is" without warranties and confers no rights.

This looks like my issue. I will need some time to test though. Any thoughts on why this would be happening to one server and one server only when we have 20+ that have been setup and configured the exact same way?

Possible to use SRM to port the old snap shot. ? Is this VM running on a Blade server if so, pls check on the hardware if there is any faulty amber lightings. :) alternative such issues occur during fail over. Therefore it might be power didn't cut over properly therefore corruption occur :)Guowen Su | CCNA, CCIP, MCP, MCSA, MCSE, MCTS, MCITP, CEH | http://www.microsoft.com/en/sg/default.aspx Our Goal? VERY SATISFIED Customers. If you're not...let's talk!!