installation bsod. Bad pool caller

Similar Questions

• Windows BSOD error 8 "Bad Pool Caller."

  Original title: Windows 8 BSOD

  Dear Windows people

  I got the dreaded Blue Screen of Death on my laptop Acer Aspire E1 - 750 cheap but good mood who gave error code 'Bad Pool Header', then 'Bad Pool Caller'. He couldn't get past this screen at start up. Using Windows 8.0, no devices (in fact, I was trying to plug a Kobo in the USB port, and does not recognize him, he was charging, led me to restart the laptop, to achieve the above error messages.

  Very surprised because it is relatively new, and the previous Amilo (Windows XP) I had, had 8 years of operation without BSOD.

  The files don't the zip.

  We need the DMP file because it contains the single record of the sequence of events that led to the accident, what drivers have been loaded, and what has been loaded.

  We prefer at least 2 DMP files to track trends and to confirm the cause.

  
  

  Please follow our instructions to find and download the files, we need to help you fix your computer. They can be found at here

  If you have any questions regarding the procedure, please ask

• Random - BSOD Bad Pool Header 0 x 00000019

  Dell laptop - Intel Core 2 Duo CPU 2.40 GHz/1.58 GHz with 2 GB of RAM

  Running Windows XP Professional with SP3

  A couple of weeks, I was getting a BSOD Bad pool Header 0 x 00000019.  Hard drive has been replaced, as according to the parameters of that time, the hard drive starts to die.

  Yesterday, I got the BSOD Bad Pool Header again.  The parameters are 0 x 00000019 (0x00000020, 0x86D1C990, 0x86D1C9A0, 0x1A02002).  Today, I got another, but the settings were 0 x 00000019 (0 x 00000020, 0x884482F8, 0 x 88448308, 0x1A020001).  I'm not able to find the answers.

  Any suggestions?

  It could be the hard drive or NTFS associated - let's get more information.
  Please provide additional information on your system:
  What is your system brand and model?
  What is your version of XP and the Service Pack?
  Describe your current antivirus and software anti malware situation: McAfee, Norton, Spybot, AVG, Avira
  !, Defender, ZoneAlarm, PC Tools, MSE, Comodo, etc..
  Click Start, run and enter in the box:
  Msinfo32
  Click on OK and when the system info summary appears, click on Edition, select all, copy, and then paste the information here.
  There will be some personal information (such as the user name and the name of the system), and anything that turns information private for you, simply delete the pasted information.
  For information about video drivers, expand components, click view, click on edit, select all, copy and then paste the information here.
  This will minimize back Q & A and eliminate guesswork.
  Download BlueScreenView here:
  http://www.NirSoft.NET/utils/blue_screen_view.html
  Unzip it and run it (BSV installs nothing) and let him complete the digitization of all of your files to dump.
  If you double-click on depressed, you will get information on it (including the field caused by the driver) and you should be able to spot the problem right away - especially if you see a model in landfills where Caused by field pilot is the same (beginning with this driver).
  Select (highlight) one or more of the most recent dump files by clicking on them and hold down the CTRL key to select multiple files.  Try to select only the most recent links that relate to your problem (perhaps five or six to start dump files).
  Click on file, save selected items and save information from the dumps to a text file on your desktop called BSOD.txt.  Open BSOD.txt with a text editor, copy the text and paste it in your next reply.
  Here's an example of report ASB to a single BSOD I initiated on purpose that indicates the cause of the accident as the pilot i8042prt.sys belonging to Microsoft Corporation:
  ==================================================
  Dump file: Mini062110 - 01.dmp
  Crash time: 21/06/2010-11:51:31
  Bug Check String: MANUALLY_INITIATED_CRASH
  Bug check code: 0x000000e2
  Parameter 1: 0x00000000
  Parameter 2: 0x00000000
  Parameter 3: 0x00000000
  Parameter 4: 0x00000000
  Caused by the driver: i8042prt.sys
  Caused by the address: i8042prt.sys + 27fb
  Description of the file: i8042 Port driver
  Product name: Microsoft® Windows® Operating System
  Company: Microsoft Corporation
  File version: 5.1.2600.5512 (xpsp.080413 - 2108)
  Processor: 32-bit
  Computer name:
  Full path: C:\WINDOWS\minidump\Mini062110-01.dmp
  ==================================================
  Send information from 5 last memory dumps.
  No matter what you use for protection against malware, please follow these steps:
  Download, install, update and do a full scan with these free malware detection programs:
  Malwarebytes (MMFA): http://malwarebytes.org/
  SUPERAntiSpyware: (SAS): http://www.superantispyware.com/
  It can be uninstalled later if you wish.

  Do not guess what the problem might be - understand and resolve it. I need YOUR voice and the points for helpful answers and propose responses. I'm saving for a pony!

• I connect to internet on my laptop using idea NET setter dongle it says the bad pool caller and will restart and restart

  Mr President, whenever I connect to internet on my laptop using idea NET setter dongle it says the bad pool caller and will restart and reboot... Here is the link to dupmp files https://onedrive.live.com/redir?resid=97d7886e9c3f12c6 mini! 104 & authkey =! AEE9bFVyH3uOKNg & ithint = % 2czip

  Hello

  Bugcheck 1000007E, {ffffffffc0000005, fffff8028a66f060, fffff8801b01b5c8, fffff8801b01ae00}

  WARNING: Unable to verify timestamp for ewusbwwan.sys
  ERROR: Module load completed but symbols can be loaded for ewusbwwan.sys
  Probably caused by: ewusbwwan.sys (ewusbwwan + 2bb5)

  ewusbwwan.sys dated 31/05/2011 driver Huawei Technologies Co.. Your USB dongle driver
  or a device attached to it.

  BugCheck C2, {b, fffff8029f4f8380, 0, fffff8029f4f8b90}

  WARNING: Unable to verify timestamp for c:\windows\system32\drivers\ewusbnet.sys
  ERROR: Module load completed but symbols can be loaded for c:\windows\system32\drivers\ewusbnet.sys
  Probably caused by: c:\windows\system32\drivers\ewusbnet.sys (ewusbnet + 2353)

  c:\windows\system32\drivers\ewusbnet.sys Ditto pilot.

  This driver update.

  Resolution of the blue screen in Windows 8/8.1 errors
  http://Windows.Microsoft.com/en-CA/Windows-8/resolve-Windows-blue-screen-errors

  ========================================================

  Check with HP Support, their drivers and documentation online and ask in their forums
  on known problems. Updated BIOS, drivers of low level chipset and on-board major
  and drivers of separate devices (see methods of updating driver below).

  BiosVersion = F.03
  BiosReleaseDate = 07/09/2012
  SystemManufacturer = Hewlett-Packard
  SystemProductName = PC HP Pavilion Sleekbook 14
  Family = 103C_5335KV G = N L = CON B = HP S = PAV X = Null
  SystemVersion = 087F1000003B5900000310100
  SystemSKU = C0P30PA #ACJ
  BaseBoardManufacturer = Hewlett-Packard
  BaseBoardProduct = 18F9
  BaseBoardVersion = 82,12

  HP support/troubleshooting & drivers
  http://welcome.HP.com/country/us/en/support.html

  Contact HP
  http://welcome.HP.com/country/us/en/contact_us.html

  HP forums
  http://h30434.www3.HP.com/PSG/

  -----------------------------------------------------------------------------------------------------

  This is my generic how updates of appropriate driver:

  This utility, it is easy see which versions are loaded: run DriverView - set the VIEW to hide
  Microsoft drivers - update those without drain in their names. (Also update BIOS and)
  low level chipset drivers.)

  -Free - DriverView utility displays the list of all device drivers currently loaded on your system.
  For each driver in the list, additional useful information is displayed: load address of the driver,
  Description, version, product name, company that created the driver and more.
  http://www.NirSoft.NET/utils/DriverView.html

  For drivers, visit manufacturer of emergency system and of the manufacturer of the device that are the most common.
  Control Panel - device - Graphics Manager - note the brand and complete model
  your video card - double - tab of the driver - write version information. Now click on
  Driver update (this can do nothing as MS is far behind the certification of drivers) - then right
  Click on - uninstall - REBOOT it will refresh the driver stack.

  Repeat this for network - card (NIC), Wifi network, sound, mouse, and keyboard if 3rd party
  with their own software and drivers and all other main drivers that you have.

  Now in the system manufacturer (Dell, HP, Toshiba as examples) site (in a restaurant), peripheral
  Site of the manufacturer (Realtek, Intel, Nvidia, ATI, for example) and get their latest versions. (Look for
  BIOS, Chipset and software updates on the site of the manufacturer of the system here.)

  Download - SAVE - go to where you put them - right click - RUN AD ADMIN - REBOOT after
  each installation.

  Always check in the Device Manager - drivers tab to be sure the version you actually install
  presents itself. This is because some restore drivers before the most recent is installed (sound card drivers
  in particular that) so to install a driver - reboot - check that it is installed and repeat as
  necessary.

  Repeat to the manufacturers - BTW in the DO NOT RUN THEIR SCANNER device - check
  manually by model.

  Look at the sites of the manufacturer for drivers - and the manufacturer of the device manually.
  http://pcsupport.about.com/od/driverssupport/HT/driverdlmfgr.htm

  Windows 8/8.1 - hardware and drivers
  http://Windows.Microsoft.com/en-us/Windows/hardware-drivers-help#hardware-drivers-help=Windows-8

  Windows 8/8.1 - Why Windows is not find my device?
  http://Windows.Microsoft.com/en-us/Windows-8/why-isn ' t-windows-conclusion-device

  Windows 8/8.1 - what happens if a device is not installed correctly
  http://Windows.Microsoft.com/en-us/Windows-8/what-device-isn ' t-installed-correctly

  ----------------------------------------------------------------------------------------

  Tests of memory intercept all errors such as memory do not match (possible even for sticks
  seemingly identical) and when the faster memory is placed in system behind the slower memory.
  So it is best to Exchange also sticks in and out to check for those, even if all the tests of memory do not
  show a problem.

  To test the RAM here control - run 4 + hours or so.<-- best="">
  www.memtest.org

  For the Windows Memory Diagnostic tool.

  WinKEY + W - type in the search-> memory box - find the top Memory Diagnostics tool
  list - and follow the prompts.

  How to run the tool in Windows 7 Memory Diagnostics (and 8/8.1) - in Windows 8 8.1
  the name is "Windows Memory Diagnostic".
  http://www.SevenForums.com/tutorials/715-memory-diagnostics-tool.html

  ======================================================

  After doing ALL the updates you can and if the problem persists, run DriverVerifier.
  (Remember to use the methods Windows 8 posted at the top of the first answer above).

  Driver Verifier can help find some BSOD problems:

  Using Driver Verifier to identify issues with Windows drivers for users advanced
  http://support.Microsoft.com/kb/244617

  How to solve the problems of driver in Windows Vista or 7.
  http://www.WinVistaClub.com/T79.html

  Using Driver Verifier
  http://msdn.Microsoft.com/en-us/library/ff554113 (v = VS. 85) .aspx

  How to use Windows drivers check Manager to solve problems and identify the Driver questions
  http://www.YouTube.com/watch?v=_VwIDD9xngM

  Driver Verifier
  http://www.techsupportforum.com/2110308-POST3.html

  Using Driver Verifier
  http://www.faultwire.com/solutions/using_driver_verifier.php

  How to use Windows drivers check Manager to solve problems and identify the Driver questions
  http://www.YouTube.com/watch?v=_VwIDD9xngM

  You can disable the driver verifier
  http://support.Microsoft.com/kb/244617

  WINDOWS key + X - RUN - type-> auditor/reset press ENTER to disable

  BlueScreenView lets you know if there is a driver specified in the error message. Also check with
  MyEventViewer at the blue screen.

  If DriverVerifier creates a minidump upload it and post the link here so we can analyze.

  I hope this helps.

  Rob Brown - Microsoft MVP<- profile="" -="" windows="" expert="" -="" consumer="" :="" bicycle=""><- mark="" twain="" said="" it="">

• We had a power outage in our area, the computer was on and running, got the blue screen of death with the following: __0x000000C2, 0 x 00000043, 0xD6C61000, 0 x 00000000, 0 x 00000000 BAD POOL CALLER

  We had a power outage in our area, the computer was on and running, got the blue screen of death with the following:
  0X000000C2, 0 X 00000043, 0XD6C61000, 0X00000000, 0X00000000 BAD POOL CALLER

  If you have not saved your data and you want to start the computer with Linux Livecd such as Knoppix and copy your data files on an external hard drive. It is a precautionary measure before the step follows because things happens. ;-)

  Then do a repair installation.

  http://www.michaelstevenstech.com/XPrepairinstall.htm

  If the repair installation does not work, test the equipment to ensure that none have been damaged during the blackout and then do a clean install of Windows.

  http://www.elephantboycomputers.com/page2.html#Hardware_Tshoot

  http://michaelstevenstech.com/cleanxpinstall.html - Clean install - how-to
  http://www.elephantboycomputers.com/page2.html#Reinstalling_Windows - what you will need at hand

  If all goes well, no equipment was damaged during the shutdown. Consider buying a power supply (battery backup). APC and Belkin are good; for a computer, simply spend about $60. MS - MVP - Elephant Boy computers - don't panic!

• I've been doing the msg of BSOD Bad Pool Header two days.

  Separated from this thread.

  We need the log files themselves (called a DMP files) because they contain the only record of the sequence of events that led to the accident, what drivers have been loaded, and what has been loaded.

  
  

  
  

  Please follow our instructions to find and download the files, we need to help you fix your computer. They can be found at here

  If you have any questions regarding the procedure, please ask

  
  

  I've been doing the msg of BSOD Bad Pool Header two days. I ran memtest and all the other tests I can think. I disabled neary all at startup and the frequency of error decreased, but it still occurs. Here is a link to the files minidump... help appreciated.

  https://www.dropbox.com/s/3esf2l07l2yvip6/minidump.zip?DL=0

  MVT

  You have several questions.

  1. you MUST update to win 8.1

  2. you have a 10 years old driver that needs to be removed associated wanatw4.sys WAN Miniport (ATW) of America Online, Inc.

  3 - your 3 year old AOL is held responsible for accidents

  Dumps memory to blame ATWPKT264. SYS - a component of your AOL software.

• Get the Bad Pool Caller

  I'm getting Bad pool caller error please help me I wil u give the silent file there is please help

  https://onedrive.live.com/redir?RESID=E8AA1ECAA522A19C! 19619 & authkey =! ALa_F2JBunaSF48 & ithint = the file % 2cdmp.

  Please help fasst

  PS: I have windows 10 build 10041

  These accidents were related to the corruption of memory (probably caused by a driver).

  Run these two tests to check your memory and find which driver is causing the problem.  Launch auditor.  You need not run memtest again unless you want to.
  

  If you are overclocking anything reset by default before running these tests.
  In other words STOP! If you don't know what it means that you're probably not  
  
  
  
  
  1-Driver Verifier (for full instructions, see our wiki here)
  
  2-Memtest. (You can learn more about running memtest here)

  
  

• Bad Pool Caller blue screen

  This is the second time I am getting blue screen when I put my laptop on the waiting screen and when I try to log on my laptop I get blue screen, reboot my computer with the Bad Pool Caller error, my driver all is up to date, can you please help?

  Hello

  Good job, please keep me updated.

  Kind regards

  Patrick

• Help with Bad Pool Caller BSOD (dump file is attached)

  Hello

  Just after I replaced the drive HARD laptop with an SSD and reinstalled Windows 8, I get random BSOD every week or so.

  Here is the link for the most recent minidump file skydrive: https://onedrive.live.com/redir?resid=9BA0B10B380B6294! 129 & authkey =! ABuY6dBEX5HA7Xw&ithint=file%2c.dmp

  If you need more, I can download those too.

  Any help would be greatly appreciated.

  Thank you!

  Work-PC

  This phenomenon was related to BdfNdisf6.sys Firewall NDIS6 BitDefender filter driver.  I would remove at least to test.

  Also and you need to update to win 8.1 as there are many, many bug fixes, it is more secure, etc.

  Microsoft (R) Windows debug 6.3.9600.17029 AMD64 Version
  Copyright (c) Microsoft Corporation. All rights reserved.

  Loading dump file [C:\Users\Ken\Desktop\071014-8468-01.dmp]
  The mini kernel dump file: only registers and the trace of the stack are available

  Symbol of validation of the path summary *.
  Location of response time (ms)
  C:\Users\Ken\Desktop OK

  Symbol of validation of the path summary *.
  Location of response time (ms)
  Deferred SRV * H:\symbols* http://msdl.microsoft.com/download/symbols
  Symbol search path is: SRV * H:\symbols* http://msdl.microsoft.com/download/symbols
  Executable search path is: C:\Users\Ken\Desktop
  Windows 8 Kernel Version 9200 MP (8 procs) free x 64
  Product: WinNt, suite: TerminalServer SingleUserTS
  By: 9200.16912.amd64fre.win8_gdr.140502 - 1507
  Computer name:
  Core = 0xfffff802 'f4011000 PsLoadedModuleList = 0xfffff802' f42ddaa0
  The debugging session: 22:22:57.777 Thu Jul 10 2014 (UTC - 04:00)
  System Uptime: 0 days 13:13:41.567
  Loading the kernel symbols
  .

  Press (cdb, ntsd, kd) ctrl-c or ctrl-BREAK (windbg) to drop the charges of symbol that take too much time.
  Run! SYM noisy before .reload to track symbols loading issues.

  ..............................................................
  ................................................................
  .........................................
  Loading user symbols
  Loading unloaded module list
  ..........
  *******************************************************************************
  *                                                                             *
  * Bugcheck analysis *.
  *                                                                             *
  *******************************************************************************

  Use! analyze - v to obtain detailed debugging information.

  BugCheck C2, {7 c, 11 1, 29001b, fffffa8010f31440}

  WARNING: Unable to verify timestamp for bdfndisf6.sys
  ERROR: Module load completed but symbols can be loaded for bdfndisf6.sys
  GetPointerFromAddress: unable to read from fffff802f4369168
  GetUlongFromAddress: cannot read fffff802f43691f8
  Probably caused by: bdfndisf6.sys (bdfndisf6 + bb33)

  Follow-up: MachineOwner
  ---------

  7: kd >! analyze - v
  *******************************************************************************
  *                                                                             *
  * Bugcheck analysis *.
  *                                                                             *
  *******************************************************************************

  BAD_POOL_CALLER (c2)
  The current thread is doing a bad pool request.  In general, it is an IRQL bad or double freeing the same allocation, etc.
  Arguments:
  Arg1: 0000000000000007, attempt to free pool which was already freed
  Arg2: 00000000000011c 1, (reserved)
  Arg3: blocking of the content of the memory of the 000000000029001b pool,
  Arg4: fffffa8010f31440, address of the block of pool is released

  Debugging information:
  ------------------

  DUMP_FILE_ATTRIBUTES: 0X8
  Generated Triage of the kernel image

  POOL_ADDRESS: non paged fffffa8010f31440

  FREED_POOL_TAG: TRPL

  BUGCHECK_STR: 0xc2_7_TRPL

  CUSTOMER_CRASH_COUNT: 1

  DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

  Nom_processus: vsserv.exe

  CURRENT_IRQL: 2

  ANALYSIS_VERSION: 6.3.9600.17029 (debuggers (dbg). 140219-1702) amd64fre

  LAST_CONTROL_TRANSFER: from fffff802f4283a6a to fffff802f406b540

  STACK_TEXT:
  fffff880 '1 a 143318 fffff802' f4283a6a: 00000000'000000 c 2 00000000'00000007 00000000'000011 c 1 00000000' 0029001b: nt! KeBugCheckEx
  fffff880 '1 a 143320 fffff880' 049b4b33: fffffa80'10f31440 fffffa80 '11-93700 fffffa80' 106a5b00 fffffa80 111 d 8701: nt! ExFreePool + 0 x 984
  fffff880 '1 a 143400 fffffa80' 10f31440: fffffa80 '11-93700 fffffa80' 106a5b00 fffffa80 111 d 8701 00000000 00000001': bdfndisf6 + 0xbb33
  "fffff880 '1 a 143408 fffffa80' 11a 93700: fffffa80'106a5b00 fffffa80 ' 111 d 8701 00000000 00000001' fffff880 ' 049b52bd: 0xfffffa80'10f31440
  fffff880 '1 a 143410 fffffa80' 106a5b00: fffffa80 111 d 8701 00000000 00000001 "fffff880 '049b52bd fffffa80' 0f0d59e0: 0xfffffa80'11 was 93700
  "fffff880'1 has 143418 fffffa80 111 d 8701: 00000000 ' 00000001 fffff880 '049b52bd fffffa80' 0f0d59e0 fffff880 ' 1a 143480: 0xfffffa80'106a5b00
  fffff880'1 a 143420 00000000 00000001': fffff880 ' 049b52bd fffffa80 '0f0d59e0 fffff880' 143480 fffffa80 1A ' 10f31440: 0xfffffa80 111 d 8701
  fffff880 '1 a 143428 fffff880' 049b52bd: fffffa80 ' 0f0d59e0 fffff880 '1 a 143480 fffffa80' 10f31440 fffff880 ' 1a 143450: 0 x 1
  fffff880 '1 a 143430 fffffa80' 0f0d59e0: fffff880 ' 143480 fffffa80 '10f31440 fffff880' 1a 1A 143450 fffff880 ' 1a 143450: bdfndisf6 + 0xc2bd
  fffff880 '1 a 143438 fffff880' 1a 143480: fffffa80 ' 10f31440 fffff880 '1 a 143450 fffff880' 1a 143450 fffff880 ' 1a 143450: 0xfffffa80'0f0d59e0
  fffff880 '1 a 143440 fffffa80' 10f31440: fffff880'1 has 143450 fffff880 '1 a 143450 fffff880' 1a 143450 00000000 00000000': 0xfffff880'1 has 143480
  fffff880 '1 a 143448 fffff880' 1a 143450: fffff880'1 has 143450 fffff880 '1 a 143450 00000000 00000000' fffff880' 049cfab0: 0xfffffa80'10f31440
  fffff880 '1 a 143450 fffff880' 1a 143450: fffff880'1 a 143450 00000000 00000000 fffff880 '049cfab0 fffff8a0' 0f171e02: 0xfffff880'1 has 143450
  "fffff880 '1 a 143458 fffff880' 143450 1a: 00000000 ' fffff880 00000000 '049cfab0 fffff8a0' 0f171e02 fffff802 ' f4282409: 0xfffff880'1 has 143450
  fffff880'1 a 143460 00000000 00000000': fffff880'049cfab0 fffff8a0 '0f171e02 fffff802' f4282409 00000000'00000010: 0xfffff880'1 has 143450

  STACK_COMMAND: kb

  FOLLOWUP_IP:
  bdfndisf6 + bb33
  fffff880'049b4b33?              ???

  SYMBOL_STACK_INDEX: 2

  SYMBOL_NAME: bdfndisf6 + bb33

  FOLLOWUP_NAME: MachineOwner

  MODULE_NAME: bdfndisf6

  Nom_image: bdfndisf6.sys

  DEBUG_FLR_IMAGE_TIMESTAMP: 52838010

  FAILURE_BUCKET_ID: 0xc2_7_TRPL_bdfndisf6 + bb33

  BUCKET_ID: 0xc2_7_TRPL_bdfndisf6 + bb33

  ANALYSIS_SOURCE: KM

  FAILURE_ID_HASH_STRING: km:0xc2_7_trpl_bdfndisf6 + bb33

  FAILURE_ID_HASH: {80fbf882-60f8-a069-dff6-ecf4434171d7}

  Follow-up: MachineOwner
  ---------

• Bad pool caller

  I have received a calling bad pool BSOD and that you run the driver verifier. I have attached a link to the DMP and Msinfo for my current set in place. Any help would be appreciated.

  Thanks in advance.

  https://onedrive.live.com/redir?RESID=FD9BA2FA39924B7F! 929 & authkey =! AIR0YAiST0RkaAM & ithint = the file % 2czip

  The pilot checked and related to Avast.  I would remove it and USE MSE in its place.

  Avast can be a cause of BSOD.

  Please delete and replace by Microsoft Security Essentials at LEAST FOR TESTER
  http://files.avast.com/files/eng/aswclear5.exe

  http://www.Microsoft.com/security_essentials/

• BSOD bad pool header

  I get the error Bad Pool Header 19-12 x I minidumps for, in the last 2 months. How can I publish a minidump here to determine what is my problem?

  I updated my drivers and it still continues and I ran CCleaner... the "fix" that is offered anywhere on the internet.

  We have some progress.

  This accident was related to the device driver wireless Extensible athrx.sys from Atheros Communications, Inc.  Before the release of win 7 is yours.  I would update to the latest version available.

  I notice that you have of moy.
  AVG can be a cause of BSOD.

  Please delete and replace by Microsoft Security Essentials at LEAST FOR TESTER

  http://www.Avg.com/ww-en/utilities'] download tools and utilities | AVG worldwide

  http://www.Microsoft.com/security_essentials/ "] Microsoft Security Essentials - free Antivirus for Windows"

• Bad Pool Caller error (Windows 8) - including the link to my Minidump file

  Hello!

  I recently received 4 blue screens; the first three were probably related to Avast, so I uninstalled ( Memory_managementerror)

  Later, says error Bad_Pool_Caller

  I have already travelled through further discussion, so here is the link to my Minidump file

  https://www.dropbox.com/s/sinr1qwyjjj43qw/dump.zip

  Also, here are the results of WhoCrashed

  
  

  Thank you very much!

  
  

  (Local) information system
  computer name: KISS
  Windows version: Windows 8, 6.2, build: 9200
  Windows dir: C:\Windows
  CPU: GenuineIntel Intel (r) Core i7-3630QM CPU @ 2.40 GHz Intel586, level: 6
  8 logical processors, active mask: 255
  RAM: 21425922048 total
  VM: 2147352576, free: 1917325312

  Crash Dump Analysis
  Crash dump directory: C:\Windows\Minidump

  Dumps are enabled on your computer.

  Wednesday, October 29, 13 16:57:33 this computer crashed
  crash dump file: C:\Windows\Minidump\102913-8937-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x7A040)
  Bugcheck code: 0xC2 (0x7, 0x11C1, 0x11AC6DA0, 0xFFFFFA8011AC6DB0)
  Error: BAD_POOL_CALLER
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that the current thread is doing a bad pool request.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Wednesday, October 29, 13 16:57:33 this computer crashed
  crash dump file: C:\Windows\memory.dmp
  This was probably caused by the following module: gdi32.sys (GDI32! D3DKMTPresent + 0xA)
  Bugcheck code: 0xC2 (0x7, 0x11C1, 0x11AC6DA0, 0xFFFFFA8011AC6DB0)
  Error: BAD_POOL_CALLER
  Bug control description: This indicates that the current thread is doing a bad pool request.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  A third-party driver has been identified as the likely cause of the system error. It is suggested that you search for an update the following driver: gdi32.sys.
  Google search: gdi32.sys BAD_POOL_CALLER

  Wednesday, October 29, 13 12:15:41 CEST your computer crashed
  crash dump file: C:\Windows\Minidump\102913-13828-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x7A040)
  Bugcheck code: 0x1A (0xFFFFF70001080000, 0x1C03, 0 x 5003, 0x1C0400003846)
  Error: MEMORY_MANAGEMENT
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that an error occurred serious memory management.
  This could be a case of corruption of memory. The corruption of memory more often happens because of software errors in the defective drivers buggy, not because of RAM modules.

  
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Wednesday, October 29, 13 11:42:59 AM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\102913-23578-01.dmp
  This was probably caused by the following module: ntfs.sys (Ntfs + 0x40C90)
  Verification of error code: 0 x 24 (0xFFFFF8800ACAE0C8, 0xFFFFF8800ACAD900, 0xB50019060B, 0xFFFFF8800197C552)
  Error: NTFS_FILE_SYSTEM
  file path: C:\Windows\system32\drivers\ntfs.sys
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT file system driver
  Bug control description: This indicates there is a problem in the NTFS file system.
  The accident took place in a standard Microsoft module. Your system configuration is perhaps incorrect. Maybe this problem is caused by another driver on your system which cannot be identified at this time.

  Tuesday, October 28, 13 18:22:31 GMT crashed your computer
  crash dump file: C:\Windows\Minidump\102813-13562-01.dmp
  This was probably caused by the following module: dxgmms1.sys (dxgmms1 + 0x263E7)
  Bug check code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF880049B53E7, 0xFFFFF8800975A4E8, 0xFFFFF88009759D20)
  Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
  file path: C:\Windows\system32\drivers\dxgmms1.sys
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: DirectX Graphics MMS
  Bug control description: This indicates that a system thread threw an exception who did not catch the error handler.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in a standard Microsoft module. Your system configuration is perhaps incorrect. Maybe this problem is caused by another driver on your system which cannot be identified at this time.

  Conclusion
  5 dumps were found and analysed. A third-party driver has been designated to be the cause of breakdowns of the system on your computer. It is strongly recommended that you check the updates for these drivers on their corporate Web sites. Click on the links below to search with Google for updates these drivers:

  Gdi32.sys

  These accidents were related to the corruption of memory (probably caused by a driver).

  Run these two tests to check your memory and find which driver is causing the problem.

  If you are overclocking anything reset by default before running these tests.
  In other words STOP!  
  If you don't know what it means that you're probably not

  1-Memtest. (You can learn more about running memtest here)
  Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Get it here
  Boot from the CD and let it run at least 5 or 6 passes.
  Remember, anytime Memtest reports errors, it can be bad RAM or a bad motherboard slot.
  Test the sticks individually and if you find a good, test it in all slots.

  If a well-known stick fails in a card mother slot but not an another is probably the slot.
  
  
  2-Driver Verifier (for full instructions, see our wiki here)
  Using Driver Verifier is a dubious proposition.
  Most of the time it will crash and it will tell you what is the driver, but sometimes, it will crash and will not tell you the driver.
  Sometimes it will crash until you can connect to Windows. If you can't mode without failure, then you will have to resort to editing the registry offline to disable driver verifier.

  I suggest that you first back up your data and make sure you have access to another computer so you can contact us in case of problems.
  Then do a system restore point (so you can restore the system using the functionality of Vista/Win7 Startup Repair).
  
  Here is the procedure:
  Go to Start and type "auditor" (without the quotes) and press enter
  Select "create of the custom settings (for code developers)" and click "Next".

  Select "Select individual settings from the list complete" and click "next".
  Select all elements EXCEPT FOR "Low Resource Simulation"
  Do not check to win 8 Concurrency stress test and the verification of the conformity of DDI, click "next".
  Select "Select the driver names from a list", then click on "next".
  Select all drivers NOT supplied by Microsoft, and then click "Next".
  Select 'Finish' on the next page.
  
  Restart the system and wait as he crashed to blue screen.
  Continue to use your system normally and if you know what are the causes of the crash, do it several times.
  The objective here is to get the system crash because Driver Verifier is stressing out the drivers.
  If it is not planted for you, then let it run for at least 36 hours of continuous operation.
  
  If you are unable to Windows because it crashes too early, try safe mode.
  If you can't mode without fail, try to use the system from the installation DVD restore to bring the system back to the previous point of restoration that you created.

• Error BSOD Bad Pool Header - Satellite C50-A-157

  Hello

  I get a blue screen bad pool header error.

  It started after I updated some drivers, was one of the drivers does not work properly since, it's the IWD bus enumerator, it has a yellow exclamation point and this error, Windows cannot load the driver for this hardware device. The driver may be corrupted or missing. (Code 39)

  I can't find a solution for this driver so I had to disable, I think that it is related to the bad pool header as I get it a lot more since the update. This often happens when I'm on the web, just from crashes and goes into the blue screen.

  Any help would be appreciated.

  Thank you.

  Hello

  Can you please tell us which laptop model you use, which are part of troubled hardware and drivers are updated.

  Please post some specific info. Your ad is fairly general.

• BSOD: DRIVER IRQL NOT LESS or EQUAL and BAD POOL CALLER.

  Since that destructive, reinstall Windows Vista after problems with the KSOD, my computer now works well except for one glaring problem.

  Stop at random, almost every day, I get a BSOD with one of these messages.

  I've done tests memory with Memtest86 and integrated utility clean Windows where all showed that my memory has no problems. In addition, according to the results of other tests, my other hardware is fine as well.

  I am at a loss to the cause.  I'll upload some files to dump here if necessary.

  I removed the COMODO firewall and re-enabled the firewall of Windows (temporary) and I did not get a BSOD again.  My computer sat for several hours.

• Help request for C:\windows\system32\config\system / Bad Pool Caller / on xp

  . Hi, I have xp sp3, and after the established cat off for switching on the pc appears the error message mentioned.  I tried f8 for boot from the sp3 installation CD and ends up with the BAD_POOL_CALLER message.  That's why I can't launch 'r' for recovery apparently safe mode.  Any suggestion would be appreciated before gratefully the cat gets it... Thank you.

  Well, if you can start on some CDs and get to a command prompt on your HARD drive, you should be able to implement the suggestion of KB307545 of Microsoft Support Engineer Halima S and "check if it helps" (I don't think it will be).

  Here's how you describe / have symptoms that indicate the need to use KB307545:

  Zero

  If you want to make a bootable CD from the Console of the Recovery XP (no XP media required) and then to implement the proposal of Microsoft Support Enginner Halima S and check if it helps.

  Here's how:

  Boot into the Recovery Console Windows using an XP bootable installation CD.

  If you have no XP bootable media (or aren't sure you have) create a bootable XP Recovery CD of Console and do not forget.

  This is not the same as recovery disks that might have come with the acquisition of the system store.

  You can make a bootable Recovery Console CD by downloading an ISO file and burn it to a CD.

  The ISO bootable image file you need to download is called:

  xp_rec_con. ISO

  Download the ISO from here:

  http://www.mediafire.com/?ueyyzfymmig

  Use a new CD and this simple and free program to burn your ISO file and create your bootable CD:

  http://www.ImgBurn.com/

  When you install ImgBurn, DO NOT install the Ask toolbar.

  Here are some instructions for ImgBurn:

  http://Forum.ImgBurn.com/index.php?showtopic=61

  It would be a good idea to test your bootable CD on a computer running.

  You may need to adjust the computer BIOS settings to use the CD-ROM drive as the first device to boot instead of the hard drive.  These adjustments are made before Windows tries to load.  If you miss it, you will need to restart the system again.

  When you start on the CD, follow the instructions:

  Press any key to boot from CD...

  Installing Windows... going to pronounce.

  Press 'R' to enter the Recovery Console.

  Select the installation that you want to access (usually 1: C:\WINDOWS)

  You may be asked to enter the password (usually empty).

  You should be in the folder C:\WINDOWS.  It's the same as the

  C:\Windows folder that you see in Solution Explorer.

  The Recovery Console allows base as file commands: copy, rename, replace, delete, chkdsk, fixboot, fixmbr, cd, etc.

  For a list of the commands in the Recovery Console, type help at the prompt of commands or read on here XP Recovery Console:

  http://www.Microsoft.com/resources/documentation/Windows/XP/all/proddocs/en-us/recovery_console_cmds.mspx?mfr=true

  When you get into RC, is if you can run a chkdsk/r...  Here's how:

  A good idea before you start things must first verify the integrity of your file system by using the chkdsk command.

  In the command prompt window, run the chkdsk command on the drive where Windows is installed to try to fix any problems on the afflicted player.

  Running chkdsk is fine, even if he finds no problem.  It won't hurt anything to run it.

  Assuming your boot drive is C, run the following command:

  CHKDSK C: /r

  Let chkdsk finish to correct the problems, he could find.

  It may take a long time for chkdsk complete or they seem to be "stuck".  Be patient.  If the HARD drive led blinks always, chkdsk is something.  Keep an eye on the amount of the percentage to be sure that it is still making progress.  It may even seem to go back sometime.

  You must run chkdsk/r again until it finds no error to correct.

  Remove the CD, and then type "exit" to exit the RC and restart the computer.

  You have not to set the BIOS to boot the disk HARD since the CD won't be.