visualizzatore eventi: Save dump cos'è??

[picagetto]

ho dei riavvi improvvisi...
quando rientro in windows mi da la finestra

"windows è stato riavviato in seguito ad un errore grave"

vado a vedere nel visualizzatore eventi e c'è save dump clikkandoci mi dà questa scritta

Il computer è stato riavviato da un controllo errori. Il controllo errori era: 0x0000007a (0x00000003, 0xc0000005, 0x20d19be8, 0x00000000). È stata salvata un'immagine della memoria in: C:\WINDOWS\Minidump\Mini011804-01.dmp.

che significa??

[picagetto]

raga aiuto.......

[Redvex]

Che ti ha registrato a cosa è dovuto il problema ma è scritto in modo non comprensibile a noi comuni mortali :rolleyes:

[picagetto]

nessuno sa che tipo di errore sia???:muro:

[WhiteBase]

Common Causes of STOP Messages 0x00000077 and 0x0000007A
Si applica a

This article was previously published under Q130801
SUMMARY

STOP Messages 0x00000077 and 0x0000007A are related kernel traps that are caused when the operating system tries to load a page into memory from the paging file on the hard disk, but cannot access the page because of either a software or hardware failure.

If you experience this issue more than one time, contact your computer or hard disk vendor.
MORE INFORMATION
The following are all common causes of STOP Messages 0x00000077 and 0x0000007A:

The paging file contained a bad block.

If the page file is on a SCSI device, the trap could have been caused by improper termination.

Bad cabling from hard disk to controller.

An error on the disk controller.

Running out of non-paged pool resources on the server.

Frequently, the cause of these traps can be determined from the second of the 4 hexadecimal parameters included in the first line of the STOP Message. Value Meaning
---------- -------
0xC0000008 STATUS_INVALID_HANDLE , an invalid HANDLE was specified.

0xC000009A STATUS_INSUFFICIENT_RESOURCES, caused by lack of non-paged
pool.

0xC000009C STATUS_DEVICE_DATA_ERROR, generally due to bad block on the
drive.

0xC000009D STATUS_DEVICE_NOT_CONNECTED, bad or loose cabling,
termination, or controller not seeing drive.

0xC000016A STATUS_DISK_OPERATION_FAILED, also caused by bad block
on the drive.

0xC0000185 STATUS_IO_DEVICE_ERROR, caused by improper termination or bad
cabling on SCSI devices.

These codes are the most common and the ones for which specific causes have been determined. For information about other possible status codes that may be returned, see the NTSTATUS.H file, which is included in the MSDN Development Platform DDK.


Purtroppo non essendo ricompreso tra questi per sapere esattamente cosa ha generato l'errora dovrai trovare qualcuno che disponga dell'msdn ddk e possa spulciarla