T410s - BAD_POOL_CALLER BSOD

Got to love this...  new T410s just out of the box.  get BSOD within first 24 hours. 
I did 2 things after I completed my Win 7 64 bit setup.  I updated the BIOS to the latest 1.14 via Thinkvantage, and installed Office 2010. 
I have been reading a lot of threads about this error, seems to be tied to a number of issues both SW drivers and HW.  Just curious if anyone else has had this happen lately.
My Box:
T410s - i5-520
4 Gigs of RAM
128 gig SSD
Intel 6300 ultimate nic card
Gobi WWAN card
All the other usual suspects...
** No switchable graphics or touch screen.
Contents of Event Viewer:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
- System
  - Provider
   [ Name]  Microsoft-Windows-Kernel-Power
   [ Guid]  {331C3B3A-2005-44C2-AC5E-77220C37D6B4}
   EventID 41
   Version 2
   Level 1
   Task 63
   Opcode 0
   Keywords 0x8000000000000002
  - TimeCreated
   [ SystemTime]  2010-06-17T04:39:46.634007200Z
   EventRecordID 5921
   Correlation
  - Execution
   [ ProcessID]  4
   [ ThreadID]  8
   Channel System
   Computer Mark-T410s
  - Security
   [ UserID]  S-1-5-18
- EventData
  BugcheckCode 194
  BugcheckParameter1 0x7
  BugcheckParameter2 0x1097
  BugcheckParameter3 0xd0016
  BugcheckParameter4 0xfffffa80040f0170
  SleepInProgress false
  PowerButtonTimestamp 0
Any help/advice would be appriciated.
Thanks
Mark

I have the exact same error.  My T410s will power itself off about once a week when in sleep mode.  Any suggestions on a resolution?
I'm not sure why this thread is titled BAD_POOL_CALLER as I don't see this error at all and it is not mentioned in the original post?
Here's the snippet from Event Viewer.  It matches pretty much exactly the one from the first post.
Log Name:      System
Source:        Microsoft-Windows-Kernel-Power
Date:          26/09/2010 12:50:00 PM
Event ID:      41
Task Category: (63)
Level:         Critical
Keywords:      (2)
User:          SYSTEM
Computer:      HHH-TP
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
    <EventID>41</EventID>
    <Version>2</Version>
    <Level>1</Level>
    <Task>63</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000002</Keywords>
    <TimeCreated SystemTime="2010-09-26T19:50:00.011604400Z" />
    <EventRecordID>8669</EventRecordID>
    <Correlation />
    <Execution ProcessID="4" ThreadID="8" />
    <Channel>System</Channel>
    <Computer>HHH-TP</Computer>
    <Security UserID="S-1-5-18839" />
  </System>
  <EventData>
    <Data Name="BugcheckCode">159</Data>
    <Data Name="BugcheckParameter1">0x3</Data>
    <Data Name="BugcheckParameter2">0xfffffa80024bda20</Data>
    <Data Name="BugcheckParameter3">0xfffff800041bc518</Data>
    <Data Name="BugcheckParameter4">0xfffffa8006c2d010</Data>
    <Data Name="SleepInProgress">true</Data>
    <Data Name="PowerButtonTimestamp">0</Data>
  </EventData>
</Event>

Similar Messages

  • BAD_POOL_CALLER BSOD

    Hi,
    I am getting BSOD with Bad_pool_caller and I have no idea what is causing the problem. I had some BSODs on win8 earlier (now using 8.1 freshly installed) and get the same BSOD. I didn't get one using Windows 7.
    Please help and thank you,
    Adrian Cristea
    P.S. I cannot provide link to dumpfile "until we are able to verify your account".
    but I can do this:
    Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    Loading Dump File [C:\Windows\Minidump\030414-29343-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*C:\symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*C:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
    Machine Name:
    Kernel base = 0xfffff803`3ea1d000 PsLoadedModuleList = 0xfffff803`3ece1990
    Debug session time: Tue Mar  4 14:06:05.932 2014 (UTC + 2:00)
    System Uptime: 0 days 18:42:33.062
    Loading Kernel Symbols
    Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
    Run !sym noisy before .reload to track down problems loading symbols.
    Loading User Symbols
    Loading unloaded module list
    *                        Bugcheck Analysis                                   
    Use !analyze -v to get detailed debugging information.
    BugCheck C2, {b, ffffe00004bb2bd8, 0, ffffe00004bb38e8}
    *** WARNING: Unable to verify timestamp for klwfp.sys
    *** ERROR: Module load completed but symbols could not be loaded for klwfp.sys
    *** WARNING: Unable to verify timestamp for kneps.sys
    *** ERROR: Module load completed but symbols could not be loaded for kneps.sys
    *** WARNING: Unable to verify timestamp for IntcDAud.sys
    *** ERROR: Module load completed but symbols could not be loaded for IntcDAud.sys
    Probably caused by : NETIO.SYS ( NETIO! ?? ::FNODOBFM::`string'+797c )
    Followup: MachineOwner
    4: kd> !analyze -v
    *                        Bugcheck Analysis                                   
    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: 000000000000000b, type of pool violation the caller is guilty of.
    Arg2: ffffe00004bb2bd8
    Arg3: 0000000000000000
    Arg4: ffffe00004bb38e8
    Debugging Details:
    FAULTING_IP:
    NETIO! ?? ::FNODOBFM::`string'+797c
    fffff800`01963f67 90              nop
    BUGCHECK_STR:  0xc2_b
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    CURRENT_IRQL:  2
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    LAST_CONTROL_TRANSFER:  from fffff8033ecaf46e to fffff8033eb6aca0
    STACK_TEXT: 
    ffffd000`21fa9008 fffff803`3ecaf46e : 00000000`000000c2 00000000`0000000b ffffe000`04bb2bd8 00000000`00000000 : nt!KeBugCheckEx
    ffffd000`21fa9010 fffff800`01963f67 : ffffe000`067d8850 ffffe000`013a4030 ffffe000`065bc901 fffff800`01d46646 : nt!ExFreePoolWithTag+0x119e
    ffffd000`21fa90e0 fffff800`01bcbcb4 : ffffe000`0479a702 ffffe000`07d45e60 00000000`00000001 fffff800`01d471c5 : NETIO! ?? ::FNODOBFM::`string'+0x797c
    ffffd000`21fa9130 fffff800`01932501 : ffffe000`071937b0 00000000`00000001 00000000`00000000 00000000`00000000 : tcpip!FlpReturnNetBufferListChain+0xd5c54
    ffffd000`21fa9180 fffff800`0192f3e7 : ffffe000`013a4030 00000000`00000000 00000000`00000000 ffffe000`065bc9d0 : NETIO!NetioDereferenceNetBufferList+0xb1
    ffffd000`21fa91f0 fffff800`01afa55b : 00000000`00000011 fffff800`01c87100 00000000`00000000 00000000`00000000 : NETIO!NetioDereferenceNetBufferListChain+0x2a7
    ffffd000`21fa92b0 fffff800`01af749a : 00000000`00000000 ffffe000`013a4030 ffffe000`0234a000 00000000`00000000 : tcpip!IppReceiveHeaderBatch+0x55b
    ffffd000`21fa93e0 fffff800`01c2cbd8 : ffffe000`077e1b30 00000000`00000000 ffffe000`0230d901 fffff800`02491700 : tcpip!IppFlcReceivePacketsCore+0x68a
    ffffd000`21fa9760 fffff800`01d396d5 : ffffd000`21fa9b02 ffffe000`0108f710 ffffd000`21fa9a99 ffffd000`21fa4000 : tcpip!IppInspectInjectReceive+0x148
    ffffd000`21fa97c0 fffff803`3ead53f9 : ffffe000`0622ec10 00000000`00001abe ffffe000`0479a710 ffffe000`0479a710 : fwpkclnt!FwppInjectionStackCallout+0xe5
    ffffd000`21fa9850 fffff800`01d4a6b6 : fffff800`01d395f0 ffffd000`21fa9a20 00000000`00000010 00000000`00000001 : nt!KeExpandKernelStackAndCalloutInternal+0xe9
    ffffd000`21fa99a0 fffff800`026d6003 : ffffe000`0479a710 ffffe000`07d45dc0 fffff800`024a5500 ffffe000`07d45dc0 : fwpkclnt!FwpsInjectTransportReceiveAsync0+0x2ea
    ffffd000`21fa9ae0 ffffe000`0479a710 : ffffe000`07d45dc0 fffff800`024a5500 ffffe000`07d45dc0 ffffd000`21fa0002 : klwfp+0x5003
    ffffd000`21fa9ae8 ffffe000`07d45dc0 : fffff800`024a5500 ffffe000`07d45dc0 ffffd000`21fa0002 ffffffff`00000001 : 0xffffe000`0479a710
    ffffd000`21fa9af0 fffff800`024a5500 : ffffe000`07d45dc0 ffffd000`21fa0002 ffffffff`00000001 fffff800`00000003 : 0xffffe000`07d45dc0
    ffffd000`21fa9af8 ffffe000`07d45dc0 : ffffd000`21fa0002 ffffffff`00000001 fffff800`00000003 fffff800`00000000 : kneps+0x22500
    ffffd000`21fa9b00 ffffd000`21fa0002 : ffffffff`00000001 fffff800`00000003 fffff800`00000000 ffffe000`013a4030 : 0xffffe000`07d45dc0
    ffffd000`21fa9b08 ffffffff`00000001 : fffff800`00000003 fffff800`00000000 ffffe000`013a4030 fffff800`026d5e64 : 0xffffd000`21fa0002
    ffffd000`21fa9b10 fffff800`00000003 : fffff800`00000000 ffffe000`013a4030 fffff800`026d5e64 ffffe000`07d45dc0 : 0xffffffff`00000001
    ffffd000`21fa9b18 fffff800`00000000 : ffffe000`013a4030 fffff800`026d5e64 ffffe000`07d45dc0 ffffe000`018561f0 : IntcDAud+0x3
    ffffd000`21fa9b20 ffffe000`013a4030 : fffff800`026d5e64 ffffe000`07d45dc0 ffffe000`018561f0 fffff800`024a5540 : IntcDAud
    ffffd000`21fa9b28 fffff800`026d5e64 : ffffe000`07d45dc0 ffffe000`018561f0 fffff800`024a5540 fffff800`026d61be : 0xffffe000`013a4030
    ffffd000`21fa9b30 ffffe000`07d45dc0 : ffffe000`018561f0 fffff800`024a5540 fffff800`026d61be 00000000`00000000 : klwfp+0x4e64
    ffffd000`21fa9b38 ffffe000`018561f0 : fffff800`024a5540 fffff800`026d61be 00000000`00000000 ffffe000`07d45dc0 : 0xffffe000`07d45dc0
    ffffd000`21fa9b40 fffff800`024a5540 : fffff800`026d61be 00000000`00000000 ffffe000`07d45dc0 00000000`00000080 : 0xffffe000`018561f0
    ffffd000`21fa9b48 fffff800`026d61be : 00000000`00000000 ffffe000`07d45dc0 00000000`00000080 ffffe000`018561f0 : kneps+0x22540
    ffffd000`21fa9b50 00000000`00000000 : ffffe000`07d45dc0 00000000`00000080 ffffe000`018561f0 ffffe000`01955870 : klwfp+0x51be
    STACK_COMMAND:  kb
    FOLLOWUP_IP:
    NETIO! ?? ::FNODOBFM::`string'+797c
    fffff800`01963f67 90              nop
    SYMBOL_STACK_INDEX:  2
    SYMBOL_NAME:  NETIO! ?? ::FNODOBFM::`string'+797c
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: NETIO
    IMAGE_NAME:  NETIO.SYS
    DEBUG_FLR_IMAGE_TIMESTAMP:  5215f7e4
    IMAGE_VERSION:  6.3.9600.16384
    BUCKET_ID_FUNC_OFFSET:  797c
    FAILURE_BUCKET_ID:  0xc2_b_NETIO!_??_::FNODOBFM::_string_
    BUCKET_ID:  0xc2_b_NETIO!_??_::FNODOBFM::_string_
    ANALYSIS_SOURCE:  KM
    FAILURE_ID_HASH_STRING:  km:0xc2_b_netio!_??_::fnodobfm::_string_
    FAILURE_ID_HASH:  {2004c761-2953-7123-0c48-7c23e2563df0}
    Followup: MachineOwner

    AC
    We do need the actual DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.  
    We prefer at least 2 DMP files to spot trends and confirm the cause.
    Please follow our instructions for finding and uploading the files we need to help you fix your computer. They can be found here
    If you have any questions about the procedure please ask
    I strongly suspect your Kaspersky but can be certain until I see the DMP files.
    Wanikiya and Dyami--Team Zigzag

  • Bad_pool_caller BSOD windows 8.1 pro

    Hi. Several times a week i get BSOD about bad_pool_caller or irq_less... so I would kindly ask for help. here is one minidump.
    https://onedrive.live.com/redir?resid=FBD3C7D7FBA9DAD0%214817
    thanks!

    My apologies, I missed that.
    This is not software/driver, that's for sure. If it is software, the only drivers I can really see having this sort of DirectX related impact are the video card drivers. With this said, ensure you are on the latest drivers, and if you already are, try a few
    versions before, or perhaps the beta if available.
    In the 0xC2, the pool was valid, yet there was a 7 as the first parameter. This indicates that the current thread attempted to free the pool, which was already freed. We can see that it was a DirectX Kernel routine, because it calls into
    nt!ExFreePoolWithTag.
    The second bug check I've seen here, 0x139, was introduced due to security failure interruption. In your case, this was also caused by DirectX.
    To be absolutely sure this isn't a low-level driver possibly causing corruption, could you please do two things?
    1. Upload and paste the link to a kernel-dump. Kernel-dumps are located at C:\Windows and named MEMORY.DMP. If there is nothing there, you may need to enable generation of them -
    http://msdn.microsoft.com/en-us/library/windows/hardware/ff540128%28v=vs.85%29.aspx
    2. Enable Driver Verifier:
    Driver Verifier:
    What is Driver Verifier?
    Driver Verifier is included in Windows 8/8.1, 7, Windows Server 2008 R2, Windows Vista, Windows Server 2008, Windows 2000, Windows XP, and Windows Server 2003 to promote stability and reliability; you can use this tool to troubleshoot driver issues. Windows
    kernel-mode components can cause system corruption or system failures as a result of an improperly written driver, such as an earlier version of a Windows Driver Model (WDM) driver.
    Essentially, if there's a 3rd party driver believed to be at issue, enabling Driver Verifier will help flush out the rogue driver if it detects a violation.
    Before enabling Driver Verifier, it is recommended to create a System Restore Point:
    Vista - START | type rstrui - create a restore point
    Windows 7 - START | type create | select "Create a Restore Point"
    Windows 8/8.1 -
    http://www.eightforums.com/tutorials/4690-restore-point-create-windows-8-a.html
    How to enable Driver Verifier:
    Start > type "verifier" without the quotes > Select the following options -
    1. Select - "Create custom settings (for code developers)"
    2. Select - "Select individual settings from a full list"
    3. Check the following boxes -
    - Special Pool
    - Pool Tracking
    - Force IRQL Checking
    - Deadlock Detection
    - Security Checks (Windows 7 & 8)
    - DDI compliance checking (Windows 8)
    - Miscellaneous Checks
    4. Select  - "Select driver names from a list"
    5. Click on the "Provider" tab. This will sort all of the drivers by the provider.
    6. Check EVERY box that is NOT provided by Microsoft / Microsoft Corporation.
    7. Click on Finish.
    8. Restart.
    Important information regarding Driver Verifier:
    - If Driver Verifier finds a violation, the system will BSOD. To expand on this a bit more for the interested, specifically what Driver Verifier actually does is it looks for any driver making illegal function calls, causing memory leaks, etc. When and/if this
    happens, system corruption occurs if allowed to continue. When Driver Verifier is enabled, it is monitoring
    all 3rd party drivers (as we have it set that way) and when it catches a driver attempting to do this, it will quickly flag that driver as being a troublemaker, and bring down the system safely before any corruption can occur.
    - After enabling Driver Verifier and restarting the system, depending on the culprit, if for example the driver is on start-up, you may not be able to get back into normal Windows because Driver Verifier will detect it in violation almost straight away, and
    as stated above, that will cause / force a BSOD.
    If this happens, do not panic, do the following:
    - Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.
    - Once in Safe Mode - Start > Search > type "cmd" without the quotes.
    - To turn off Driver Verifier, type in cmd "verifier /reset" without the quotes.
    ・    Restart and boot into normal Windows.
    If your OS became corrupt or you cannot boot into Windows after disabling verifier via Safe Mode:
    - Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.
    - Once in Safe Mode - Start > type "system restore" without the quotes.
    - Choose the restore point you created earlier.
    -- Note that Safe Mode for Windows 8/8.1 is a bit different, and you may need to try different methods:
    5 Ways to Boot into Safe Mode in Windows 8 & Windows 8.1
    How long should I keep Driver Verifier enabled for?
    I recommend keeping it enabled for at least 24 hours. If you don't BSOD by then, disable Driver Verifier. I will usually say whether or not I'd like for you to keep it enabled any longer.
    My system BSOD'd with Driver Verifier enabled, where can I find the crash dumps?
    They will be located in %systemroot%\Minidump
    Any other questions can most likely be answered by this article:
    http://support.microsoft.com/kb/244617
    Regards,
    Patrick
    “Be kind whenever possible. It is always possible.” - Dalai Lama

  • T410 Win8 - BSOD when attaching external projector

    Hello,
    I have such a problem:
    my T410 with Windows 8 hangs as soon as I choose "Duplicate screen" option when I have attached external projecto to VGA port.
    Have you got any solutions? So far new NVidia drivers are not available.
    Best regards,

    Hi w454385
    How about updating your BIOS and driver with ThinkVantage System Update to see if the issue persist? If issue persist, contact Tech Support.
    Peter  | I  2013
    W520 (4284-A99)
    Does someone’s post help you? Give them kudos as a reward, as they will do better to improve | Mark it as solved if the solution works for you, so it could be reference for others in the future | Please do not email me regarding technical problems, you could post it in the forum
    =====================================
    Sound Enhancement (Post comments, share mixes, etc.)
    Dolby Home Theater v4 ; IdeaPad Slate Tablet

  • T410 NVIDIA BSOD caused by nvlddmkm.sys

    Hi all,
    I have lot of BSOD (1/week at least) caused by nvlddmkm.sys
    I have the latest driver according to lenovo update.
    I'm on Win7 x64.
    This is not caused by overheating I'm not running any game or 3d application,
    GPU idles ~60C.
    Could someone help me what to do?
    (Some time ago I tried the driver from NVIDIA page, but had the same experience, now I'm back on the Lenovo "official" driver.)

    hey nuri,
    could you try the following ?
    - uninstall the current driver you have installed
    - -restart your system and let Win7 install its generic driver
    - check if it happens again
    WW Social Media
    Important Note: If you need help, post your question in the forum, and include your system type, model number and OS. Do not post your serial number.
    Did someone help you today? Press the star on the left to thank them with a Kudo!
    If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"!
    Follow @LenovoForums on Twitter!
    Have you checked out the Community Knowledgebase yet?!
    How to send a private message? --> Check out this article.

  • Bad Pool Caller - Blue Screen of Death

    Windows Blue Screens of Death (BSoDs) happen whenever your computer encounters something it doesn’t know how to process, so it shuts itself down to prevent any damage. Sometimes BSoDs happen once and you don’t see them again when you restart — however, this isnt always the case and a BSoD may show up repeatedly.
    In this article we will look at issues causing a bad_pool_caller BSoD. What has happened is that a thread in the laptop's processor has made a bad pool request. This means that it’s asking to use resources that are unavailable, nonexistent, or in use by another thread. It could also mean that the pool header is corrupted — regardless of the particular error, it, like most BSoDs, is caused by driver issues.
    Drivers are what makes your computer work. Every device connected to your computer, and nearly every component inside it has a software driver that determines how Windows interacts with your device. When driver issues are encountered- which is fairly common on new operating systems like Windows 8 — it can cause a lot of problems, but, fortunately, sometimes there is an easy fix.
    Recently Connected and Installed Device
    Try to determine which device was last connected or installed before an error appeared. Often this can be a new peripheral device. Go to Device Manager (in the Control Panel) and find the driver for the recently connected peripheral device driver. From there, you can get Windows to search for updates, you can disable it, or you can uninstall it entirely. You can also disconnect the problem device and perform a system restore to before the device was connected and supporting software was installed.
    Recently Installed Program
    If your drivers aren’t the problem, a recently installed program may be the issue. If you can determine what program you installed that started this, uninstall it or perform a system restore to before the program was installed, and, after a restart, you should be good to go.
    System Restore
    Windows 7 and earlier
    Windows 8
    Any further issues that cannot be resolved may require your computer to be repaired.

    Every time we try to connect his Nano it causes the PC to crash with this Bad Pool Caller message.
    is the BADPOOLCALLER citing a specific file, Laurita? if so, what is it called? (exact spelling please.)
    if it's not citing a specific file, let's try getting a minidump to the Apple engineers for a look.
    To set up your machine to capture a minidump, right click on "My Computer", select "Properties", select the "Advanced" tab, select the "Startup and Recovery" Settings button, select "small memory dump" from the popup. When it crashes, look for the MiniDump file. It's usually in the folder "C:\WINDOWS\Minidump" and is called something like Mini<number>-<number>.dmp.
    Find that file and send it as an attachment to this email address.
    in the email to Roy, be sure to include the following information:
    - A link to the thread on Apple Discussions where the issue is being discussed
    - The username you are using in the thread
    - The version of iTunes you are using or trying to use
    - the version of Windows you are using (mention service packs)
    - A concise description of the issue you are seeing
    - The exact text of the error message you are seeing

  • BSOD: bad_pool_caller, while accessing Internet (youtube video, bgm, online games)

    Dear all readers of this writing,
    I truly want to get help or advice of solving my blue screen problem called "bad_pool_caller".
    Even, I nicknamed myself as "bad_pool_caller of death" because this caused several painful experiences while playing online games. Furthermore I am just a beginner about computers, so even this small problem makes me crazy.
    Let me introduce my problem and what I have done to solve this problem.
    -Symptoms
    this bad_pool_caller problem does not occur in offline. I found that none of problem occurs even while playing single player games over 7 hours like Far cry3 or bioshock infinite.
    Only while accessing Internet, this problem occurs.
    Especially, while playing any youtube videos
    even also other sort of video players, almost within 20 seconds, my computer shut down by bad_pool_caller error.
    and video's buffering is extremely slow.
    This is not just a Internet access problem I think, because I have another my own laptop and when I play youtube video of my laptop, it plays well.
    Also, when I enter a posting linked with bgm files, and try to install and play online games like starcraft 2, same things happens.
    (Although the frequency is lower than that of bad poor caller, Driver IRQL Less or equal error
    pops up while playing online games.
    During surfing Internet without these, bad pool caller error does not happen, so I think these three things(youtube video, listening bgm, online games) have much to do with my error.
    -What I have done
    I tried to solve by myself after I found this link.
    http://social.technet.microsoft.com/Forums/windows/en-US/e5e06b4e-6ed0-4eab-80ab-56c334f924be/windows-8-blue-screen-of-death-bsod-badpoolcaller?forum=w8itproperf
    I was very happy when I found this because the situation of the writer in upper link is almost same with that of mine.
    As the answer written, I format my C drive(Toshiba) and install windows 8.1 full version completely and upgraded graphic drive(GTX 760) and upgraded latetest windows 8.1 beta version upgrade of Wireless lan card drive(Netgear N900).
    However, you know, still this error occurs...
    -Guess the cause
    I know that most bad pool caller problem arise from Hard drive and memory corruption.
    But, my desktop PC is bought only a month ago and I bought quite a good SSD and HDD and Ram for playing high quality games.
    So I don't think the main cause is my SSD or HDD. My graphic card is also a new one.
    I suspect the cause is my network adapter, wireless lan card (USB) because this connects Internet access between my desktop PC and Louter.
    I am living in University dorm and using louter using with other students together.
    For getting Internet access of my desktop PC, I've bought wireless lan card (Netgear N 900) and I think this lan card causes problem such as windows 8.1 compatible
    But I fully upgraded and updated lan card driver and reinstalled several times and this N900 is not bad lan card so I don't determine this is the real cause.
    Here is link of my minidump record files.
    https://onedrive.live.com/#cid=CF99CE81DCA9027A&id=CF99CE81DCA9027A%21943
    (most error is about bad_pool_caller, but one is about Driver_IRQL_Less or Equal)
    and sorry for my poor English writing skills because I am international student arrived US only 3 months. If you have some things that cannot understand of my writing, just ask me again.
    Thanks for your help in advance.

    2: kd> lmvm NETIO
    start end module name
    fffff800`00800000 fffff800`00879000 NETIO (private pdb symbols)
    Loaded symbol image file: NETIO.SYS
    Mapped memory image file: Image path: \SystemRoot\system32\drivers\NETIO.SYS
    Image name: NETIO.SYS
    Timestamp: Thu Aug 22 19:37:08 2013 (5215F7E4)
    CheckSum: 0007A220
    ImageSize: 00079000
    File version: 6.3.9600.16384
    Product version: 6.3.9600.16384
    File flags: 0 (Mask 3F)
    File OS: 40004 NT Win32
    File type: 3.6 Driver
    File date: 00000000.00000000
    Translations: 0409.04b0
    CompanyName: Microsoft Corporation
    ProductName: Microsoft® Windows® Operating System
    InternalName: netio.sys
    OriginalFilename: netio.sys
    ProductVersion: 6.3.9600.16384
    FileVersion: 6.3.9600.16384 (winblue_rtm.130821-1623)
    FileDescription: Network I/O Subsystem
    LegalCopyright: © Microsoft Corporation. All rights reserved.
    Hi,
    As you said,you have updated your NIC driver.
    Did this issue happend when you used the wired LAN?
    I think this is related to wireless driver.
    I suggest that you try other wirless card to test this issue.
    Regards,
    Kelvin Xu
    TechNet Community Support

  • T410 Windows 7 Professional 64-Bit Install BSOD

    Hi, I am hoping someone can help me with resolving the issues I'm having trying to install Win7Pro 64-Bit
    I recently upgraded the memory on my Lenovo T410 Thinkpad from 4GB to 8GB under Windows 7 32-Bit but as I later found out that there wasn't a reliable hack to allow me to use the extra RAM so I decided to move all my files off the machine and then do a clean install of Windows 7 32-Bit.
    Unfortunately, I have had nothing but problems with the install, resulting in a BSOD every time. To give full details of what I have tried, see the list below:
    Downloaded a version of Win7Pro 64-Bit and created a bootable USB using Microsoft's bootable USB creation software
    Tried to boot and install the software
    Downloaded another 2 different versions of Win7Pro 64-Bit for COA installs from the Microsoft website and created the bootable USB again with each of these and tried the installation again.
    Used the Rufus software to create the bootabe USB drive (version rufus-1.4.9) and this gave the same results.
    I also used the Novicorp WinToFlash 0.8.0009 software to create the bootable USB but this made no difference.
    I have tried deleting the other partitions on the hard drive when given the option in the initial stages of the Win7 64-Bit setup but this made no difference.
    I then created a UEFI bootable USB drive and tried this and this had the same issues
    All in, I think I have tried the install about 10 times and have never managed to get anywhere with it.
    Results
    The furthest I have got with this is that the laptop boots from the USB and begins the install. It copies the Windows installation files over and then begins to expand the files. After successfully expending the files, it crashes with the BSOD with no real information on what can be causing the issue.
    On the penultimate installation attempt, the message that came up was a BSOD message saying "Ntfs.sys - Address FFFFF88001C....... etc"
    On the last attempt, I got the message "Windows installation encountered an unexpected error. Very that the installation sources are accessible, and restart the installation. Error code: 0x0000005"
    What I have ruled out
    The memory being an issue - this is because the machine seemed to work perfectly with the new memory modules in Win7 32-Bit and the issue only came up when running the 64-Bit versions
    Win7 64-Bit ISOs being corrupt - because this would not occur on all ISO files but may occur on one... I have done a check on the MD5 of the downloaded files and they are all as they should be. An example of one is ed15956fe33c13642a6d2cb2c7aa9749    X17-59186.iso.
    Research I have done
    I have looked in this forum and other sites and just cannot find a definitive answer on why I'm having the issue. I had seen something pointing to it possbly being due to me not using the UEFI boot option but trying this did not help.
    I researched what the "Error code: 0x0000005" meant and found a page on microsoft support asking me to check hardware as the issue could be related to a hard drive problem. I am currently running the hard drive diagnostic program and it's a slow process.
    Can anyone help me with this? I'm really stuck!
    Solved!
    Go to Solution.

    delprimero wrote:
    What I have ruled out
    The memory being an issue - this is because the machine seemed to work perfectly with the new memory modules in Win7 32-Bit and the issue only came up when running the 64-Bit versions
    If I were you I would still run Memtest+ on that RAM, run it overnight and allow several passes.
    Just to be 100% sure that the RAM isn't the culprit, (unless you already did that in which case my point would be moot)
    My 2 cents only...
    /L40SX/240/240X/2*340CSE/360PE/365XD/380D/380E/380XD/380Z/390/560E/560X/2*570/2*600/600E/750Cs/755C/760CD/760EL/760XD/770E/A20p/A22p
    A31/i1600/G40/R50p/R61i/S30/SL510/2*T22/4*T4x/11*T6x/6*T4x0x/6*T5x0/3*W5x0/W700/3*X2x/4*X3x/3*X4x/5*X6x/3*X6xT/10*X2xx/2*X200T/4*X30x/Z60m/3*Z61x
    Comunidad en Español  English Community  Deutsche Community   Русскоязычное Сообщество

  • BSOD or Restarting After Upgrading Ram On My T410

    Hi
    Recently I bought two new rams, DDR3 1333. After I Installed one of them, In boot time when windows 7 logo appears, BSOD happens (some times it restarts, depending on which ram slot i use). I've tried to find similar problems that could help me but I could'nt find a useful one. T410's  catalogue tells us that it is compatible with DDR3 1333 althought in my core i7 620M datasheet it tells just support 1066 but I know it should not to be a problem because the ram  downgrade its speed.
    Is there any solution or I should try to find a 1066 DDR3 ram?
    Thanks.

    Hello,
    Who is the manufacturer of your new ram, and what is the model number?  There are reports here from time to time of compatibility issues between some ThinkPads and some brands of RAM.  Corsair is often mentioned as a problem.
    Z.
    The large print: please read the Community Participation Rules before posting. Include as much information as possible: model, machine type, operating system, and a descriptive subject line. Do not include personal information: serial number, telephone number, email address, etc.  The fine print: I do not work for, nor do I speak for Lenovo. Unsolicited private messages will be ignored. ... GeezBlog
    English Community   Deutsche Community   Comunidad en Español   Русскоязычное Сообщество

  • Windows 8 Blue Screen Of Death (BSOD) BAD_POOL_CALLER

    Hi,
    I have been using windows 8 for the past week and have issues with BSOD appearing at random intervals and over the lat few days more frequently. After performing several rebuilds of the OS and carefully selecting Windows 8 supported applications i still
    continue to receive this error.
    I have reviewed the minidump files and the cause of the issues seems to be with ntoskrnl.exe
    I have contacted microsoft support and sony vaio support and they advise e to rebuild every time or restore the system to a previous working version. Unfortunately this does not resolve the issue and i find myself back at the beginning again.
    Could anyone advise on this issue and how to resolve?
    Thanks
    Matt

    hi, i am using windows 8 on sony waio and i am getting this error. I guess i am getting this error when i am using dongle of idea net setter(huwaie) but as you suugested i have the link to my newest dmp file. please go through it and suggest what can be
    done.
    update the huawei driver:
    * Bugcheck Analysis *
    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
    This is a very common bugcheck. Usually the exception address pinpoints
    the driver/function that caused the problem. Always note this address
    as well as the link date of the driver/image that contains this address.
    Some common problems are exception code 0x80000003. This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG. This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG. This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff880068210aa, The address that the exception occurred at
    Arg3: fffff88005be5568, Exception Record Address
    Arg4: fffff88005be4da0, Context Record Address
    Debugging Details:
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.
    FAULTING_IP:
    ewusbwwan+210aa
    fffff880`068210aa 440fb608 movzx r9d,byte ptr [rax]
    EXCEPTION_RECORD: fffff88005be5568 -- (.exr 0xfffff88005be5568)
    ExceptionAddress: fffff880068210aa (ewusbwwan+0x00000000000210aa)
    ExceptionCode: c0000005 (Access violation)
    ExceptionFlags: 00000000
    NumberParameters: 2
    Parameter[0]: 0000000000000000
    Parameter[1]: ffffffffffffffff
    Attempt to read from address ffffffffffffffff
    CONTEXT: fffff88005be4da0 -- (.cxr 0xfffff88005be4da0)
    rax=5757575757575757 rbx=0000000000000500 rcx=26b791d663d80000
    rdx=0000000000000000 rsi=0000000000000001 rdi=fffff980133c6bb5
    rip=fffff880068210aa rsp=fffff88005be57a0 rbp=fffff980133c6bbd
    r8=0000000000000000 r9=fffff88005be5400 r10=00000000ffffffff
    r11=0000000000000000 r12=0000000000000480 r13=0000000000000001
    r14=fffffa800858c000 r15=fffff980133c6b00
    iopl=0 nv up ei ng nz na po nc
    cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
    ewusbwwan+0x210aa:
    fffff880`068210aa 440fb608 movzx r9d,byte ptr [rax] ds:002b:57575757`57575757=??
    Resetting default scope
    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
    CURRENT_IRQL: 0
    ERROR_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.
    EXCEPTION_PARAMETER1: 0000000000000000
    EXCEPTION_PARAMETER2: ffffffffffffffff
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80012d5a168
    GetUlongFromAddress: unable to read from fffff80012d5a1f8
    ffffffffffffffff
    FOLLOWUP_IP:
    ewusbwwan+210aa
    fffff880`068210aa 440fb608 movzx r9d,byte ptr [rax]
    BUGCHECK_STR: AV
    LAST_CONTROL_TRANSFER: from fffff88005be0000 to fffff880068210aa
    STACK_TEXT:
    ewusbwwan
    0x0
    0x0
    ewusbwwan
    IMAGE_NAME: ewusbwwan.sys
    Loaded symbol image file: ewusbwwan.sys
    Image path: ewusbwwan.sys
    Image name: ewusbwwan.sys
    Timestamp: Thu Dec 23 05:18:25 2010
    "A programmer is just a tool which converts caffeine into code"

  • T410s bluetooth driver update causing BSOD

    A bluetooth driver update seems to be the cause of bluescreen crashes on my T410s running windows 7 64bit.  this has happened with all bluetooth driver updates I attempted to install in the past year.  a windows optional update installed a broadcom bluetooth driver which caused crashes. I unstalled the update and the system returned to normal. two lenovo updates had the same problem specifically: thinkpad bluetooth drivers 6.5.1.4500, and 6.2.1.3100.
    for anyone having similar problems, I found that using the older 6.2.0.9421 bluetooth driver has resolved the issue.

    If it's not broken, don't fix it. 
    Release notes mention anything that affects you?  No?  Skip it. 

  • BSOD with BAD_POOL_CALLER when uploading jpg using webutil

    Forms 9.0.4, WebUtil 1.05, JInitiator 1.3.1.13, Oracle Drive 10.2.0.0.3, client OS XP SP2
    I use the following code on a WHEN-BUTTON-PRESSED trigger to upload jpg images to the database:
    declare
       myfilename varchar2(240);
       r_upload boolean;
       v_fabase_code fabase.base%type;
    begin
       default_value('c:\','global.default_directory');
       myfilename := webutil_file.file_open_dialog(
          :global.default_directory
          ,null
          ,'JPG|*.jpg|TIFF|*.tiff'
          ,'Select image...');
       if myfilename is not null then
          :global.default_directory := substr(myfilename,1,instr(myfilename,'\',-1));
          r_upload := webutil_file_transfer.client_to_db_with_progress(
             myfilename
             ,'FADRAWING'
             ,'PROFILE'
             ,'FABASE_BASE = '''||:FADRAWING.FABASE_BASE||''' and lv_drawing_type_id = '||:fadrawing.lv_drawing_type_id
             ,'Uploading...'
             ,'File upload in progress...'
             ,false);
       end if;
       commit;
       execute_query;
    end;This works excellent, except the file to upload resides on a OCS drive to which I'm connected via Oracle Drive.
    Steps to reproduce:
    Press button,
    select a file on the OCS drive,
    after upload press the button again -> BSOD ("Blue screen of death")
    I can reproduce this on three different machines, all running XP SP2. If I default the starting directory of the file_open_dialog to 'c:\' instead of :global.default_directory then it works. If I default the starting directory of the file_open_dialog to the directory on the OCS drive I straightly get the BSOD after pressing the button.
    I know that the Oracle Drive is quite slow and often defers file actions, but would this cause a BSOD?
    Any comments are appreciated.
    Thanks
    Gerald

    CREATE TABLE FADRAWING
      FABASE_BASE         VARCHAR2(10 BYTE),
      LV_DRAWING_TYPE_ID  NUMBER(20)       ,
      PROFILE             BLOB,
    )Then create a simple form including webutil with a data block for the table and 2 items for FABASE_BASE and LV_DRAWING_TYPE_ID and a button for my code (comment the line
    v_fabase_code fabase.base%type;)
    Enter values and save. Then press the button as previously described.
    Gerald

  • Windows 8.1 BSOD Bad_Pool_Caller HELP Please

    Hi,I've been getting the BAD_POOL_CALLER.I recently installed windows 8.1.Here is my minidump link.please help me.https://skydrive.live.com/?cid=2af6aae703583497#cid=2AF6AAE703583497&id=2AF6AAE703583497%21148

    010714-38984-01.dmp 2014-01-07 7:01:11 PM BAD_POOL_CALLER 0x000000c2 00000000`00000007 00000000`00001205 00000000`00000000 ffffe000`05c15668 msrpc.sys msrpc.sys+1553769 Kernel Remote Procedure
    Call Provider Microsoft® Windows® Operating System Microsoft Corporation 6.3.9600.16384 (winblue_rtm.130821-1623) x64 ntoskrnl.exe+14dca0     C:\WINDOWS\Minidump\010714-38984-01.dmp 8 15 9600 300,912 2014-01-07
    7:03:53 PM 
    010714-43437-01.dmp 2014-01-07 6:56:05 PM BAD_POOL_HEADER 0x00000019 00000000`00000020 ffffe000`021dabe8 ffffe000`021dadb8 00000000`041dab68 mountmgr.sys mountmgr.sys+502769 Mount Point Manager Microsoft®
    Windows® Operating System Microsoft Corporation 6.3.9600.16384 (winblue_rtm.130821-1623) x64 ntoskrnl.exe+14dca0     C:\WINDOWS\Minidump\010714-43437-01.dmp 8 15 9600 300,912 2014-01-07
    6:57:27 PM 
    010714-40531-01.dmp 2014-01-07 4:51:29 PM BAD_POOL_CALLER 0x000000c2 00000000`00000007 00000000`00001205 00000000`00000000 ffffe000`04e7f848 NETIO.SYS NETIO.SYS+d769 Network I/O Subsystem Microsoft®
    Windows® Operating System Microsoft Corporation 6.3.9600.16384 (winblue_rtm.130821-1623) x64 ntoskrnl.exe+14dca0     C:\WINDOWS\Minidump\010714-40531-01.dmp 8 15 9600 300,912 2014-01-07
    4:52:48 PM 
    010614-48703-01.dmp 2014-01-06 9:32:06 PM BAD_POOL_CALLER 0x000000c2 00000000`00000007 00000000`00001205 00000000`00000000 ffffe000`05cd1758 mountmgr.sys mountmgr.sys+1161769 Mount Point Manager Microsoft®
    Windows® Operating System Microsoft Corporation 6.3.9600.16384 (winblue_rtm.130821-1623) x64 ntoskrnl.exe+14dca0     C:\WINDOWS\Minidump\010614-48703-01.dmp 8 15 9600 300,912 2014-01-06
    9:33:27 PM 
    010614-48140-01.dmp 2014-01-06 7:32:57 PM BAD_POOL_CALLER 0x000000c2 00000000`00000007 00000000`00001205 00000000`00010101 ffffe000`05e83178 msrpc.sys msrpc.sys+13a2769 Kernel Remote Procedure
    Call Provider Microsoft® Windows® Operating System Microsoft Corporation 6.3.9600.16384 (winblue_rtm.130821-1623) x64 ntoskrnl.exe+14dca0     C:\WINDOWS\Minidump\010614-48140-01.dmp 8 15 9600 300,912 2014-01-06
    7:34:12 PM 
    010614-45937-01.dmp 2014-01-06 7:27:52 PM BAD_POOL_CALLER 0x000000c2 00000000`00000007 00000000`00001205 00000000`90a5785b ffffe000`07885818 NETIO.SYS NETIO.SYS+d769 Network I/O Subsystem Microsoft®
    Windows® Operating System Microsoft Corporation 6.3.9600.16384 (winblue_rtm.130821-1623) x64 ntoskrnl.exe+14dca0     C:\WINDOWS\Minidump\010614-45937-01.dmp 8 15 9600 300,912 2014-01-06
    7:29:22 PM 
    010614-36890-01.dmp 2014-01-06 6:01:13 PM BAD_POOL_CALLER 0x000000c2 00000000`00000010 ffffe000`07ec61d8 00000000`12fffc90 ffffe000`07ec61f0 msrpc.sys msrpc.sys+11c6769 Kernel Remote Procedure
    Call Provider Microsoft® Windows® Operating System Microsoft Corporation 6.3.9600.16384 (winblue_rtm.130821-1623) x64 ntoskrnl.exe+14dca0     C:\WINDOWS\Minidump\010614-36890-01.dmp 8 15 9600 300,912 2014-01-06
    6:02:56 PM 
    010614-42046-01.dmp 2014-01-06 3:26:26 PM BAD_POOL_CALLER 0x000000c2 00000000`00000007 00000000`00001205 00000000`08860678 ffffe000`08860708 NETIO.SYS NETIO.SYS+d769 Network I/O Subsystem Microsoft®
    Windows® Operating System Microsoft Corporation 6.3.9600.16384 (winblue_rtm.130821-1623) x64 ntoskrnl.exe+14dca0     C:\WINDOWS\Minidump\010614-42046-01.dmp 8 15 9600 300,912 2014-01-06
    3:28:05 PM 
    010614-35687-01.dmp 2014-01-06 1:20:34 PM BAD_POOL_CALLER 0x000000c2 00000000`0000000b ffffe000`046d3698 00000000`046d3690 ffffe000`046d4488 NETIO.SYS NETIO.SYS+d769 Network I/O Subsystem Microsoft®
    Windows® Operating System Microsoft Corporation 6.3.9600.16384 (winblue_rtm.130821-1623) x64 ntoskrnl.exe+14dca0     C:\WINDOWS\Minidump\010614-35687-01.dmp 8 15 9600 300,856 2014-01-06
    1:22:27 PM 
    122913-45671-01.dmp 2013-12-29 1:00:11 PM BAD_POOL_CALLER 0x000000c2 00000000`00000007 00000000`00001205 00000000`00000000 ffffe000`0222b688 acpiex.sys acpiex.sys+157879f ACPIEx Driver Microsoft®
    Windows® Operating System Microsoft Corporation 6.3.9600.16384 (winblue_rtm.130821-1623) x64 ntoskrnl.exe+14dca0     C:\WINDOWS\Minidump\122913-45671-01.dmp 8 15 9600 300,912 2013-12-29
    1:01:33 PM 
    122913-35218-01.dmp 2013-12-29 11:37:06 AM BAD_POOL_CALLER 0x000000c2 00000000`00000007 00000000`00001205 00000000`00380036 ffffe000`07101858 NETIO.SYS NETIO.SYS+d79f Network I/O Subsystem Microsoft®
    Windows® Operating System Microsoft Corporation 6.3.9600.16384 (winblue_rtm.130821-1623) x64 ntoskrnl.exe+14dca0     C:\WINDOWS\Minidump\122913-35218-01.dmp 8 15 9600 300,912 2013-12-29
    11:38:17 AM 
    122913-47609-01.dmp 2013-12-29 11:21:50 AM BAD_POOL_CALLER 0x000000c2 00000000`00000007 00000000`00001205 00000000`d03a4001 ffffe000`0686c658 NETIO.SYS NETIO.SYS+d769 Network I/O Subsystem Microsoft®
    Windows® Operating System Microsoft Corporation 6.3.9600.16384 (winblue_rtm.130821-1623) x64 ntoskrnl.exe+14dca0     C:\WINDOWS\Minidump\122913-47609-01.dmp 8 15 9600 300,856 2013-12-29
    11:23:21 AM 
    122613-35343-01.dmp 2013-12-26 10:44:37 PM BAD_POOL_CALLER 0x000000c2 00000000`00000007 00000000`00001205 00000000`05961a10 ffffe000`05961b98 msrpc.sys msrpc.sys+10c179f Kernel Remote Procedure
    Call Provider Microsoft® Windows® Operating System Microsoft Corporation 6.3.9600.16384 (winblue_rtm.130821-1623) x64 ntoskrnl.exe+14dca0     C:\WINDOWS\Minidump\122613-35343-01.dmp 8 15 9600 300,912 2013-12-26
    10:45:45 PM 
    122613-55531-01.dmp 2013-12-26 10:30:13 PM BAD_POOL_HEADER 0x00000019 00000000`00000020 ffffe000`0224b9b8 ffffe000`0224c6a8 00000000`b4cff080 acpiex.sys acpiex.sys+f9d769 ACPIEx Driver Microsoft®
    Windows® Operating System Microsoft Corporation 6.3.9600.16384 (winblue_rtm.130821-1623) x64 ntoskrnl.exe+14dca0     C:\WINDOWS\Minidump\122613-55531-01.dmp 8 15 9600 300,912 2013-12-26
    10:31:52 PM 
    121913-47000-01.dmp 2013-12-19 7:31:36 PM DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000d1 00000000`00000028 00000000`00000002 00000000`00000000 fffff800`0197c43f CI.dll CI.dll+0 Code Integrity Module (Test) Microsoft®
    Windows® Operating System Microsoft Corporation 6.3.9600.16384 (winblue_rtm.130821-1623) x64 ntoskrnl.exe+14dca0     C:\WINDOWS\Minidump\121913-47000-01.dmp 8 15 9600 300,912 2013-12-19
    7:35:00 PM 

  • Bad_Pool_Caller - Audigy 2

    This is a new thread from an old one...easier to find the problem this way.
    I am having BSOD with error Bad_Pool_Caller with my Audigy 2 ZS card. I have had this problem ever since installing the new Audigy 2 ZS install replacement disc I got the other day. This installation is also wrecking havoc on my multi-monitor system. Basically I can't run my second video card when I install the new drivers or the Audigy software.
    My system is as follows:
    MSI K7N2 Delta2 Platinum MB
    AMD Athlon 3200+ 400mhz CPU
    Ram: 2 - 52MB PC 3200 running DDR at 400mhz
    GeForce4 4600 Ti AGP in 4x with fast writes Video card by PNY
    GeForce4 MX 4000 PCI by eVGA
    ATI TV Wonder Pro Remote edition
    Audigy 2 ZS Platinum
    A number of USB devices on USB 2.0 hubs
    So... I did a whole days worth, and I mean a whole day, of troubleshooting. Here is what I found...
    NOTE: I had my system working with my multi-monitor, TV tuner, and the Audigy card prior to the new install disc. I can't seem to find out which driver I was using though as I have not been able to get the system work work as it was before I had to do a clean install because of the BSOD.
    Using driver version .84. - EAX 4.0 Advanced HD driver update I am able to boot into windows XP Pro if I disable the sound card under safe mode first and then after I am in Windows I can enable the sound card. I am not able to install any Audigy software though with out causing an Error 0 on my PCI video card (the 2nd card). If I just try to boot straight into Windows I freeze immediately after the Windows XP logo or I get a BSOD Bad_Pool_Caller
    Using driver version .84.40, same problem as above.
    Using driver version .84.50, same problem as above.
    Using driver version .84.055, immediate BSOD Bad_Pool_Caller. Unable to use the trick above.
    I have tried all kinds of combinations of PCI slots. I have also disabled piece by piece the startup items and the services that are non-microsoft under MSCONFIG without any difference. I have also removed all the USB devices with difference. All of my MB drivers, graphics drivers, TV drivers, and my BIOS are all the latest editions, no beta versions. My system is not overclocked. I am not running a lot of programs at the moment as I just did a clean install of Windows XP Pro...yay for me...blah.
    I have to go into the registry after each driver test to remove ALL references to Creative, and I mean all or else the next driver immediately BSODs. You guys sure to leave a lot of mess in the registry even after I use the ZAP proggy thing you have.
    I am utterly frustrated beyond belief. I came back to Creative Sound after using a different sound card for a number of years because I read some good reviews. So far I am not too happy that I did.

    Ok, further research so to speak...
    I broke down and removed my PCI graphics card (the 2nd video card - GeForce MX 4000) and I still get the Bad_Pool_Caller screen immediately after the Windows XP logo on boot unless I disable the sound card prior to booting (through safe mode). I can then boot into Windows XP and reenable the sound card. It is a pain in the butt. This is all still without any software save the drviers installed.

  • Windows 8.1 Error Code (BAD_POOL_CALLER) "0x490"

    So I recently had a issue with my Windows 8 that prevented me from using my computer. I was happily editing an image on my Windows 8.1 PC when the whole computer crashed. So as anybody would I reset the computer to find a BSOD awaiting me on Bootup. The
    error code being "BAD_POOL_CALLER" which is from what I can understand a driver related issue. I could no access safe mode and windows repair was not picking up the issue. 
    So I then proceeded to format the hard drive using a Ubuntu (unmounted) disk with the application "Gparted" to format the hard drive to a Fat32 file system in a hope that whatever driver was causing the issue would be promptly deleted from the
    hard drive. Once I had formatted the HD to Fat32, I re-formatted it to NTFS to re-install a fresh version of Windows 7 on the HD. 
    So I installed this on to the HD with no issues at all, until it came to re-booting for the first time when I got the blue screen of death again but this time the cause was "0x049". So I let Windows try to repair the issue which unsurprisingly
    it could not figure out what was wrong. I have tried safe mode which does not work, I have tried all the "BootRec.exe" commands in the command prompt in system recovery options window. And nothing seems to help, does anybody know if this could be
    a problem with the hard drive as I tried it in another computer and it boots fine, so I am leading myself to believe it may be a problem with a BIOS driver?  

    You may have a BIOS problem, but there are no drivers for the BIOS.  The BIOS is the system firmware.  You will have to go to the support website of the computer/motherboard manufacturer to look for a BIOS update as Windows has nothing to do with
    the BIOS - that is the sole responsibility of the computer/motherboard manufacturer.
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”

Maybe you are looking for