New built computer wont install XP.

[infin|ty]

well, I couldnt find my other thread for some reason from yesterday so I made a new one. I got the new mobile 2500+ chip b/c the other chip core was well....chipped.

I set it up and everything works. I set first boot device to cdrom and go to install XP Home. It will format it and then it will do the regular routine like restart once thats done. After it reboots I have had it freeze at the windows load screen, a blank lightblue page which is right after the windows loading, and after that, right when it starts to install the actually XP software.

The mouse still moves but the screen freezes. I'm not sure wth is wrong and im getting upset. It always freezes right in that time period.

If I had my HDD on the wrong jumpers it wouldnt even start to format right? I have it on single or master which is not jumper in it at all.

Any ideas?

 

[infin|ty]

please?

 

[Osiris]

Hmm, mysterious... I have 2 ideas:

1) Check you're running your ram at the right settings. If its CL2.5 Ram, running it at CL2 will make it unstable and liable to do that sort of thing. This can be checked in the bios.

2) If thats not the problem, just leave it when it freezes and see if it wakes up a bit later. My box a few years ago used to do this when installing win98, it looked like it was dead but would start going again after 10 minutes or so.

I don't think the jumpers have anything to do with the problem, the bios wouldn't even see the HD if that was whats wrong.

 

[HvyMtl]

Ok, is it a dual memory bus motherboard? I have run into occasions that if both buses are populated with memory, XP (heck, 98se, Me, 2000) can freeze since the os has no clue how to handle the dual bus until the motherboard drivers are loaded...
So, make sure only one bus has memory in it until after that all important driver install.
As for hard drive format, that prolly is not the problem, as XP would not install on an incorrectly formatted drive. What format is the drive in Fat32, or NTFS?
If you have a drive overlay (software from the drive's manufacturer such as seagate or western digital that allows you to format and partition the drive) previously installed and its say 3+ years old, that could cause a problem, but only if you are trying to have XP install as NTFS - the older overlays dont know what to do with that new file structure.

 

[infin|ty]

Hmm, mysterious... I have 2 ideas:

1) Check you're running your ram at the right settings. If its CL2.5 Ram, running it at CL2 will make it unstable and liable to do that sort of thing. This can be checked in the bios.

2) If thats not the problem, just leave it when it freezes and see if it wakes up a bit later. My box a few years ago used to do this when installing win98, it looked like it was dead but would start going again after 10 minutes or so.

I don't think the jumpers have anything to do with the problem, the bios wouldn't even see the HD if that was whats wrong.

I let it sit while I went it to town for about an hour and a half and I came back and it was still frozen.

I only have one stick of ram in it. (Dimm 1)

It's NTFS, I've tried quick and regular format. I took out the video card to see if the refurbished 9700pro was causing any graphics problems but it still froze. I'm gunna try installing it all with onboard video this time.

This hdd has never had info on it, I deleted the partition anyways and then installed.

Thanks, any more ideas? I'll try that CL thing when it's done formating.

 

[infin|ty]

uhh prolly just gunna burn this pc.

 

[LadyJaqie]

switch the ram to another socket. reseat the processor, reseat the vidcard, hell reseat EVERYTHING!

try removing the parts one at a time from the system and booting it...

try swapping some things, everything you can, into another system one piece at a time.

maybe also there was just a data error when trying to cinstall XP that it didnt like. try starting the thing fresh after using ZAPHD on it. (google for it)

what about underclocking the FSB and also therefore the processor? try that...

 

[infin|ty]

switch the ram to another socket. reseat the processor, reseat the vidcard, hell reseat EVERYTHING!

try removing the parts one at a time from the system and booting it...

try swapping some things, everything you can, into another system one piece at a time.

maybe also there was just a data error when trying to cinstall XP that it didnt like. try starting the thing fresh after using ZAPHD on it. (google for it)

what about underclocking the FSB and also therefore the processor? try that...

I'll try some stuff like that. Couldnt find zaphd btw..buy I did find a hard ass kids hangman game I lost trying to find the word pink

 

[DocSavage]

Run memtest86+ from www.memtest.org on it. Also give us a complete list of components you have installed on it. I have seen a pci card in a particular slot keep Win XP from installing.

 

[infin|ty]

Run memtest86+ from www.memtest.org on it. Also give us a complete list of components you have installed on it. I have seen a pci card in a particular slot keep Win XP from installing.

Just did everything and put it on a floppy and noticed it dosnt have a floppy power cable!! What do I do now?

 

[Mushroom Prince]

yeah talk to me on aim at mushrooomprince


this is the EXACT same problem that I had in building my machine.

 

[DocSavage]

Um... if you have a cd burner, you can download the iso version that creates a bootable cd.

 

[HvyMtl]

bad memory or motherboard or vid card or geez just too many &*^&% things it can be at this point... so I suggest test everything you can in a system that is working perfectly (as ors perfectly as it can under XP) see if you can find the culprit that way...
Good luck