BAD_POOL_CALLER Error

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Since downloading the latest set of Microsoft Updates last week (19th
September), my Sagem Fast modem appears to be causing BAD_POOL_CALLER errors
(error code 000000c2, parameter1 00000007, parameter2 00000cd4, parameter3
020d0001, parameter4 884f88c0).

On start up, the modem appears to connect, but at a slightly slow line
speed. It will then fail to connect to my ISP server. On resetting the modem
I get the blue screen error

After a couple of restarts, the PC runs CHKDSK to counter an NTFS error at
which point everything is fine again... until I restart.

I didn't add any hardware last week (In fact not for 3 weeks without any
problems at all).

Any ideas ?
 
Dorftrottel said:
Since downloading the latest set of Microsoft Updates last week (19th
September), my Sagem Fast modem appears to be causing BAD_POOL_CALLER errors
(error code 000000c2, parameter1 00000007, parameter2 00000cd4, parameter3
020d0001, parameter4 884f88c0).

On start up, the modem appears to connect, but at a slightly slow line
speed. It will then fail to connect to my ISP server. On resetting the modem
I get the blue screen error

After a couple of restarts, the PC runs CHKDSK to counter an NTFS error at
which point everything is fine again... until I restart.

I didn't add any hardware last week (In fact not for 3 weeks without any
problems at all).

Any ideas ?

Try reinstalling the drivers for the modem, using the latest version
from the modem manufacturer's web site.

Good luck

Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2008)
On-Line Help Computer Service
http://onlinehelp.bc.ca

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."
 
Thanks for your response, I probably should have mentioned that I've already
done that ! Even tried the version in between, just in case.
 
That refers to hardware drivers,try running VERIFIER From run,you might
go to search at microsoft,type it in & get the info for it.
 
It is possibly due to the internal modem. Removing the internal modem should
resolved the issue.
 
Back
Top