Random BSODs due to BAD_POOL_CALLER

Page 1 of 2 12 LastLast

  1. GTM
    Posts : 9
    Windows 10 Pro
       #1

    Random BSODs due to BAD_POOL_CALLER


    For the last few months I have been getting these random BSODs. All due to BAD_POOL_CALLER with Bug Check Code 0x000000c2. I ran MEMTEST for 24+ hours without any issues so there is no problem with the system memory. Then downloaded a utility (BlueScrenView) which analyzed the minidump and it highlighted three MS drivers (fwpkclnt.sys, NETIO.SYS, and ntoskrnl.exe). I contacted MS support to see if they could help diagnose the real issue but that was fruitless.
      My Computer


  2. GTM
    Posts : 9
    Windows 10 Pro
    Thread Starter
       #2

    Additional info


    Adding the minidump analyses from the BlueScreenView utility
      My Computer


  3. Posts : 545
    seL4
       #3

    I do not see any crash dumps in your attachment, could you please run our new collection tool at the bottom of the posting instructions page.
      My Computer


  4. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #4

    There are two dumps included at the bottom of the BlueScreenView images.

    Never mind, just .txt files, sorry.
      My Computers


  5. GTM
    Posts : 9
    Windows 10 Pro
    Thread Starter
       #5

    I am sorry, but I do not have the dumps. I must have erased them. I will make sure the next time I get the BSOD to include the dumps in the collection package. Nevertheless, thanks a lot for trying to help.
      My Computer


  6. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #6

    Two things I would do right away. Uninstall Iolo System Mechanic.
    Update your NVIDIA GeForce GTX 1050 to the latest driver as follows:

    I suggest completely uninstalling the Nvidia display drivers using Display Driver Uninstaller (DDU) from WagnardMobile here: Official Download Here. Do this in Safe Mode. Then get the latest driver for your Nvidia card here: NVIDIA Driver Downloads. Version 399.07 dated 2018.8.27 is currently available.

    Then do a custom install of only the NVidia graphics driver and the PhysX driver.

    See if that gets rid of the problem.
      My Computers


  7. GTM
    Posts : 9
    Windows 10 Pro
    Thread Starter
       #7

    Took another BSOD and this time I made sure that the dump was not deleted, so I ran the collector and collected the dump as well as the other files. I will upload the .zip file.

    As far as updating the video driver, I'll do that as well. I have a question regarding IOLO System Mechanic. Why do you recommend that I uninstall this app? I have no problem uninstalling a problem app, but I would like to know if that Is the cause of the BSODs.

    Thanks for your help.
      My Computer


  8. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #8

    I'm not a fan of IOLO anything. Seen to many problems caused by it. Some people swear by it, others swear at it.

    IOLO does not have a good reputation here. Your choice. You cxan wait and see what the next BSOD shows.
      My Computers


  9. GTM
    Posts : 9
    Windows 10 Pro
    Thread Starter
       #9

    I am not married to IOLO System Mechanic. I have been using it mostly to control startup tasks and cleanup the windows registry, since I am not aware of any other utilities that can do so easily/safely. I used to use a utility called "PC Tools Registry Mechanic" which was very good, but it was bought by Symantec and then they killed it as they killed the "Partition Magic" and "Drive Image" utilities.

    I did update the video drivers using the method you recommended.

    The last BSOD (for which I collected all the pertinent data and the minidump) and uploaded it yesterday occurred before I updated the video drivers.

    Hopefully you guys will be able to determine the app/driver that caused the BSODs.

    Thanks for your help,

    George
      My Computer


  10. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #10

    Will have to wait for the next BSOD so we can look at the dump then.

    Startup tasks can be controlled from the Startup tab of Task Manager.
    Registry really does not need to be cleaned. Doing so is more of a "feel good" operation than something that benefits the system. I knowas I do it to but I also know it's not necessary.
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 11:21.
Find Us




Windows 10 Forums