Automatic restart (Mountable_Boot_Volume error)

I had a problem that surfaced about a month ago where I can't start up my computer. When I turn on my CPU I get the screen where it gives you the option to start normally, last known good configurations, safe mode, etc. No matter what option I select the computer will automatically restart itself. One thing I did was to disable automatic restart for failures and then I get a blue screen that says Mountable_Boot_Volume so I have to restart again. I do have a Windows XP OS.

 

The error is probably UNmountable Boot Volume. Chkdsk usually will fix this error.

Boot from the XP CD. It will load files and then give you the option to hit "R" for repair. It should ask you which Windows to sign into. There is usually only one available so enter "1" and hit <enter>. It may prompt for a password if so enter your Administrator password or if you haven't set one just hit <enter>. Your prompt should be C:\Windows> or similar. Type chkdsk c: /r and hit enter. It will check the file system for errors. Try rebooting without the CD and see if you get any further into Windows.

If not, try Last Know Good Configuration again.

 

I pressed R to do the recovery console and for some reason it didn't ask me which windows to log onto. I got the command prompt and I typed chkdsk /r then pressed enter. But I got a blue screen error that said:

c0000139 {entry point not found}

The procedure entry NTserializeboot could not be located in the dynamic
library ntdll.dll.

 

I think your C: drive may have errors so it doesn't sign you into Windows. Try again with the specific command:

chkdsk c: /r

to see if it will run.

 

Same issue came up. I don't have a Windows XP cd, i burned it from here :

http://artellos.com/arcdc-page

But Im not sure if that is the cause of the problem though.

 

I've been reading threads and haven't come up with a working solution. You definitely have corruption of the C: drive, the problem is that chkdsk won't run so we can't fix the errors.

I'll continue reading to see if I find anything. From what I have seen a Linux CD would be able to read your files so there is a chance you could save important files if we can't figure out how to get chkdsk to run.

That artello's disk should be fine. I think the problem with chkdsk not running is something to do with how the filesystem on the HD is corrupted. Some pretty experienced troubleshooters have not had much luck with this problem so I'm not sure what I will find.

 

I'm not coming up with anything definitive. I think there are two options for alternatives to chkdsk. But I haven't tried either. I will look at them tonight when I get a chance to figure out if there is a way to run them and what exactly they do.

I'll just post links if you want to read them. The idea would be to let Linux mount the HD and try to fix the problem. Then Windows might be able to read the drive and do the normal chkdsk.

I'm going to try this out using a PartedMagic version of Linux tonight to see how it goes. My filesystem isn't damaged but I will test out the command anyway on an old HD. http://www.makeuseof.com/tag/fix-corrupted-windows-ntfs-filesystem-ubuntu/
Same program just another link showing the command at the end: https://wiki.archlinux.org/index.php/NTFS-3G#Damaged_NTFS_Filesystems

The other would be an alternative to chkdsk but it has to be run from Windows. That would mean connecting your HD to another computer to run it. I'm not sure if that is a possibility for you but if it is then you could also try running normal chkdsk from the other computer and you may have better luck. http://majorgeeks.com/CheckDisk_d6511.html

 

I finally got it work. I downloaded and created another boot CD. When I booted, they didn't ask for the administrator password. I entered chkdsk /r and it worked then. When it finished after like 2 hours it said chkdsk /r again and I pressed enter and it did its thing for 30 minutes. After that I typed exit and my computer started up as normal

 

Thanks for posting back. Chkdsk is the only solution for that problem but it is hard to find any way to run it without the recovery console or a working Windows computer. I'm glad you got it to run.

If this only happened once and has only now been fixed you are probably fine. If the same error has been occurring randomly then your HD may be failing. If your HD is a couple of years old you may want to run a HD diagnostic to see if its SMART status is good or bad.

The short test for your manufacturer will tell you the SMART status. SMART is an early warning system that keeps track of problems and when a threshold is reached the status goes to bad. A bad SMART status predicts HD failure. Can't hurt to run the diagnostic and see what it says. It is not full-proof but gives you a basic idea if there have been errors in the past.