XP Laptop Slow to start up

Gambler

Gambler wrote: »

Nope, I'm using zone alarm. Cleaned up with Tuneup2006 which seemed to speed it up but now it's gone slow again and is not even loading the task bar and start up menu once I get past the XP Users log in page.

I fixed this previously by doing a system restore. But today the problem has occurred again but there are surprisingly no restore points available.

Any help appreciated on how I can get my desktop and taskbar sorted.

thanks

Browntoa

do me a hijackthis log first

http://www.tomcoyote.org/hjt/

let me see if there is something untowards going on

Cricri

I fixed a similar problem yesterday.
What I do is check the event log, look for errors and how long the PC got stuck on them, then sort the errors out (with focus on the ones which stuck the PC for some time).

To access the log, type Windows+R to get to the "Run" dialog, type compmgmt.msc and enter.

Bobolink

Cricri wrote: »

I fixed a similar problem yesterday.
What I do is check the event log, look for errors and how long the PC got stuck on them, then sort the errors out (with focus on the ones which stuck the PC for some time).

To access the log, type Windows+R to get to the "Run" dialog, type compmgmt.msc and enter.

I've categorised it so it's errors at the top, but it says "Application Error" or "Application Hang" but when I click properties I can't see details of any possible program error. I've got Symantec Corporate installed if that matters. How do I find which application is causing the errors?

IE7 has been unstable for the past couple of weeks or so... :think:

Cricri

Sorry, I should have mentionned, you need to look at the "System" log. It even tells you at what time the events occur, so you can match that with your slowdown. Typically, when I have a slowdown, I've got a large gap between an error event (symbolised by a red icon) and another event (which can well be another error).
So for instance yesterday, I realised my PC was getting stuck for a minute or two looking for the parallel port, so I simply re-enabled it in the BIOS and my problem was sorted.