On Sun 28-2-2016 07:54:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022816-5984-01.dmp
This was probably caused by the following module: win32kfull.sys (win32kfull!vUnmapFileFD+0x2F)
Bugcheck code: 0x1A (0x41793, 0xFFFFF68144D7DB68, 0x16E, 0x16D)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\win32kfull.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Full/Desktop Win32k Kernel Driver
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 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.
On Sun 28-2-2016 07:54:06 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32kfull.sys (win32kfull!vUnmapFileFD+0x2F)
Bugcheck code: 0x1A (0x41793, 0xFFFFF68144D7DB68, 0x16E, 0x16D)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\win32kfull.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Full/Desktop Win32k Kernel Driver
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 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.
On Sat 27-2-2016 08:13:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022716-3750-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x41201, 0xFFFFF6BFFE0CE3B8, 0x95A0000102DEB025, 0xFFFFE0005DB3D130)
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 25-2-2016 08:28:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022516-6031-01.dmp
This was probably caused by the following module: win32kfull.sys (win32kfull!ComputeFileviewCheckSum+0x21)
Bugcheck code: 0x1A (0x5003, 0xFFFFF58010804000, 0x1570, 0x15660002AD0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\win32kfull.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Full/Desktop Win32k Kernel Driver
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 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.
On Wed 24-2-2016 09:59:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022416-3046-01.dmp
This was probably caused by the following module: win32kbase.sys (win32kbase!EngIsSemaphoreOwnedByCurrentThread+0xA)
Bugcheck code: 0x50 (0xFFFFE000633B4FAA, 0x0, 0xFFFFF803EBB3D7F0, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\win32kbase.sys
product: Microsoft® Windows®-besturingssysteem
company: Microsoft Corporation
description: Base Win32k Kernel-stuurprogramma
Bug check description: This indicates that invalid system memory has been referenced.
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.
On Tue 23-2-2016 06:47:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022316-3640-01.dmp
This was probably caused by the following module: aswsnx.sys (aswSnx+0x28FB1)
Bugcheck code: 0x50 (0xFFFFC00155A2C5B8, 0x0, 0xFFFFF80357291793, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\aswsnx.sys
product: Avast Antivirus
company: AVAST Software
description: avast! Virtualization Driver
Bug check description: This indicates that invalid system memory has been referenced.
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: aswsnx.sys (avast! Virtualization Driver, AVAST Software).
Google query: AVAST Software PAGE_FAULT_IN_NONPAGED_AREA
On Mon 22-2-2016 16:03:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022216-3812-01.dmp
This was probably caused by the following module: ci.dll (CI!memcmp+0x53)
Bugcheck code: 0x50 (0xFFFFC00101043EB0, 0x0, 0xFFFFF801170FD493, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ci.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Code Integrity Module
Bug check description: This indicates that invalid system memory has been referenced.
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.
On Mon 22-2-2016 08:36:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022216-3593-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x5003, 0xFFFFF58010804000, 0x32B, 0x7FFCEBB19009)
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 Sat 20-2-2016 07:24:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022016-3609-01.dmp
This was probably caused by the following module: ntfs.sys (NTFS! ?? ::NNGAKEGL::`string'+0x172D0)
Bugcheck code: 0x139 (0x3, 0xFFFFD00073787500, 0xFFFFD00073787458, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows®-besturingssysteem
company: Microsoft Corporation
description: NT-bestandssysteemstuurprogramma
Bug check description: The kernel has detected the corruption of a critical data structure.
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.
On Fri 19-2-2016 09:47:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021916-3781-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xEF (0xFFFFE0005DDAC840, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
Bug check description: This indicates that a critical system process died.
There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Conclusion
--------------------------------------------------------------------------------
38 crash dumps have been found and analyzed. Only 10 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:
aswsp.sys (avast! self protection module, AVAST Software)
ffusb2audio.sys (Focusrite USB 2.0 Audio Driver, Focusrite Audio Engineering Limited.)
aswsnx.sys (avast! Virtualization Driver, AVAST Software)