XP hangs up
This is a discussion about XP hangs up in the Everything New Technology category; ive reformatted several times, used different copies of XP, and changed processors, but my computer is still freezing up on me. it could be a matter of a few seconds, to several minutes, i can just turn on the computer, open a program, it doesnt matter, it freezes up no matter what i do.
ive reformatted several times, used different copies of XP, and changed processors, but my computer is still freezing up on me. it could be a matter of a few seconds, to several minutes, i can just turn on the computer, open a program, it doesnt matter, it freezes up no matter what i do. it boots into XP fine, but once there it hardly goes any further. any ideas, suggestions....
Participate in our website and join the conversation
This subject has been archived. New comments and votes cannot be submitted.
Jul 31
Jul 31
0
3 minutes
Responses to this topic
OP
thanks for the reply! actually, the computer was only connected to the internet upon installation of XP pro to download service packs. it has not been connected since thenand no software has been installed. im guessing eventviewer is a windows program? ill look for it tonite and post a reply.
Hey munkiep,
Here are a few pointers...
Fresh install - Not a problem with this version of windows.
Boots fine - Not a problem with windows again. Could be a RAM issue if it just so happens that the boot process is not using the bad portion of your RAM but your programs are. This is probably not your problem. An idea though.
Lockups after booting - Usually caused by a hardware conflict, or a driver issue with some of your hardware. Video or Audio is usually the problem.
Sometimes, on a newly built system, it is wise to check for BIOS updates.
If you are a novice, eventviewer will seem like greek to you. Usually lockups will not allow the event to be logged because the computer froze right after the problem occured. Look anyway! If there is something there it should tell you if some file has conflicted with another file. You would then need to find out what that file is associated with.
Lastly, if your motherboard chipset is anything other than Intel with an AMD processor, or it is something very current from Intel, you will need to see if your motherboard drivers need to be updated. The motherboard hardware information file would need to be installed. I've heard horror stories from people using VIA chipsets with Windows and they did not update the INF file and install any needed drivers.
Good luck.
Here are a few pointers...
Fresh install - Not a problem with this version of windows.
Boots fine - Not a problem with windows again. Could be a RAM issue if it just so happens that the boot process is not using the bad portion of your RAM but your programs are. This is probably not your problem. An idea though.
Lockups after booting - Usually caused by a hardware conflict, or a driver issue with some of your hardware. Video or Audio is usually the problem.
Sometimes, on a newly built system, it is wise to check for BIOS updates.
If you are a novice, eventviewer will seem like greek to you. Usually lockups will not allow the event to be logged because the computer froze right after the problem occured. Look anyway! If there is something there it should tell you if some file has conflicted with another file. You would then need to find out what that file is associated with.
Lastly, if your motherboard chipset is anything other than Intel with an AMD processor, or it is something very current from Intel, you will need to see if your motherboard drivers need to be updated. The motherboard hardware information file would need to be installed. I've heard horror stories from people using VIA chipsets with Windows and they did not update the INF file and install any needed drivers.
Good luck.
Perhaps you could give us some of the devices that are installed on your machine - name of the video card (which drivers you are using), USB devices, CD Roms, etc. Bring up your startup manager (Start-Run - type msconfig) and look in all of the tabs, but particularly Start to see what you have initially loading that may conflict with something else in the system.
