Bad pool header bsod when playing rainbow six siege

[veredaux]

Everytime i play rainbow six siege in a couple of minutes my comp would just have a bsod , sometimes it says bad pool header and sometimes it says system thread no exception , please help
-OS=Windows 10
-Cpu=x4 860k
VGA=R9 270
RAM=8GB(Forgot the brand name)
PSU=Venom rx 700w 80+
HDD=Toshiba 500GB

 

[SkillR]

try to use WhoCrashed to gather more info.

 

[veredaux]

try to use WhoCrashed to gather more info.

On Sat 22/04/2017 16:30:15 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: Unknown (0xFFFF9C86AA41AB40)
Bugcheck code: 0xC2 (0x7, 0x0, 0x0, 0xFFFF9C86AA41AB40)
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.


On Fri 21/04/2017 20:46:00 your computer crashed
crash dump file: C:\WINDOWS\Minidump\042117-25328-01.dmp
This was probably caused by the following module: npfs.sys (Npfs+0xC3ED)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80806CBC3ED, 0xFFFFB700605AFC80, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\drivers\npfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NPFS 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.

 

[SkillR]

Try to install driver 17.3.3 (use the guide on this forum to delete the newer)

 

[johnbl]

basically you have a bad driver, it freed up a kernel memory address twice,
the first time it worked, the second time it did not own the memory address so windows called a bugcheck.

pool is just memory areas shared by device drivers. if a device driver frees up a memory block, then the windows memory manager gives the block to another driver. If the first driver frees up the memory a second time, it causes the other driver to crash.

you would have to provide the actual memory dump files from c:\windows\minidump. Ie put them on a cloud service like microsoft one drive, share the files for public access and post a link.

generally, you would fix this by going to the motherboard vendors website and updating the motherboard drivers to the current version.
These are the only drivers that windows update does not provide.

sometimes you will have to turn on debugging flags to find the name of the bad driver. (verifier.exe)