Windows Forum

Ask something
Discussion Locked

Physical memory dump on Memory upgrade

0 helpful
13 replies

by cg it

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

M/B MSI K7T Ultra ARU original memory 512 PC 2100 DDR. O/S Windows 2000 SBS. HD Quantum Fireball AS 20BG [O/S partition 6.0 GB].
Question: Upgraded amount of memory from 512MB to 768MB using Kingston value ram. After installation of dimm and startup, Windows began a physical memory dump to disk. This dump creates low HD freespace for virtual memory resulting in pagefile resize.

Question: How to get windows to recognize and use the additional 256MB above 512MB.

13 replies

by cg it

Further details. The original memory was two each 256 MB PC2100 Kingston value ram in slots 1 & 2. []banks 0,1,2,3,] The motherboard will accept up to 3 GB (3 each 1 GB Dimms). What's in there now is 3 each 256 MB dimms. All identical. I can take out the additional 256 MB and everything reverts back to normal [except my available physical memory is 100MB (low)].

by maxwell edison

I've noticed in the past that if your memory is mis-matched you may have problems. I suspect this may be the case with your upgrade.

I've always had better luck using identical memory sticks.

by maxwell edison

I just noticed your additional comment about the (3) 256MB DIMMS being identical.

Two things:

Are you sure they are absolutely identical? I always use the wallpaper analogy: The pattern number may be the same, but if the lot number is different then there are probably discrete differences in pattern and/or color. In the case of memory, the specifications may be the same, but the chips on the DIMMS may be from a different "lot".

Another thing to try is this: Try just the two original slots, but replace only one of the DIMMS with your new DIMM. Do you still have the same thing happen? If yes, I would indeed suspect mis-matched memory, or perhaps you've got a bad stick.

by maxwell edison

I just noticed your additional comment about the (3) 256MB DIMMS being identical.

Two things:

Are you sure they are absolutely identical? I always use the wallpaper analogy: The pattern number may be the same, but if the lot number is different then there are probably discrete differences in pattern and/or color. In the case of memory, the specifications may be the same, but the chips on the DIMMS may be from a different "lot".

Another thing to try is this: Try just the two original slots, but replace only one of the DIMMS with your new DIMM. Do you still have the same thing happen? If yes, I would indeed suspect mis-matched memory, or perhaps you've got a bad stick.

by cg it

I've done what you suggested and again, no problems as long as the total physcial memory is 512 MB. I've run the server with just the new memory, then with one old module and the new one, rotated them through the slots and still no problems. I've also taken the new one and put them into another computer. Again, no problems as long as the total physical memory stays at 512 or below. Above 512 is where the memory dump starts. It isn't the module it's self[see above]. This acts like Windows ME and98 where above 512 MB the O/S can't operate yet I'm running Windows 2000 SBS and on the workstation I tested the module Windows 2000.

by maxwell edison

Look at Microsoft Knowledge Base Article - Q226448, “Event ID 49 Is Logged After Adding Random Access Memory”.

A Memory.dmp file is created when a kernel mode STOP error occurs on a computer that has the "crash dump" feature enabled. If the page file is unable to accommodate a Memory.dmp file, debugging the problem is not possible. The page file is configured for crash dump when your computer starts, and the behavior described earlier in this article is logged when the physical memory on the computer is greater than the size of the Pagefile.sys file.

SYMPTOMS:
When you add random access memory (RAM) to a computer that is configured to create a crash dump (Memory.dmp) file, the size of the Pagefile.sys file does not automatically increase to accommodate the Memory.dmp file. Also, you may receive the following error message in the System Log: (see the article)

CAUSE:
This behavior occurs to give administrators the flexibility to increase the size of the page fileat their discretion.

STATUS:
This behavior is by design.

RESOLUTION:
To work around this behavior, use the appropriate method:

A. Increase the Size of the Pagefile.sys File:

1. Right-click My Computer, and then click Properties.2. Click the Advanced tab, and then click Performance Options.

3. Under Virtual Memory, click Change.

4. Set the initial size of the page file that exists on the same partition as the operating system to be one and a half times the size of the amount of RAM installed in the computer.

-or-

(continued...)

by maxwell edison

B. If you no longer want to save the Memory.dmp file:

1. Right-click My Computer, and then click Properties.

2. Click the Advanced tab, and then click Startup and Recovery.

3. Select none in the Write debugging information to option, and then click OK.

4. Restart your computer.

Link to article:

http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q226448&

More related articles:

http://www.labmice.net/hardware/memory.htm

http://www.labmice.net/troubleshooting/memorydumps.htm

(LabMice is a great informational site.)

REMOVE SPACES from the pasted URL.

by maxwell edison

The comment you made on the 11th would indicate that the cause of your problem is indeed outlined in the Microsoft article listed above. I would surmise that when Windows is initially installed, and the amount of memory is detected, then Windows will set the size of the page files accordingly. If this is the case, then it stands to reason that a fresh install of Windows would indeed recognize the additional memory. But I would also assume that you could, according to this article, make the adjustments after the fact.

by cg it

I'm keeping this question open for right now as I'm doing some tests on a test network. What I've done so far is to load up an identical server with 768 MB of DDR memory using three each 256 MB modules, all from Crucial. I've then made a clean install of Windows 2000 Advanced Server. So far no problems with a memory dump during installation or during network testing with 4 workstations. What appears to have happened is that Windows didn't like changing the memory on it, (from initiall 512MB up to 768MB). If I have inital 768 MB THEN install Windows Server, no problems arise.

This discussion is closed to new replies.