HDD insists on running in PIO mode instead of UDMA Mode 5

A few hours ago I wiped my C drive to reinstall XP due to some really weird shit.

Everything went fine, but I noticed that HDD access seemed somewhat slow, so I went the device manager to check some things out. Turns out my HDD is set to PIO mode instead of UDMA 5. I even have it set to "DMA if available", but it insists on using PIO. I know it was using UDMA 5 before the reinstall, why would it change now?

I've heard that it'll automatically change to a slower mode if there are a lot of read/write errors. Does this mean I have a dying drive, or are there some other settings I need to look at?

Motherboard supports Ultra ATA/100, drive is a Maxtor 6B250R0 which is also Ultra ATA/100.
I haven't made any changes recently, other than reinstalling Windows XP. No bios changes, no hardware changes, nothing.

Like I said, it was running fine before. Does anyone know what would make it switch and refuse to switch back and also how to fix it? Help please :(

Did you install the Intel INF chipset update? (assuming you're using an Intel and not AMD)

Did you install the Intel INF chipset update? (assuming you're using an Intel and not AMD)

Nope, but I can't remember ever doing it in the past either.
Motherboard uses Intel Socket 478 (old system), would this help?

I’ve had times when after I’d install the INF update the system would redetect hard drive controllers.

Well I tried the updated chipset drivers, it didn't work. I also tried uninstalling the IDE controller through the Device Manager, rebooting, and letting it install it again. Didn't work either. I ended up trying a whole bunch of other solutions I found using Google, none of those worked either.

I finally tried reinstalling again. Went into Device Manager first thing, it still showed the drive as using PIO. Immediately installed chipset drivers and Intel Application Accelerator, rebooted...and it was fine.

Never had to use the chipset drivers since I switched from Win98 to XP a few years ago.
Dunno WTF it was so hard to fix, but I finally got it. Thanks for the help.