Sudden change in behavior...

slipd · 28 Feb 2012 at 10:02

Hey guys,

My main windows 7 machine (see sig) has started acting weird again! I say again because its done it once before, displaying exactly the same sort of behavior!

To start, last night, everything normal - windows was idle, had about 10 tabs in firefox running in the background, went to bring them up and they sluggishly came up but with a "not responding" caption next to the pages title. Then about 4 minutes later I get a "this is taking a long time to respond" error. In the end I tire of waiting and force a shutdown - by this time there is no functionality other than mouse movement. Turned the machine back on and although windows took a longer than usual time to start up, it was okay. I scheduled a chkdsk for the next reboot and did a quick hard drive scan (the hd is what I'm suspecting). This morning when I turned on after logging in I was still looking a the welcome screen over 40 minutes later :mad:

Forced another restart and since then, touches wood, things have been okay. I've had a look in the windows system log and the only thing I can that could be causing the problem is:

Any ideas

Blue160 · 28 Feb 2012 at 10:51

I had a similar problem the other week which turned out to be caused by Adobe shockwave player crashing. Uninstalling with revo uninstaller then reinstalling solved it. Worth trying

slipd · 28 Feb 2012 at 17:05

I don't appear to even have shockwave installed

Could it be a windows update?

Philtor · 29 Feb 2012 at 00:49

I thought HDD also whilst reading your post. Check it with the vendors own diagnostic tool perhaps to see what comes back. If nothing then Memtest may be worth running as well to rule out your RAM.

slipd · 29 Feb 2012 at 19:33

Could Microsoft Security Essentials be to blame? My computer froze earlier and the only thing that was running was firefox and an automatic MSE scan...

slipd · 15 Mar 2012 at 18:58

It was definitely MSE... since uninstalling a couple of days back my machine hasn't missed a beat

Always seemed to freeze up as soon as an auto-scan was started?

Maybe I need to try a different version?

theheyes · 15 Mar 2012 at 19:19

I had some MSE trouble the other day but I put it down to a bad stick of RAM which I found. However, after reading this I think it might have been a coincidence and there was a separate problem with an MSE update.