1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

XP installation hangs when installing/booting [on new build]

Discussion in 'PC Hardware' started by Fallschirmjager, 2006/05/22.

  1. 2006/05/22
    Fallschirmjager

    Fallschirmjager Inactive Thread Starter

    Joined:
    2006/05/22
    Messages:
    2
    Likes Received:
    0
    Hi, Here is my problem, I couldn't find anything similar in the FAQ.
    Have new MLB, Power supply, memory and AMD 64 bit processor, and 1 gig of RAM (single SIMS). All hardware is compatable. The MLB is a MSI K8 Socket 939. The only thing on the system that isn't onboard the MLB is the wireless net interface card (which is also new).

    When installing XP (no other pre-exsisting OS) I have partitioned the HD (which is new) and started installation the system will hang. It has hung up at different stages of installing or rebooting. I have finally got XP on the system and started to reboot after the install. It hangs at the splash screen for Windows XP (where the bottom bar moves then just freezes). The system simply stops. I have re-installed along with re-partitioning and formatting several times. All the hardware is seen in BIOS. I can't seem to get any further. Microsoft's support has not been able to resolve the problem they just say, "Thats strange ".

    Does anyone have any suggestions or has anyone run into the same problem. I could understand if there had been a different OS on the system but the harddrive new out of the box. I don't get any errors on memory, etc. from the BIOS.
     
    Fallschirmjager,
    #1
  2. 2006/05/22
    Whiskeyman Lifetime Subscription

    Whiskeyman Inactive Alumni

    Joined:
    2005/09/10
    Messages:
    1,772
    Likes Received:
    37
    Could be a problem with the optical drive or XP cd.
     
    Whiskeyman,
    #2


  3. to hide this advert.

  4. 2006/05/22
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    Fallschirmjager - Welcome to the Board :)

    Sorry to hear you have problems - a few more details please ....

    What is the size of the hard drive and is it a SATA drive or a PATA drive (EIDE):

    How did you partition the drive?

    The BIOS will only tell you if the memory is basically non-existent - it does not detect minor errors in the module.

    If you have a floppy drive I suggest you run the Windows Memory Diagnostic tool to check out the memory.

    I have moved your thread with title edit to the Hardware forum where it will draw in more expert attention.
     
    PeteC,
    #3
  5. 2006/05/22
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
    Examine the Setup log files for anything that may indicate what may be causing the problem. To do this, press SHIFT+F10 to open a command prompt after the first restart, and after any subsequent restarts, if Setup stops responding. In the Windows folder (usually C:\Windows), look for the Pnplog.txt file. This log file is only created during setup if there is an issue that is detected with hardware. The log file should include the hardware that Setup will skip on the next restart.

    You can also review the Setupapi.log file, the Setupact.log file, and the Setuperr.log file (in the Windows folder) to try to determine which device Setup was trying to detect when it stopped responding. To locate the device that is the most likely cause of the issue, read the last 10 to 15 lines at the end of the files.

    Note: You may have to look for the last class installer to load in the Setupapi.log file. This may tell you the device class instead of the specific device.
     
    Arie,
    #4
  6. 2006/05/23
    mattman

    mattman Inactive Alumni

    Joined:
    2002/06/10
    Messages:
    8,198
    Likes Received:
    63
    A new build/rebuild? I would suggest pulling and reseating all the connections except the CPU itself (although you could check the temperature readouts for the CPU in the BIOS/CMOS settings). Remove the wireless network card until you get the system stable.

    Matt
     
    mattman,
    #5
  7. 2006/05/29
    Fallschirmjager

    Fallschirmjager Inactive Thread Starter

    Joined:
    2006/05/22
    Messages:
    2
    Likes Received:
    0
    Hi Gang,

    Thanks for the suggestions. Followed the steps you guy suggested and found the problem. I pulled and reseated all connections and while pulling the CD/DVD drives I found that the jumpers were set on both devices as Slave Drives on the same EIDE cable (DOH!). :eek: Talk about feeling r-e-a-l-l-y STUPID!

    It was a complete new build system, but in the process for some silly reason (probably cause it was 2AM) the jumpers were set wrong.

    Thanks a ton for all the help. Now where else can a person get help from Malta, Australia, the UK (got a friend from Swindon UK, and Scotland) among other places. This BBS is super!

    The moderator can mark this Sherlock Holme's case closed. WOO HOO!
     
    Last edited: 2006/05/29
    Fallschirmjager,
    #6
  8. 2006/05/29
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    Glad to hear you got it sorted :) Guess we've all been there - one time or another!
     
    PeteC,
    #7

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Accept Learn More...