bad_pool_caller

Whoops. I had another incident today. Seems in the evening if I leave my
computer on I end up with the blue screen of death.

Last time the problem showed 0x~c2 (0x~40, 0x~00, 0x8~00, 0x~00) with
comment that C:\windows\system32/imm32.dll is not valid.

This time it showed 0x~0A, 0x~16, 0x~02, 0x804G469A)

After the first incident I googled imm32.dll and one of the hits was
Registrybooster 2 which I purchased and ran. It showed over 400 registry
problems which it "corrected". I'd hoped that might take care of the
problem but today it puked again with the above info.

Anyone have help for me? I have downloaded 3 pages of info about bug check
0xC2:bad_pool_caller but don't really know what I'm reading. It suggests I
activate driver verifier to get more information. I printed it all out.
Before
I run the verifier commands can someone tell me exactly what that does.

As an additional question... I downloaded a new imm32.dll file sine it said
mine wasn't valid. It won't let me install it from normal operations. If I
enter the Safe mode can I do that? Any problems with replacing it?

"Panic" <smartwit@home.com> wrote in message
news:ebmDvmmbIHA.1188@TK2MSFTNGP04.phx.gbl...
> Whoops. I had another incident today. Seems in the evening if I leave
> my
> computer on I end up with the blue screen of death.
>
> Last time the problem showed 0x~c2 (0x~40, 0x~00, 0x8~00, 0x~00) with
> comment that C:\windows\system32/imm32.dll is not valid.
>
> This time it showed 0x~0A, 0x~16, 0x~02, 0x804G469A)
>
> After the first incident I googled imm32.dll and one of the hits was
> Registrybooster 2 which I purchased and ran. It showed over 400 registry
> problems which it "corrected". I'd hoped that might take care of the
> problem but today it puked again with the above info.
>
> Anyone have help for me? I have downloaded 3 pages of info about bug
> check
> 0xC2:bad_pool_caller but don't really know what I'm reading. It suggests I
> activate driver verifier to get more information. I printed it all out.
> Before
> I run the verifier commands can someone tell me exactly what that does.
>
>
>

Use System Restore to return your Windows installation to its state
prior to running the registry cleaner. Now you know why very few
experienced users recommend using these registry cleaners, they cause
more problems than purport to fix! There were absolutely no problems
with your registry, until you ran Registrybooster 2!

John

Panic wrote:

> Whoops. I had another incident today. Seems in the evening if I leave my
> computer on I end up with the blue screen of death.
>
> Last time the problem showed 0x~c2 (0x~40, 0x~00, 0x8~00, 0x~00) with
> comment that C:\windows\system32/imm32.dll is not valid.
>
> This time it showed 0x~0A, 0x~16, 0x~02, 0x804G469A)
>
> After the first incident I googled imm32.dll and one of the hits was
> Registrybooster 2 which I purchased and ran. It showed over 400 registry
> problems which it "corrected". I'd hoped that might take care of the
> problem but today it puked again with the above info.
>
> Anyone have help for me? I have downloaded 3 pages of info about bug check
> 0xC2:bad_pool_caller but don't really know what I'm reading. It suggests I
> activate driver verifier to get more information. I printed it all out.
> Before
> I run the verifier commands can someone tell me exactly what that does.
>
>
>

I had the bad_pool_caller problem prior to using Registrybooster 2. I made
a registry backup before running it and can return my registry to its
original state if I need to. Registrybooster 2 did seem to screw up the
ability for iTunes to program my iPod. iTunes locked up and wouldn't
program the iPod. I figured it must have something to do with my registry
so I downloaded a current iTunes and reinstalled it. It must have replaced
some lost registry links when it installed because it fixed the problem.

"John John" <audetweld@nbnet.nb.ca> wrote in message
news:e3Q5TumbIHA.5160@TK2MSFTNGP05.phx.gbl...
> Use System Restore to return your Windows installation to its state prior
> to running the registry cleaner. Now you know why very few experienced
> users recommend using these registry cleaners, they cause more problems
> than purport to fix! There were absolutely no problems with your
> registry, until you ran Registrybooster 2!
>
> John
>
> Panic wrote:
>
>> Whoops. I had another incident today. Seems in the evening if I leave
>> my
>> computer on I end up with the blue screen of death.
>>
>> Last time the problem showed 0x~c2 (0x~40, 0x~00, 0x8~00, 0x~00) with
>> comment that C:\windows\system32/imm32.dll is not valid.
>>
>> This time it showed 0x~0A, 0x~16, 0x~02, 0x804G469A)
>>
>> After the first incident I googled imm32.dll and one of the hits was
>> Registrybooster 2 which I purchased and ran. It showed over 400 registry
>> problems which it "corrected". I'd hoped that might take care of the
>> problem but today it puked again with the above info.
>>
>> Anyone have help for me? I have downloaded 3 pages of info about bug
>> check
>> 0xC2:bad_pool_caller but don't really know what I'm reading. It suggests
>> I
>> activate driver verifier to get more information. I printed it all out.
>> Before
>> I run the verifier commands can someone tell me exactly what that does.
>>
>>
>>
>

When I said it fixed the problem, I meant only the problem with iTunes vs my
iPod. The original problem of my computer shutting down with the
bad_pool_caller warning still exists. I'll repeat my indications right here
so there should be no confusion.

>>> Whoops. I had another incident today. Seems in the evening if I leave
>>> my
>>> computer on I end up with the blue screen of death.
>>>
>>> Last time the problem showed 0x~c2 (0x~40, 0x~00, 0x8~00, 0x~00) with
>>> comment that C:\windows\system32/imm32.dll is not valid.
>>>
>>> This time it showed 0x~0A, 0x~16, 0x~02, 0x804G469A)
>>>
>>> After the first incident I Googled imm32.dll and one of the hits was
>>> Registrybooster 2 which I purchased and ran. It showed over 400
>>> registry
>>> problems which it "corrected". I'd hoped that might take care of the
>>> problem but today it puked again with the above info.
>>>
>>> Anyone have help for me? I have downloaded 3 pages of info about bug
>>> check
>>> 0xC2:bad_pool_caller but don't really know what I'm reading. It suggests
>>> I
>>> activate driver verifier to get more information. I printed it all out.
>>> Before
>>> I run the verifier commands can someone tell me exactly what that does.



"Panic" <smartwit@home.com> wrote in message
news:%2330O%230obIHA.1188@TK2MSFTNGP04.phx.gbl...
>I had the bad_pool_caller problem prior to using Registrybooster 2. I made
>a registry backup before running it and can return my registry to its
>original state if I need to. Registrybooster 2 did seem to screw up the
>ability for iTunes to program my iPod. iTunes locked up and wouldn't
>program the iPod. I figured it must have something to do with my registry
>so I downloaded a current iTunes and reinstalled it. It must have replaced
>some lost registry links when it installed because it fixed the problem.
>
> "John John" <audetweld@nbnet.nb.ca> wrote in message
> news:e3Q5TumbIHA.5160@TK2MSFTNGP05.phx.gbl...
>> Use System Restore to return your Windows installation to its state prior
>> to running the registry cleaner. Now you know why very few experienced
>> users recommend using these registry cleaners, they cause more problems
>> than purport to fix! There were absolutely no problems with your
>> registry, until you ran Registrybooster 2!
>>
>> John
>>
>> Panic wrote:
>>
>>> Whoops. I had another incident today. Seems in the evening if I leave
>>> my
>>> computer on I end up with the blue screen of death.
>>>
>>> Last time the problem showed 0x~c2 (0x~40, 0x~00, 0x8~00, 0x~00) with
>>> comment that C:\windows\system32/imm32.dll is not valid.
>>>
>>> This time it showed 0x~0A, 0x~16, 0x~02, 0x804G469A)
>>>
>>> After the first incident I googled imm32.dll and one of the hits was
>>> Registrybooster 2 which I purchased and ran. It showed over 400
>>> registry
>>> problems which it "corrected". I'd hoped that might take care of the
>>> problem but today it puked again with the above info.
>>>
>>> Anyone have help for me? I have downloaded 3 pages of info about bug
>>> check
>>> 0xC2:bad_pool_caller but don't really know what I'm reading. It suggests
>>> I
>>> activate driver verifier to get more information. I printed it all out.
>>> Before
>>> I run the verifier commands can someone tell me exactly what that does.
>>>
>>>
>>>
>>
>
>