Unsolved
This post is more than 5 years old
31 Posts
0
9665
January 4th, 2004 21:00
BSOD Bad Pool Caller
Occasionally I get a BSOD with the first parameter OxC2 on my W2K machine. I got some guideance via Google, and a suggestion to run Verifier.exe from directory system32. Running verifier just opens a diagnostic program that does not seem to do anything. Maybe it just runs in the background and waits for the next occurrence. Has anyone had this BSOD, and any suggestions on how to fix it. Microsoft Technet says its either a driver or hardware failing.
No Events found!


jwatt
4.4K Posts
0
January 5th, 2004 18:00
What module is listed as containing the address where the bluescreen occurs? That may offer a hint as to which driver's causing the crash.
Jim
Frank Curry
31 Posts
0
January 5th, 2004 21:00
jwatt
4.4K Posts
0
January 6th, 2004 00:00
The line of interest is the one that contains " *** Address (xxxx) base at (yyyy,) DateStamp (zzzz) - (module name)". The "module name" may point us to what driver (or other module) is causing the crash.
Jim
Frank Curry
31 Posts
0
January 6th, 2004 10:00
Frank Curry
31 Posts
0
January 6th, 2004 10:00
jwatt
4.4K Posts
0
January 6th, 2004 16:00
Is the bluescreen associated with any particular activity? The only one I've experienced, described in this thread, was highly patterned, although the pattern was somewhat difficult to determine.
Jim
Frank Curry
31 Posts
0
January 7th, 2004 10:00