dmboot: Failed to start volume Volume1 (no mountpoint) - Then it restarts.

I have an XP system, a dual core processor, recent graphics card, two gigs of memory. Three hard drives, one by itself, two in a partition. One hard drive in the parition hasn't worked for a while, and there's no data on it. However, would be nice to get it working. It might also be the cause of the restarting, I can't be sure. I'm not entirely on top of this whole computer thing.

Around the time of the restarts, this error is found in Event Viewer: dmboot: Failed to start volume Volume1 (no mountpoint)

I came across this answer, and I believe I have an SCSI setup, but the link that was provided was a little confusing:

Restarts range from five minutes to entire days. My work is at a standstill, and I'm desperate.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Duncan MeyersCommented:
What is the PC? Is it  a brand-name or a home-built unit?

Now to the hard drives - you have two drives in one partition. Are the drives connected to an on-board RAID controller? If one drive isn't working, it should be quite safe to disconnect it. If your stability issues go way then it was most likely a problem with the drive.

FWIW - I recently upgraded my PC to 2.5GB RAM and the PC became ridiculously unstable. Turned out that the heat from the extra RAM was enough to overwhelm my PC case ventilation. One more fan and it's been perfect ever since.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
JoeyJoJrShabodooAuthor Commented:
It's home-built by my stepfather. I asked him about it, and he thinks it might be the motherboard or video card, since there was some restarting when he was installing drivers for the video card, then it magically went away. A few months later, this happens. That's his hunch.

And no, they're not connected to a RAID controller, there isn't one. If this is the case, guess it wouldn't be safe to remove the drive?

And I thought it was a heat problem at first as well, but restarts happened within a minute, or immediately as I logged on (randomly), and there's already a good amount of fans inside. One on the side, some on the back.
Duncan MeyersCommented:
Try turning off overclocking if it's been turned on.

Also - download a copy of Knoppix from, burn it to a CD and boot from the CD. If the system still reboots randomly then you've most likely got a hardware problem. If the system is now stable, then you can almost certainly say that you have a driver or some other software issue.
The Ultimate Tool Kit for Technolgy Solution Provi

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy for valuable how-to assets including sample agreements, checklists, flowcharts, and more!

Test your RAM using memtest96+, also use the disk manufacturer's tools to individually test the Disks. You'll find those tools on the UBCD. Also within XP right click "My Computer", select "Properties", "Advanced", Startup and recovery "Settings", and disable "Automatically Restart". Next time your system may show a Bluescreen and not just restart. Post the stop code you get on that BSOD. Also look for a minidump folder and upload the latest dumps to here.
Could also slave the hdd that has 2 partitions to another xp pro dekstop
 slave to the CDROM master slave on the other computer, it's simple enough just unpower both pull out the power degauze yourslef just incase,
remove a couple of srews the ide cable and power
 move the jumper on the rear to slave
 it has a diagram on top,
on the other desktop unpower too
pull out the master slaved rom drive
and plug in the ide and power connector into this hdd.. sit it ontop of the tower if it reaches okay.
put the power in again and boot
it takes longer
 if there is no problem with hdd itself the windows will bsod and not boot.
If there is no problem with the actual hdd and only windows master boot record or whatever is damaged the windows on this system will load and find new hardware.

scan it for viruses first, then save off his files before testing and checking.
you save his emails store folder as is etc.
then check the partitions in disc manager control panel administraive tools computer manager disc manager. You could even format it from here
if you choose to and create one partition.
JoeyJoJrShabodooAuthor Commented:
The problem was fixed a different way: a new motherboard was installed, which appears to have fixed everything.

However, all these answers have information that may prove helpful to me and others down the road, so have some points, everyone.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
System Utilities

From novice to tech pro — start learning today.