I use the program Virtual Router Plus to create a wifi hotspot on my desktop and connect my phone to it for game streaming. I'm using this wifi adapter here https://www.tp-link.com/us/products/details/Archer-T2U.html
Most of the time it works. But sometimes, when I open the hotspot program and click "Start Virtual Router Plus" to create the hotspot, I get a bluescreen with the error BAD_POOL_CALLER.
The wifi adapter I'm using has two hardware versions and, thus, two different drivers. I'm not sure which hardware version I have, but I tried both drivers and both have this issue.
I used driver verifier, but it didn't find any unsigned drivers or drivers built for older versions of Windows.
I used WhoCrashed from www.resplendence.com to analyse the crash. Here are the results:
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Mon 07.01.2019 14:30:53 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\010719-22328-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0xC2 (0x7, 0x1200, 0x4020009, 0xFFFFE0013FAB1C20)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Most of the time it works. But sometimes, when I open the hotspot program and click "Start Virtual Router Plus" to create the hotspot, I get a bluescreen with the error BAD_POOL_CALLER.
The wifi adapter I'm using has two hardware versions and, thus, two different drivers. I'm not sure which hardware version I have, but I tried both drivers and both have this issue.
I used driver verifier, but it didn't find any unsigned drivers or drivers built for older versions of Windows.
I used WhoCrashed from www.resplendence.com to analyse the crash. Here are the results:
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Mon 07.01.2019 14:30:53 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\010719-22328-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0xC2 (0x7, 0x1200, 0x4020009, 0xFFFFE0013FAB1C20)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.