Re: Win2008 R2 not writing crash dump file

2011-03-30 Thread Mike Leone 
On 3/30/2011 1:01 PM, Jonathan Link wrote:
> Or just do it now.  Planned outages, even during business hours are
> alwyas better than unplanned ones.  You also seem to have an element of
> unpredictability here, so...

True. However, the instructions are a bit scary - they say that the
patch may not work, if the motherboard is bad ... and then the flashing
would fail, and you wouldn't be able to boot the computer *at all*. :-(

So we think we'll do it Sat. This way, if it bricks the mobo, at least
we have a 4 hour turnaround for a new mobo 


~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

Re: Win2008 R2 not writing crash dump file

2011-03-30 Thread Jonathan Link 
Or just do it now.  Planned outages, even during business hours are alwyas
better than unplanned ones.  You also seem to have an element of
unpredictability here, so...



On Wed, Mar 30, 2011 at 12:58 PM, Kennedy, Jim  wrote:

> Nice. I would just do it now and blame it on the ongoing crash problem.  :)
>
> -Original Message-
> From: Mike Leone [mailto:oozerd...@gmail.com]
> Sent: Wednesday, March 30, 2011 12:57 PM
> To: NT System Admin Issues
>  Subject: Re: Win2008 R2 not writing crash dump file
>
> My co-worker found an HP alert about Proliant DL360 G6s (like this)
> where they can be subject to random reboots, exactly as we have been.
> Apparently, it's a known issue with this model server shipped before Nov
> 2009. Has to do with system board revision earlier than "0S". If the
> serial number is xxx947 or earlier, you may have it.
>
> There's a "Online Flash Component for Windows - System Programmable
> Logic Device" update available. (HP document ID: c01955503)
>
> 3 guesses as to what we're doing with that server this evening ... :-)
>
> I'll keep the list posted.
>
>
>
> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~
> ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~
>
> ---
> To manage subscriptions click here:
> http://lyris.sunbelt-software.com/read/my_forums/
> or send an email to listmana...@lyris.sunbeltsoftware.com
> with the body: unsubscribe ntsysadmin
>
> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~
> ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~
>
> ---
> To manage subscriptions click here:
> http://lyris.sunbelt-software.com/read/my_forums/
> or send an email to listmana...@lyris.sunbeltsoftware.com
> with the body: unsubscribe ntsysadmin
>
>

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

RE: Win2008 R2 not writing crash dump file

2011-03-30 Thread Kennedy, Jim 
Nice. I would just do it now and blame it on the ongoing crash problem.  :)

-Original Message-
From: Mike Leone [mailto:oozerd...@gmail.com] 
Sent: Wednesday, March 30, 2011 12:57 PM
To: NT System Admin Issues
Subject: Re: Win2008 R2 not writing crash dump file

My co-worker found an HP alert about Proliant DL360 G6s (like this)
where they can be subject to random reboots, exactly as we have been.
Apparently, it's a known issue with this model server shipped before Nov
2009. Has to do with system board revision earlier than "0S". If the
serial number is xxx947 or earlier, you may have it.

There's a "Online Flash Component for Windows - System Programmable
Logic Device" update available. (HP document ID: c01955503)

3 guesses as to what we're doing with that server this evening ... :-)

I'll keep the list posted.



~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

Re: Win2008 R2 not writing crash dump file

2011-03-30 Thread Mike Leone 
My co-worker found an HP alert about Proliant DL360 G6s (like this)
where they can be subject to random reboots, exactly as we have been.
Apparently, it's a known issue with this model server shipped before Nov
2009. Has to do with system board revision earlier than "0S". If the
serial number is xxx947 or earlier, you may have it.

There's a "Online Flash Component for Windows - System Programmable
Logic Device" update available. (HP document ID: c01955503)

3 guesses as to what we're doing with that server this evening ... :-)

I'll keep the list posted.



~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

Re: Win2008 R2 not writing crash dump file

2011-03-30 Thread Mike Leone 
On 3/30/2011 10:08 AM, Paul Adams wrote:
> Wow that sounds exactly like the problem we had with a DL380G6 about a
> year ago.  HP shipped us a new mainboard before they figured it out.
> Check your version of the ilo firmware.  If it's late 1.6x or early 1.7x

2.05, it says. Good thought, tho.

Looks like the ROM BIOS is just slightly out of date (it's from Dec
2010), but otherwise, we look up to date, from what I can see of
firmware and drivers ...

> there were a lot of problems with random reboots exactly as you
> describe.  We updated the firmware to 1.8x and it's been fine since
> then.  Turning off ASR in HP system management helped but didn't
> eliminate the problem altogether.  If you look in your event log and see
> duplicate messages about the temperature and fan sensors you have a
> likely culprit.

Not seeing anything in the event logs, that's part of the problem. No
bugchecks, no alerts, no warnings, no nothing. All normal messages, then
"The last system restart was unexpected".

> Good luck with it.  I had a second G6 server with similar problems that
> ended up being an actual bad system board (acted like someone was
> yanking both power cords at the same time) so I'd definitely open a case
> with HP if you have warranty on it and have not done so already. 

Yeah, I think that's what will have to be done. I think we need to boot
from SmartStart and run the diagnostics ...

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

RE: Win2008 R2 not writing crash dump file

2011-03-30 Thread Paul Adams 
Wow that sounds exactly like the problem we had with a DL380G6 about a
year ago.  HP shipped us a new mainboard before they figured it out.
Check your version of the ilo firmware.  If it's late 1.6x or early 1.7x
there were a lot of problems with random reboots exactly as you
describe.  We updated the firmware to 1.8x and it's been fine since
then.  Turning off ASR in HP system management helped but didn't
eliminate the problem altogether.  If you look in your event log and see
duplicate messages about the temperature and fan sensors you have a
likely culprit.

Good luck with it.  I had a second G6 server with similar problems that
ended up being an actual bad system board (acted like someone was
yanking both power cords at the same time) so I'd definitely open a case
with HP if you have warranty on it and have not done so already. 

Paul

The disclaimer below does not necessarily reflect my views but is
automagically generated by company elves.

-Original Message-
From: Maglinger, Paul [mailto:pmaglin...@scvl.com] 
Sent: Wednesday, March 30, 2011 9:40 AM
To: NT System Admin Issues
Subject: RE: Win2008 R2 not writing crash dump file

I'd start with the simple stuff.  
Power cord in tight?  
Is the server in a clean server room?  If not (or even if it is), check
the fans and heat sinks for dust and clean it out.
Speaking of fans, are all of them running?  Air vents not blocked?

-Paul

-Original Message-
From: Mike Leone [mailto:oozerd...@gmail.com]
Sent: Wednesday, March 30, 2011 7:38 AM
To: NT System Admin Issues
Subject: Win2008 R2 not writing crash dump file

I've got a Win2008 R2 server that has decided that it is a yo-yo, and is
rebooting daily (at different times), sometimes twice within like 20
minutes. In Control Panel, I have "Kernel memory dump" chosen under
"Write debugging information", with the value "%SystemRoot%\MEMORY.DMP
(and checked off "Overwrite any existing file").

But I never get any dump file - there are no files *.DMP anywhere on the
server. And I don't know why it's not writing one. I want to run one
through the WinDbg debugger, hopefully yo have it point at the problem
(bad device driver, I'm guessing).

The event log only says the previous shutdown was unexpected - never
lists any bugcheck values or anything. So I'm sort of flying blind at
this point.

What would cause the DMP file to never be written? How can I get a DMP
to analyze?

~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~
<http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

---
To manage subscriptions click here:
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~
<http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

---
To manage subscriptions click here:
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin



Confidentiality Note: This message is intended for use only by the individual 
or entity to which it is addressed and may contain information that is 
privileged, confidential, and exempt from disclosure under applicable law. If 
the reader of this message is not the intended recipient or the employee or 
agent responsible for delivering the message to the intended recipient, you are 
hereby notified that any dissemination, distribution or copying of this 
communication is strictly prohibited. If you have received this communication 
in error, please contact the sender immediately and destroy the material in its 
entirety, whether electronic or hard copy. Thank you.



~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

RE: Win2008 R2 not writing crash dump file

2011-03-30 Thread Maglinger, Paul 
I'd start with the simple stuff.  
Power cord in tight?  
Is the server in a clean server room?  If not (or even if it is), check
the fans and heat sinks for dust and clean it out.
Speaking of fans, are all of them running?  Air vents not blocked?

-Paul

-Original Message-
From: Mike Leone [mailto:oozerd...@gmail.com] 
Sent: Wednesday, March 30, 2011 7:38 AM
To: NT System Admin Issues
Subject: Win2008 R2 not writing crash dump file

I've got a Win2008 R2 server that has decided that it is a yo-yo, and is
rebooting daily (at different times), sometimes twice within like 20
minutes. In Control Panel, I have "Kernel memory dump" chosen under
"Write debugging information", with the value "%SystemRoot%\MEMORY.DMP
(and checked off "Overwrite any existing file").

But I never get any dump file - there are no files *.DMP anywhere on the
server. And I don't know why it's not writing one. I want to run one
through the WinDbg debugger, hopefully yo have it point at the problem
(bad device driver, I'm guessing).

The event log only says the previous shutdown was unexpected - never
lists any bugcheck values or anything. So I'm sort of flying blind at
this point.

What would cause the DMP file to never be written? How can I get a DMP
to analyze?

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

---
To manage subscriptions click here:
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

Re: Win2008 R2 not writing crash dump file

2011-03-30 Thread Mike Leone 
On 3/30/2011 9:10 AM, James Rankin wrote:
> What flavour of system is it? On branded stuff (HP, Dell, IBM, etc.) 

HP Proliant 380 G6.

> you can usually set threshholds within the management software to perform
> recovery actions under certain conditions. If you have a functioning
> ILO/DRAC/other management card, you can also sometimes replay the last
> restart, to see if it actually was a BSOD or something else.
> 
> If you do have management software and agents loaded, it may be a good
> idea to get the server to all its latest hardware patch levels.

Yeah, that's our next step, I think.

> 
> On 30 March 2011 14:06, Mike Leone  > wrote:
> 
> On 3/30/2011 8:39 AM, James Rankin wrote:
> > You sure it's a BSOD?
> 
> No, I'm not, actually.
> 
> > Could be a thermal condition, amongst many other
> > things. Does it have any ASR values set?
> 
> Don't think so. Not sure how to check. Don't think we've set anything ..
> 
> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~
> ~   ~
> 
> ---
> To manage subscriptions click here:
> http://lyris.sunbelt-software.com/read/my_forums/
> or send an email to listmana...@lyris.sunbeltsoftware.com
> 
> with the body: unsubscribe ntsysadmin
> 
> 
> 
> 
> -- 
> "On two occasions...I have been asked, 'Pray, Mr Babbage, if you put
> into the machine wrong figures, will the right answers come out?' I am
> not able rightly to apprehend the kind of confusion of ideas that could
> provoke such a question."
> 
> *IMPORTANT: This email is intended for the use of the individual
> addressee(s) named above and may contain information that is
> confidential, privileged or unsuitable for overly sensitive persons with
> low self-esteem, no sense of humour or irrational religious beliefs. If
> you are not the intended recipient, any dissemination, distribution or
> copying of this email is not authorised (either explicitly or
> implicitly) and constitutes an irritating social faux pas.
> 
> Unless the word absquatulation has been used in its correct context
> somewhere other than in this warning, it does not have any legal or no
> grammatical use and may be ignored. No animals were harmed in the
> transmission of this email, although the kelpie next door is living on
> borrowed time, let me tell you. Those of you with an overwhelming fear
> of the unknown will be gratified to learn that there is no hidden
> message revealed by reading this warning backwards, so just ignore that
> Alert Notice from Microsoft.
> 
> However, by pouring a complete circle of salt around yourself and your
> computer you can ensure that no harm befalls you and your pets. If you
> have received this email in error, please add some nutmeg and egg
> whites, whisk and place in a warm oven for 40 minutes.*
> 
> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~
> ~   ~
> 
> ---
> To manage subscriptions click here:
> http://lyris.sunbelt-software.com/read/my_forums/
> or send an email to listmana...@lyris.sunbeltsoftware.com
> 
> with the body: unsubscribe ntsysadmin
> 


~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

Re: Win2008 R2 not writing crash dump file

2011-03-30 Thread Mike Leone 
On 3/30/2011 8:51 AM, Kennedy, Jim wrote:
> Not a direct answer to your question but something to look
> at..did
you just install the Feb updates...

No. Not yet. We usually do Windows updates around the middle of the
following month, but we haven't done any to this server, since it
started rebooting daily right around the middle of the month ... and I
just looked through the list of installed updates, and don't see either
of those updates.

>look for 393802 and MAYBE 2264207.
>One of them, probably the first one has some issues with video card
>drivers that were written badly. See if there are updates for your vid
>card drivers or remove those two updates. HP is having a fair amount of
>trouble with this one, I had one server doing this. No newer vid card
>drivers available so I pulled those two updates and it is fine ever since.

I'll look to see if there are any newer drivers or HP firmware updates.

Thanks for the tip.

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

Re: Win2008 R2 not writing crash dump file

2011-03-30 Thread James Rankin 
What flavour of system is it? On branded stuff (HP, Dell, IBM, etc.) you can
usually set threshholds within the management software to perform recovery
actions under certain conditions. If you have a functioning ILO/DRAC/other
management card, you can also sometimes replay the last restart, to see if
it actually was a BSOD or something else.

If you do have management software and agents loaded, it may be a good idea
to get the server to all its latest hardware patch levels.

On 30 March 2011 14:06, Mike Leone  wrote:

> On 3/30/2011 8:39 AM, James Rankin wrote:
> > You sure it's a BSOD?
>
> No, I'm not, actually.
>
> > Could be a thermal condition, amongst many other
> > things. Does it have any ASR values set?
>
> Don't think so. Not sure how to check. Don't think we've set anything ..
>
> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~
> ~   ~
>
> ---
> To manage subscriptions click here:
> http://lyris.sunbelt-software.com/read/my_forums/
> or send an email to listmana...@lyris.sunbeltsoftware.com
> with the body: unsubscribe ntsysadmin
>



-- 
"On two occasions...I have been asked, 'Pray, Mr Babbage, if you put into
the machine wrong figures, will the right answers come out?' I am not able
rightly to apprehend the kind of confusion of ideas that could provoke such
a question."

*IMPORTANT: This email is intended for the use of the individual
addressee(s) named above and may contain information that is confidential,
privileged or unsuitable for overly sensitive persons with low self-esteem,
no sense of humour or irrational religious beliefs. If you are not the
intended recipient, any dissemination, distribution or copying of this email
is not authorised (either explicitly or implicitly) and constitutes an
irritating social faux pas.

Unless the word absquatulation has been used in its correct context
somewhere other than in this warning, it does not have any legal or no
grammatical use and may be ignored. No animals were harmed in the
transmission of this email, although the kelpie next door is living on
borrowed time, let me tell you. Those of you with an overwhelming fear of
the unknown will be gratified to learn that there is no hidden message
revealed by reading this warning backwards, so just ignore that Alert Notice
from Microsoft.

However, by pouring a complete circle of salt around yourself and your
computer you can ensure that no harm befalls you and your pets. If you have
received this email in error, please add some nutmeg and egg whites, whisk
and place in a warm oven for 40 minutes.*

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

Re: Win2008 R2 not writing crash dump file

2011-03-30 Thread Ben Scott 
On Wed, Mar 30, 2011 at 8:37 AM, Mike Leone  wrote:
> I've got a Win2008 R2 server that has decided that it is a yo-yo, and is
> rebooting daily (at different times), sometimes twice within like 20
> minutes. In Control Panel, I have "Kernel memory dump" chosen under
> "Write debugging information", with the value "%SystemRoot%\MEMORY.DMP
> (and checked off "Overwrite any existing file").

  Turn off the auto-reboot-on-crash thing.  It's an option in the same
dialog box.

  IIRC, some STOP errors don't write info to disk because they blew up
in the I/O subsystem.  But you can always read the text off the blue
screen.

  If it still reboots, it's not a BugCheck.

-- Ben

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

Re: Win2008 R2 not writing crash dump file

2011-03-30 Thread Mike Leone 
On 3/30/2011 8:43 AM, Christopher Bodnar wrote:
> Doesn't sound like it's actually crashing. It's rebooting for some as
> yet unknown reason. I would check hardware issues first (bad memory,
> disk issues, power supply. etc.)

That's what we're begining to believe, too. Since I get no DMP file, and
nothing in event log about "bugcheck".

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

Re: Win2008 R2 not writing crash dump file

2011-03-30 Thread Mike Leone 
On 3/30/2011 8:39 AM, James Rankin wrote:
> You sure it's a BSOD? 

No, I'm not, actually.

> Could be a thermal condition, amongst many other
> things. Does it have any ASR values set?

Don't think so. Not sure how to check. Don't think we've set anything ..

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

RE: Win2008 R2 not writing crash dump file

2011-03-30 Thread Kennedy, Jim 
Not a direct answer to your question but something to look at..did you just 
install the Feb updates...look for 393802 and MAYBE 2264207. One of them, 
probably the first one has some issues with video card drivers that were 
written badly. See if there are updates for your vid card drivers or remove 
those two updates.  HP is having a fair amount of trouble with this one, I had 
one server doing this. No newer vid card drivers available so I pulled those 
two updates and it is fine ever since.

-Original Message-
From: Mike Leone [mailto:oozerd...@gmail.com] 
Sent: Wednesday, March 30, 2011 8:38 AM
To: NT System Admin Issues
Subject: Win2008 R2 not writing crash dump file

I've got a Win2008 R2 server that has decided that it is a yo-yo, and is 
rebooting daily (at different times), sometimes twice within like 20 minutes. 
In Control Panel, I have "Kernel memory dump" chosen under "Write debugging 
information", with the value "%SystemRoot%\MEMORY.DMP (and checked off 
"Overwrite any existing file").

But I never get any dump file - there are no files *.DMP anywhere on the 
server. And I don't know why it's not writing one. I want to run one through 
the WinDbg debugger, hopefully yo have it point at the problem (bad device 
driver, I'm guessing).

The event log only says the previous shutdown was unexpected - never lists any 
bugcheck values or anything. So I'm sort of flying blind at this point.

What would cause the DMP file to never be written? How can I get a DMP to 
analyze?

~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ 
<http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

Re: Win2008 R2 not writing crash dump file

2011-03-30 Thread Christopher Bodnar 
Doesn't sound like it's actually crashing. It's rebooting for some as yet 
unknown reason. I would check hardware issues first (bad memory, disk 
issues, power supply. etc.)




Chris Bodnar, MCSE, MCITP
Technical Support III
Distributed Systems Service Delivery - Intel Services
Guardian Life Insurance Company of America
Email: christopher_bod...@glic.com
Phone: 610-807-6459
Fax: 610-807-6003



From:   Mike Leone 
To: "NT System Admin Issues" 
Date:   03/30/2011 08:38 AM
Subject:    Win2008 R2 not writing crash dump file



I've got a Win2008 R2 server that has decided that it is a yo-yo, and is
rebooting daily (at different times), sometimes twice within like 20
minutes. In Control Panel, I have "Kernel memory dump" chosen under
"Write debugging information", with the value "%SystemRoot%\MEMORY.DMP
(and checked off "Overwrite any existing file").

But I never get any dump file - there are no files *.DMP anywhere on the
server. And I don't know why it's not writing one. I want to run one
through the WinDbg debugger, hopefully yo have it point at the problem
(bad device driver, I'm guessing).

The event log only says the previous shutdown was unexpected - never
lists any bugcheck values or anything. So I'm sort of flying blind at
this point.

What would cause the DMP file to never be written? How can I get a DMP
to analyze?

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin



-
This message, and any attachments to it, may contain information
that is privileged, confidential, and exempt from disclosure under
applicable law.  If the reader of this message is not the intended
recipient, you are notified that any use, dissemination,
distribution, copying, or communication of this message is strictly
prohibited.  If you have received this message in error, please
notify the sender immediately by return e-mail and delete the
message and any attachments.  Thank you.
~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

Re: Win2008 R2 not writing crash dump file

2011-03-30 Thread James Rankin 
You sure it's a BSOD? Could be a thermal condition, amongst many other
things. Does it have any ASR values set?

On 30 March 2011 13:37, Mike Leone  wrote:

> I've got a Win2008 R2 server that has decided that it is a yo-yo, and is
> rebooting daily (at different times), sometimes twice within like 20
> minutes. In Control Panel, I have "Kernel memory dump" chosen under
> "Write debugging information", with the value "%SystemRoot%\MEMORY.DMP
> (and checked off "Overwrite any existing file").
>
> But I never get any dump file - there are no files *.DMP anywhere on the
> server. And I don't know why it's not writing one. I want to run one
> through the WinDbg debugger, hopefully yo have it point at the problem
> (bad device driver, I'm guessing).
>
> The event log only says the previous shutdown was unexpected - never
> lists any bugcheck values or anything. So I'm sort of flying blind at
> this point.
>
> What would cause the DMP file to never be written? How can I get a DMP
> to analyze?
>
> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~
> ~   ~
>
> ---
> To manage subscriptions click here:
> http://lyris.sunbelt-software.com/read/my_forums/
> or send an email to listmana...@lyris.sunbeltsoftware.com
> with the body: unsubscribe ntsysadmin
>



-- 
"On two occasions...I have been asked, 'Pray, Mr Babbage, if you put into
the machine wrong figures, will the right answers come out?' I am not able
rightly to apprehend the kind of confusion of ideas that could provoke such
a question."

*IMPORTANT: This email is intended for the use of the individual
addressee(s) named above and may contain information that is confidential,
privileged or unsuitable for overly sensitive persons with low self-esteem,
no sense of humour or irrational religious beliefs. If you are not the
intended recipient, any dissemination, distribution or copying of this email
is not authorised (either explicitly or implicitly) and constitutes an
irritating social faux pas.

Unless the word absquatulation has been used in its correct context
somewhere other than in this warning, it does not have any legal or no
grammatical use and may be ignored. No animals were harmed in the
transmission of this email, although the kelpie next door is living on
borrowed time, let me tell you. Those of you with an overwhelming fear of
the unknown will be gratified to learn that there is no hidden message
revealed by reading this warning backwards, so just ignore that Alert Notice
from Microsoft.

However, by pouring a complete circle of salt around yourself and your
computer you can ensure that no harm befalls you and your pets. If you have
received this email in error, please add some nutmeg and egg whites, whisk
and place in a warm oven for 40 minutes.*

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

Win2008 R2 not writing crash dump file

2011-03-30 Thread Mike Leone 
I've got a Win2008 R2 server that has decided that it is a yo-yo, and is
rebooting daily (at different times), sometimes twice within like 20
minutes. In Control Panel, I have "Kernel memory dump" chosen under
"Write debugging information", with the value "%SystemRoot%\MEMORY.DMP
(and checked off "Overwrite any existing file").

But I never get any dump file - there are no files *.DMP anywhere on the
server. And I don't know why it's not writing one. I want to run one
through the WinDbg debugger, hopefully yo have it point at the problem
(bad device driver, I'm guessing).

The event log only says the previous shutdown was unexpected - never
lists any bugcheck values or anything. So I'm sort of flying blind at
this point.

What would cause the DMP file to never be written? How can I get a DMP
to analyze?

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin