I totally agree with what you're saying re diagnostics, etc. Point I'm making
is that I seen lots of messages about this problem and they all take that
path (and rightly so) but I'm yet to see a positive outcome.
Having seen this pattern of no outcome 'everywhere' it's disapointing that
the problem is not being given greater attention by MS.
BTW, when we (those with the problem) see 'Not Responding' we're not talking
seconds but multiple minutes for a response - then all the clicks happen at
once. For me it can happen against almost any program - Internet Explorer,
Windows Explorer, Outlook, non-MS programs, .... the lot.
If you ask me I'd say there's a lock somewhere that's timing out. Questin
is, what's setting it and why? I suspect it's at the GUI level - cpu is not
being hit, and Task manager shows normal background paging activity.
VERY FRUSTRATING!!!
"zachd [MSFT]" wrote:
Quote:
>
> "simcity" <simcity@xxxxxx> wrote in message
> news:6E60ABDD-F802-4F05-8101-1AF3CF034BE5@xxxxxx Quote:
> > I also have the same problem (over multiple Vista machines). I've been
> > searching the Internet for "vista not.responding" and it looks to be a
> > common
> > problem.
>
> ... with the notation that most every "not responding" issue you run into
> will likely be different. If you see more than ~12 people with the same
> exact "not responding" *cause*, then you've pretty clearly identified a bug.
> =\
> Quote:
> > Many of the "help replies" start off with stuff like "how much memory do
> > you
> > have", "is your anti-virus turned on", etc, etc. Many of them then get
> > side-tracked. As far as I can tell none of them provide an answer.
>
> Yes, those are good initial trouble-shooting steps attempting to check on
> basic problems. If you say "I have done these XXX things" in your problem
> report, you are less likely to get those basic questions re-asked. Then
> again, I do get too many "I do not have sound" problems that resolve
> themselves by people plugging in or turning on their speakers. =)
>
> The most useful question that anybody can ask in this sort of situation is
> also the hardest to analyze the answer for:
> What's the fault bucket information for that crash according to the Problem
> Reports and Solutions Center control panel's "View Problem History"?
>
> This and the crash DMP file produced by the crash/hang can *potentially*
> lead to a solution, but without that data, it's the equivalent of saying "I
> hurt" to the doctor. Diagnostics really do have to be run. And most
> systems are fascinatingly varied, so even if I completely understand Joe's
> system from A to Z, Imelda's system might be completely different. You
> really always need to get the diagnostics done so you can properly figure
> out what's going on where.
>
> -Zach
> --
> Speaking for myself only.
> See http://zachd.com/pss/pss.html for some helpful WMP info.
> This posting is provided "AS IS" with no warranties, and confers no rights.
>