Windows 10: SYSTEM_THREAD_EXCEPTION_NOT_HANDLE (NETIO.SYS) / Bad Pool Caller Error BSOD's

Discus and support SYSTEM_THREAD_EXCEPTION_NOT_HANDLE (NETIO.SYS) / Bad Pool Caller Error BSOD's in Windows 10 BSOD Crashes and Debugging to solve the problem; Hello, these past two weeks I've began receiving several BSOD's a day since I installed Driver Booster and updated all my drivers across my OS. I... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by BalrogKin, Jul 6, 2019.

  1. BalrogKin Win User

    SYSTEM_THREAD_EXCEPTION_NOT_HANDLE (NETIO.SYS) / Bad Pool Caller Error BSOD's


    Hello, these past two weeks I've began receiving several BSOD's a day since I installed Driver Booster and updated all my drivers across my OS.


    I also installed Bitdefender Total Security and had to reinstall my wireless drivers like Qualcomm and Realtek again because Driver Booster seemed to have messed them up. I am sure its software-based, and its due to these drivers or combination of file and driver, but I just don't know enough. Today I just uninstalled my Realtek wireless driver only for the Realtek wireless PCI-card because I am ethernet-bound now.


    Luckily enough I have three minidumps I can post here. I'm not sure exactly how, so I will try to post them in text.


    Microsoft (R) Windows Debugger Version 10.0.18914.1001 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Users\Meow\Desktop\070619-69281-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available


    ************* Path validation summary **************
    Response Time (ms) Location
    Deferred srv*
    Symbol search path is: srv*
    Executable search path is:
    Windows 10 Kernel Version 17134 MP (12 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 17134.1.amd64fre.rs4_release.180410-1804
    Machine Name:
    Kernel base = 0xfffff801`bb00e000 PsLoadedModuleList = 0xfffff801`bb3bb170
    Debug session time: Sat Jul 6 18:22:05.321 2019 (UTC - 4:00)
    System Uptime: 0 days 6:36:11.036
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ................................................................
    .........
    Loading User Symbols
    Loading unloaded module list
    ................
    For analysis of this file, run
    !analyze -v
    nt!KeBugCheckEx:
    fffff801`bb1b8ab0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffae0e`7c058ba0=000000000000007e
    2: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
    This is a very common bugcheck. Usually the exception address pinpoints
    the driver/function that caused the problem. Always note this address
    as well as the link date of the driver/image that contains this address.
    Some common problems are exception code 0x80000003. This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG. This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG. This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff80b0797714c, The address that the exception occurred at
    Arg3: ffffae0e7c059b58, Exception Record Address
    Arg4: ffffae0e7c0593a0, Context Record Address

    Debugging Details:
    ------------------

    *** WARNING: Unable to verify checksum for win32k.sys

    KEY_VALUES_STRING: 1

    Key : AV.Dereference
    Value: NullClassPtr

    Key : AV.Fault
    Value: Read

    Key : Analysis.CPU.Sec
    Value: 3

    Key : Analysis.Elapsed.Sec
    Value: 4

    Key : Analysis.Memory.CommitPeak.Mb
    Value: 70


    PROCESSES_ANALYSIS: 1

    SERVICE_ANALYSIS: 1

    STACKHASH_ANALYSIS: 1

    TIMELINE_ANALYSIS: 1


    DUMP_CLASS: 1

    DUMP_QUALIFIER: 400

    BUILD_VERSION_STRING: 17134.1.amd64fre.rs4_release.180410-1804

    SYSTEM_MANUFACTURER: Micro-Star International Co., Ltd

    SYSTEM_PRODUCT_NAME: MS-7C02

    SYSTEM_SKU: To be filled by O.E.M.

    SYSTEM_VERSION: 1.0

    BIOS_VENDOR: American Megatrends Inc.

    BIOS_VERSION: 1.20

    BIOS_DATE: 09/21/2018

    BASEBOARD_MANUFACTURER: Micro-Star International Co., Ltd

    BASEBOARD_PRODUCT: B450 TOMAHAWK (MS-7C02)

    BASEBOARD_VERSION: 1.0

    DUMP_TYPE: 2

    BUGCHECK_P1: ffffffffc0000005

    BUGCHECK_P2: fffff80b0797714c

    BUGCHECK_P3: ffffae0e7c059b58

    BUGCHECK_P4: ffffae0e7c0593a0

    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

    FAULTING_IP:
    NETIO!StreamInvokeCalloutAndNormalizeAction+5c
    fffff80b`0797714c 488b7008 mov rsi,qword ptr [rax+8]

    EXCEPTION_RECORD: ffffae0e7c059b58 --
    (.exr 0xffffae0e7c059b58)
    ExceptionAddress: fffff80b0797714c (NETIO!StreamInvokeCalloutAndNormalizeAction+0x000000000000005c)
    ExceptionCode: c0000005 (Access violation)
    ExceptionFlags: 00000000
    NumberParameters: 2
    Parameter[0]: 0000000000000000
    Parameter[1]: 0000000000000008
    Attempt to read from address 0000000000000008

    CONTEXT: ffffae0e7c0593a0 --
    (.cxr 0xffffae0e7c0593a0)
    rax=0000000000000000 rbx=ffffae0e7c059f18 rcx=ffffae0e7c059df0
    rdx=0000000000000000 rsi=0000000000000000 rdi=ffff8181495c53b0
    rip=fffff80b0797714c rsp=ffffae0e7c059d90 rbp=ffffae0e7c059e19
    r8=0000000000000040 r9=0000000000000000 r10=fffffffffffffa98
    r11=0000000000000568 r12=ffffae0e7c05a298 r13=ffff8181550cbd00
    r14=0000000000000568 r15=ffff81815688daf0
    iopl=0 nv up ei pl zr na po nc
    cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
    NETIO!StreamInvokeCalloutAndNormalizeAction+0x5c:
    fffff80b`0797714c 488b7008 mov rsi,qword ptr [rax+8] ds:002b:00000000`00000008=????????????????
    Resetting default scope

    CPU_COUNT: c

    CPU_MHZ: f0a

    CPU_VENDOR: AuthenticAMD

    CPU_FAMILY: 17

    CPU_MODEL: 8

    CPU_STEPPING: 2

    BLACKBOXBSD: 1 (
    !blackboxbsd)


    BLACKBOXPNP: 1 (
    !blackboxpnp)


    CUSTOMER_CRASH_COUNT: 1

    PROCESS_NAME: System

    CURRENT_IRQL: 0

    FOLLOWUP_IP:
    NETIO!StreamInvokeCalloutAndNormalizeAction+5c
    fffff80b`0797714c 488b7008 mov rsi,qword ptr [rax+8]

    BUGCHECK_STR: AV

    READ_ADDRESS: fffff801bb45a388: Unable to get MiVisibleState
    Unable to get NonPagedPoolStart
    Unable to get NonPagedPoolEnd
    Unable to get PagedPoolStart
    Unable to get PagedPoolEnd
    0000000000000008

    DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE

    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

    EXCEPTION_CODE_STR: c0000005

    EXCEPTION_PARAMETER1: 0000000000000000

    EXCEPTION_PARAMETER2: 0000000000000008

    ANALYSIS_SESSION_HOST: DESKTOP-8648F6U

    ANALYSIS_SESSION_TIME: 07-06-2019 21:26:11.0240

    ANALYSIS_VERSION: 10.0.18914.1001 amd64fre

    LAST_CONTROL_TRANSFER: from fffff80b07976d03 to fffff80b0797714c

    STACK_TEXT:
    ffffae0e`7c059d90 fffff80b`07976d03 : ffff8181`5688da00 ffff8181`495c53b0 ffffae0e`7c05a298 ffff8181`495c53b0 : NETIO!StreamInvokeCalloutAndNormalizeAction+0x5c
    ffffae0e`7c059e70 fffff80b`07976639 : ffff8181`49600014 fffff80b`0962eae0 00000000`00000001 ffff8181`550cbdb0 : NETIO!StreamProcessCallout+0x2c7
    ffffae0e`7c059fa0 fffff80b`07975087 : 00000000`00000014 ffff8181`550cbdb0 ffff8181`48b631c0 ffffae0e`7c05a790 : NETIO!ProcessCallout+0x9d9
    ffffae0e`7c05a130 fffff80b`07972d88 : 00000000`00000005 00000000`00000000 ffff8181`47bdca00 ffffae0e`7c05a501 : NETIO!ArbitrateAndEnforce+0x4a7
    ffffae0e`7c05a320 fffff80b`079b4a80 : ffff8181`52f439f0 ffffae0e`7c05a811 ffff8181`514ca750 ffffae0e`7c05a958 : NETIO!KfdClassify+0x2f8
    ffffae0e`7c05a740 fffff80b`079b44ca : 00000000`00000000 ffffae0e`7c05a8e1 00000000`00000568 00000000`00000000 : NETIO!StreamInternalClassify+0x104
    ffffae0e`7c05a860 fffff80b`079b149b : 00000000`00000014 ffff8181`48b63010 00000000`00000000 ffff8181`5eba52c0 : NETIO!StreamInject+0x23a
    ffffae0e`7c05a930 fffff80b`07d1893d : ffff8181`48b63010 00000000`00000106 00000000`00000000 fffff80b`00000001 : NETIO!FwppStreamInject+0x13b
    ffffae0e`7c05a9c0 fffff80b`0765c9cf : ffff8181`5bfe8010 00000000`00000568 ffff8181`5eba52c0 00000000`00000000 : fwpkclnt!FwpsStreamInjectAsync0+0xfd
    ffffae0e`7c05aa20 ffff8181`5bfe8010 : 00000000`00000568 ffff8181`5eba52c0 00000000`00000000 00000000`00000106 : vsdatant+0xc9cf
    ffffae0e`7c05aa28 00000000`00000568 : ffff8181`5eba52c0 00000000`00000000 00000000`00000106 00000000`00000014 : 0xffff8181`5bfe8010
    ffffae0e`7c05aa30 ffff8181`5eba52c0 : 00000000`00000000 00000000`00000106 00000000`00000014 00000000`00000001 : 0x568
    ffffae0e`7c05aa38 00000000`00000000 : 00000000`00000106 00000000`00000014 00000000`00000001 ffff8181`5eba52c0 : 0xffff8181`5eba52c0


    THREAD_SHA1_HASH_MOD_FUNC: f5f75d1dc79db0d1ea4dc3b4f9e6a0415cf4ea7c

    THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 679adae60ee987ce62869089e24ccbd7544be1fd

    THREAD_SHA1_HASH_MOD: af182c9526e476607c647aba1ed63b74db95b578

    FAULT_INSTR_CODE: 8708b48

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: NETIO!StreamInvokeCalloutAndNormalizeAction+5c

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME:
    NETIO

    IMAGE_NAME: NETIO.SYS

    DEBUG_FLR_IMAGE_TIMESTAMP: 90332b2

    IMAGE_VERSION: 10.0.17134.441

    STACK_COMMAND: .cxr 0xffffae0e7c0593a0 ; kb

    BUCKET_ID_FUNC_OFFSET: 5c

    FAILURE_BUCKET_ID: AV_NETIO!StreamInvokeCalloutAndNormalizeAction

    BUCKET_ID: AV_NETIO!StreamInvokeCalloutAndNormalizeAction

    PRIMARY_PROBLEM_CLASS: AV_NETIO!StreamInvokeCalloutAndNormalizeAction

    TARGET_TIME: 2019-07-06T22:22:05.000Z

    OSBUILD: 17134

    OSSERVICEPACK: 829

    SERVICEPACK_NUMBER: 0

    OS_REVISION: 0

    SUITE_MASK: 272

    PRODUCT_TYPE: 1

    OSPLATFORM_TYPE: x64

    OSNAME: Windows 10

    OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

    OS_LOCALE:

    USER_LCID: 0

    OSBUILD_TIMESTAMP: 2019-06-07 01:21:36

    BUILDDATESTAMP_STR: 180410-1804

    BUILDLAB_STR: rs4_release

    BUILDOSVER_STR: 10.0.17134.1.amd64fre.rs4_release.180410-1804

    ANALYSIS_SESSION_ELAPSED_TIME: 1379

    ANALYSIS_SOURCE: KM

    FAILURE_ID_HASH_STRING: km:av_netio!streaminvokecalloutandnormalizeaction

    FAILURE_ID_HASH: {c2ca2d1f-cfdc-88d5-c7bc-7693b8f0de04}

    Followup: MachineOwner
    ---------


    :)
     
    BalrogKin, Jul 6, 2019
    #1

  2. BSOD Bad Pool Caller Win 10 avc3.sys

    Hey can you help me please? I've been getting BSOD for a while now with the error Bad Pool Caller. I ran drive verifier and it mentioned avc3.sys. The link below leads to the dump files and sysinfo.

    Dump Files
     
    NichStephens, Jul 6, 2019
    #2
  3. JosephYen Win User
    BSOD - Bad Pool Caller

    I keep getting a Bad Pool Caller BSOD on windows 10

    IBM T420 - 8GB ram - 186gb free of 320gb - Not overclocked.

    The memory diagnostic returns no errors and I haven't had any new hardware for over a year.

    Any suggestions?

    Here's my minidumps

    https://drive.google.com/open?id=1haRMGnXLLI8sY9IZi7mijZUl9VszAA5I
     
    JosephYen, Jul 6, 2019
    #3
  4. almogc Win User

    SYSTEM_THREAD_EXCEPTION_NOT_HANDLE (NETIO.SYS) / Bad Pool Caller Error BSOD's

    BSOD Bad Pool Caller 0xC2


    BSOD Bad Pool Caller 0xC2
     
    almogc, Jul 6, 2019
    #4
Thema:

SYSTEM_THREAD_EXCEPTION_NOT_HANDLE (NETIO.SYS) / Bad Pool Caller Error BSOD's

Loading...
  1. SYSTEM_THREAD_EXCEPTION_NOT_HANDLE (NETIO.SYS) / Bad Pool Caller Error BSOD's - Similar Threads - SYSTEM_THREAD_EXCEPTION_NOT_HANDLE NETIO SYS

  2. Bad Pool Caller

    in AntiVirus, Firewalls and System Security
    Bad Pool Caller: Hello, I keep getting a bad pool caller screen and my laptop turns off, I have tried to do a security update but it stops and gives the message below: - Feature update to Windows 10, version 1809 -Error 0x800705b9 I am not sure what to do as it is happening frequently...
  3. Bad Pool Caller

    in Windows 10 Drivers and Hardware
    Bad Pool Caller: Why am I getting this error and blue screen ON A BRAND NEW COMPUTER? Windows 10 https://answers.microsoft.com/en-us/windows/forum/all/bad-pool-caller/6fcc5cb6-97a3-455e-8c45-85786a952213
  4. Bad Pool Caller - ksthunk.sys

    in Windows 10 Drivers and Hardware
    Bad Pool Caller - ksthunk.sys: Link to the dump file: https://www.dropbox.com/s/1d6c84iwo50eb68/102218-13468-01.dmp?dl=0 WhoCrashed info: On Tue 10/23/2018 12:02:03 AM GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\102218-13468-01.dmp This was probably caused by the following module:...
  5. BSOD - Bad Pool Caller

    in Windows 10 Drivers and Hardware
    BSOD - Bad Pool Caller: Hi, I'm experiencing some problems with BSOD with error message Bad Pool Caller. It appears only when I play Witcher 3 with Afterburner on (I dont have to overclock, I'm turning it on because of monitoring) and randomly sometimes video freezes, sound is still playing for a...
  6. blue screen bad pool caller

    in Windows 10 BSOD Crashes and Debugging
    blue screen bad pool caller: how can I fix "bad pool caller" blue screen? https://answers.microsoft.com/en-us/windows/forum/all/blue-screen-bad-pool-caller/d4c03c76-8557-4373-b11e-71f092c6fac0
  7. BSOD bad pool caller

    in Windows 10 BSOD Crashes and Debugging
    BSOD bad pool caller: I had a BSOD on windows 10 with the message: for more info look online for: BAD POOL CALLER There was no value. I have the impression the BSOD is caused by an original windows 7 desktop application (GNS3.exe) which hanged (not responding) when I loaded a project. I closed...
  8. Randomly getting Bad Pool Caller BSOD

    in Windows 10 BSOD Crashes and Debugging
    Randomly getting Bad Pool Caller BSOD: Hey, 2 days ago I got my first BSOD in a long time and I didn't think much of it but now I've been getting more and I'm not sure why. It was running fine last week and since then I've gotten a new keyboard (Roccat Isku FX) and installed the driver/software for it and a...
  9. BSOD : Bad Pool Caller Windows 10 pro

    in Windows 10 BSOD Crashes and Debugging
    BSOD : Bad Pool Caller Windows 10 pro: Hi! I'm having for a while a BSOD Bad pool caller. All the drivers and software in my OS are up to date. I don't think it's a memory problem, the Windows Memory Diagnostic gave me no errors, I also tried the SFC /SCANNOW to try fixing the file systems, and also chkdsk /r to...
  10. BSOD Bad Pool Caller 0xC2

    in Windows 10 BSOD Crashes and Debugging
    BSOD Bad Pool Caller 0xC2: BSOD Bad Pool Caller 0xC2 82811