You Mac people are starting to have another convert on your hands. I don't know how much longer I can put up with Windows and its many "quirks."

The latest is that after experiencing a bit of oddities in the OS, I checked the event viewer. It has messages and a few warnings that I'm not concerned about. It even has some errors I'm not concerned about because I know what they are and they're not a problem. However, I do have one error that concerns me.

I've been Googling for a while now, and I've found some threads but they don't really help/apply to me (naturally). Given the amount of problems I had earlier with my SATA controllers, I'm inclined to think that it's one of them that's the problem, but what does it mean by "\Device\Harddisk0\D"? I would assume that drive 0 would be my OS drive, but what's the D for?

I can't be sure that this is the cause of the various problems I've been having (freezing sometimes, my CD burns keep failing), but it's an error that seems like something I should fix.

Help?

That's why I love finding information in the IT world. Given the symptoms, assume it's hardware related, and try the SATA system. New cable (shorter?), new PCI controler card even, update SATA controler drivers, update BIOS, and maybe even a motherboard RMA for faulty onboard SATA.

I've heard so many bad things about onboard IDE RAID drivers of years gone by that I'm nervous of these "new fangled" onboard controlers. The SATA doesn't happen to be a Promise chipset, does it, because that's what has a bad rap in my book for IDE RAID controlers.

Maybe newsgroups and forums discussing your motherboard (typically by manufacturer; alt.comp.periphs.mainboard.*) will reveal common problems similar to yours. Good luck.

HardDisc0 (zero) indicates that the drive is on the first controller, 'D' is the partition on that drive.

Dunno!

If you go control panel->Administrative Tools->Computer Management and then click on "Disk Management", what does it say there? What is the volume name of the drive?

I had problems rebuilding my PC, in the end updating the Promise drivers and BIOS fixed the issues I'd been having.

Dignan: Is the motherboard an NForce board? Did you install the nForce drivers? When I installed the drivers for my nForce board it asked if I wanted to install the advanced hard drive controller drivers. I said no since I've heard some people had problems with these drivers.

I have that board. I don't remember that about the drivers, though.

Well, I don't know if I'm going to be able to fix this soon. I'd forgotten that my OS drive is actually plugged into the PCI card. It doesn't suprise me at all that this card isn't great. It was like $15.

I would ditch the card but I need all three drives and I can't move the drive to the onboard controller, because I can't get the system to boot when the drive is on the other controller.

Oh well, I'll either get a good card with more ports, or wait until I replace the mobo in this system.

Can anyone tell me what kind of problems could be caused as a result of this error? Otherwise, thanks for all the help, folks!

Can't you set the harddrive controller to be a standard type in Device manager? Then you should be able to boot off another controller. That's what I did when I changed the motherboard on one of my computers and didn't want to reinstall Windows. Might also need to change which partition it's on in boot.ini.

Stig..

I don't think that's the problem. The problem is that my mobo seems to decide that if there's a controller card on the system, that's the one I have to boot from. I can switch the order that the controllers boot in, but if I set the onboard first (and put the OS drive on it), it just stops at "Verifying DMI Pool Data..." and doesn't boot.