5punk

So!
Everytime I start my computer, it freezes/lock up every now and then, where it just stops doing things for a few seconds, then continues on like nothing ever happened. It does this for a while then it seems to stop doing it altogether, and it only does this when I start it up.
It seems to have happened after I installed that impulse (steam clone) program, but there are no restore points from before that date, sadly...
Something tells me I had this before and solved through disk fragmentation or the like, but I can't remember...

Cheers!

I'm afraid all I can offer is this;

[media]http://www.youtube.com/watch?v=JAIOzM7SsMo[/media]





Also, does it do it in safe mode?

Apparently not.

Could mean it's driver related. If you think it might be down to a particular bit of software, use msconfig (put it in your run promt) to trim down what programs start up on erm.. startup, and see if it keeps doing it.

I might try updating my drivers first, and see what happens. Cheers pants!

Dog Pants wrote:Could mean it's driver related. If you think it might be down to a particular bit of software, use msconfig (put it in your run promt) to trim down what programs start up on erm.. startup, and see if it keeps doing it.

As a side note, I've stopped using MSConfig and moved onto the registry to remove programs from startup in XP.

For ref:
HKEY_LOCAL_MACHINE/SOFTWARE/MICROSOFT/WINDOWS/CURRENTVERSION/RUN

Also some entries exist in the same location but as part of the HKEY_CURRENT_USER branch.

Quite handy if it's not a service as it means you can run MSConfig in normal mode rather than selective.

I use Crap Cleaner to manage start-up items, it's under tools in the app's sidebar.

Aye, CCleaner's great. AutoRuns is also great, as it covers everything from Scheduled Tasks to services.

In this instance though, I'd use MSConfig to enable Boot Logging (Boot tab, Boot options, check Boot log). When you next boot, it'll write everything to a text file (ntbtlog.txt in your Windows directory). That should tell you about any drivers that failed to load (as opposed to drivers it *didn't* load, which is apparently fine).

Could be a disk on the way out, or misbehaving. Check the Event Viewer, Windows Logs, System for NTFS errors.

Stoat wrote:In this instance though, I'd use MSConfig to enable Boot Logging (Boot tab, Boot options, check Boot log). When you next boot, it'll write everything to a text file (ntbtlog.txt in your Windows directory). That should tell you about any drivers that failed to load (as opposed to drivers it *didn't* load, which is apparently fine).

I tried that, but so far I didn't have any failed drivers, but on the couple of restarts I had today the stuttering didn't return so I'm guessing it'll be back tomorrow morning.