Hier is de Whocrashed log file
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Fri 5-10-2018 10:36:47 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\100518-11609-01.dmp
This was probably caused by the following module:
ntoskrnl.exe (nt+0x1A9490)
Bugcheck code: 0xC2 (0x7, 0x63526442, 0x4110003, 0xFFFF8086792D52E0)
Error:
BAD_POOL_CALLER
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 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 5-10-2018 09:42:55 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\100518-11703-01.dmp
This was probably caused by the following module:
ntoskrnl.exe (nt+0x1A9490)
Bugcheck code: 0xC2 (0x7, 0x63526442, 0x411000E, 0xFFFFB208B78A5F00)
Error:
BAD_POOL_CALLER
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 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 5-10-2018 09:40:07 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\100518-11859-01.dmp
This was probably caused by the following module:
ntoskrnl.exe (nt+0x1A9490)
Bugcheck code: 0xC2 (0x7, 0x63526442, 0x411000C, 0xFFFFA70F6332D730)
Error:
BAD_POOL_CALLER
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 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 5-10-2018 09:37:16 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\100518-11921-01.dmp
This was probably caused by the following module:
ntoskrnl.exe (nt+0x1A9490)
Bugcheck code: 0xC2 (0x7, 0x63526442, 0x4110004, 0xFFFFDF0B01161890)
Error:
BAD_POOL_CALLER
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 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 5-10-2018 08:26:11 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\100518-11953-01.dmp
This was probably caused by the following module:
ntoskrnl.exe (nt+0x1A9490)
Bugcheck code: 0xC2 (0x7, 0x63526442, 0x4110001, 0xFFFF9789347F3680)
Error:
BAD_POOL_CALLER
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 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Conclusion
9 crash dumps have been found and analyzed. Only 5 are included in this report. 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.
