Hi, I've been getting the blue screen of death about once a day on a
computer that I'm running a Visual C++ 6.0 application (whose code I
partially wrote) on. If I look in the system event logs, the most
common error is BAD_POOL_CALLER 0x000000c2 (0x0000007,
0x00000cd4, ....), which is apparently caused by a faulty driver or
faulty software. I am running this same piece of software along with
other software on a second computer, and it also (infrequently) blue
screens with that same error. .dmp files have been created but I don't
have any experience with reading these. Is there a way to determine
which piece of software caused the error?

I read that dumpchk.exe and windbg can both read these files, but
which one can tell me more about the error? Thank you!

Note, I can't actually post the .dmp file online because it is on a
classified computer.

"Julie" <(E-Mail Removed)> wrote in message
news:ba337d19-87e0-4d5b-9f1e-(E-Mail Removed)...
> Hi, I've been getting the blue screen of death about once a day on a
> computer that I'm running a Visual C++ 6.0 application (whose code I
> partially wrote) on. If I look in the system event logs, the most
> common error is BAD_POOL_CALLER 0x000000c2 (0x0000007,
> 0x00000cd4, ....), which is apparently caused by a faulty driver or
> faulty software. I am running this same piece of software along with
> other software on a second computer, and it also (infrequently) blue
> screens with that same error. .dmp files have been created but I don't
> have any experience with reading these. Is there a way to determine
> which piece of software caused the error?
>
> I read that dumpchk.exe and windbg can both read these files, but
> which one can tell me more about the error? Thank you!
>
> Note, I can't actually post the .dmp file online because it is on a
> classified computer.


If it only crashes on the app whose code you wrote...
then I'd say that's your problem.

If you cannot post the dump then it's not too likely anyone will be able to
tell you where ther problem lies

Happy hunting!

"Julie" <(E-Mail Removed)> wrote in message
news:ba337d19-87e0-4d5b-9f1e-(E-Mail Removed)...
> Hi, I've been getting the blue screen of death about once a day on a
> computer that I'm running a Visual C++ 6.0 application (whose code I
> partially wrote) on. If I look in the system event logs, the most
> common error is BAD_POOL_CALLER 0x000000c2 (0x0000007,
> 0x00000cd4, ....), which is apparently caused by a faulty driver or
> faulty software. I am running this same piece of software along with
> other software on a second computer, and it also (infrequently) blue
> screens with that same error. .dmp files have been created but I don't
> have any experience with reading these. Is there a way to determine
> which piece of software caused the error?
>
> I read that dumpchk.exe and windbg can both read these files, but
> which one can tell me more about the error? Thank you!
>
> Note, I can't actually post the .dmp file online because it is on a
> classified computer.

Please don't multipost. If you feel the need to post in more than one
group, using crossposting.
Multiposting vs Crossposting
http://www.blakjak.demon.co.uk/mul_crss.htm

If you check your identical post in the xp.general group, I replied with
this:

There are a couple of freeware utilities you can use to read the dump
files more easily and try to determine what drivers are involved. I use
both:

WhoCrashed:
http://www.resplendence.com/whocrashed

Nirsoft's BlueScreenView:
http://www.nirsoft.net/utils/blue_screen_view.html

--
Glen Ventura
MS MVP Oct. 2002 - Sept. 2009
CompTIA A+
http://dts-l.net/

On Feb 9, 4:12*pm, "glee" <gle...@spamindspring.com> wrote:
> "Julie" <julievogelm...@gmail.com> wrote in message
>
> news:ba337d19-87e0-4d5b-9f1e-(E-Mail Removed)...
>
>
>
>
>
> > Hi, I've been getting the blue screen of death about once a day on a
> > computer that I'm running a Visual C++ 6.0 application (whose code I
> > partially wrote) on. If I look in the system event logs, the most
> > common error *is BAD_POOL_CALLER 0x000000c2 (0x0000007,
> > 0x00000cd4, ....), which is apparently caused by a faulty driver or
> > faulty software. I am running this same piece of software along with
> > other software on a second computer, and it also (infrequently) blue
> > screens with that same error. .dmp files have been created but I don't
> > have any experience with reading these. Is there a way to determine
> > which piece of software caused the error?
>
> > I read that dumpchk.exe and windbg can both read these files, but
> > which one can tell me more about the error? Thank you!
>
> > Note, I can't actually post the .dmp file online because it is on a
> > classified computer.
>
> Please don't multipost. *If you feel the need to post in more than one
> group, using crossposting.
> Multiposting vs Crosspostinghttp://www.blakjak.demon.co.uk/mul_crss.htm
>
> If you check your identical post in the xp.general group, I replied with
> this:
>
> There are a couple of freeware utilities you can use to read the dump
> files more easily and try to determine what drivers are involved. *I use
> both:
>
> WhoCrashed:http://www.resplendence.com/whocrashed
>
> Nirsoft's *BlueScreenView:http://www.nirsoft.net/utils/blue_screen_view..html
>
> --
> Glen Ventura
> MS MVP *Oct. 2002 - Sept. 2009
> CompTIA A+http://dts-l.net/- Hide quoted text -
>
> - Show quoted text -

Sorry about the multiposting. Thanks, glee, I responded to your other
post.

philo: My machine is not just running my software, but also running
other apps like ClearCase, McAfee, etc. Also, since I am unable to
post the .dmp, I am trying to find out how to examine the .dmp myself.

<snip>

philo: My machine is not just running my software, but also running
other apps like ClearCase, McAfee, etc. Also, since I am unable to
post the .dmp, I am trying to find out how to examine the .dmp myself.


ok


http://support.microsoft.com/kb/315263