Re: Question About Kernal Dumps, system crashing

Tech-Archive recommends: Speed Up your PC by fixing your registry

I would resist the temptation to tinker with settings or reinstall anything until you diagnose this. It's interesting that all three crashes may have happened at the same time, given the DST change.

Do you think the error you posted happened at the time of a reboot (the error message time seems much later than what you previously mentioned)? How do you know the server is actually rebooting? After you set the minidump settings, it'll be interesting to see if a dump file is created at this time.

Did you double-check your UPS? If the UPS is set to do something based on the time, it's probably off an hour due to DST - I just checked one of mine, and it's off an hour.

"Steve" <Steve@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:73671557-095B-48A9-AA7A-69DA00274435@xxxxxxxxxxxxxxxx
Thanks for your response. All of this started happening after I fixed an
issue routing faxes to sharepoint, uninstalling and reinstalling fax and
intranet components, re-applying service packs, etc. An NTFRS issue presented
itself afterwards and I was able to fix that, now the system is doing the
re-boot every night.

I shall switch it over to mini dump and see what happens, follow up on that
tomorrow, if the sbs crashes again.

The first two crashes happened at 12:03am in the morning, the latest one,
last night, happened at 1:03am. The event logs showed no indication of
anything happening during those hours. The only thing i know for sure was
running is the sbs backup which kicks off at 9pm and is usually completed by
3am. The only 3rd party program running on the box is trend micro anti-virus
and IMFcompanion. Everything else is SBS provided, and installed using
defaults.

I ran the latest SBS Best Practices Analyzer and the only concern it had was
the sharepoint instance does not use SQL Server 2000 SP4, everything else
checked out fine. As far as i know SQL server is not even installed.



"Dave Nickason [SBS MVP]" wrote:

You can do a small memory dump instead of a kernel dump. If you someone
(like MS Support) tells you they need a full dump, you can always change the
setting back at that time.

If the overnight system crash results in a minidump, see this article for
the technique to get useful information from the dump file:

http://blogs.technet.com/petergal/archive/2006/03/23/422993.aspx

The other thing is, can you tell from the timing of the crashes what might
be going on when it happens? Backup, Exchange tasks, etc?

"Steve" <Steve@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:0B253D67-5F03-4BB8-97C2-8981E6172003@xxxxxxxxxxxxxxxx
> My SBS2003 STD continues to reboot nightly, this time with the > following.
> I
> found the exact error, requested and downloaded the hotfix, only to > find
> that
> i already had it applied. I read somewhere else to download and apply
> hotfix
> KB937455, which is a newer version of the previous KB. I was also told > to
> refer to KB307973 to check for proper settings in the kernal dump
> properties.
> I'm running sbs on a 32-bit box with 4gb of mem. In KB307973 it states
> that
> 'the maximum amount of space that must be available for a kernal memory
> dump
> on a 32-bit system is 2GB plus 16MB' Just below that is a table that > says
> the
> 'Paging file should be no smaller than 2GB plus 16mb'... which is true?
> The
> system allocated and recommended Paging File size is 6142MB or 6GB. > What
> are
> the correct settings?
>
> KB937455 also does not describe the error and stop codes i am
> experiencing,
> though it does address the random re-boot issues. Any Advice is
> Appreciated!
>
> Event Type: Error
> Event Source: System Error
> Event Category: (102)
> Event ID: 1003
> Date: 3/13/2008
> Time: 6:42:38 AM
> User: N/A
> Computer: PFLSERVER
> Description:
> Error code 1000007f, parameter1 00000008, parameter2 80042000, > parameter3
> 00000000, parameter4 00000000.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 53 79 73 74 65 6d 20 45 System E
> 0008: 72 72 6f 72 20 20 45 72 rror Er
> 0010: 72 6f 72 20 63 6f 64 65 ror code
> 0018: 20 31 30 30 30 30 30 37 1000007
> 0020: 66 20 20 50 61 72 61 6d f Param
> 0028: 65 74 65 72 73 20 30 30 eters 00
> 0030: 30 30 30 30 30 38 2c 20 000008,
> 0038: 38 30 30 34 32 30 30 30 80042000
> 0040: 2c 20 30 30 30 30 30 30 , 000000
> 0048: 30 30 2c 20 30 30 30 30 00, 0000
> 0050: 30 30 30 30 0000
>
>


.

Relevant Pages

  • Re: Question About Kernal Dumps, system crashing
    ... As the system reboots an event entry is made that the last shutdown was ... minidump settings, it'll be interesting to see if a dump file is created at ... I shall switch it over to mini dump and see what happens, ... if the sbs crashes again. ...
    (microsoft.public.windows.server.sbs)
  • Re: Question About Kernal Dumps, system crashing
    ... if the sbs crashes again. ... the sharepoint instance does not use SQL Server 2000 SP4, ... tells you they need a full dump, ... refer to KB307973 to check for proper settings in the kernal dump ...
    (microsoft.public.windows.server.sbs)
  • Re: Crash with recent kernel on wireless
    ... You should use the kernel image with the debugging symbols here. ... Dump Length: 190091264B ... pointer. ... Most of crashes even failed to save vmdump due to double faults. ...
    (freebsd-stable)
  • Re: Crash with recent kernel on wireless
    ... build and install a kernel, you get two kernel images on 7.x; ... Dump Length: 190091264B ... pointer. ... Most of crashes even failed to save vmdump due to double faults. ...
    (freebsd-stable)
  • Re: Crash with recent kernel on wireless
    ... You should use the kernel image with the debugging symbols here. ... Dump Length: 190091264B ... pointer. ... Most of crashes even failed to save vmdump due to double faults. ...
    (freebsd-stable)