Error Message "bad pool caller"

[Amitesh]

Sponsored Links

One of my cousin is facing a problem with a error message saying "Bad Pool Caller" after a blue screen appeared. But when trying to second time then it boots perfectly. This happens on several booting interval.

Can anyone help with this. As i don't want to spoil any of the part of my cousins computer.

Please Help...!

[Eric B]

Go into the System preferences and disable the Auto-restart after a crash.
This will leave the BSOD on the screen so you can catch the useless, cryptic
information and report it back here, so someone who knows about such things
can help.

Start>Control Panel>System>Advanced System Settings (note: may require
Administrator Privileges), then click on the Settings button under "Startup
and Recovery" and uncheck the box marked " Automatically restart."

OR

Guess the choice now is to do a clean install.

[Sam.D]

If I understand this correctly, Heidi this is a "bad pooler call" in setup--not on a Vista that's already on the box that we can fix via Win RE or some other method.

So your mission here is to get Vista installed.

The most common causes of your problem far and away statistically are a
problem with a truncated download at some point corrupting your ISO or a
problem with the burn.

1) Burn slowly. 4X should be fine. Some of this probably varies with the DVD writer and the media.

2) Make sure to select an ISO tab if there is one on the burning software,
and make sure to close the session on the burn.

3) Try this tweak on your Windows XP drive and burn from there:

Get to Dev Manager by typing devmgmt.msc in run/win key + pause break or
Rt.click My Computer>Prop>hardware tab>Device Manager if you like 5 steps
instead of one cmd. If you're set to PMI here change to DMO and if set to
DMO change to PMI using these 5 steps:

1) Click the + in front of IDE ATA/ATAPI Controllers
2) Double Click the Secondary IDE Controller
3) Click Advanced Settings
4) Under Device 1 Next to Transfer Mode choose DMA (or vise versa)>Click
OK
5) Reboot your System

6) Check your burn with a CRC utility and the links for this are below
including the direct Taco Bell link. It is very classy, sophisticated, and
very Wagner Edstrom/McCann Ericson esque for MSFT to adopt a Taco Bell url
for their public Beta 2 CRC checker. Rock on Redmond Rednecks.

Obtain CRC Utility for Vista Beta 2 Here: (The CRC utility is a way to check
the integrity of the ISO Burn which is probably where your problem
lies--it's #1 on the list):

Here's a link:

The CRC utility for Beta 2 is contained here (Scroll down to the bottom
under "Additional Information"

Microsoft Windows® Software Development Kit (SDK) for Beta 2 of Windows
Vista and WinFX Runtime Components

DOWNLOAD

Additional Information:

To verify that your download of an ISO file for the Windows SDK Beta 2 build
is not corrupt, download the CRC Utility. (Note: this is not a Microsoft
application. Use at your own risk.)

To run the CRC test, open a command prompt and run the utility. providing it
the name of the file (i.e. crc
c:\6.0.5383.1.1.WindowsSDK_Vista_idw.DVD.Rel.img) The CRC utility will run
two tests on the ISO: it will verify if the ISO is valid, and it will give
the AutoCRC signature for the file. The AutoCRC signature for the Windows
SDK Beta 2 ISO is 0x28434EEF. You should also confirm the size of the ISO is
correct: 1.14 GB (1,229,355,008 bytes).

If it fails any of these three tests, re-download the ISO.

[Macarenas]

A good first place to start is to try updating all of the drivers for your particular laptop. You will need to download them from Sony's web page.

Try also checking for bad memory using a program like Memtest86+.

[Raine]

Your problem is caused by Lavasoft Ad-Watch and their real-time monitoring drivers which have an invalid memory reference in them somewhere.

Uninstall Ad-Watch (w/ Windows Vista's "Windows Defender" you don't need a 3rd party adware monitoring program anyway) and that should take care of the problem.

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: 00000007, Attempt to free pool which was already freed
Arg2: 0000113d, (reserved)
Arg3: 900008c2, Memory contents of the pool block
Arg4: 824b0978, Address of the block of pool being deallocated

Debugging Details:
------------------

GetPointerFromAddress: unable to read from 825315ac
Unable to read MiSystemVaType memory at 825117e0



POOL_ADDRESS: GetPointerFromAddress: unable to read from 825315ac
Unable to read MiSystemVaType memory at 825117e0
824b0978

BUGCHECK_STR: 0xc2_7

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

LAST_CONTROL_TRANSFER: from 824e7ce8 to 824d8681

STACK_TEXT:
b53ab6bc 824e7ce8 000000c2 00000007 0000113d nt!KeBugCheckEx+0x1e
b53ab730 824acc25 824b0978 00000000 ba586780 nt!ExFreePoolWithTag+0x17f
b53ab760 a5a1c7ca 84f5d690 84fff468 b53ab8d4 nt!IopfCompleteRequest+0x227
WARNING: Stack unwind information not available. Following frames may be wrong.
b53ab770 82625101 00000914 00001634 00000001 AWRTPD+0x7ca
b53ab8d4 82622c86 84fff468 b53ab90c b53aba1c nt!PspInsertThread+0x56e
b53abd30 8248caaa 025ef69c 025ef680 02000000 nt!NtCreateUserProcess+0x6df
b53abd30 77800f34 025ef69c 025ef680 02000000 nt!KiFastCallEntry+0x12a
025ef958 00000000 00000000 00000000 00000000 0x77800f34


STACK_COMMAND: kb

FOLLOWUP_IP:
AWRTPD+7ca
a5a1c7ca ?? ???

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: AWRTPD+7ca

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: AWRTPD

IMAGE_NAME: AWRTPD.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4664104f

FAILURE_BUCKET_ID: 0xc2_7_AWRTPD+7ca

BUCKET_ID: 0xc2_7_AWRTPD+7ca

Followup: MachineOwner