WE locks up constantly

+ No BSOD, just this which happens constantly with Vista:

Description:
A problem caused this program to stop interacting with Windows.

Problem signature:
Problem Event Name: AppHangB1
Application Name: explorer.exe
Application Version: 6.0.6001.18000
Application Timestamp: 47918e5d
Hang Signature: 0826
Hang Type: 0
OS Version: 6.0.6001.2.1.0.768.3
Locale ID: 1033
Additional Hang Signature 1: f351b522552acefa7e76d2dda9a1d08f
Additional Hang Signature 2: 42b0
Additional Hang Signature 3: 27366395cf11a070c2326ba541af814a
Additional Hang Signature 4: 0826
Additional Hang Signature 5: f351b522552acefa7e76d2dda9a1d08f
Additional Hang Signature 6: 42b0
Additional Hang Signature 7: 27366395cf11a070c2326ba541af814a

Read our privacy statement:
http://go.microsoft.com/fwlink/?link...3&clcid=0x0409

+ This NEVER happened with W/XP or W/98SE both of which has several times
the added software this PC with Vista has.

I don't think anybody will be able to meaningfully interpret or even guess
at any AppHangB1 problem events without specifically getting access to the
generated dump file produced during the hang event. That when placed under
a debugger such as that within the Windows Debugging Toolkit should pinpoint
**about** where it's blocking/locking up.

Of course standard logic about "what was recently added?" may point you to
any newly introduced source of failure.

--
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.
--
"news.microsoft.com" <> wrote in message
news:%...
>+ No BSOD, just this which happens constantly with Vista:
>
> Description:
> A problem caused this program to stop interacting with Windows.
>
> Problem signature:
> Problem Event Name: AppHangB1
> Application Name: explorer.exe
> Application Version: 6.0.6001.18000
> Application Timestamp: 47918e5d
> Hang Signature: 0826
> Hang Type: 0
> OS Version: 6.0.6001.2.1.0.768.3
> Locale ID: 1033
> Additional Hang Signature 1: f351b522552acefa7e76d2dda9a1d08f
> Additional Hang Signature 2: 42b0
> Additional Hang Signature 3: 27366395cf11a070c2326ba541af814a
> Additional Hang Signature 4: 0826
> Additional Hang Signature 5: f351b522552acefa7e76d2dda9a1d08f
> Additional Hang Signature 6: 42b0
> Additional Hang Signature 7: 27366395cf11a070c2326ba541af814a
>
> Read our privacy statement:
> http://go.microsoft.com/fwlink/?link...3&clcid=0x0409
>
> + This NEVER happened with W/XP or W/98SE both of which has several times
> the added software this PC with Vista has.
>
>
>

"zachd [MSFT]" <> wrote in message
news:%...
>
> I don't think anybody will be able to meaningfully interpret or even guess
> at any AppHangB1 problem events without specifically getting access to the
> generated dump file produced during the hang event. That when placed
> under a debugger such as that within the Windows Debugging Toolkit should
> pinpoint **about** where it's blocking/locking up.

Where do I find this "Windows Debugging Toolkit?" Because now, when I do
use IE7 rather then Mozilla, it too "stops responding" and locks up. I never
had any of these problems with W98SE or W/XP. Also, Windows Task Manager
doesn't end the "hung' or locked up WE and now IE7 when clicked on "End
Task." This always ended the task in XP on the rare occasion something
locked up.

>
> Of course standard logic about "what was recently added?" may point you to
> any newly introduced source of failure.

Only the software I need for my graphics work which is nothing real special.
This is after all a work machine. It's not only for fun and play. I added
the same software basically I had on both W98SE and XP. But these freezes
occurred from day one, days before files were moved over and software added.
They're just becoming more frequent. A check-disk found no problems I know
of. Also did a defrag. That didn't help either. Right now I can't close IE7
because "Task Manager" doesn't shut down programs as it did in XP.


>
> --
> 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.
> --
> "news.microsoft.com" <> wrote in message
> news:%...
>>+ No BSOD, just this which happens constantly with Vista:
>>
>> Description:
>> A problem caused this program to stop interacting with Windows.
>>
>> Problem signature:
>> Problem Event Name: AppHangB1
>> Application Name: explorer.exe
>> Application Version: 6.0.6001.18000
>> Application Timestamp: 47918e5d
>> Hang Signature: 0826
>> Hang Type: 0
>> OS Version: 6.0.6001.2.1.0.768.3
>> Locale ID: 1033
>> Additional Hang Signature 1: f351b522552acefa7e76d2dda9a1d08f
>> Additional Hang Signature 2: 42b0
>> Additional Hang Signature 3: 27366395cf11a070c2326ba541af814a
>> Additional Hang Signature 4: 0826
>> Additional Hang Signature 5: f351b522552acefa7e76d2dda9a1d08f
>> Additional Hang Signature 6: 42b0
>> Additional Hang Signature 7: 27366395cf11a070c2326ba541af814a
>>
>> Read our privacy statement:
>> http://go.microsoft.com/fwlink/?link...3&clcid=0x0409
>>
>> + This NEVER happened with W/XP or W/98SE both of which has several times
>> the added software this PC with Vista has.
>>
>>
>>
>
>

"zachd [MSFT]" <> wrote in message
news:%...
>
> I don't think anybody will be able to meaningfully interpret or even guess
> at any AppHangB1 problem events without specifically getting access to the
> generated dump file produced during the hang event. That when placed
> under a debugger such as that within the Windows Debugging Toolkit should
> pinpoint **about** where it's blocking/locking up.
>
> Of course standard logic about "what was recently added?" may point you to
> any newly introduced source of failure.
>

This is the new freeze - IE7. Task manager wont shut it down. In fact,
sometimes Task Manager freezes.

Description:
A problem caused this program to stop interacting with Windows.

Problem signature:
Problem Event Name: AppHangB1
Application Name: iexplore.exe
Application Version: 7.0.6001.18000
Application Timestamp: 47918f11
Hang Signature: 803a
Hang Type: 4
OS Version: 6.0.6001.2.1.0.768.3
Locale ID: 1033
Additional Hang Signature 1: f7efe276593c95c1656cd904ccc629f0
Additional Hang Signature 2: 7a18
Additional Hang Signature 3: f66c6e30cef3122742f3a0e5e95d35db
Additional Hang Signature 4: e60f
Additional Hang Signature 5: f9cc4bc3830d3726a27b9a11908148c0
Additional Hang Signature 6: b945
Additional Hang Signature 7: 2e8c6edebbfdaae6a85d9ec72fcaf15c

Read our privacy statement:
http://go.microsoft.com/fwlink/?link...3&clcid=0x0409

"news.microsoft.com" <> wrote in message
news:...
> This is the new freeze - IE7. Task manager wont shut it down. In fact,
> sometimes Task Manager freezes.

You might get a little more data added to that that *might* be illuminative
if you make sure to Check for Solutions, but the data as currently provided
probably isn't going to mean anything to anyone. =(

-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.

Look up "Debugging Tools for Windows" on MSDN.microsoft.com and you should
see it. It's not for the average user or even most power users - it's
generally a developer toolset.

You probably want to simply capture a dump of the hang and put that up
someplace (megaupload?) where people can look at it.

This is probably a non-trivial task for you if you're not a pretty high
level power user, but if you're trying to approach it from the AppHangB1
side of things, that's probably the easiest way to move forward.

> Only the software I need for my graphics work which is nothing real
> special. This is after all a work machine. It's not only for fun and
> play. I added the same software basically I had on both W98SE and XP.
> But these freezes occurred from day one, days before files were moved over
> and software added.

That's already good information. Knowing at what point things were
introduced helps isolate out the interesting data.

Given the data so far, I'd actually probably run chkdsk if I were you.
Looking at that hang dump would probably be interesting, but that may be
beyond your means to get that uploaded to be looked at. =\

--
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.
--
"news.microsoft.com" <> wrote in message
news:...
> "zachd [MSFT]" <> wrote in message
> news:%...
>>
>> I don't think anybody will be able to meaningfully interpret or even
>> guess at any AppHangB1 problem events without specifically getting access
>> to the generated dump file produced during the hang event. That when
>> placed under a debugger such as that within the Windows Debugging Toolkit
>> should pinpoint **about** where it's blocking/locking up.
>
> Where do I find this "Windows Debugging Toolkit?" Because now, when I do
> use IE7 rather then Mozilla, it too "stops responding" and locks up. I
> never had any of these problems with W98SE or W/XP. Also, Windows Task
> Manager doesn't end the "hung' or locked up WE and now IE7 when clicked on
> "End Task." This always ended the task in XP on the rare occasion
> something locked up.

does it hang if you right click the IE desktop icon and pick start without
add-ons?

"news.microsoft.com" <> wrote in message
news:...
> "zachd [MSFT]" <> wrote in message
> news:%...
>>
>> I don't think anybody will be able to meaningfully interpret or even
>> guess at any AppHangB1 problem events without specifically getting access
>> to the generated dump file produced during the hang event. That when
>> placed under a debugger such as that within the Windows Debugging Toolkit
>> should pinpoint **about** where it's blocking/locking up.
>>
>> Of course standard logic about "what was recently added?" may point you
>> to any newly introduced source of failure.
>>
>
> This is the new freeze - IE7. Task manager wont shut it down. In fact,
> sometimes Task Manager freezes.
>
> Description:
> A problem caused this program to stop interacting with Windows.
>
> Problem signature:
> Problem Event Name: AppHangB1
> Application Name: iexplore.exe
> Application Version: 7.0.6001.18000
> Application Timestamp: 47918f11
> Hang Signature: 803a
> Hang Type: 4
> OS Version: 6.0.6001.2.1.0.768.3
> Locale ID: 1033
> Additional Hang Signature 1: f7efe276593c95c1656cd904ccc629f0
> Additional Hang Signature 2: 7a18
> Additional Hang Signature 3: f66c6e30cef3122742f3a0e5e95d35db
> Additional Hang Signature 4: e60f
> Additional Hang Signature 5: f9cc4bc3830d3726a27b9a11908148c0
> Additional Hang Signature 6: b945
> Additional Hang Signature 7: 2e8c6edebbfdaae6a85d9ec72fcaf15c
>
> Read our privacy statement:
> http://go.microsoft.com/fwlink/?link...3&clcid=0x0409
>
>

"Not Even Me" <> wrote in message
news:%...
> does it hang if you right click the IE desktop icon and pick start without
> add-ons?

WE, not IE. A system restore cured the problem.... forever I hope.

>
> "news.microsoft.com" <> wrote in message
> news:...
>> "zachd [MSFT]" <> wrote in message
>> news:%...
>>>
>>> I don't think anybody will be able to meaningfully interpret or even
>>> guess at any AppHangB1 problem events without specifically getting
>>> access to the generated dump file produced during the hang event. That
>>> when placed under a debugger such as that within the Windows Debugging
>>> Toolkit should pinpoint **about** where it's blocking/locking up.
>>>
>>> Of course standard logic about "what was recently added?" may point you
>>> to any newly introduced source of failure.
>>>
>>
>> This is the new freeze - IE7. Task manager wont shut it down. In fact,
>> sometimes Task Manager freezes.
>>
>> Description:
>> A problem caused this program to stop interacting with Windows.
>>
>> Problem signature:
>> Problem Event Name: AppHangB1
>> Application Name: iexplore.exe
>> Application Version: 7.0.6001.18000
>> Application Timestamp: 47918f11
>> Hang Signature: 803a
>> Hang Type: 4
>> OS Version: 6.0.6001.2.1.0.768.3
>> Locale ID: 1033
>> Additional Hang Signature 1: f7efe276593c95c1656cd904ccc629f0
>> Additional Hang Signature 2: 7a18
>> Additional Hang Signature 3: f66c6e30cef3122742f3a0e5e95d35db
>> Additional Hang Signature 4: e60f
>> Additional Hang Signature 5: f9cc4bc3830d3726a27b9a11908148c0
>> Additional Hang Signature 6: b945
>> Additional Hang Signature 7: 2e8c6edebbfdaae6a85d9ec72fcaf15c
>>
>> Read our privacy statement:
>> http://go.microsoft.com/fwlink/?link...3&clcid=0x0409
>>
>>
>
>