Windows version: Windows 10 , 10.0, build: 10240
Windows dir: C:\WINDOWS
Hardware: 20C5A0L8ID, LENOVO
CPU: GenuineIntel Intel(R) Core(TM) i5-4210M CPU @ 2.60GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 3995566080 bytes total




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Thu 10/1/2015 5:00:34 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\100115-34937-01.dmp
This was probably caused by the following module: hal.dll (hal+0xB01)
Bugcheck code: 0xC2 (0x7, 0x1254, 0x4160076, 0xFFFFE00096AA9D00)
Error: BAD_POOL_CALLER
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
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 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 Thu 10/1/2015 5:00:34 AM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x6BBCD)
Bugcheck code: 0xC2 (0x7, 0x1254, 0x4160076, 0xFFFFE00096AA9D00)
Error: BAD_POOL_CALLER
file path: C:\WINDOWS\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
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 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 Thu 10/1/2015 4:28:05 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\100115-38281-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14CC20)
Bugcheck code: 0xC2 (0x7, 0x1254, 0x160000, 0xFFFFE000CF646010)
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.