BSOD when watching twitch. Error: BAD_POOL_CALL

Hi,About a few weeks ago i updated to Windows 10 Creators update. After that my BSOD nightmare begun. I have updated all drivers. Googled around and reset my tcpip stack. Attaching log as instructed. Any help is much appreciated. It mainly happens when i am watching twitch but i have encountered it on other sites. Games even heavy games do not cause it. Only when browsing. Also i think it is not only during chrome session i think i have seen it at least once or twice during other browser usage.

Hello atk :)

All the recent crash dumps show the following:

*** WARNING: Unable to verify timestamp for e2xw10x64.sys
*** ERROR: Module load completed but symbols could not be loaded for e2xw10x64.sys

Code:

0: kd> lmvm e2xw10x64
Browse full module list
start             end                 module name
fffff80c`a2b10000 fffff80c`a2b39000   e2xw10x64 T (no symbols)           
    Loaded symbol image file: e2xw10x64.sys
    Image path: \SystemRoot\System32\drivers\e2xw10x64.sys
    Image name: e2xw10x64.sys
    Browse all global symbols  functions  data
    Timestamp:        Thu Mar 09 19:20:54 2017 (58C1AB16)
    CheckSum:         0002D9F1
    ImageSize:        00029000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

This driver is associated with the Killer Network (aka Qualcomm Atheros) and could be related to your crashes. Try using an older network driver, maybe find one off the manufacturers website rather than using the one chosen by W10.

I have updated to the newest driver from Killer, as post Creator's update the old one had a massive memory leak.

The new driver fixed that but then this BSOD issues showed up. Not sure if it is related to the new driver from Killer or old one could have had the same issue if i have let it run long enough.

I will check if there is newer driver, but rolling back to old could lead me to the memory leak again.

OK, looks like you are narrowing it down. Anyway of remembering which driver was being used prior to the update?

I will have a look once i am at home.
It was again Killer's driver, just older version. I didn't need to update it as it worked fine. But after the recent Win Updates the old one went into memory leakage.

As soon as i get home i will check and write here.

Hello !!!
You were right it might be the Killer drivers.
I just downloaded the newest driver and reading through the release notes i found this:

1030 Rivet Filtering Engine BAD_POOL_CALLER BSOD from end-user1006 Rivet Filtering Engine BSOD from end-user
This was released 5-th of may so quite hot out of the oven. Will install and report. If no crashes in the next week will mark as solved so other people can see it.