Re: Server rebooting - MiniDump queries - New memory

Well I didn't bill for 12 hours. I installed their old memory at my
problem account in a test machine and watched tv, went to bed, did
other things when testing. If memory may be bad there is only one way
to resolve the question. Test it when the server is off line. No ifs,
ands or buts. Well just have them buy 2 new stick. If you are not
running a server the memory is just regular old cheap ram at $120 a
stick. or it might be memory that cost $200 a stick.

If you want to test on the cheap remove one stick and see how it runs.
If it runs poorly install the other stick and run with just that
stick. Of course if your server requires 2 sticks to run then you are
back to testing off line or buying new memory. Aslo note that bad
wiring in the motherboard could cause problems. Rare but this can be
checked with off line memory checking.

On Tue, 20 Feb 2007 11:11:49 -0000, "Blue Wezza"
<blue-wezza@xxxxxxxxxxxxxxxx> wrote:

Hi,

Unfortunately i administer the server remotely. Hence under the terms of my
contract the server owner could not afford for me to spend twelve hours on
site testing both memory sticks - I was wondering if there is a way to test
inside 2003 SBS at all?

Thanks

Wesley

"Jim Behning SBS MVP" <jimbehning@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:63djt2tjknmrf17huo7mqfm1bo8nc9g0tr@xxxxxxxxxx
Run a memory checker on the server. I use goldmemory but there are
other products my friends use. You run this from a bootable floppy.
The server is off line while checking memory. Last time I had this
problem was when I installed 4 new sticks of memory in the server.
Server ran fine for 2 months. I removed the new memory, installed the
old memory. I tested the memory one stick at a time for 6 hours each
stick until I found the problem stick. Every stick passed with the
first pass. The problem module did not show up until it had been run
for hours. You are also in luck if your server has memory that you can
check in a workstation. Some memory will not run in workstation
motherboards which may not be designed for ECC ram.

On Mon, 19 Feb 2007 09:42:39 -0000, "Blue Wezza"
<blue-wezza@xxxxxxxxxxxxxxxx> wrote:

Hi,

Hi,

I have had a 2003 sbs server which has degenerated in stability over a
period. I added an adaptec 2420sa raid adapter and put 3 x 250Gb wd caviar
raid drives in, RAID5, then installed the operating system again - all
user
settings added afterwards (no disaster recovery) - only old work and data
added.

Approx 3 times per day the server reboots, leaving a mini dump behind. I
interpreted these minidump which all led to memory corruption, so i have
just swapped out the 2x1Gb RAM. However the server has just rebooted
again,
here is the minidump:


Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Mini021907-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is:
C:\Symbols;C:\symcache;srv*c:\symcache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2003 Kernel Version 3790 (Service Pack 1) MP (2 procs) Free
x86 compatible
Product: LanManNt, suite: SmallBusiness TerminalServer
SmallBusinessRestricted SingleUserTS
Built by: 3790.srv03_sp1_rtm.050324-1447
Kernel base = 0x80800000 PsLoadedModuleList = 0x808a6ea8
Debug session time: Mon Feb 19 09:21:07.610 2007 (GMT+0)
System Uptime: 1 days 0:57:53.453
Loading Kernel Symbols
..............................................................................................................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {3452, fc0201, c0884f68, 80}

Probably caused by : memory_corruption (
nt!MiDeleteAddressesInWorkingSet+155 )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00003452, The subtype of the bugcheck.
Arg2: 00fc0201
Arg3: c0884f68
Arg4: 00000080

Debugging Details:
------------------


BUGCHECK_STR: 0x1a_3452

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP

PROCESS_NAME: spoolsv.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 8084c103 to 80827451

STACK_TEXT:
ba516a8c 8084c103 0000001a 00003452 00fc0201 nt!KeBugCheckEx+0x1b
ba516c48 8084c24d 88f8d7d8 88f8d7d8 00000000
nt!MiDeleteAddressesInWorkingSet+0x155
ba516c68 8094b539 88f8da00 885206f0 00000080
nt!MmCleanProcessAddressSpace+0x111
ba516cf0 8094b5b7 00000080 ba516d4c 8082d8b8 nt!PspExitThread+0x5f1
ba516cfc 8082d8b8 885206f0 ba516d48 ba516d3c nt!PsExitSpecialApc+0x1d
ba516d4c 80888cd4 00000001 00000000 ba516d64 nt!KiDeliverApc+0x1ae
ba516d4c 7c82ed54 00000001 00000000 ba516d64 nt!KiServiceExit+0x56
WARNING: Frame IP not in any known module. Following frames may be wrong.
0087ffb8 00000000 00000000 00000000 00000000 0x7c82ed54


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiDeleteAddressesInWorkingSet+155
8084c103 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!MiDeleteAddressesInWorkingSet+155

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 42435b14

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0x1a_3452_nt!MiDeleteAddressesInWorkingSet+155

BUCKET_ID: 0x1a_3452_nt!MiDeleteAddressesInWorkingSet+155

Followup: MachineOwner
---------

Does anyone have ideas that they can throw to me - im sinking!

Thanks

Wes



.

Relevant Pages

  • Re: Terminal Server 2000 pausing
    ... Is the server itself pausing or is it actually the network side of things? ... Have you run perfmon gathering everything over a period and then analysing ... This should also tell you if memory is ... > You caould also suspect improperly installed Office 2000 install or faulty ...
    (microsoft.public.windows.terminal_services)
  • Re: how to correct http 502 Proxy Error "no buffer space is supported", "64-Host not availabe",
    ... It looks like some kind of memory leak issue to me. ... You should install the ... ISA Server already ... > and all clients can connect internet Well. ...
    (microsoft.public.isa)
  • Re: 2003 R2 SETUP2.EXE generates "Program too big to fit in memory
    ... It is from CD2 of the Select Media for Windows ... The install of Windows was a clean install on one server and an upgrade on ... Normally when I see "Program too big to fit in memory" this is a corrupted ...
    (microsoft.public.windows.server.setup)
  • RE: server problems
    ... This newsgroup only focuses on SBS technical issues. ... >Thread-Topic: server problems ... >> web proxy service or SQL Server will normally use large memory. ...
    (microsoft.public.windows.server.sbs)
  • Re: The Blue Screen of Death
    ... Win 2000 server the computer stops with the old Blue Screen ... but today I was trying to install SP4 and the same thing happened. ... Both of these actions use a lot of memory. ... the server in a Domain what happens to all the workstations? ...
    (microsoft.public.win2000.general)