Windows XP Installation - computer freezes

[MartyMcFly3]

Update: Took out the processor. Replaced it with an AMD Sempron 2500+.... It now works. Thanks for the help folks.

Hey everyone. I am going insane trying to figure out what is going on. I built a new computer so first let me get the Specs out of the way.

Specs:

Antec Solution SLK2650-BQE Black Steel ATX Mid Tower Computer Case 350W Power Supply
BIOSTAR M7NCG 400 Socket A (Socket 462) NVIDIA nForce2 IGP Micro ATX AMD Motherboard
AMD Mobile Athlon XP-M 2200+ (35W) Barton 266MHz FSB Socket A Processor Model AXMD2200FJQ4C
2 sticks of mushkin SP3200 512MB 184-Pin DDR SDRAM DDR 400 (PC 3200) Unbuffered System Memory (only have one in there right now)
Western Digital Caviar SE WD800JB 80GB 7200 RPM IDE Ultra ATA100 Hard Drive

I am having trouble during the installation of XP Pro. It goes through the first part fine (Preparing Installation), but after the computer restarts, it seems to lock up during the actual installation of it.

This build has been the most frustrating for me definitely (although its only my 2nd one). Im posting this here because I'd like to get it done and over with today.

Could it be the fact that the processor is mobile? Bad memory?

Any help is GREATLY appreciated!

Thanks in advance.

 

[MartyMcFly3]

Anyone?

 

[wasserkool]

hmm, if it locks during the WinXP intall, it is most likely an hardware issue

the biggest culprit is the RAM, try with one stick of RAM first and see which stick locks.

 

[MartyMcFly3]

Originally posted by: wasserkool
hmm, if it locks during the WinXP intall, it is most likely an hardware issue

the biggest culprit is the RAM, try with one stick of RAM first and see which stick locks.

Like i said, I currently only have one in. Ive gone back and forth with those and dont see a problem with the RAM.

 

[Bozo Galora]

This type prob can be many things

Have you formatted/partitioned yet?
If so, use manuf utility to delete them and do it with XP install
Is HDD set to master and at end of cable (black)?
Does your BIOS show the CPU correctly at first boot screen?
Correct MOBILE Voltage set?
Have you set correct CPU/FSB manually in BIOS?

Or, using a USB mouse or keyboard (or exotic keyboard), for which drivers have to be loaded. When first installing always use PS mouse connection (take out adapter), and el cheapo PS $7 keyboard.

Plus, only leave one working optical drive you are using in system, in other ide channel.

Plus, disable DMA/auto in bios - Use PIO4

Or, a bad sector on HDD where system is to installed will do it. Manuf drive test utility will rule this out or in. (Complete long test)

And as was said, bad RAM - so once again Memtest 86 worth a shot.

One can run the install in safe mode which tends to help with driver conflicts.
One can install in DOS mode......
There are two setup commands on CD - winnt.exe and winnnt32.exe
winnt.exe is 16 bit DOS
Use a win98 boot disc to navigate to this file on CD or do it directly.

 

[MartyMcFly3]

Originally posted by: Bozo Galora
This type prob can be many things

Have you formatted/partitioned yet? Yes
If so, use manuf utility to delete them and do it with XP install
Is HDD set to master and at end of cable (black)? Yes
Does your BIOS show the CPU correctly at first boot screen? Yes
Correct MOBILE Voltage set? Dunno. Think I might just buy a different processor
Have you set correct CPU/FSB manually in BIOS? No

Or, using a USB mouse or keyboard (or exotic keyboard), for which drivers have to be loaded. When first installing always use PS mouse connection (take out adapter), and el cheapo PS $7 keyboard. Using standard mouse/keyboard

Plus, only leave one working optical drive you are using in system, in other ide channel. Did

Plus, disable DMA/auto in bios - Use PIO4

Or, a bad sector on HDD where system is to installed will do it. Manuf drive test utility will rule this out or in. (Complete long test)

And as was said, bad RAM - so once again Memtest 86 worth a shot. Dont think its the RAM but ill give it a shot

Im kinda hellbent on thinking its the processor. Im going to buy a non-mobile one and try it out. Its just a basic computer for my Aunt and I would have gotten a non-mobile one if I saw that I was ordering mobile at the time. (My mistake)

 

[StormRider]

Did you try upping the memory voltage just a tiny bit? Or maybe upping the processor voltage a tiny bit.

From my past experience, whenever I have the WinXP install lock up, it's usually caused by too low voltage on either the memory or processor.

 

[MartyMcFly3]

Originally posted by: StormRider
Did you try upping the memory voltage just a tiny bit? Or maybe upping the processor voltage a tiny bit.

From my past experience, whenever I have the WinXP install lock up, it's usually caused by too low voltage on either the memory or processor.

I have messed with the voltage in the past and it didnt work...

 

[Bozo Galora]

A couple of points were noted during testing. The board refused to adopt a CAS latency of 2 clocks at any speed, but it would run tRAS at a 2T setting. We used the above settings for benchmarking. It'll take users a while to fine-tune the BIOS.

http://www.neoseeker.com/resourcelink.html?rlid=68923
+++++++++++++++

Introduction
http://compreviews.about.com/od/cpus/l/aaAMDXPM2600.htm
AMD has been very popular with the enthusiast community for some time thanks to the success of the Athlon XP line of processors. These processors generally sold for below Intel's competing Pentium line yet allowed for equal or better performance at lower clock speeds. This difference in clock versus performance has even lead Intel to change its marketing of their latest line of processors. The Athlon XP 2500+ earned a reputation as a very strong overclocking processor. Its low cost to performance ratio made it very popular with those on a tight budget as well.

Today we take a look at another AMD processor that is becoming popular with the enthusiast crowd, but it's a processor that is geared towards the mobile market. Let's see how well the AMD Athlon XP-M 2600+ can perform compared to the previous XP 2500+.

XP vs. XP-M

Before going into the details of how the processor performs, let's take a look at what exactly the difference between the XP and XP-M processor. Both processors look identical and share the same pin layout. This allows both processors to run on the Socket A based motherboards that can support their speeds. In fact, each of the processors used in this review are based on the same Barton core from AMD. So what is the difference?


Close Up of the AMD Athlon XP-M 2600+

The difference comes in how the processors are handled post-production. The first difference is in their power usage. The XP-M processors are those that test to run properly at lower voltages (approximately 1.45 volts vs. 1.65 volts) so they consume less power. This is especially important for mobile systems that run on batteries.

Another important difference is in the clock speed and multiplier settings. The XP processors are defined by a specific bus speed and multiplier that sets its particular PR rating. In the case of the XP-M processors, the bus speed is typically fixed, but the multiplier must be able to float between a range of multipliers to help the system conserve power during low CPU usage. This combined with the wider range of voltage tolerances makes them perfect for overclocking.

Benchmarking

Since the XP-M 2600+ doesn't have a defined set of clock speeds in most desktop BIOS, all testing with the processor was done with overclocking. Manual clock and multiplier settings were done and compared to the overclocking results from my Athlon XP 2500+ Review. For additional information on overclocking, check out the What is Overclocking? article.
==========

Id be willing to bet if you put in a CAS 2.5 setting and a VGA vid card and turned off onboard video - it would install.

 

[MartyMcFly3]

Update: Took out the processor. Replaced it with an AMD Sempron 2500+.... It now works. Thanks for the help folks.