Boot Disk Error

[devildogelite]

Since there are a lot of people on this forum that know a lot more about computers than I do I hope someone here can help me. I was using my computer as normal and went to plug something into the usb port. There appeared to be a spark at the usb port and then the screen went black, it began to reboot. As it was booting it said that there was a boot disk error, this is the first time I have ever had this problem. I put in the windows 7 cd and it got to repair but it could not recognize the drive. I eliminated that the hdd failed because I plugged it into a different computer and it worked. If anyone could help me I would greatly appreciate it.

[Ad Bot]

[Miga]

Sounds like something got fried, probably the motherboard.

You'll probably have to buy a new one.

[devildogelite]

Sounds like something got fried, probably the motherboard.

You'll probably have to buy a new one.

Thats exactly what I was thinking but didn't want to rush into buying one without any advice first

[SeventhSandwich]

Your hard drive ashploded.

If you even can, try rebooting your computer and listening for any sounds on the hard drive area.

If it makes no sound I guarantee you have a dead hard drive.

[devildogelite]

Your hard drive ashploded.

If you even can, try rebooting your computer and listening for any sounds on the hard drive area.

If it makes no sound I guarantee you have a dead hard drive.

No, Im using the hdd on another computer right now, I had to reinstall windows 7 on it though. All of my old stuff is on it and it works fine

[Miga]

Your hard drive ashploded.

If you even can, try rebooting your computer and listening for any sounds on the hard drive area.

If it makes no sound I guarantee you have a dead hard drive.

If it exploded, it probably wouldn't work in another computer, which he said it did.

Fried motherboard, like I said.

[dkamm65]

Put in your repair disc and select command prompt.

Type "bootsect /nt60 ALL" without quotes and press enter.

Reboot and it should might be fixed.

[SeventhSandwich]

If it exploded, it probably wouldn't work in another computer, which he said it did.

Fried motherboard, like I said.

Didn't see that.
Motherboard probably.

[Miga]

Put in your repair disc and select command prompt.

Type "bootsect /nt60 ALL" without quotes and press enter.

Reboot and it should be fixed.

It wouldn't even detect the HDD though, he said, so I doubt that would work.

[Tom]

It gave him an error. His MBR probably got messed up somehow, try what dkamm said. Not recognize != not detect.

[Tokthree]

It could be something as simple as a fried cable, don't rush into buying new hardware until you're positive that the problem isn't something cheaper.

Even if I'm wrong, it can't hurt to be sure :D

[dkamm65]

It wouldn't even detect the HDD though, he said, so I doubt that would've worked.

I put in the windows 7 cd and it got to repair

The repair screen is where you select command prompt.

It sounds like the boot sector for his drive was damaged. The command I wrote should fix that.

[devildogelite]

It sounds like the boot sector for his drive was damaged. The command I wrote should fix that.

Wouldn't that make it have a boot disk error on the other computer though?

[Miga]

The repair screen is where you select command prompt.

It sounds like the boot sector for his drive was damaged. The command I wrote should fix that.

I put in the windows 7 cd and it got to repair but it could not recognize the drive.

It seems like he got to "Repair" but it couldn't detect the hard drive. It usually has to look for OS's on the HDD first before you can get to command prompt, so he probably couldn't get to command prompt anyway. (at least, it does with my DVD of Vista).

That's at least what I think he's trying to say.

Wouldn't that make it have a boot disk error on the other computer though?

If it does work, no.

[dkamm65]

Well that was my first though cause I had a problem booting into Win7 last week, and I had to use this fix. If it doesn't work for him, it's probably something broken on the motherboard, as already stated.