Bad Pool Caller BSOD RRS feed

  • Question

  • Hey guys,

    I got a new VAIO S15 with Win 8 and I am getting the Bad Pool Caller error with BSOD. 

    There is a link to my dmp files: http://sdrv.ms/11ZxXm3

    Can anybody please be so kind and take a look at them? I would be really grateful.


    Wednesday, June 19, 2013 3:22 PM


All replies

  • Your problem is probably caused by the fact you have 2 x Anti Virus programs.

    That is NOT a good idea. More is not best.

    AVG & McAffe can be a contributing cause of BSOD'S.

    Please remove both for testing purposes.

    Note Defender should then be turned on for protection.



    Should defender not enable you can download it (and read about it) at these links.

    Defender download http://www.microsoft.com/en-us/download/windows-defender-details.aspx

    *** WARNING: Unable to verify timestamp for avgwfpa.sys
    *** ERROR: Module load completed but symbols could not be loaded for avgwfpa.sys
    GetPointerFromAddress: unable to read from fffff8002b3cc168
    GetUlongFromAddress: unable to read from fffff8002b3cc1f8
    Probably caused by : avgwfpa.sys ( avgwfpa+5e48

    Advice offered in good faith. It is your decision to implement same. Dyami & Wanikiya, Team ZigZag.

    Wednesday, June 19, 2013 7:29 PM
  • Hi! I got a "Bad Pool Caller" BSOD while i was playing a game (dirt 3) Here is my minidump:


    Monday, October 6, 2014 6:06 PM
  • JH

    This is related to memory & Old drivers.  Please run driver verifier and upgrade the driver listed below from the vista era.

    These crashes were related to memory corruption (probably caused by a driver). 

    Please run these tests to verify your memory and find which driver is causing the problem.  

    If you are overclocking (pushing the components beyond their design) you should revert to default at least until the crashing is solved. If you don't know what it is you probably are not overclocking.

    Since it is more likely to be a driver please run verifier first.
    1-Driver verifier (for complete directions see our wiki here)

    If verifier does not find the issue we can move on to this.
    2-Memtest. (You can read more about running memtest here)

    If you cannot boot after enabling verifier reboot into safe mode
    In Vista & win 7 (F8)

    Co-Authored by  JMH3143

    emupia2k.sys    3/20/2008 4:17:22 AM                               
    ctsfm2k.sys    3/20/2008 4:17:29 AM                           
    ctoss2k.sys    3/20/2008 4:17:40 AM                             
    ha10kx2k.sys    3/20/2008 4:18:06 AM                              
    ctaud2k.sys    3/20/2008 4:19:33 AM                               
    ctprxy2k.sys    3/20/2008 4:19:34 AM                            
    CTEDSPIO.SYS    3/20/2008 4:19:53 AM                              
    CTEDSPSY.SYS    3/20/2008 4:19:58 AM                      
    COMMONFX.SYS    3/20/2008 4:20:02 AM                   

    Wanikiya and Dyami--Team Zigzag

    Monday, October 6, 2014 6:15 PM
  • All of those driver files you mentioned are for my pci soundcard (creative e-mu 1820) it is old and still only has beta drivers for newer operating systems but it has not really given me issues during all these years. Ofcourse it might have uncompatibilites with some software/hardware but i have not encoutered any yet.

    I did 10 passes of memtest and it gave no errors. I did drop my memory frequency from 2133mhz to 1866mhz before i ran memtest. These G-skill ripjaws should handle 2133mhz with my Asrock z77 extreme4 but maybe i don't have enough airflow (over the memory) or maybe they need some voltage adjustment.

    I have have done zero overclocking on this system during the last six months or so.

    I installed new updates for windows and ran ccleaner and got rid of unused registry entries.

    Everything seems to run fine now. Thank you! I'll do some more stress testing to be sure.

    Monday, October 6, 2014 11:42 PM