2 reasons I can think of: . Issues with the disk that may have generated the stop error code may also prevent the system from being able to write to it
. Not having enough free space at the time the dump occurred. Are you doing minidumps or full dumps? If full, then you'd need as much space available as there is memory. HTH and good luck. From: Sam Cayze [mailto:[email protected]] Sent: Tuesday, April 07, 2009 5:20 PM To: NT System Admin Issues Subject: RE: Memory.dmp check. ________________________________ From: Rod Trent [mailto:[email protected]] Sent: Tuesday, April 07, 2009 4:14 PM To: NT System Admin Issues Subject: RE: Memory.dmp Did you check to make sure the .dmp filename hasn't change from the default? From: Sam Cayze [mailto:[email protected]] Sent: Tuesday, April 07, 2009 5:05 PM To: NT System Admin Issues Subject: Memory.dmp Any circumstances this file wouldn't be created on a stop error on Win2003? And I would assume the modification date/time would match the crash, right? I just got a crash and Memory.dmp's last mod. date = Jan 2006 :( -Sam ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
