Windows Forum

Ask something
Discussion Locked

Dumping Physical Memory

0 helpful
3 replies

by pferme

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have a small network that was running WinNT server and Win95 on the client machines. The client pc's were upgraded to Win2000 Pro and the server was upgraded to Win2000 server. This was an upgrade not a fresh install. Now about once a week, the server will go into a blue screen and show the message "Dumping Physical Memory" count to ten then restart itself. The server hardware is new, and all software used is Win2000 compatible. They mostly use OfficeXP. The only other application constantly running is McAffee virus scanner, but it was designed for NT and 2000 server. The memory dump file was 511Meg. Bit hard to open. So I set the machine to give me smaller memory dump files. Do you know what makes 2000 perform this memory dump and can Isend the dmp file to Microsoft to analyse?

3 replies

by timthetoolman

Hi,

A memory dump is caused by an exception in priviliged code (such as device drivers or NT's kernel)

I believe you can send dumps to Microsoft but I suspect they would charge you for it and take months too. Maybe I'm being hard on them there, I've never sent a dump off myself...

Normally its possible to solve these problems without resorting to sending off the dump.

Are there any messages in the event log that can help you diagnose which application is causing the problem?

Haveyou looked at the BSOD to see what caused it? You may need to set the machine up to not auto reboot on failure to catch this.

It might help to set up performance monitoring to a log so you can analyse the system just before it crashes. For example, perhaps there's a memory leak somewhere - you'll see that in pagefile usage continually increasing over the week.

Hope this helps,
Cheers,
Tim.

This discussion is closed to new replies.