<div>
You do get a BSOD though?<br />
<br />
memory dumps are created as %SystemRoot%\MEMORY.DMP<br />
<br />
you could turn of automatic rebooting after a BSOD to see what (if any) goes wrong
</div>


You do get a BSOD though?

memory dumps are created as %SystemRoot%\MEMORY.DMP

you could turn of automatic rebooting after a BSOD to see what (if any) goes wrong

<div>
What im after is trying to figure out why im not getting memory dumps, id like the server to auto reboot and come back up so users can get back on etc.
</div>


What im after is trying to figure out why im not getting memory dumps, id like the server to auto reboot and come back up so users can get back on etc.

<div>
This wasnt a solution, it was a link to a page that I'd already seen
</div>


This wasnt a solution, it was a link to a page that I'd already seen

<div>
<div class="content wysiwyg-content">
No Memory.dmp file has been generated after a crash.<br />
<br />
The paging file is spread across C / D drives like so:<br />
<br />

<div class="bullet"></div>
C:\ 20gb, 10 gb free - Paging file is set a custom size of 400mb with a maximum size of 400mb<br />
<br />

<div class="bullet"></div>
D:\ 30gb, 26gb free - Paging file is set at a custom size of 2048mb and a maximum size of 8186mb<br />
<br />
Ive read that no memory dump will be generated if the paging file isn't on the primary drive. But im not too sure of the above scenario when its split across 2 drives. It was set to generate a kernel memeory dump but I have now changed that to a mini dump. Im thinking that a kernel memory dump may not have been generated because it is pointing to %SystemRoot%\Minidump and there is only 400mb given to the paging file on this drive. <br />
<br />
Please can someone explain exactly how this setup would work?<br />
<br />
<br />

</div>
</div>


No Memory.dmp file has been generated after a crash.

The paging file is spread across C / D drives like so:

C:\ 20gb, 10 gb free - Paging file is set a custom size of 400mb with a maximum size of 400mb

D:\ 30gb, 26gb free - Paging file is set at a custom size of 2048mb and a maximum size of 8186mb

Ive read that no memory dump will be generated if the paging file isn't on the primary drive. But im not too sure of the above scenario when its split across 2 drives. It was set to generate a kernel memeory dump but I have now changed that to a mini dump. Im thinking that a kernel memory dump may not have been generated because it is pointing to %SystemRoot%\Minidump and there is only 400mb given to the paging file on this drive. 

Please can someone explain exactly how this setup would work?




Memory Dump

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).

Windows Server 2003

The Microsoft Legacy Operating System topic includes legacy versions of Microsoft operating systems prior to Windows 2000: All versions of MS-DOS and other versions developed for specific manufacturers and Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions, and Windows Mobile.

Microsoft Legacy OS

This topic area includes legacy versions of Windows prior to Windows 2000: Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions including Windows Mobile.