I have been trying to install XP on a brand new Maxtor 40gb 2700 ata133.
Using Maxtor utilities, I've low level formatted into 1 NTFS partition.
Currently, old disk can still boot XP and Windows recognises the Maxtor drive and can transfer files to and fro.
Removing old disk and setting Pioneer CDRW to boot first, ran the XP cd.
The installation confirms the partition and installation continues.
After the 16 bit copy of files, the pc will reboot in 10 seconds....Blue screen.
Restart manually, "error writing to disk".
At this point, I run all diagnostics on the new HDD, no probs.
(don't ask what the error message of the blue screen read, I forget)
Here is the rest of the hardware, ASUS P4S8X-X motherboard, 512 branded DDR2700, GeForce 256 32MB AGP graphics (don't laugh),
350w power supply, P4 2.4 533mhz, ps2 keyboard, usb optical mouse, that's about all.
Now, I have the new HDD on Master jumper settings and 133 ide cable plugged into primary slot. I also have the latest beta bios from asus.
Everything looks ideal. In fact, the old hard drive had been installed with XP on this exact config.
So, the only thing that has changed is the new hard drive.
Side note, sometimes trying to install XP, the system will reboot without the blue screen and enter the 32-bit XP setup, goes through checking hardware, gets through 75% of that and reboots to "Operating system could not be loaded. This then removes the NTFS format and labels the drive as unknown. Grrr
Going home tonight to try without jumber on HDD, and a few bios tweeks as they are all default, Oh and check out what the blue screen is and what it means.
Any suggestions would be greatly appreciated.
Want to enjoy fewer advertisements and more features? Click here to become a Hardware Analysis registered user.
i dont know much about your motherboard (never owned one) but you could check to make sure there are no overclocking features running from the bios. my msi board began overclocking automatically after updating the bios and had to turn the settings down to stop the bsods.
This is kind of a long shot, but I had a similar situation that was resolved by clearing the CMOS. Follow the instructions for the mobo on doing it (generally just shorting a jumper on the mobo for a couple seconds). If I recall, the BSOD I was getting during an XP Pro install said, according to support.microsoft.com, that it could be due to a variety of things including bad data in the CMOS. I cleared it, and bingo - it worked.
I think it may be the hard drive. Tried clearing the CMOS, no joy
I ran a burn in test on my Maxtor drive and everything passed. Last ditch effort tried to copy large files to drive and it kept stating that it could not pass the file, may be corrupt or in use, it wasn't in use. Tried everything. positive it my hdd. Anyone know a good utility to deep scan sectors on drive and possibly repair? I should just return it come to think of it.
Here's a hunch...If you have the old hard drive try that...does it work, if it does,i would start it in safe mode and remove the hard drive driver,from the system in device manager,then i would shut down,install the new hard drive. But if that doesn't work, i would try to boot using the win xp cd...and repair.
All in an HP Case that I got with my old P3 800mhz @128MB SDRAM/ 32MB TNT2 AGP - says 185W on the back, 12v @ only 4A!!
I'm thinking I have a power deficiency, but would that cause I disk read error?? Should I try to clear the CMOS or would that cause problems down the line? If I clear CMOS what exactly does that entail?
I'm so sad, I was so excited to get my new MOBO/CPU/RAM and now I'm just dejected!!!!
You need to go back and use the Maxtor MaxBlast CD and do a zero fill on the hard drive. Maxtor told me not to use their CD to make the partition, let the OS make it. I wiped and reinstalled and it rebooted no problem. The full fill takes about 5 1/2 hours on a 80GB HD so if you can't be patient try a directory wipe, but I suspect it would probably be better to completely wipe that sucker and start fresh.