Windows suddenly refuses to load

[thesilversurfer]

Greetings. I am running an AMD 64 3500+ on a Asus A8V- delux motherboard, with 1 gig of ram, and a MSI GeForce FX5700LE 256mb graphics card, with a videologic 5.1 sound card. Running win XP Pro (no service packs)

I have my primary hd chained with a CDRW, with the second chain having a DVD drive, and i also have one SATA hard drive.

My problem arose when i plugged in a second hard drive, and reformeted it from within windows xp, then installed another copy of windows XP onto that hard drive.

That all went fine, and after it was installed, the new hard drive worked fine, so i plugged it back into its own PC.

Now when i come to start up my PC, after i have selected the correct windows xp to run (and if anyone can tell me how to remove the other choice, i would be gratefull), it starts to load, and right at the point where the windows logon screen (the one with the accounts listed) comes up, it either pauses for a short time then crashes, or instantly crashes.

I have tried reinstalling windows on it from a bood disk, but even with all the correct (as far as i can see) boot settings, it goes through looking for a boot disk and cannot find one, then goes onto the 'select os' screen, and repeats.

I have tried plugging this hard drive into yet another of my machines, and evenually managed to reinstall windows onto it, and the first time i ran it on the 3rd machine it went fine, so i turned it off, unplugged it, and put it back into my machine, only for it to still have the same problem.

Can anyone help?

This forum has helped me before, and i hope it will again. thanks in advance

-Nathe

<A HREF="http://www.nathe.netfirms.com" target="_new">http://www.nathe.netfirms.com</A>

 

[thesilversurfer]

I have been trying to get it running still, and have managed to get an error message, which is a start.

when it loads windows, it starts loading, then brings up a blue error screen saying:

A problem has been detected and windows has been shut down to prevent damage to your computer

some stuff about if this is the first time, and look for viruses

then the error code: ***STOP: 0x0000007B (0xF8951640,0xC0000034,0x00000000,0x00000000)

anyone know what i can do?

please!

<A HREF="http://www.nathe.netfirms.com" target="_new">http://www.nathe.netfirms.com</A>

 

[riser]

You're installing Windows on a select set of hardware, removing the hard drive, putting it into another computer (different hardware?) and then problems occurs?

IDE drive problems. Find out what IDE chipset you have in your computer that you want to put the hard drive in, install those, then put the hard drive in the new computer. Can't say I've tried it before but it has a shot.

http://support.microsoft.com/default.aspx?scid=kb;en-us;316401

Riser

 

[thesilversurfer]

Essentially thats what is happeing (i think you have it right), though the problem is actually with the computer which i used to install XP with. that computer now refuses to load its own version of XP (the hard drive that was put in temporarily was fine in the machine its now in) it is the hd which stayed in the computer which now refuses to load.

I will take a look at the info you provided, and post back later.

thank you for your time

<A HREF="http://www.nathe.netfirms.com" target="_new">http://www.nathe.netfirms.com</A>

 

[Codesmith]

You are not supposed to install XP to a on one PC then attempt to move that installation to another computer unless its uses all the same hardware.

Yes sometimes you can move an XP installation to a new system and have it work without problems if the motherboars use very similar chipsets, but you should never depend on this working.

When you installed XP into a second hard drive you created a dual boot environment. I have had nothing but bad luck with dual boot enviroments. My guess is that some of the system files needed to run the original OS ended up beign moved to the 2nd hard drive.

If I want the option to be able to boot into two or more seperate I always use a 3rd party boot utility which "hides" the operation systems from each other.

Anyway to remove whatever the dual boot setup did to the hard drive try deleting all the partions. If that doesn't work zero the drive.

Then from now on only install XP on the machine for which it is intended.

 

[thesilversurfer]

I have installed windows XP onto one hd like this before with no problems.

As things are, ive had to go back to university, so no longer have all my stuff with me, and have had to resort to installing windows 98 on the malfunctioning drive, which is less than statasfactory, but at least it runs (once if finished installing all the drivers anyway)

I will take your advice about the 3rd party software next time i try and do anything like that again, though i did not 'move the instalation', i simply plugged in the other hd, fired up windows on the main hd, then formatted the second hd (as it was not working on its own), intalled win xp from the cd in windows, then it naffed up.

I tired the same thing (minus reformatting) to the main drive in another machine running win 98, and it ran on that machine, but as soon as i removed it it went breasts up again (possibly because i didnt use a 3rd party boot utility)

Thanks for your info and time :)

I will be sure to use that info in future installations :)

<A HREF="http://www.nathe.netfirms.com" target="_new">http://www.nathe.netfirms.com</A>

 

[Zoron]

All I can say is WHY?

It's easier to install XP on the other drive when it's in the computer it belongs to... why go through the trouble of connecting it to your computer, installing it, then moving it back to the other computer?

<font color=red> If you design software that is fool-proof, only a fool will want to use it. </font color=red>

 

[thesilversurfer]

Sorry to drag this topic back up. I've been at a connectionless abode for a few days.

The reason that I did this was because the computer it was on was not working at all, and some of its components had not arrived.

Since I am the 'computer expert' in the family, I had to fix it.

Since the hd was not working properly, and would not load unless it was a secondary hd, I connected it to my PC, formatted it, and reinstalled windows xp on it.

I have done this several times from a computer running windows 98 with no problem, but it really screwed things up.

Needless to say i will take the advice to use a 3rd party utility next time i try it.

<A HREF="http://www.nathe.netfirms.com" target="_new">http://www.nathe.netfirms.com</A>

 

[Codesmith]

You can move windows 9x to a new computer and it will detect hardware changes, install the prober drivers and hopefully work fine.

Window XP is designed not to work on a different motherboard!

Check microsoft's knowledge base, they desined XP to specifically prevent this type of clonning.

Technically you shouldn't even be doing this between 100% identical hardware without first using their sysprep utility then doing a mini-install on the new system.

Sometimes it works anyway, I have even had a BIOS update force a complete reinstallation!

If you installed XP on computer A then moved the hard drive to B you and it worked you got lucky. Don't expect it to happen again.

I found that moving between KT133, KT333 and KT400 chipsets is possible, but you have to make sure that you uninstall and reinstall all the motherboard drivers or you system will run like crap and you may have weird problems.

For example it was very difficult to get my USB 2.0 working stable after ghosting from a KT133 to a KT400.

 

[thesilversurfer]

The last few times i have done it i did it from identical computers, which is probably why it worked ok.

As I said, the advice is now onboard, and I will not do things like i have done in future D

<A HREF="http://www.nathe.netfirms.com" target="_new">http://www.nathe.netfirms.com</A>