BSOD Bad Pool Caller

[Blisslen]

Just BSOD'd upon unplugging and plugging back in my Logitech G502 mouse.

Dump file: https://www.dropbox.com/s/l7lzg0xkv33awe1/012915-22750-01.dmp?dl=0

 

[Peasant]

1. Use BlueScreenView to read the minidumps and note the BCCode or Stop codes, the Cause and
the Time.
2. Run MyEventViewer and check for entries at the same time or a second (or) so before the BCCode
or Stop Codes from the BlueScreenView.

3. Look up the code on FaultWire - the solutions offered there are usually excellent.

0x00000000 to 0x00000003F
http://www.faultwire.com/solutions_index/fatal_error-1.html#IssueList
0x00000040 to 0x0000007F
http://www.faultwire.com/solutions_index/fatal_error-2.html#IssueList
0x00000080 to 0x000000BF
http://www.faultwire.com/solutions_index/fatal_error-3.html#IssueList

0x000000C0 to 0x000000FF
0x00000100 or higher
http://www.faultwire.com/solutions_index/fatal_error-5.html#IssueList

4. Post the BCCode or Stop Codes, Parameters, the Cause, and related information into a message
in this forum for detailed help.This error is usually a driver issue and display adapter (video) driver is the most suspect though it
could be others. Antivirus/antispyware/security programs, hardware (heat) and major software issues
can also cause the error. When you get to the driver section of the troubleshooter use my generic
methods in the next message and then return to the troubleshooter if needed. Memory issues are
another possibility after drivers.
Have you added hardware recently or updated drivers? Be sure to look in Control Panel - Windows
Updates to see if any drivers were updated there. Other lessor possibilities include antivirus/anti-
spyware/security programs.

 

[Peasant]

This error is usually a driver issue and display adapter (video) driver is the most suspect though it
could be others. Antivirus/antispyware/security programs, hardware (heat) and major software issues
can also cause the error. When you get to the driver section of the troubleshooter use my generic
methods in the next message and then return to the troubleshooter if needed. Memory issues are
another possibility after drivers.
Have you added hardware recently or updated drivers? Be sure to look in Control Panel - Windows
Updates to see if any drivers were updated there. Other lessor possibilities include antivirus/anti-
spyware/security programs.

 

[johnbl]

looks like you have a hypervisor running, so it kind of depends on how you were runing the logitech driver to determine the fault. But on a normal system I would just look for a driver update first.

--------
looks like the logitech driver ladfGSRamd64.sys freed the same memory block twice. first time was ok the second time cause a bugcheck because it no longer owned the memory block. I would look for a file update newer than apr 15 2013

----------------
BAD_POOL_CALLER (c2)
The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 0000000000000007, Attempt to free pool which was already freed
Arg2: 0000000000001200, (reserved)
Arg3: 000000004c411c20, Memory contents of the pool block
Arg4: ffffe00049a20d50, Address of the block of pool being deallocated







Loaded symbol image file: ladfGSRamd64.sys
Image path: \SystemRoot\system32\DRIVERS\ladfGSRamd64.sys
Image name: ladfGSRamd64.sys
Timestamp: Mon Apr 15 11:39:15 2013 (516C4953)