Memory.DMP
Ok, there is a way to set the memory dump file to either 64kb, Kernel or to none instead of having the default setting (currently sucking up like 256MB of my HD. . . 1) How safe is it to change this option? 2) What is the best option to choose? 3) What will happen if I delete the file? (think I've done this before ...
Ok, there is a way to set the memory dump file to either 64kb, Kernel or to none instead of having the default setting (currently sucking up like 256MB of my HD...
1) How safe is it to change this option?
2) What is the best option to choose?
3) What will happen if I delete the file? (think I've done this before and nothing went bad then...)
4) What is the full file for? Can I browse the content in anyway, or is it just computer stuff that wont make any sense?
5) Is there a similarity/connection between this Mem dump and the Pagefile?
1) How safe is it to change this option?
2) What is the best option to choose?
3) What will happen if I delete the file? (think I've done this before and nothing went bad then...)
4) What is the full file for? Can I browse the content in anyway, or is it just computer stuff that wont make any sense?
5) Is there a similarity/connection between this Mem dump and the Pagefile?
Participate on our website and join the conversation
This topic is archived. New comments cannot be posted and votes cannot be cast.
Responses to this topic
1 - If you are running a simple home system or network, then I would suggest setting it to the kernel or 64K mark to preserve space. You are really going to be doing no good keeping it at 256MB, if you don't plan on sending that 256MB to Microsoft tech support for analysis upon having a crash. You will not hurt your system by changing this setting. All you are affecting is how much is RAM is being dumped to disk for analysis following a crash.
2 - Normal Home/Power User: kernel or 64k, Big Business Server operator: 256MB, extremely paranoid home user that likes to read hex: 256MB.
3 - Nothing. (Its the data that was in RAM at the time of the crash)
4 - The file is data that was in RAM at the time of the crash. Sure you can browse the content, most of it is not very exciting.
5 - Sort of. The page file is used for paging parts of RAM to disk. In reality..if you have a LOT of ram (1GB and above), you don't really NEED a page file...I'm sure there are some that will argue this..
Hope this helps.
-Ben
2 - Normal Home/Power User: kernel or 64k, Big Business Server operator: 256MB, extremely paranoid home user that likes to read hex: 256MB.
3 - Nothing. (Its the data that was in RAM at the time of the crash)
4 - The file is data that was in RAM at the time of the crash. Sure you can browse the content, most of it is not very exciting.
5 - Sort of. The page file is used for paging parts of RAM to disk. In reality..if you have a LOT of ram (1GB and above), you don't really NEED a page file...I'm sure there are some that will argue this..
Hope this helps.
-Ben
