Bad Pool Header BSOD

you would have to provide the memory dump from c:\windows\minidump directory
if you have a utility for charging apple products you should update it or remove it.
- update the BIOS to the current version to get USB fixes
- update the motherboard drivers from the motherboard vendor. The bios and motherboard drivers need to match versions.

if you continue to have problems, you would need to change the memory dump type to kernel, wait for the next bugcheck and put the c:\windows\memory.dmp file
this is just because the minidump does not store the USB info required to figure out the problem. kernel and full memory dumps do provide the info.

with a bad usb driver (like the old versions of applecharger) cause the USB ports to turn on and off hundreds or thousands of times a second. Just enough to really slow things down but not long enough to cause a bugcheck.

there are utilities like usbview.exe that can display the problem but it is in the windows ddk and is hard to get to. you might try this one:http://www.uwe-sieber.de/usbtreeview_e.html

it is also likely that your USB wireless driver is corrupting the driver memory pool.
it can be something simple like freeing the same memory location twice.
this can happen for various reasons. fixes involve update of the BIOS USB chipset drivers for the usb 2.x ports and update of any external usb 3.0 drivers as well as updating the actual wireless driver. Note: it is kind of a pain because usb drivers become hidden when you unplug the usb device and the driver can be associated with various USB ports.
(usbview.exe helps show the problem, sometimes you can unhide the driver in control panel then remove the bad driver from the driver store.
https://technet.microsoft.com/en-us/library/cc730875(v=ws.11).aspx
(you have to remove the device, stop plug and play, remove the driver using pnputil.exe, install the new driver, start plug and play again)

usb caused pool corruptions are common with drivers of certain dates.
just because the USB spec changed over the years.
in 2012 the usb 2.2 spec came out and the bios had to be updated. if you have a USB driver before then it can corrupt data.
in 2013 the usb 3.0 spec was finished, many bios before them had their own version and require a bios update to match the drivers that came out after early 2013.

it also depends on the device that is plugged in, and into what type of port.
all the info is contain in the kernel memory dump but not the mini memory dump.