XP hates me..

[Kazuya17]

Well guys i've been facing alot of problems this week, the main problem is getting XP to run without having to format after rebooting.

2 errors i got after 8 formats and 4 fresh installations:

Diskerror, CTRL+ALT+DEL to restart the system (or something similar)

And no harddrive detected on XP installation, even with slipstreamed SATA/RAID drivers. I got no clue why, the only thing i did lately was updating my BIOS software and replacing my old 1.25 GB RAM with 2 GB. (HD: Seagate Barracuda 200GB 7200.7 (ST3200822AS)).

Everytime i run without SATA/RAID drivers the harddisk gets detected and i install XP just as normally, then boot up for the second part and everything seems to turn out fine. Then i boot up XP to install some drivers and basic software, then reboot to complete it. Then i get the error about Diskerror.

I hope this makes any sense cause i'm out of idea's.

PS. I also hope i placed this in the right section, if not then my topic can be moved to right place.

Greetings

Edited October 8, 2008 by Kazuya17

[Nexus_06]

Sounds like HD failure to me.

[AO3]

What is the HDD connection? IDE?

[Kazuya17]

I got a SATA HD, but i can give IDE support from bios, as it seems to work without SATA drivers. Though thats where the error-after-first-reboot starts showing up.

Attempt to create some screenshots:

Edited October 8, 2008 by Kazuya17

[nadav]

Try installing one driver at a time, rebooting each time to try and isolate the rogue driver/software. Also, run Memtest86+ to see if maybe the new RAM is faulty.

[IcemanND]

you can also test your hard drive with seatools. http://www.seagate.com/www/en-us/support/downloads/seatools

[DedNDave]

i would be tempted to put a volt meter on the little battery

besides what appears in the BIOS editor, there are some other

hd related parameters stored in the RTC RAM

but, if everything was fine before you changed BIOS,

and now it isn't, that is also an indicator

go to the AMI website and see if you are the only one having this problem

there may be a compatibility issue with your m/b