memory dump

I got a purple screen for dumping of physical memory . how can i prevent this from happening again, I could not get the error number in time because computer had restarted.

 

Which version of Windows are you running (Vista, Win7 sp1, etc)?
Do you mean BLUE screen?
Which program were you using to dump memory?

You can use BlueScreenView to retrieve the error number of the BSOD which you should include in your next post.

 

Along with what rustysavage said, there are ways to prevent the computer from automatically restarting after a blue screen but, they differ from XP to Vista/7/8. You can also specify which kind of dump you want (Small(64K), Kernel, etc.). The minidump file is located in the C:\WINDOWS\minidump folder. Attach the file as a ZIP archive to your next post.

 

how do i attach the file as a zip file i'm in the minidump folder

 

minidump file

 

Probably a bad hard drive, specifically, bad sectors within the paging file looking most likely.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_STACK_INPAGE_ERROR (77)
The requested page of kernel data could not be read in.  Caused by
bad block in paging file or disk controller error.
In the case when the first arguments is 0 or 1, the stack signature
in the kernel stack was not found.  Again, bad hardware.
An I/O status of c000009c (STATUS_DEVICE_DATA_ERROR) or
C000016AL (STATUS_DISK_OPERATION_FAILED)  normally indicates
the data could not be read from the disk due to a bad
block.  Upon reboot autocheck will run and attempt to map out the bad
sector.  If the status is C0000185 (STATUS_IO_DEVICE_ERROR) and the paging
file is on a SCSI disk device, then the cabling and termination should be
checked.  See the knowledge base article on SCSI termination.
Arguments:
Arg1: c000000e, status code
Arg2: c000000e, i/o status code
Arg3: 00000000, page file number
Arg4: 00662000, offset into page file

Debugging Details:
------------------


[b]ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.

DISK_HARDWARE_ERROR: There was error with disk hardware[/b]

BUGCHECK_STR:  0x77_ffffffffc000000e

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

PROCESS_NAME:  System

LAST_CONTROL_TRANSFER:  from 80520df2 to 8053385e

STACK_TEXT:  
f7b4ecf0 80520df2 00000077 c000000e c000000e nt!KeBugCheckEx+0x1b
f7b4ed60 804e801e c03b4da4 c03b4da4 00000001 nt!MiMakeOutswappedPageResident+0x362
f7b4ed8c 804e6bfd 001ab3d0 00000000 873bf8a0 nt!MmInPageKernelStack+0xf0
f7b4eda4 804e6be0 871ab430 80579575 00000000 nt!KiInSwapKernelStacks+0x16
f7b4edac 80579575 00000000 00000000 00000000 nt!KeSwapProcessOrStack+0x89
f7b4eddc 804fa857 804e6b5c 00000000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND:  kb

[b]FOLLOWUP_IP: 
nt!MiMakeOutswappedPageResident[/b]+362
80520df2 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiMakeOutswappedPageResident+362

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  51d4e4f2

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  0x77_ffffffffc000000e_nt!MiMakeOutswappedPageResident+362

BUCKET_ID:  0x77_ffffffffc000000e_nt!MiMakeOutswappedPageResident+362

Followup: MachineOwner
---------

 

I noticed it will do that when my my hard drive space is really low, could that be it

 

It will do what when your disk space is low?

 

memory dump