Windows 10: BSOD BAD_POOL_CALLER NETIO.sys

Hi,my PC has been crashing several times a week for a few months now,even though I have already updated all the drivers I can get from the manufacturer mainboard: MSI. With WinDbg.exe i was able to determine that it is ultimately due to the NETIO.sys file.But the cause is probably to be found in a previous component, but I don't see it. Can you analyze the minidump in more detail and tell me what the problem is? Thank you very much Dropbox: https://www.dropbox.com/scl/fi/3h1wy2clt6jev76tjgn69/Dumps.zip?rlkey=d29dbyzvp5h535xk8o3f73a76&dl=1 Translated with DeepL.com free version

:)

 

BSOD Bad_Pool_Caller Win10 on Dell Inspiron

Here is some info that may help. May be your network driver. One of the posts suggest a program that will give more info on what crashed. Hope this helps you.

BSOD caused by ndis.sys, NETIO.SYS and ntoskrnl.exe

 

How to stop blue screen netio sys errors

how do you stop blue screen errors namely netio sys

 

BSOD - BAD_POOL_CALLER

Hi Gerry,

Do not worry any further as I have resolved the problem.

I downloaded another program called WhoCrashed which was able to analyse the MEMORY.DMP file which told me the below. As this only appears to happen during surfing the web and my BAD_POOL_CALLERS had issues with the TCP drivers within Windows, it makes perfect
sense. I have Googled the issue and found that the Killer Networking drivers are simply rubbish, to run a full uninstall, and just install the drivers without the software suite. Should this continue to happen again, I will try uninstalling the drivers, disabling
the device, and use my Intel NIC as I have two ethernet ports on my motherboard (EVGA Z270 Classified K). It's annoyed me a little as I have lost my overclock settings now after running a CMOS so I will have to play around with those over the weekend but at
least it's not a hardware issue and I can resolve it over time

I apologise for wasting your time as it could have been used helping someone else.

Thank you!

- Mitch

On Fri 17/03/2017 00:28:51 your computer crashed

crash dump file: C:\Windows\memory.dmp

This was probably caused by the following module: e2xw1.sys (e2xw10x64+0x892D)

Bugcheck code: 0xC2 (0x7, 0x0, 0x3, 0xFFFFB088BDD203D8)

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. It is suggested you look for an update for the following driver: e2xw1.sys .

Google query: e2xw1.sys BAD_POOL_CALLER