Colif :
i cant read dump files but this can:
http://www.resplendence.com/whocrashed its free for home users
Run a scan once its installed and paste the results in here, if you can't work it out yourself.
ntoskrnl.exe is part of windows, its unlikely to be the cause.
On Sun 13/03/2016 13:37:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031316-7046-01.dmp
This was probably caused by the following module: win32kfull.sys (win32kfull+0xDC9CC)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960060DC9CC, 0xFFFFD000229AF710, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 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 13/03/2016 13:37:33 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32kfull.sys (win32kfull!NtUserMessageCall+0x12AC)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960060DC9CC, 0xFFFFD000229AF710, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 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 13/03/2016 13:13:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031316-7453-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x19 (0xE, 0xFFFFC001486F4D90, 0xFFFFC001486B1590, 0x6A74640B62D4CB3C)
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.
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 13/03/2016 12:48:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031316-4437-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip! ?? ::FNODOBFM::`string'+0x2DF59)
Bugcheck code: 0x139 (0x3, 0xFFFFD00020DD3ED0, 0xFFFFD00020DD3E28, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
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 Sun 13/03/2016 12:48:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031316-8703-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x41792, 0xFFFFF680003B1688, 0x10, 0x0)
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 Sun 13/03/2016 11:01:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031316-7468-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0xEEA53)
Bugcheck code: 0xD1 (0xCD2, 0xB, 0x1, 0xFFFFF8014970D511)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 364.51
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 364.51
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 364.51 , NVIDIA Corporation).
Google query: NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Sun 13/03/2016 01:09:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031316-11406-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x41793, 0xFFFFF68176369608, 0x9, 0x8)
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 Sun 13/03/2016 00:16:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031316-35125-01.dmp
This was probably caused by the following module: ntfs.sys (NTFS!NtfsAcquireExclusiveFcb+0x78)
Bugcheck code: 0xA (0x40, 0xFF, 0x2F, 0xFFFFF800C4F48B82)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
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.
On Tue 08/03/2016 21:02:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030816-4750-01.dmp
This was probably caused by the following module: ci.dll (CI!I_MapAndSizeDataFile+0x160)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8018350285D, 0x0, 0x50)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 a kernel-mode program generated an exception which the error handler did not catch.
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 07/03/2016 20:15:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030716-4546-01.dmp
This was probably caused by the following module: win32kbase.sys (win32kbase+0x465CD)
Bugcheck code: 0x50 (0xFFFFD000232499C2, 0x0, 0xFFFFF960C85D65CD, 0x1)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\win32kbase.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Base Win32k Kernel 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.
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.
Facebook
Twitter
Instagram