molto semplice, lo installi clicki analizza e si guarda i file dump, se ce ne sono.
Ok ho fatto il test, il file dump trovato è Crash dump directory: C:\WINDOWS\Minidump.
Crash dumps are enabled on your computer.
poi i crash di questi giorni:
On Fri 19/06/2020 14:21:53 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\061920-19234-01.dmp
This was probably caused by the following module:
ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x61948, 0x402D7F66, 0x1, 0x402D7F66)
Error:
MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 19/06/2020 14:21:53 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module:
ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x61948, 0x402D7F66, 0x1, 0x402D7F66)
Error:
MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 18/06/2020 13:35:57 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\061820-21734-01.dmp
This was probably caused by the following module:
dxgkrnl.sys (dxgkrnl!DXGADAPTER::SetPowerComponentActiveCBWorker+0x45E)
Bugcheck code: 0xA (0xFFFFFFFFFFFFFFF8, 0x2, 0x0, 0xFFFFF8076CA68E8D)
Error:
IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\dxgkrnl.sys
product:
Microsoft® Windows® Operating System
company:
Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.