BleepingComputer.com: Mildly strange startup behaviour

When i start my computer, somewhere between logging in and finishing with loading all startup entries, it is as if all read/write commands are paused, for up to a minute. It doesnt seem to appear at a specific point in time, as sometimes even AVG has finished starting, whilst other times the start button has not even appeared yet.

What happens is that the hdd goes dead silent. If all the icons has appeared on the desktop i can manoeuvre around, lagg-lessly, but i can not start an application or even open a folder.

It is annoying, since it adds a minute to my boot-up time, but i dont even know what to google.

Aid appreciated

What you describe...if I'm interpreting correctly...is the norm.

I've never known XP to permit user activity until all startups have loaded, including the firewall.

Louis

System manufacturer and model?

This post has been edited by hamluis: 15 November 2010 - 02:04 PM

Windows XP sp3
HP Pavilion 061 ED741AA-B1U t3166.

And it happens between logging in (when windows is finished starting) and everything done. It doesnt just prevent me from starting stuff, it pauses the loading of startup applications as well. The few times it doesnt happen the comp starts alot quicker. Also, it has not always behaved like this.

Well...it could be anything...without an error message or something reflecting a problem other than your observations, it's somewhat dangerous (IMO) to guess.

If it only occurs on boot...I would guess hard drive or PSU...but those are just guesses, not suggestions.

You might review your Event Viewer logs for possible clues.

How To Use Event Viewer - http://www.bleepingcomputer.com/forums/topic40108.html

Louis

Apparently, something called EvntAgnt could not find some reg values. Following the fix suggestion here: http://support.microsoft.com/default.aspx?scid=kb;en-us;832790 i added the values and the errors doesnt show. I rebooted and it did not happen, though i think i need a few more reboots before i am convinced. However, so far it seems fixed.

Thank you (and facepalm to me for not checking the obvious event log)!

Let us know if it reappears .

Louis