Post Reply

Prompt [Q] CrashDumpFile Avoid Replacement (READ TEXT TO AVOID MISUNDERSTANDINGS!!!!!]

OP Hannah Stern

3rd September 2014, 06:51 PM   |  #1  
OP Senior Member
Thanks Meter: 8
 
136 posts
Join Date:Joined: Aug 2014
You know, there is getting a „%SysRoot%\Memory.DMP" created, when your Computer Crashes and it does get REPLACED, OWERWRITTEN after a second crash.
You can rename the Dump File „MEMORY.DMP" (to whatever) to avoid this but,
you probably do know, that there's an option for „Not owerwrite already existing files" („bestehende dateien nicht überschreiben.")

BUT, THAT WILL CAUSE that after the first „Memory.Dmp" there will not be created a „Memory2.Dmp" or a „MEMORY.Dmp2" but just nothing.
I do prefer, that every crash will create a new dump file without any deleting, owerwriting, replacing or discarding: just without any loss of information.
First Crash: „MEMORY.DMP"
Second Crash: „MEMORY (2).Dmp" or Memory2.dmp or memory.dm2 or Memory.002 or Memory.Dmp2 or 02.Memory.Dmp or Mem·0002 or Memory~2.Dmp or whatever, an alternative filename without a replacement of the original file.

Another Possibility: Mem2010112512582436 or Memory20130626203154 or Memory20090424[TIME·Whatever]GMT+1
[My Favourite way to store time&date: the „YYYYMMDDHHMMSS"-TimeStamp]

Is that or something like that actually possible?
Post Reply Subscribe to Thread

Tags
bsod, crash, dmp, dump, memory
Previous Thread Next Thread
Thread Tools
Display Modes