Blue Screen

  • Thread starter Laurie Witchalls
  • Start date
L

Laurie Witchalls

I have been getting the blue screen every few days with the following error
message 0x0000008E(0xC0000002,0x80537BD2,0xEE82A1C8,0x00000000). Following
reboot it is usally OK, but still annoying. Is there any way of identfying
what is causing this problem?

Thanks

Laurie
 
R

Ron Martell

Laurie Witchalls said:
I have been getting the blue screen every few days with the following error
message 0x0000008E(0xC0000002,0x80537BD2,0xEE82A1C8,0x00000000). Following
reboot it is usally OK, but still annoying. Is there any way of identfying
what is causing this problem?

Thanks

Laurie

See MVP Jim Eshelman's web page for STOP errors at
http://aumha.org/a/stop.htm and click on the "8E: Kernel Mode
Except..." link in the left side column.

In your instance the error was caused by the device driver, windows
component, or application program that is using memory address
0x80537BD2. There is a procedure which may allow you to track the
specific device driver involved but it is a bit complex and requires
the use of Excel (or a comparable spreadsheet) to facilitate the
tracing. Post a response back here if you want to try this.

Good luck

Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2008)
On-Line Help Computer Service
http://onlinehelp.bc.ca
Syberfix Remote Computer Repair

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."
 
G

Gerry Cornell

Laurie

http://msdn2.microsoft.com/en-us/library/ms794023.aspx

Are there any yellow question marks in Device Manager? Right click
on the My Computer icon on your Desktop and select Properties,
Hardware,Device Manager. If yes what is the Device Error code?

Try Start, Run, type "sigverif.exe" without quotes and hit OK. What
drivers are listed as unsigned? Disregard those which are not
checked.

Do you have a Windows XP CD? Does it include the SP2 update or did
you download later?

--

Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
 
L

Laurie Witchalls

I would like to track down the root of the problem so would welcome you
advice on the procedure.

Many thanks

Laurie
 
L

Laurie Witchalls

Gerry

Answers to your questions:
There are no yellow warning messages.
There are unsigned drivers although I am not too sure how I should approach
them can you help?
SP2 came preloaded and I only have DVDs to restore, having created them as
part of the computer setting up.

Thanks

Laurie
 
R

Ron Martell

Laurie Witchalls said:
I would like to track down the root of the problem so would welcome you
advice on the procedure.

Many thanks

Laurie
Identifying the cause of STOP errors using PSTAT & Excel

Many times when a STOP error occurs the information provided does not
specifically identify the application, device driver, or other
component file where the error occurred. However the 4 parameters
associated with the STOP (bugcheck) code will very often include one
that is the address where the error occurred. You first need to look
up the detailed information about the specific STOP code in order to
determine if the address is included and if so which of the 4
parameters has the address.

You can identify the meaning of each of the parameters for your
specific STOP code at:
http://msdn2.microsoft.com/en-us/library/ms789516.aspx

The second step in the procedure is to identify the addresses that
each active process is being loaded at. The PSTAT utility will
provide this information. On some systems the PSTAT utility may
already be present. Check this by opening a Command Prompt window
(Start - Run - CMD) and entering the following command:

PSTAT /?

If PSTAT is not on your computer you can download it free from
Microsoft. The download is called "Windows XP Service Pack 2 Support
Tools" and it is available from
http://www.microsoft.com/downloads/...76-9BB9-4126-9761-BA8011FABF38&displaylang=en
With PSTAT installed on your computer the next step is to open a
Command Prompt window again (Start - Run - CMD) and generate a report
with PSTAT. Because you need to copy part of the information from
this report (and only part) it is best to create the report as a text
file. In the Command Prompt window enter the following command:

PSTAT > C:\JUNK\PSTAT.TXT

You may change C:\JUNK\ to whatever drive and folder that you want to
save the report into.

Now open the saved file in Notepad. Start - Run - NOTEPAD
C:\JUNK\PSTAT.TXT

Scroll down the file, about 80% of the way to the end of the file and
you will find a head line:

ModuleName Load Addr Code Data Paged LinkDate

It is the information from this line to the end of the file that we
want to copy from this file and save as a separate file. Select the
block of text and copy it to the clipboard. Open a new notepad window
and paste the clipboard contents into it. Save this file under a
different name. I use PSTAT2.TXT and put it into the same C:\JUNK
folder.

Now launch Microsoft Excel and use File - Open to bring the PSTAT2.TXT
file into Excel. Excel will automatically parse the file into
columns. Once this is done use DATA - SORT to sort the entire
spreadsheet based on the value in Column B (Load Addr).

It is now a simple task to read down the addresses until you find the
highest value that is less than the address where the error occurred.
That module (name in column A) is the prime suspect for the cause of
your error.

Good luck

Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2008)
On-Line Help Computer Service
http://onlinehelp.bc.ca
Syberfix Remote Computer Repair

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."
 
G

Gerry Cornell

Laurie

A list of unsigned drivers (if not overlong) with versions might be
helpful.

Is there a copy of an Event Viewer Report covering the Blue Screen.
If yes please post a copy.


--


Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
 
R

Ron Martell

Laurie Witchalls said:
Ron

Thanks for the guidance.

Attached is the sorted PSTAT file.

My error message is 0x0000008E(0xC0000002,0x80537BD2,0xEE82A1C8,0x00000000)
and the bug check listing suggests address is 80537BD2 which then seems to
point to module ntkrnlpa.dll as the culprit.

Are you able to advise how I deal with this to eliminate the problem?

ntkrnlpa.exe is a Windows system file. It may have been damaged or
corrupted. Open a Command Prompt window and enter the following
command:

SFC /SCANNOW

If that does not resolve the issue then we need to look elsewhere for
the cause. One instance of this same error was eventually resolved by
replacing the RAM (defective), and others have been solved by getting
the updated Motherboard drivers from the motherboard/computer
manufacturer's web site.

To test the RAM in your computer use one of the following free memory
test utilities. It is best to let these tests run for an extended
period (e.g. overnight):
DocMemory http://www.simmtester.com
Windows Memory Diagnostic http://oca.microsoft.com/en/windiag.asp
Memtest86: http://www.memtest.org

Good luck

Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2008)
On-Line Help Computer Service
http://onlinehelp.bc.ca
Syberfix Remote Computer Repair

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads


Top