what does BAD_POOL_CALLER stand for?

[Lt. Max]

i for some reason get this BSOD when shutting down after letting the computer run for a couple of days straight..

anyone know what it means?
i tried searching it didnt really come up with any concrete information, so yeah.

tia

max

[mdcomp]

Everything I found about that error has talked about faulty device driver or a failed memory operation. Here is an article that I think will specifically help you: MSKB 314492 (http://support.microsoft.com/default.aspx?scid=kb;en-us;314492&Product=winxp) . Try seeing if there is some kind of device conflict or a device is not working correctly. Check the device manager and system information for that.

Matt

[Lt. Max]

ok cool tnx.. ill check out my drivers

max

[redduc900]

In addition to Matt's MSKB link regarding debugging a Stop 0xC2 or Stop 0x000000C2 error, here's a link to a MS TechNet article that may also be of some help to you...

Stop 0xC2 or BAD_POOL_CALLER (http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechnol/winxppro/reskit/prmd_stp_czgw.asp)

Like Matt mentioned, this Stop error is usually caused by a faulty driver or software. :)

[Lt. Max]

hmm.. interesting it just happend while joining a desert combat server.. i think ill redo my nvidia drivers.

this is what it gives under technical:

0x000000c2 (0x00000007, 0x00000cd4, 0x024c008, 0x851308410)


max

[Lt. Max]

ok definatley not nvidia drivers i just installed the ones in windows update and i still bsod... damit. what could it be..

max

[redduc900]

I would suggest running Event Viewer (in order to access the error logs, and check for any critical errors)...Start | Run | Type eventvwr.msc and hit OK | Highlight "Application" and "System" independently in the LH pane | Right click the error message(s) (critical errors are in Red), and select "Properties" | Write down a couple of the error messages exactly as they appear (under the "Description" field), and post them in this thread.

Also, open the System Information tool by typing msinfo32 in the Run box | Expand "Components" | Highlight "Problem Devices", and look for any problems that might be listed there. ;)