This is an update and redo to avoid confusion.

2-12 -08 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 (2-10-08) 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)

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.

UPDATE: 02-17-08 Today I ran verifier/standard and it showed a problem
with grfilter.sys with codes
0x~D6 (0x95973000, 0x~00, 0xF77119347, 0X~00)
GRFILTER.SYS ADDRESS F77119347 BASE AT F7717000. DATESTAMP 420112b3

I googled grfilter.sys and found it IS not a windows file and a possible
intruder that can be removed using add/remove.
It is in Windows\system32\drivers folder. Does that sound like a good idea?
I also downloaded a valid imm32.dll file and did a FC compare that showed no
difference between the new version I downloaded and the one I have in my
system32 folder.

Any help would be appreciated. Again my system works fine most of the time.
Only in the evenings when it is unused for several hours do I experience
that blue screen of death problem.

>This is an update and redo to avoid confusion.
>
>2-12 -08 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 (2-10-08) 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)
>
>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.
>
>UPDATE: 02-17-08 Today I ran verifier/standard and it showed a problem
>with grfilter.sys with codes
>0x~D6 (0x95973000, 0x~00, 0xF77119347, 0X~00)
>GRFILTER.SYS ADDRESS F77119347 BASE AT F7717000. DATESTAMP 420112b3
>
>I googled grfilter.sys and found it IS not a windows file and a possible
>intruder that can be removed using add/remove.
>It is in Windows\system32\drivers folder. Does that sound like a good idea?
>I also downloaded a valid imm32.dll file and did a FC compare that showed no
>difference between the new version I downloaded and the one I have in my
>system32 folder.
>
>Any help would be appreciated. Again my system works fine most of the time.
>Only in the evenings when it is unused for several hours do I experience
>that blue screen of death problem.
>

From what I can tell, grfilter.sys is related to the NDIS packet
redirector driver. Are your network card drivers up to date?

- Thee Chicago Wolf

"Thee Chicago Wolf" <.@.> wrote in message
news:(E-Mail Removed)...
> >This is an update and redo to avoid confusion.
>>
>>2-12 -08 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 (2-10-08) 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)
>>
>>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.
>>
>>UPDATE: 02-17-08 Today I ran verifier/standard and it showed a problem
>>with grfilter.sys with codes
>>0x~D6 (0x95973000, 0x~00, 0xF77119347, 0X~00)
>>GRFILTER.SYS ADDRESS F77119347 BASE AT F7717000. DATESTAMP 420112b3
>>
>>I googled grfilter.sys and found it IS not a windows file and a possible
>>intruder that can be removed using add/remove.
>>It is in Windows\system32\drivers folder. Does that sound like a good
>>idea?
>>I also downloaded a valid imm32.dll file and did a FC compare that showed
>>no
>>difference between the new version I downloaded and the one I have in my
>>system32 folder.
>>
>>Any help would be appreciated. Again my system works fine most of the
>>time.
>>Only in the evenings when it is unused for several hours do I experience
>>that blue screen of death problem.
>>
>
> From what I can tell, grfilter.sys is related to the NDIS packet
> redirector driver. Are your network card drivers up to date?
>
> - Thee Chicago Wolf
I have an isolated desktop machine using a continuous cable connection.
Would that have a network card driver?

>> From what I can tell, grfilter.sys is related to the NDIS packet
>> redirector driver. Are your network card drivers up to date?
>>
>> - Thee Chicago Wolf
>I have an isolated desktop machine using a continuous cable connection.
>Would that have a network card driver?

Huh? Continuous what? I don't know what that is. Go to Start >
Settings > Control Panel > System > Device Manager > Network Adapter

What does it say there? Click twice on the device listed there and
then click on the tab that says driver? What's the date and version?
Click the driver details button? What is the name of the file?

- Thee Chicago Wolf

Did you run a memory (RAM) test on the machine?

http://oca.microsoft.com/en/windiag.asp or http://www.memtest86.com/

Different bugcheck messages (0x0A & 0xC2) both of which can be caused by
bad RAM. Maybe you should eliminate hardware as a possible cause.

John

Panic wrote:

> This is an update and redo to avoid confusion.
>
> 2-12 -08 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 (2-10-08) 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)
>
> 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.
>
> UPDATE: 02-17-08 Today I ran verifier/standard and it showed a problem
> with grfilter.sys with codes
> 0x~D6 (0x95973000, 0x~00, 0xF77119347, 0X~00)
> GRFILTER.SYS ADDRESS F77119347 BASE AT F7717000. DATESTAMP 420112b3
>
> I googled grfilter.sys and found it IS not a windows file and a possible
> intruder that can be removed using add/remove.
> It is in Windows\system32\drivers folder. Does that sound like a good idea?
> I also downloaded a valid imm32.dll file and did a FC compare that showed no
> difference between the new version I downloaded and the one I have in my
> system32 folder.
>
> Any help would be appreciated. Again my system works fine most of the time.
> Only in the evenings when it is unused for several hours do I experience
> that blue screen of death problem.
>
>

"Thee Chicago Wolf" <.@.> wrote in message
news(E-Mail Removed)...
>>> From what I can tell, grfilter.sys is related to the NDIS packet
>>> redirector driver. Are your network card drivers up to date?
>>>
>>> - Thee Chicago Wolf
>>I have an isolated desktop machine using a continuous cable connection.
>>Would that have a network card driver?
>
> Huh? Continuous what? I don't know what that is. Go to Start >
> Settings > Control Panel > System > Device Manager > Network Adapter
>
> What does it say there? Click twice on the device listed there and
> then click on the tab that says driver? What's the date and version?
> Click the driver details button? What is the name of the file?
>
> - Thee Chicago Wolf

Thanks, Wolf. I went to intel(R) Pro/100 VE Network Connection and checked
for an updated driver. It installed an update and now is dated 12/6/2007,
version 8.9.47.0. We'll see if that helps. New details:
PCI\VEN_8086&DEV_1039&SUBSYS_4000107B&REV_82\4&29817089&0&40F0

At first I thought you were referring to a LAN card driver that's why I said
it is an isolated machine with internet cable.

FYI. It seems installing the updated driver for my Network Adapter has done
the trick. It's been several days now with no "blue screen of death" on my
computer. Thanks to all who helped. Thanks Wolf!

"Panic" <(E-Mail Removed)> wrote in message
news:ecSDzu$(E-Mail Removed)...
>
> "Thee Chicago Wolf" <.@.> wrote in message
> news(E-Mail Removed)...
>>>> From what I can tell, grfilter.sys is related to the NDIS packet
>>>> redirector driver. Are your network card drivers up to date?
>>>>
>>>> - Thee Chicago Wolf
>>>I have an isolated desktop machine using a continuous cable connection.
>>>Would that have a network card driver?
>>
>> Huh? Continuous what? I don't know what that is. Go to Start >
>> Settings > Control Panel > System > Device Manager > Network Adapter
>>
>> What does it say there? Click twice on the device listed there and
>> then click on the tab that says driver? What's the date and version?
>> Click the driver details button? What is the name of the file?
>>
>> - Thee Chicago Wolf
>
> Thanks, Wolf. I went to intel(R) Pro/100 VE Network Connection and
> checked for an updated driver. It installed an update and now is dated
> 12/6/2007, version 8.9.47.0. We'll see if that helps. New details:
> PCI\VEN_8086&DEV_1039&SUBSYS_4000107B&REV_82\4&29817089&0&40F0
>
> At first I thought you were referring to a LAN card driver that's why I
> said it is an isolated machine with internet cable.
>

>FYI. It seems installing the updated driver for my Network Adapter has done
>the trick. It's been several days now with no "blue screen of death" on my
>computer. Thanks to all who helped. Thanks Wolf!

Thanks for keeping us updated. This is good info to pass along to
others with the same issue.

- Thee Chicago Wolf