WIN2K BSOD: BAD_POOL_CALLER

[cirrus1]

Once in a while like 3 or 4 days and very random my computer BSOD's with a BAD_POOL_CALLER error. This is a thing that have just come up. I don't recall doing any changes to the hardware and driver configuration.

It comes unprovoked even when the computer is idling, and not more often when gaming.

I've done some research and the only thing I have come up with, is that it have been seen with the combination of playing the game HalfLife on the Iwill KA266 M/B.

For reference I'm using an A7V 1.01.

My guess is that it's video driver related...but as always other thoughts are welcome

I'm reformatting the computer soon anyway but I'd like to know what this is

Thanks

 

[scotters]

MS KB shows only one direct reference:


<< &quot;Stop 0xC2 BAD_POOL_CALLER&quot; Error Message on Print Server
SYMPTOMS
A Windows 2000-based print server may randomly stop responding (hang) with a &quot;Stop&quot; error message on a blue screen. The stop code is 0xC2, and the first parameter is always 0x00000007.

When this occurs, you may not be able to log on until after several &quot;Stop&quot; errors and restarts. The System event log on the server will contain many printing-related error messages.



CAUSE
When it is processing some kinds of print jobs, Win32k.sys might doubly free a pool. This causes the &quot;Stop&quot; error message.



RESOLUTION
To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, please see the following article in the Microsoft Knowledge Base:

Q260910 How to Obtain the Latest Windows 2000 Service Pack






STATUS
Microsoft has confirmed this to be a problem in the Microsoft products that are listed at the beginning of this article.

This problem was first corrected in Windows 2000 Service Pack 1.

>>

 

[scotters]

What is shown in the event viewer?

 

[cirrus1]

It seems like it haven't logged the event even though it is instructed to.

Found this other thing though:

-------------------------------------------
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7026
Date: 02-06-2001
Time: 18:54:18
User: N/A
Computer: ANDREAS
Description:
The following boot-start or system-start driver(s) failed to load:
i8042prt
-------------------------------------------
Only thing is that this error occurs at every startup and I seriously doubt that a failing driver would cause random BSOD's like this.

After some looking I've found that this is the driver that controls usually controls my PS/2 keyboard and mouse which I now have on the USB. But when the BSOD's started comming I still had my K/B and mouse on the PS/2.

 

[cirrus1]

A little note: I use SP2

 

[scotters]

MS Knowledgebase has tons of references to i8042prt...all seem to point to a USB issue with keyboard or mouse. Are yours by change Logitech?

 

[cirrus1]

Yep. Logitech Cordless Itouch K/B and cordless Mouseman

 

[scotters]

MS KB link at MS
RESOLUTION
WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

For information about how to edit the registry, view the &quot;Changing Keys and Values&quot; Help topic in Registry Editor (Regedit.exe) or the &quot;Add and Delete Information in the Registry&quot; and &quot;Edit Registry Data&quot; Help topics in Regedt32.exe. Note that you should back up the registry before you edit it. If you are running Windows NT or Windows 2000, you should also update your Emergency Repair Disk (ERD).

The fastest way to get mouse and keyboard functionality back is to use Recovery Console to replace the file, and then use Registry Editor to change the reference to the correct file:

Start the computer to Recovery Console.


Change to the %SystemRoot%\System32\Drivers folder.


Type the following lines, pressing ENTER after each line:


ren l8042prt.sys l8042prt.lgt
copy i8042prt.sys l8042prt.sys
disable lkbdfltr
disable lmoufltr
disable lsermous
Type exit to quit Recovery Console, and then reboot the computer.


After the computer reboots, start Registry Editor.


Change the registry entry for the mouse and keyboard to:


HKEY_Local_Machine\System\CurrentControlSet\Services\ i8042prt:Imagepath=System32\Drivers\i8042prt.sys
Note that the entry is using a lowercase &quot;L&quot; in the name. L8042.sys should be changed to i8042prt.sys.

This refreed to Mouseware 8.x...maybe there is a newer driver?