BSOD Bad_Pool_Caller

Page 2 of 3 FirstFirst 123 LastLast

  1. Posts : 11
    New Jersey
    Thread Starter
       #11

    May I get a member of the bsod team to chime in on this as well?
    No offense to Laith.
    Last edited by dogethrowaway; 28 Apr 2015 at 16:45.
      My Computer


  2. Posts : 2,781
    Windows 10 Pro x64
       #12

    That's good because Driver Verifier caught the misbehaving driver. It's WinCDEmu who caused it. Uninstall it.
      My Computer


  3. Posts : 11
    New Jersey
    Thread Starter
       #13

    Laith said:
    That's good because Driver Verifier caught the misbehaving driver. It's WinCDEmu who caused it. Uninstall it.
    What do the dumps say though to you? Mainly because I need that NIwincdemu.sys file. It is part of Native instruments. So I don't think that is the file causing the blue screens.

    Someone in the reddit thread said this when analyzing the dumps.
    "It's always crashing with the Realtek USB Wireless network driver on the stack (the Linksys device uses a Realtek chip), so I'm pretty sure that's causing this."

    I just need the bad pool caller to be fixed and not have a driver verifier bsod.
      My Computer


  4. Posts : 2,781
    Windows 10 Pro x64
       #14

    The BAD_POOL_CALLER blamed WinCDEmu. I said wrong.
      My Computer


  5. Posts : 11
    New Jersey
    Thread Starter
       #15

    Laith said:
    The BAD_POOL_CALLER blamed WinCDEmu. I said wrong.
    ... I don't have this program on my computer...
      My Computer


  6. Posts : 2,781
    Windows 10 Pro x64
       #16

    Well, the driver i said before was the thing causing the BSODs.
      My Computer


  7. Posts : 11
    New Jersey
    Thread Starter
       #17

    Laith said:
    Well, the driver i said before was the thing causing the BSODs.

    Can I get a member of the BSOD Team in this post? Before I make another thread?
      My Computer


  8. Posts : 2,781
    Windows 10 Pro x64
       #18

    Sure can do. I'll bring Golden to assist you.
      My Computer


  9. Posts : 19,383
    Windows 10 Pro x64 ; Xubuntu x64
       #19

    There is no need for another thread - Laith is 100% correct. WinDBG clearly identifies WinCDEmu.sys as the problem. It belongs to NATIVE INSTRUMENTS GmbH ISO mounter software.
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck C9, {215, fffff88004432eab, fffff98003ffae10, 0}
    
    *** WARNING: Unable to verify timestamp for NIWinCDEmu.sys
    *** ERROR: Module load completed but symbols could not be loaded for NIWinCDEmu.sys
    Probably caused by : NIWinCDEmu.sys ( NIWinCDEmu+9eab )
    
    Followup: MachineOwner
    ---------
    
    7: kd> lmvm NIWinCDEmu
    start             end                 module name
    fffff880`04429000 fffff880`04449000   NIWinCDEmu T (no symbols)           
        Loaded symbol image file: NIWinCDEmu.sys
        Image path: \SystemRoot\system32\DRIVERS\NIWinCDEmu.sys
        Image name: NIWinCDEmu.sys
        Timestamp:        Wed Sep 26 21:10:33 2012 (5062E9B1)
        CheckSum:         0002433D
        ImageSize:        00020000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    As you can see the driver is quite outdated. Check the software developer for a newer driver, or uninstall the software.

    You also seem to have issues with the Realtek wireless USB adapter driver:
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck C2, {7, 109b, 40e0007, fffffa800cdbcf30}
    
    *** WARNING: Unable to verify timestamp for rtwlanu.sys
    *** ERROR: Module load completed but symbols could not be loaded for rtwlanu.sys
    GetPointerFromAddress: unable to read from fffff80003115100
    GetUlongFromAddress: unable to read from fffff800031151c0
    GetUlongFromAddress: unable to read from fffff80003083a38
    Probably caused by : vwififlt.sys ( vwififlt!FilterSendNetBufferListsComplete+151 )
    
    Followup: MachineOwner
    ---------
    Check for updates here:
    Realtek
      My Computer


  10. Posts : 2,781
    Windows 10 Pro x64
       #20

    That's what i tried to say. He has 2 WiFi drivers which i think is causing the problems with the Realtek BSOD.
      My Computer


 
Page 2 of 3 FirstFirst 123 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 06:58.
Find Us