• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

XP installation stops loading at "32 minute mark"

C

civilicious

Senior member
i've been trying to reinstall a fresh copy of windows xp for the past
couple of days and have been running into the same problem every time.
After reformatting the HD and beginning installation of windows, i
noticed that it stops installing at the "32 minute mark" where it is
"installing network." the system doesnt freeze up or anything, but it
just doesnt continue with the installation. ive tried loading windows
about 5 times now and it stops at the exact same point everytime. any
suggestions?
 
thanks for your quick replies. Larry, i tried rebooting and letting it continue loading but it still stops loading at the 32 minute mark. Gholam, i have tried installing windows without a network card and i still come up unsuccessful. 🙁
 
Ok, I had this problem a while ago, and I'm almost positive this might help.

Go to your BIOS, and make sure you have all of the standard defaults for all of the speeds (Processor, ram, etc.) I had mine UNDERCLOCKED, and I had the same problem. Every time I tried to install WinXP, it would freez, same with Win2k.

Play around with the speeds. Something like "Fail Safe" Defaults or "Optimal."

I hope this helps.




KeyserSoze
 
Hit shift+F10 to open a command prompt. Run taskmgr from there and end-task the process hanging the system. If it's hanging on some piece of hardware, setup should continue fine after that.
 
Hmmm, Video Card ?
Swap Video cards and see if it will finish, then change back to first card.
Could be a driver issue, I've seen that happen with and older ATI Rage Pro.
Swapped card, everything worked fine from that point on.
 
Which is why he should simply end-task the process handling the detection. If it's non-critical, the setup will continue and he can battle the driver issue from within windows. If it is critical (which I doubt at this stage in setup) he has a hardware issue he'll need to deal with.

One step immediately shows you where to focus your troubleshooting. 🙂
 
thanks so much for the help guys. i plan on tackling the problem later on tonight after work. ill let you kow how it works out. thanks again.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top