System hangs at boot in Windows XP Pro splash screen

[John7]

Hi,



A brand new customer's computer hangs at power up boot in the
Windows splash screen. A shutdown reboot works fine.

System:
Intel E6400, 2GB ram, 3x 320GB in Raid5, Samsung SH-S183A DVD-writer,
Asus P5B-E i965 deluxe, Asus Geforce6 7300GS 512MB pcie16, card reader
Win XP pro, Office 2007 SBE, McAfee AV, all updates.


To track this down I made an additional boot.ini entry to create a bootlog.
(creates ntbtlog.txt by supplementary option: /sos /bootlog)
We made a bootlog (ntbtlog.txt) at a succesful boot for reference.

Then the customer powered up the pc, choose Boot and Create Bootlog.
After the system hung, he had to press reset and booted normally.

Now it appeares that nothing has been added to the bootlog file.
There are NO Stop Errors, restart option has been disabled.
The hang causes the system to rebuild the RAID5 disk configuration.

How can I track down this problem ?


TIA,
John7

 

[Guest]

Have you tried starting in safe mode to see if it's hanging from one of the
drivers being loaded?

-Brian

 

[nesredep egrob]

Hi,



A brand new customer's computer hangs at power up boot in the
Windows splash screen. A shutdown reboot works fine.

System:
Intel E6400, 2GB ram, 3x 320GB in Raid5, Samsung SH-S183A DVD-writer,
Asus P5B-E i965 deluxe, Asus Geforce6 7300GS 512MB pcie16, card reader
Win XP pro, Office 2007 SBE, McAfee AV, all updates.


To track this down I made an additional boot.ini entry to create a bootlog.
(creates ntbtlog.txt by supplementary option: /sos /bootlog)
We made a bootlog (ntbtlog.txt) at a succesful boot for reference.

Then the customer powered up the pc, choose Boot and Create Bootlog.
After the system hung, he had to press reset and booted normally.

Now it appeares that nothing has been added to the bootlog file.
There are NO Stop Errors, restart option has been disabled.
The hang causes the system to rebuild the RAID5 disk configuration.

How can I track down this problem ?


TIA,
John7

I think you will find it is a hardware fault. I had the same on a W2K. It would
stop athe point where it allows you to hit F2 or F12. I could often get the
computer going by removing power (switch on the back) and restoring.

I had some trouble and removed all excess items and also some on the motherboard
(clean start). I have now been going for 6 - 8 weeks with no trouble at all so I
am sure it is a faulty joint, most likely on the motherboard. As a retired TV
tech having a look at printed circuit nowadays, I shall eventually get another
board - shame - this is an Intel board.

Borge in sunny Perth, Australia

 

[John7]

Thanks Brain,


Yes, of course ... I will give it a try.


John7

 

[John7]

Thanks for responding.


I had hoped the Windows bootlog would provide some clues but it didn't. I
suspect
hardware too but have no clue where to look yet, but I will. I have seen 2
thermal
motherboard disconnects in 5 years now but on boards older than 7 years.
Even though it is a brand new board, there might be a bad soldering joint.

I will keep your suggestion in my mind.


Regards,
John7