Single Occurrence- BAD_POOL_CALLER-Possible Driver Problems

[PaulMChem]

As the name suggests I've had a BSOD happen to me right on reboot after having disabled some Toshiba drivers to improve Startup time. It hasn't repeated since then, but I want to solve the issue nevertheless. It may be caused by my wireless/graphics driver.Here's the report archive:

 

[axe0]

Hi PaulMChem,

It seems you've had more BSODs than described.
The 0xC2 doesn't hold enough to pinpoint the cause. It's only showing what the parameters are already telling, a double freeing of the same pool.
If you really would want to continue troubleshooting, I would need you to run driver verifier.

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 follow this tutorial to run driver verifier.

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.