Re: Blue screen of death when closing connections
- From: Lefty Bigfoot <nunya@xxxxxxxxxxxxx>
- Date: Sat, 01 Oct 2005 16:29:45 GMT
Matthew Chapman wrote
(in article
<slrndjt98h.kcs.matthewc@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>):
> 0xab just indicates a certain type of memory leak, there are a
> number of different issues that have been reported here that are
> resulting in 0xab, mostly related to fonts. Your numbers don't
> follow any of the patterns I recognise, though.
Again, I'd be much more interested in solving the other problem
which leads up to this, but apparently that doesn't ring any
bells here.
> It would be worth trying 901150 to see if that resolves the BSOD
> (you can find a copy here: http://arizstuart.tripod.com/).
I'm not sure I want to install an unreleased hotfix on a
production system, especially one obtained from a third party
website instead of Microsoft. I think I'm going to try and
avoid it until a production update is available.
> If you want to try and diagnose it further you can do the
> following:
>
> (1) Install Debugging Tools for Windows from
> http://www.microsoft.com/whdc/devtools/debugging/default.mspx
> (2) File -> Open Crash Dump -> C:\WINDOWS\MEMORY.DMP
> (3) Type the following in the command window:
> !analyze -v
> !poolused 8
> and report the results. If it complains about symbols you may
> need to also do:
> .symfix
> .reload
I'll look into this, thanks.
> Windows can't know that this problem exists until it actually
> terminates the session, and finds that there's unfreed memory
> left over. Arguably, it should just emit a warning somewhere and
> discard the remaining memory.
Yes. Blue screening for a memory leak doesn't make sense,
unless you've leaked it all and can't recover.
> However, there might also be wider
> integrity problems at the root of the leak, which is I guess why
> Microsoft chose the "safer" route of stopping the system.
Safer for MS, or safer for my users? When dozens of people have
work in flight roll over, over 1300 bytes, that doesn't make any
sense.
>> Also, I am curious if anyone has a cure for the stuck session
>> problem which precedes this problem?
>
> I think it may be unrelated.
As I said before, it NEVER happens unless I manually disconnect
a session through the manager. It happens almost exactly timed
to the mouse click. No exceptions (no pun intended).
> Do you have any extra software
> such as antivirus etc which runs in each session?
Most are running only Office and IE currently, typically word,
excel, outlook and IE are the only apps being used.
--
_ __ _
| | ___ / _| |_ _ _
| | / _ \ |_| __| | | |
| |__| __/ _| |_| |_| |
|_____\___|_| \__|\__, |
|___/
All of God's creatures have a place..........
..........right next to the potatoes and gravy.
.
- References:
- Re: Blue screen of death when closing connections
- From: Lefty Bigfoot
- Re: Blue screen of death when closing connections
- Prev by Date: Using PsSetCreateProcessNotifyRoutine on Terminal Services
- Next by Date: Re: cached profiles are not being deleted...?
- Previous by thread: Re: Blue screen of death when closing connections
- Next by thread: Re: Blue screen of death when closing connections
- Index(es):
Relevant Pages
|
