Ciao, ecco qua, grazie
Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
Windows dir: C:\Windows
Hardware: P5K SE, , ASUSTeK Computer INC.
CPU: GenuineIntel Intel(R) Core(TM)2 Duo CPU E6550 @ 2.33GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 6441525248 bytes total
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sun 16/07/2017 15:23:07 your computer crashed
crash dump file: C:\Windows\Minidump\071617-17674-01.dmp
This was probably caused by the following module:
ntoskrnl.exe (nt+0x7CD40)
Bugcheck code: 0x19 (0x20, 0xFFFFF8A00FB18688, 0xFFFFF8A00FB18C18, 0x5594939)
Error:
BAD_POOL_HEADER
file path: C:\Windows\system32\ntoskrnl.exe
product:
Microsoft® Windows® Operating System
company:
Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 16/07/2017 15:23:07 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: 0x19 (0x20, 0xFFFFF8A00FB18688, 0xFFFFF8A00FB18C18, 0x5594939)
Error:
BAD_POOL_HEADER
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Conclusion
2 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
Read the topic
general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
