Diagnosing blue screen of death

[Julie]

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.

 

[glee]

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.

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

 

[Julie]

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 -

Thanks! I'll see if I can get those installed. I think my IT guy is
currently locating dumpchk.exe. Have you used that, and do you have
any idea if your utilities might provide more information than this
one?

 

[Tim Meddick]

You could use my batch-file (stopcode.bat) to see if the particular "stop
code" has a description for it.

Download the simple installation file [StopCode.exe] from the web-page
below :
http://www.4shared.com/file/mWb6QLlt/StopCode.html

....and then save this file to the root of your system [C:] drive and
double-click on it to automatically install it.

Also, a file named [Help.txt] will appear in the root of your [C:] drive
(if the installation was successfull) which gives you a breif descrption
usage and sysntax instructions for the batch-file.

For instance; for your particular stop-code, after installing my
batch-file, you would type the following at the command prompt ;

STOPCODE[.BAT] C2

...(the text between the square brackets is optional) and this would return
the information :

"BAD_POOL_CALLER"

a simple google search for that text would releal that indicates that the
current thread is making a bad pool request. ;
http://www.osronline.com/ddkx/ddtools/bccodes_8k9z.htm

The error code descriptions can turn out to be quite detailed in their own
right, but I had not looked-up this particular one until just now and, as
it turns out, it is a particularly short and uninformative one.

However, it is still usefull to be able to include this description or even
quote just that when searching online for the answer.

Having done that, I found the web-page (url above) which I think provides
some very usefull information. Also, I think that possible causes of this
code are corrupt ram or a corrupted driver.

==

Cheers, Tim Meddick, Peckham, London.

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 -

Thanks! I'll see if I can get those installed. I think my IT guy is
currently locating dumpchk.exe. Have you used that, and do you have
any idea if your utilities might provide more information than this
one?

 

[glee]

Thanks! I'll see if I can get those installed. I think my IT guy is
currently locating dumpchk.exe. Have you used that, and do you have
any idea if your utilities might provide more information than this
one?

All dumpchk.exe does is verify that a dump file is good, it does not do
any debugging or other analysis.
How to use Dumpchk.exe to check a Memory Dump file
http://support.microsoft.com/kb/315271

For that, you would use the Microsoft Debugging Tools and Symbols
packages. They are NOT easy to use. The utilities I suggested will do
a lot of that work for you. In fact, WhoCrashed downloads and installs
the Windows Debugging Tools and uses them in its analysis.

Try the utilities I suggested first, and post back with what they
report.

 

[Tester]

Don't waste your valuable time. These messages are completely useless
and you are not likely to understand them. If you keep getting these so
called BSOD then you will be wise to reformat, and reinstall the
operating system.

 

[glee]

Don't waste your valuable time. These messages are completely useless
and you are not likely to understand them. If you keep getting these
so called BSOD then you will be wise to reformat, and reinstall the
operating system.

That's some pretty poor advice. Just because you can't understand them
doesn't mean they are useless. BAD_POOL_CALLER errors usually are due to
a buggy or outdated driver, or buggy software application. Your advice
is akin to telling someone to rebuild their car's engine because the
spark plug wires need replacing.

 

[Tester]

That's some pretty poor advice. Just because you can't understand them
doesn't mean they are useless. BAD_POOL_CALLER errors usually are due to
a buggy or outdated driver, or buggy software application. Your advice
is akin to telling someone to rebuild their car's engine because the
spark plug wires need replacing.

My advice is pretty good. You daddy didn't tell you that "outdated
driver" will never give you BSOD. Why should it? If it was working
when it was released then why should it stop working now? Computers
have brains like yours and they are not able to distinguish outdated
drivers unless you are advising the OP to start using those rogue
drivers scanners available almost everywhere online!

 

[glee]

My advice is pretty good. You daddy didn't tell you that "outdated
driver" will never give you BSOD. Why should it? If it was working
when it was released then why should it stop working now? Computers
have brains like yours and they are not able to distinguish outdated
drivers unless you are advising the OP to start using those rogue
drivers scanners available almost everywhere online!

It most certainly can give you a BSOD. First of all, I said a "buggy or
outdated driver". A display driver can work fine for years, and then
cause problems as demands on the driver change....such as from changes
in plug-ins or controls used on web pages, just as one example. You
have heard of drivers being written to supplant older drivers in order
to fix issues, haven't you? Bugs in drivers can show up long after
their release, once new demands are made on them that did not exist at
the time the driver was written.

"Outdated drivers" also refers to drivers used by programs (anti-virus
apps and many others). Some of these apps are updated regularly,
including the drivers files. "Outdated drivers" also refers to recently
installed devices or apps whose drivers may not be the most recent.
There are also cases of "new" drivers causing BSODs and needing to be
rolled back. Even in Vista and Seven, driver incompatibilities cause
BSODs.

If you think BSODs require formatting and reinstalling, and are not
worth troubleshooting, you really don't know what you are talking about.

 

[Tester]

OUTDATED DRIVERS NEBER GIVES YOU BSOD. PERIOD.

"Outdated drivers" also refers to drivers used by programs
(anti-virus apps and many others). Some of these apps are updated
regularly,

THEREFORE, OUTDATED DRIVERS ARE PRETTY GOOD. YOU DIDN'T SAY UPDATED
DRIVES ARE BUGGY DID YOU?. YOU CLEARLY USED THE WORD OUTDATED. DON'T
YOU LIE TO US HERE.

 

[Peter Foldes]

OUTDATED DRIVERS NEBER GIVES YOU BSOD. PERIOD.

It most certainly can give you a BSOD

--
Peter
Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.
This posting is provided "AS IS" with no warranties, and confers no rights.
http://www.microsoft.com/protect

 

[Peter Foldes]

Julie

See the following link


http://aumha.org/a/stop.php#0xc2
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.
a.. 0x000000C2 {KB 265879} Win 2000, Win XP
b.. 0x000000C2: BAD_POOL_CALLER {KB 310527} Win XP (upgrading Compaq Professional
Workstation AP550 from Win 2000 to XP)
c.. Computer with ATI RAGE FURY MAXX Video Adapter Stops Responding After Upgrade
to Win XP {KB 307151} Win XP

--
Peter
Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.
This posting is provided "AS IS" with no warranties, and confers no rights.
http://www.microsoft.com/protect

 

[glee]

OUTDATED DRIVERS NEBER GIVES YOU BSOD. PERIOD.


THEREFORE, OUTDATED DRIVERS ARE PRETTY GOOD. YOU DIDN'T SAY UPDATED
DRIVES ARE BUGGY DID YOU?. YOU CLEARLY USED THE WORD OUTDATED. DON'T
YOU LIE TO US HERE.

Not only don't you know what you're talking about, you have a reading
comprehension problem. If you had read (and quoted) my entire reply, I
already explained how outdated drivers such as video drivers can cause
BSODs. I then added more info about how updated drivers can *also*
cause them. You have taken one sentence out of context in an attempt to
deflect the focus away from your ignorance.
Outdated drivers can and have given BSODs. Apparently you don't have
much real-world computer experience.

 

[Aardvark]

Is it safe to simply click on the links where indicated on that
destination page?

Yes.

Indeed, is it safe to click on the link *you* have posted here in *this*
thread?

Yes.

FYI
HTH
HAND

 

[FromTheRafters]

Is it safe to simply click on the links where indicated on that
destination page?

Whether or not a link is safe, depends entirely on your system.

[...]

 

[Aardvark]

Aardvark is quite adamant that the links *are* safe.

Yup. Every link on the page that I clicked took me to a M$ page.

Who 'tests' them so that poorly protected,

I did. They're safe.

naive computer users don't
get themselves co-opted into a botnet?

The fools, the fools.

 

[Tester]

Not only don't you know what you're talking about, you have a reading
comprehension problem. If you had read (and quoted) my entire reply, I
already explained how outdated drivers such as video drivers can cause
BSODs. I then added more info about how updated drivers can *also*
cause them. You have taken one sentence out of context in an attempt to
deflect the focus away from your ignorance.
Outdated drivers can and have given BSODs. Apparently you don't have
much real-world computer experience.

OUTDATED DRIVERS NEVER GIVES YOU BSOD. PERIOD. Now go and lick my ass.

 

[glee]

OUTDATED DRIVERS NEVER GIVES YOU BSOD. PERIOD. Now go and lick my
ass.

There are literally hundreds if not thousands of cases over the years of
outdated drivers causing BSODs in the various versions of Windows. I
have seen it and corrected it on numerous of my clients' computers, as
have most techs. I suggest you lick your own ass, since your head is
already fairly far up it.

BSODs caused by outdated drivers....here's just a tiny sampling of the
large number of cases:

http://www.vistax64.com/crashes-debugging/287050-bsod-help.html

http://www.sevenforums.com/crashes-debugging/129676-bsod-crash-please-debug-me.html

http://www.sevenforums.com/crashes-debugging/130853-blue-screen-restart-bsod.html

http://social.answers.microsoft.com...e/thread/a2e40df9-987b-4ea4-896e-23ea1080ccd1

http://h30434.www3.hp.com/t5/Notebook-Operating-systems-and/DV3-2000-CTO-and-BSOD/m-p/350729

 

[FromTheRafters]

On 10/02/2011 12:44, Peter Foldes wrote:
Julie

See the following link


http://aumha.org/a/stop.php#0xc2


Is it safe to simply click on the links where indicated on that
destination page?

Whether or not a link is safe, depends entirely on your system.

[...]

Please would you expand on that statement, FTR?

W h e t h e r o r n o t a l i n k i s s a f e , d e p e n d
s e n t i r e l y o n y o u r s y s t e m .

....but I don't see how that helps.

Aardvark is quite adamant that the links *are* safe.

Maybe he was answering a different question, like 'Do you trust them?'
or 'Are they trustworthy?'.

Who 'tests' them so that poorly protected, naive computer users don't
get themselves co-opted into a botnet?

Nobody, it's a jungle out there.

Okay, what could possibly be "unsafe" about a link?

Maybe it doesn't go where you believe it does, and/or the place it does
indeed go tries to compromise your machine. Success and failure depend
on your system at that point.

 

[glee]

Drivers when suitable on one system WILL ALWAYS WORK WITHOUT GIVING
BSOD even after 10 years. PERIOD. I can have your daughter if she
can give me regular blow jobs!.

So, you think being stupid and crude enhances your credibility?
You and Tester keep making these absolute statements that you cannot
back up, so you both just hurl insults. Meanwhile, there is plenty of
documentation and the personal experience of credible techs that show
you are incorrect.