Re: Question About Kernal Dumps, system crashing

That stop code looks to be in the 0x7F arena (hardware)...

http://support.microsoft.com/?kbid=137539

Run diagnostic software and test the RAM in the computer. Replace any RAM
reported as bad. Also, make sure all the RAM in the computer is the same
speed. This is MS's tester:

http://oca.microsoft.com/en/windiag.asp

or you can use memtest86:

http://www.memtest86.com/


--
Allan Williams



"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: Why is VS.Net 2005 so SLOW?
    ... It takes just more than 2 minutes to load the combos. ... " I'm hoping their hotfixes are fixed before they make it into SP1." ... I hear there's a hotfix for that. ... I think M$ tried to scale in such a way that low end RAM systems would work ...
    (microsoft.public.vstudio.development)
  • Re: Windows Explorer errors caused by NTDLL.DLL
    ... It talks about getting a hotfix, ... Unless you come up with the exact text of a Stop Error, ... definitely test the RAM, though. ... that you wait for the next Windows XP service pack that contains this ...
    (microsoft.public.windowsxp.general)
  • Re: Why is VS.Net 2005 so SLOW?
    ... every hotfix I've added has fixed one ... You'll probably have to wait for the SP1 ... Transition from web page design view to source view is hideously slow ... I think M$ tried to scale in such a way that low end RAM systems would work ...
    (microsoft.public.vstudio.development)
  • Re: Event ID 9582
    ... There's no issue with applying the hotfix, ... Exchange service pack like SP2), ... Last week I have installed 4GB of RAM on my Exchange server. ... Memory is fragmented in such a way that normal operations can fail. ...
    (microsoft.public.exchange.admin)
  • Re: Server Reboots everday at 1AM
    ... against that in the KB to see if you need the hotfix. ... >>every day - with a pure ram issue, ... >> will have a hardware diagnostic available as a free download. ... >>> this memory test and it is still crashing every night at just before 1AM ...
    (microsoft.public.windows.server.sbs)
Loading