Hi, all!
This regards two problems, actually, and I don't know if they're related.
I was getting KMODE BSODs in win32k.sys constantly. I was using Diskeeper and ZoneAlarm. I finally came across a Usenet post regarding Norton Speedisk (I think) and ZoneAlarm and their incompatibility with W2K SP2's version of win32k.sys. I downgraded to the SP1 version and that error seems to have gone away.
Problem number two is bad_pool_caller errors. I uninstalled ZoneAlarm a long time ago so that's not an issue. I did, however, disable Diskeeper's set-it-and-forget-it feature and the bad_pool_caller seems to have gone away also, though only for about sixteen hours. It used to occur every four or so hours.
Can anyone associate bad_pool_caller errors with Diskeeper? I hate to give it up. I can only get minidumps when this happens so I don't have much information to work with to trace the problem directly to Diskeeper. For some reason my system won't dump all the memory when I get this error.
Thanks!
This regards two problems, actually, and I don't know if they're related.
I was getting KMODE BSODs in win32k.sys constantly. I was using Diskeeper and ZoneAlarm. I finally came across a Usenet post regarding Norton Speedisk (I think) and ZoneAlarm and their incompatibility with W2K SP2's version of win32k.sys. I downgraded to the SP1 version and that error seems to have gone away.
Problem number two is bad_pool_caller errors. I uninstalled ZoneAlarm a long time ago so that's not an issue. I did, however, disable Diskeeper's set-it-and-forget-it feature and the bad_pool_caller seems to have gone away also, though only for about sixteen hours. It used to occur every four or so hours.
Can anyone associate bad_pool_caller errors with Diskeeper? I hate to give it up. I can only get minidumps when this happens so I don't have much information to work with to trace the problem directly to Diskeeper. For some reason my system won't dump all the memory when I get this error.
Thanks!
