Windows 10: BSOD bad_pool_caller, possibly related to wi-fi adapter

Hi, I've had some issues with a BSOD for over a year now, first when I was running Windows 8 and now still with Windows 10. It first appeared after I got a USB wi-fi adapter which I replaced with an adapter that connected to the motherboard, but the BSODs have not stopped. I inquired about it a few months ago on several other forums. It was apparently related to some driver that the USB adapter installed (the name of which I can no longer remember), but I was unable to uninstall it or delete it without my wi-fi becoming unusable. I'm also unable to use a wired connection in my apartment, though I'm not sure that would even be possible if I deleted the driver. The error code I get is "bad_pool_caller", but I believe I used to get "irql_not_less_or_equal" as well.

For some background, the BSOD usually appears when I'm doing something intensive over the internet like watching video on YouTube or Twitch, streaming audio, etc.

Here's my debug folder:

Attachment 35395

:)

 

Wifi and lots of other issues

If it is a Dell, how old is it and what model?

I believe some Wi-Fi adapters are not compatible with Win 10. And it seems some of these updates are moving more devices all the time.

If it is a laptop, you have the option to replace the Wi-Fi adapter which would possibly upgrade the Wi-Fi and Bluetooth, possibly.

 

Recurring BSOD crashes after using specific software (Axure RP Pro)

The causes of the BSOD's are related to BAD_POOL_CALLER and SYSTEM_SERVICE_EXCEPTION related to the drivers; ntoskrnl.exe+16c560 and win32kbase.sys

 

Hi pdmchubby,

Welcome to the 10forums.

I have analysed the most recent dump files and they all seem to be caused by the NETIO.sys (Network In/Output) driver.
Because this is a system file, there are 2 options for now to go through.

1.
Please do the following:

• Open an admin command prompt
• Copy/paste "sfc/scannow" (without quotes) and press enter
• When it finished reboot your system
• Open again an admin command prompt
• Enter sfc/scannow again

If sfc/scannow doesn't say "Windows Resource Protection did not find any integrity violation", please upload the cbs.log file located at {windows partition}\Windows\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.



2.





Diagnostic Test

DRIVER VERIFIER


Warning Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.
Please read and run driver verifier.

A windows driver is blamed in a few crashes, but that usually means that a 3rd party driver is actually the cause.
Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.



Note Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

 

Here's my CBS file, system scan didn't find any violations.

CBS

 

Only when sfc did not say that I asked for the upload*Wink

 

Sorry, the double-negative phrasing confused me.

I ran Driver Verifier and got two BSODs once the computer booted back into Windows, this time with the error "DRIVER_OVERRAN_STACK_BUFFER". Not sure what the next step is, so I'll just throw up my dump files again in case you need them.

Attachment 35673

 

The cause of the crashes are the Logitech Camera driver
Check for updates here
Code: 3: kd> lmvm lvrs64start end module name fffff802`00830000 fffff802`00884000 lvrs64 T (no symbols) Loaded symbol image file: lvrs64.sys Image path: \SystemRoot\system32\DRIVERS\lvrs64.sys Image name: lvrs64.sys Timestamp: Tue Oct 23 04:11:24 2012 (5085FCCC) CheckSum: 00058CF8 ImageSize: 00054000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/quote]
The Nvidia Video driver has also been flagged, 1 time.
I'm not sure if this will be a problem.
Code: 3: kd> lmvm nvlddmkmstart end module name fffff801`ffb60000 fffff802`00648000 nvlddmkm T (no symbols) Loaded symbol image file: nvlddmkm.sys Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys Image name: nvlddmkm.sys Timestamp: Thu Jul 23 02:15:19 2015 (55B03217) CheckSum: 00AA405B ImageSize: 00AE8000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/quote]

 

Alright, I updated and/or got rid of those drivers and the BSODs are definitely less frequent now, so it has helped, but I still get them maybe once every day or two. I'm uploading my logs again in case you can find any other bad drivers.

Attachment 37433

 

Please install the drivers you have removed, you need these drivers.

Please do the following

• Search services.msc and open it
• Search Nvidia Streamer Service
• Right click > properties
• Change startup type to disable

 

The only driver I removed was my Logitech one, I still need that? I couldn't find the appropriate update and I don't really need the webcam. I just updated my Nvidia drivers.

I disabled Nvidia streamer service as instructed.

 

Sorry, I thought you removed the Nvidia drivers, I still have to get used to some things in the logs.

Usually when people cannot find an update they are suggested to try an older version.
I'm not sure if removing the driver could cause trouble, but I would let it as it is if it doesn't give trouble.

 

I'm still having BSOD problems (just had one a few minutes ago in fact), so I'm uploading another set of minidump files to see what the issue is.

Attachment 38844