Re: Blue Console
- From: rossk <rkovelman@xxxxxxxxxxxxxxxx>
- Date: Wed, 6 Feb 2008 20:18:42 -0800 (PST)
when I run the SBS Best practice analyzer it is saying that the VM
Largest block size on the server is low and may cause reliability
problems. Current largest block is 71MB. The store.exe process has
been running for 2 days. Any ideas why this is in there?
On Feb 6, 10:35 am, "Claus" <cjo...@xxxxxxxxxxxxx> wrote:
You would look for unexplained increases. Depending on how often the freeze
occurs you would check the Task Manager every hour or 6 hours or daily and
compare the numbers. You can click on each column to order the display to
make it easier. As I said, memory leaks are not easy to diagnose.
The other approach is to do a clean boot (only MS programs) and then add one
program at a time until you run into the issue. This isn't always very
practical as the client would loose some functionality over a longer period
of time. So I would first monitor via the Task Manager and see if something
shows up.
--
Claus"rossk" <rkovel...@xxxxxxxxxxxxxxxx> wrote in message
news:73679b13-3153-417b-818f-31100113c62b@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
You explained what the handles means in a way but what should I look
for under the other catagories? Or what do they mean?
~Ross
On Feb 5, 8:11 pm, "Claus" <cjo...@xxxxxxxxxxxxx> wrote:
You need to add the PID so you can cross reference the service in the
"tasklist /svc" command.
The other columns I normally add for a suspected memory leak (if not
already
there) are:
Mem Usage
Peak Mem Usage
VM Size
Paged Pool
NP Pool
Handles
Especially watching the number of Handles increase can be an indication of
a
memory leak.
--
Claus"rossk" <rkovel...@xxxxxxxxxxxxxxxx> wrote in message
news:bef97144-23cd-46d1-b1a8-54e8ba09f394@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Being that I am learing as we all are and for people that further
search on this same issue what are those colums to add?
On Feb 5, 6:54 pm, "Claus" <cjo...@xxxxxxxxxxxxx> wrote:
It's not easy to diagnose but there are ways to narrow it down. Your PF
is
a
bit small assuming you have 4GB RAM but it will not cause a crash. As I
mentioned earlier, this is most likely a memory leak. Lets wait and see
if
it happens again. We can then add some columns to your Task Manager and
you
can monitor which processes might be the likely culprit.
I will continue monitoring this thread, so if this happens again, let me
know and I will give you some columns to add.
--
Claus"rossk" <rkovel...@xxxxxxxxxxxxxxxx> wrote in message
news:3fdab89e-eaa9-4fb5-93bb-d2b02f330435@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Today it has not happened. The PF is now 3327 min and max. So there
is no way to see why it crashed like that?
On Feb 5, 10:03 am, "Claus" <cjo...@xxxxxxxxxxxxx> wrote:
One of the most common reasons for this is a memory leak. The page
file
change wouldn't cause that. It is a very good idea to have min and max
the
same size. What size did you set it to?
Has the issue reoccurred?
--
Claus"rossk" <rkovel...@xxxxxxxxxxxxxxxx> wrote in message
news:c1066696-4e8c-4fa2-be77-d0ed32539971@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Wow sorry guys for the confusion. This was NOT a BSOD, just a blue
screen. The thing I changed which was recomended from the SBS best
practice analyzer was to change the page file of the system so the min
and max were the same amount and the same size as the system memory.
I also made updates to the virus scanner (CA eTrust) becuase that was
causing a memory leak in poolmon. This was just a blue screen, all
connections to the server stoped. I waited a good 15 min till a
reboot to see if I would get a BSOD but nothing.
Any ideas?
On Feb 4, 10:15 pm, "Claus" <cjo...@xxxxxxxxxxxxx> wrote:
The OP is not talking about a BSOD. According to his description,
the
server
hangs and a "hard reboot" will not create a memory dump file.
--
Claus"Holz" <n...@xxxxxxxx> wrote in message
news:47a7cda2$0$30705$4c368faf@xxxxxxxxxxxxxxxxx
On Mon, 04 Feb 2008 16:41:37 -0800, rossk wrote:
I was curious where or what log I can check as to why the SBS 03
Welcome to BSOD (Blue Screen Of Death)
When a server crashes this way, there is a memory dump, I believe
it
is
called memory.dmp (you do not get the file if you do not have a
large
enough virtual memory file space allocated).
There is a command called dumpchk that will verify the dump and
display
information about it. This command can be found in the Windows XP
Support
Tools (http://tinyurl.com/4uhnu). You can copy dumpchk.exe into
the
same
folder as the memory.dmp file, open a command prompt, go the
directory
and type "dumpchk memory.dmp" (no quotes).
Understanding the dump is a different story, may try posting it
here.
--
:-)
.
- References:
- Blue Console
- From: rossk
- Re: Blue Console
- From: Holz
- Re: Blue Console
- From: Claus
- Re: Blue Console
- From: rossk
- Re: Blue Console
- From: Claus
- Re: Blue Console
- From: rossk
- Re: Blue Console
- From: Claus
- Re: Blue Console
- From: rossk
- Re: Blue Console
- From: Claus
- Re: Blue Console
- From: rossk
- Re: Blue Console
- From: Claus
- Blue Console
- Prev by Date: SBS IIS Chaos
- Next by Date: Re: SBS With VOIP Phones
- Previous by thread: Re: Blue Console
- Next by thread: Re: Blue Console
- Index(es):
Relevant Pages
|
