Whiplash
Future Aviator
+40|6047|Central Texas
The error was "BAD_POOL_CALLER"

The error string was...

0x000000C2 (0x00000007, 0x00000CD4, 0xE480EDD8, 0xE36EF150)

I tried to google that, but nothing came up. Does anyone know what it means?
rdx-fx
...
+955|6858
http://msdn.microsoft.com/en-us/library/ms681381.aspx 

might help you translate the error codes.


I'm thinking the BLT drive went AWOL. 
DUnlimited
got any popo lolo intersting?
+1,160|6730|cuntshitlake

According to http://aumha.org/a/stop.htm it's a faulty driver or some buggy software.
0x000000C2: BAD_POOL_CALLER
A kernel-mode process or driver incorrectly attempted to perform memory operations. Typically, a faulty driver or buggy software causes this.
Were you installing drivers or opening some program or doing something else specificly when this occurred?

Also don't worry about it if it does not reoccur.
main battle tank karthus medikopter 117 megamegapowershot gg
Whiplash
Future Aviator
+40|6047|Central Texas
I wasn't doing anything. I was just on another forum and it happened out of nowhere. If it doesn't happen again then that would be good, but if it does what should I do? Find the problem?
DUnlimited
got any popo lolo intersting?
+1,160|6730|cuntshitlake

Well this describes how to debug the code in win2k, but I am not sure how it applies to XP/Vista/whatever windows version you are running.
main battle tank karthus medikopter 117 megamegapowershot gg
Scorpion0x17
can detect anyone's visible post count...
+691|7032|Cambridge (UK)
BSODs are unbelievably difficult to diagnose.

As DU said - if it doesn't happen again, don't worry about it - probably just a stray cosmic ray.

If it does happen again, then firstly you need to try to see if there's any pattern in the occurrences - that may give a clue is to what is causing it.

Now, if it seems totally random, then it's most likely a hardware issue.

BUT, a software issue is easier to diagnose and fix - if there's a pattern to when it BSOD - say it's a case of it only ever does it when you open application X, then reinstall application X.

If it appears to be a part of windows, or there either seems to be a pattern, but you can't discern what software is causing it, or it's random, then do a complete reinstall of windows, make sure all your drivers are up-to-date, and then install any additional apps/games/etc.

If after all that, you still get the same BSOD, then it's hardware.

And this is where it gets tricky - cos it could be any single component causing the problem - the only way to work out which it is is to swap each one out, and then back in, one at a time until the BSOD goes away.

Finally if the BSODs are random and different each time, and you get other weird random behaviour, suspect your PSU.
SpIk3y
Minister of Silly Walks
+67|6406|New Jersey
From my experience, the majority of *recurring* BSODs are caused by driver issues.

Board footer

Privacy Policy - © 2025 Jeff Minard