Colif :
since you only have one minidump, try downloading this and running a scan:
http://www.resplendence.com/whocrashed
it might find the other and spell it out for us
It might show us the cause other than blaming ntoskrnl.exe which is unlikely to have done it without being pushed
Paste results here
I installed
Whocrash analysis :
System Information (local)
--------------------------------------------------------------------------------
Computer name: JESSILEN-PC
Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
Windows dir: C:\Windows
Hardware: 700G7C, SAMSUNG ELECTRONICS CO., LTD., SAMSUNG_NP1234567890
CPU: GenuineIntel Intel(R) Core(TM) i7-3610QM CPU @ 2.30GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 17149550592 bytes total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\minidump
Crash dumps are enabled on your computer.
On Wed 4/27/2016 3:09:38 AM GMT your computer crashed
crash dump file: C:\Windows\minidump\042716-41246-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC80)
Bugcheck code: 0xA (0x4418, 0x2, 0x0, 0xFFFFF800030D9F42)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Wed 4/27/2016 1:25:02 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFFA800CC8AA80)
Bugcheck code: 0xC2 (0x7, 0x109B, 0xC08000C, 0xFFFFFA800CC8AA80)
Error: BAD_POOL_CALLER
Bug check description: This indicates that the current thread is making a bad pool request.
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.
Google query: BAD_POOL_CALLER
Facebook
Twitter
Instagram