Windows 10: My C Drive Boot, Page File, Crash Dump

,How to fix my C drive turn into Simple volume than Primary volume

:)

 

windows 10 OS crash dump drive location

Is there a way to move crash dump location in the same manner paging file can be moved.

ok I need to expand the question:

move location crash dump is generated from not merely the final save destination.

I have moved page file from C drive to D drive

aka the page file is now on disk other than boot volume. boot volume page file is disabled.

I want the SMSS.exe to look for page file on disk other than boot volume.

according to: Understanding Crash Dump Files - Microsoft Community Hub

"Returning to the subject of how the dump file itself is generated, If a dump is configured, the system makes a copy of the disk miniport driver used to write to the boot volume in memory and prepends the driver name with "dump_". The system also checksums all of the components involved with writing a crash dump, (including the copied disk miniport driver), the I/O manager functions that write the dump and the map of where the boot volume's page file is on the disk. This checksum is saved. When the KeBugCheck function executes it checksums these components again and compares this checksum to the one created at boot. If these checksums do not match, no dump file is written (because of the risk of corrupting the disk). If the checksum matches, the dump information is written directly to the sectors on disk occupied by the page file. The file system driver is completely bypassed - because it may be corrupted or be the cause of the crash. When SMSS.EXE enables paging during the boot process, the system examines the boot volume's page file to see if there is a crash dump present. If one exists, then this part of the page file is protected. This makes all (or part) of the boot volume's page file unusable during the early part of the boot process. This may result in notifications that the system is low on virtual memory - a temporary condition. Later in the boot process, WINLOGON.EXE calls the SAVEDUMP.EXE process to extract the dump from the page file and copy it to the final location that is specified in the Dump File field."

According to this crash dump can only be enabled if paging file on boot disk is enabled.

The dump file field in "startup and recovery" of "system properties" does not change the source of crash dump location merely the copy of it.













I does not seem to matter how big page file on D: is so long as page file on C: is disabled crush dump cannot be enabled.

HKLM\System\CurrentControlSet\Control\CrashControl registry key. is also set to drive D: and windows still expects page file at C to enable crash dump

:-(

 

How to give new hard drive "boot, page file, crash dump" status

I bought a new 2tb hybrid hard drive and cloned my old 1tb hard drive onto it so that they both contained a copy of my windows 10 OS and all my files. Then I switched their SATA ports so that my new drive was in the first slot, and made sure the boot order in BIOS booted from the new drive first.

Everything works fine, but the only thing that bothers me is that when I go to disk management, the main partition of my old drive says "boot, page file, crash dump, primary partition" whereas my new drive's main partition only says "primary partition". And besides that, the sidebar in file explorer shows the windows logo over the icon of the hard drive for my old drive, but not my new one. (See the second screenshot for this behavior if you don't know what I mean)

Here are screenshots:

1. http://archive.is/EcuHC
   
2. http://tinypic.com/r/vcrwqs/9
   

What do these things mean? Is it anything to worry about? How can I remedy it? Would it help if I changed the drive letters? (Currently the old drive is still C and the new one is G. I'm just reluctant to change them and break a bunch of links)

 

Page File

Set minimum and maximum to a constant number as suggested by others, that will help reduce fragmentation on the drive coz of different page file sizing.