@Federico83 ecco qua:
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 26/06/2017 11:10:23 your computer crashed
crash dump file: C:\Windows\Minidump\062617-3953-02.dmp
This was probably caused by the following module:
ntoskrnl.exe (nt+0x1509A0)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF80334CBEF37, 0xFFFFD00027BEC2B0, 0x0)
Error:
SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 26/06/2017 11:10:23 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module:
aswmonflt.sys (aswMonFlt+0x51BB)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF80334CBEF37, 0xFFFFD00027BEC2B0, 0x0)
Error:
SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\aswmonflt.sys
product:
Avast Antivirus
company:
AVAST Software
description: Avast File System Minifilter for Windows 2003/Vista
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: aswmonflt.sys (Avast File System Minifilter for Windows 2003/Vista, AVAST Software).
Google query:
AVAST Software SYSTEM_SERVICE_EXCEPTION
On Mon 26/06/2017 10:48:50 your computer crashed
crash dump file: C:\Windows\Minidump\062617-3953-01.dmp
This was probably caused by the following module:
nvlddmkm.sys (nvlddmkm+0x9BE89C)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8002109D89C, 0xFFFFD000230F61D0, 0x0)
Error:
SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product:
NVIDIA Windows Kernel Mode Driver, Version 382.53
company:
NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 382.53
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 382.53 , NVIDIA Corporation).
Google query:
NVIDIA Corporation SYSTEM_SERVICE_EXCEPTION
On Sun 25/06/2017 22:03:29 your computer crashed
crash dump file: C:\Windows\Minidump\062617-3968-01.dmp
This was probably caused by the following module:
aswbidsdrivera.sys (aswbidsdrivera+0x3B1B0)
Bugcheck code: 0xBE (0xFFFFF800CCE711B0, 0x80000004610DC021, 0xFFFFD00021761D80, 0xB)
Error:
ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\drivers\aswbidsdrivera.sys
product:
Avast
company:
AVAST Software s.r.o.
description: IDS Application Activity Monitor Driver.
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: aswbidsdrivera.sys (IDS Application Activity Monitor Driver., AVAST Software s.r.o.).
Google query:
AVAST Software s.r.o. ATTEMPTED_WRITE_TO_READONLY_MEMORY
On Sun 25/06/2017 21:37:43 your computer crashed
crash dump file: C:\Windows\Minidump\062517-3906-01.dmp
This was probably caused by the following module:
ntoskrnl.exe (nt+0x1509A0)
Bugcheck code: 0x1A (0x41287, 0x2B, 0x0, 0x0)
Error:
MEMORY_MANAGEMENT
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 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. 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
29 crash dumps have been found and analyzed. Only 5 are included in this report. 3 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 382.53 , NVIDIA Corporation)
aswbidsdrivera.sys (IDS Application Activity Monitor Driver., AVAST Software s.r.o.)
aswmonflt.sys (Avast File System Minifilter for Windows 2003/Vista, AVAST Software)
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.
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.