virtualbox.org

Hello community

I'm new to Virtualbox and am having some major issues. However, I don't believe it is contingent on VirtualBox but on the Windows NT os. We have a Windows 7 box running a vmdk of Windows NT. Everything was working fine until the power went off. The pc went offline then started rebooting. During the reboot the power flicked off again and now everytime I try to run the Virtualbox Windows NT is showing a bluescreen (bsod) and giving the error KMODE_EXCEPTION_NOT_HANDLED. The Windows NT file system is ntfs. I've tried to reset the FT bit I have read that should fix it. If I boot to Dos 6.22 disk the ntfs drive doesn't show and when I try booting to Windows XP disk it says c:\disksave.exe cannot be found even tho it is there. I've tried changing the VB everyway I can think of. There is data on the virtual disk we cannot loose. I was able to setup the VD as a secondary and copy the needed files off it, but would like to get the entire system back up. Also tried repairing the winnt install but that just gives boot_device_not_accessible bsod.

Does anyone have any ideas on what I can try?

Thanks for any and all help!!

Only way I know of is to restore from backup.

I clone my important guests regularly so if something like this happens I can get back up running in minutes.

The guy that originally set up the system had set the server to make a copy of the vmdk periodically. It looks like it backed it up one time and never worked again. Unfortunately that backed was corrupted and did not work. After loading the backup img of the partition it would say can't read from disk, cycle redundancy error.

However, I was able to fix the original problem KMODE_EXCEPTION_NOT_HANDLED in ntskrnl.exe by using another virtual drive with NT. I loaded the working NT drive to boot to and the drive I was trying to fix as slave. Next I went to d:\winnt\system32\config and renamed the system and software registry hives on the non-working version. After that loaded up regedt32, saved the software and system registry hives from hklm on the working computer and saved them to the non working version. Shutdown and opened the non-working version and it booted. After that I shutdown again, loaded the same configuration as before with the previously non-working drive as slave, reloaded the backup registry hives to the previously non-working drive, returning it to original, and everything was back to normal after that.

Hope that can help someone else in the same position.