Two questions about an error message

  • Thread starter Thread starter Mark
  • Start date Start date
M

Mark

Hi all,

I'm working on a new system that has Windows XP Pro installed. SP2 was
installed also. I am now getting blue screens with messages like: "Bad
Pool Header" but I am unable to read the entire message before it
disappears. My first question is: Is the dump written to disk anywhere
or can I set this to halt for me so I can read it? My other questions
is: Is this a driver issue and are there any debugging tools that I can
use to pinpoint the error(s)?

Thanks in advance.
Mark
 
Mark said:
Hi all,

I'm working on a new system that has Windows XP Pro installed. SP2 was
installed also. I am now getting blue screens with messages like: "Bad
Pool Header" but I am unable to read the entire message before it
disappears. My first question is: Is the dump written to disk anywhere
or can I set this to halt for me so I can read it? My other questions
is: Is this a driver issue and are there any debugging tools that I can
use to pinpoint the error(s)?

Thanks in advance.
Mark

What happens after the blue screen? Does the computer reboot itself?

If so then open Control Panel - System - Advanced and click on the
Settings button in the Startup and Recovery (bottom) section. In the
Startup and Recovery window click on the checkbox for "automatically
restart" to clear it then click on Apply and OK as needed to exit.

That should keep the blue screen message on the display long enough
for you to read it completely and to make note of the contents,
including all of the parameters. In fact you will probably have to
manually power off and restart the computer.

Post the complete contents of the blue screen message(s) back here if
you need further assistance with that, or you can check them out
yourself at MVP Jim Eshelman's STOP errors page at
http://www.aumha.org/win5/kbestop.htm

Good luck


Ron Martell Duncan B.C. Canada
--
Microsoft MVP
On-Line Help Computer Service
http://onlinehelp.bc.ca

"The reason computer chips are so small is computers don't eat much."
 
Ron Martell said:
What happens after the blue screen? Does the computer reboot itself?

If so then open Control Panel - System - Advanced and click on the
Settings button in the Startup and Recovery (bottom) section. In the
Startup and Recovery window click on the checkbox for "automatically
restart" to clear it then click on Apply and OK as needed to exit.

That should keep the blue screen message on the display long enough
for you to read it completely and to make note of the contents,
including all of the parameters. In fact you will probably have to
manually power off and restart the computer.

Post the complete contents of the blue screen message(s) back here if
you need further assistance with that, or you can check them out
yourself at MVP Jim Eshelman's STOP errors page at
http://www.aumha.org/win5/kbestop.htm

Good luck


Ron Martell Duncan B.C. Canada
--
Microsoft MVP
On-Line Help Computer Service
http://onlinehelp.bc.ca

"The reason computer chips are so small is computers don't eat much."

I found out how to disable the "Automatic Restart". Now I can at least
read the dump screens. Since then (naturally) the error has not
occurred. I'm sure it will since I have not resolved the problem.

I was also directed to this page:
http://tinyurl.com/4qj38

Thanks for the link.
Mark
 
I found out how to disable the "Automatic Restart". Now I can at least
read the dump screens. Since then (naturally) the error has not
occurred. I'm sure it will since I have not resolved the problem.

I was also directed to this page:
http://tinyurl.com/4qj38

Thanks for the link.
Mark

I think you will find Jim Eshelman's page somewhat more useful than
the MSDN because from Jim's page there are links to the relevant MSDN
item (per your link) and also, where appropriate, to the Windows
Resource Kits and to articles in the Microsoft Knowledge Base that
relate to that specific error code.

Good luck


Ron Martell Duncan B.C. Canada
--
Microsoft MVP
On-Line Help Computer Service
http://onlinehelp.bc.ca

"The reason computer chips are so small is computers don't eat much."
 
Back
Top