• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

How do I boot my computer (WinXP) after my IDE drivers are corrupted?

UNCjigga

Lifer
Okay, this is the age old Win2k/XP issue with 'UNMOUNTABLE_BOOT_VOLUME' and other associated STOP errors related to the disk subsystem.

I recently installed some new IDE drivers to go along with my SiS735 chipset--these replaced the Microsoft default XP drivers and offered MUCH improved performance under ATA 100. Unfortunately, my older ATA 33 slave drive had issues with the driver and would often develop corrupt sectors, etc. while in use.

I decided to do a driver rollback so I could move back to the default drivers. Big mistake. Apparently I should never use IDE drivers that have not been WHQL tested!!! After I rolled back drivers, the 'child' Primary/Secondary ATA devices were still there--it showed two primaries and two secondaries (one each had yellow exclamation of course!) Under Win98, I would simply boot in safe mode, remove ALL devices, reboot, and let plug&play reinstall the controller. Of course in WinXP I cannot remove any controller associated with the boot volume--safe mode or not! There was no other way to get the proper drivers recognized.

After toying around a bit, things got worse. Somehow Windows XP redetected my SiS IDE controller as a SCSI CONTROLLER, and subsequently labeled my hard drives as SCSI DEVICES--which they most definately are NOT! I don't know how this happened, but I couldn't get it to go back. After that, I could only boot in safe mode or VGA mode, but now for some reason I cannot boot in ANY mode.

So, back to my original question. How do I solve issues with the IDE subsystem in WinXP. Have we made ANY progress since Win2k??? I remember back when I upgraded my motherboard and how I lost my Win2k setup because the chipset was different...I do NOT want to go through this again!
 
First you could try booting in safe mode and removing the IDe drivers and having windows re-detect everything first. If that doesn't work I think the only way out is to boot off the CD ROM and do a recovery-mode install.
 
I tried both--didn't work. Safe mode doesn't LET you remove the controller or offending devices if the boot drive is attached, and I couldnt' figure out how to run recovery mode off the cd-rom (should've made those ASR disks!) All I could get was the stupid console.
 
You don't need to use the recovery console.

Either try safe mode and roll back the IDE driver, or do a repair off the CD.
 
Back
Top