Blue Screen- Windows 10 - Bad_ Pool_ Caller

carlitoswayec

Distinguished
Sep 24, 2013
28
0
18,530


I only have the home version and this is what I can see from that minidump:

On Thu 3/31/2016 14:58:25 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\033116-24546-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F4D0)
Bugcheck code: 0xC2 (0x7, 0x1254, 0x0, 0xFFFFE001A0DC87D8)
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.

Before this dump, I have records of 6 more crashes that date back up to the end of December last year. All point to the same module. After my post, I have had 3 more crashes but they point to two other modules: tcpip.sys and mwac.sys (Malwarebytes).

Not sure if these last 3 are related to all others.


Thank you!