Rob said:
OK, I found the information in the Event Viewer, but it is not telling me
anything useful. Here is the info:
Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 9/10/2007
Time: 6:18:28 PM
User: N/A
Computer: YOUR-4DACD0EA75
Description:
Error code 1000008e, parameter1 c0000005, parameter2 bfa281bd, parameter3
8a9c82c0, parameter4 00000000.
Data:
0000: 74737953 45206d65 726f7272 72452020
0010: 20726f72 65646f63 30303120 38303030
0020: 50202065 6d617261 72657465 30632073
0030: 30303030 202c3530 32616662 64623138
0040: 6138202c 32386339 202c3063 30303030
0050: 30303030
Your error is called KERNEL_MODE_EXCEPTION_NOT_HANDLED
The parameter 1 value indicates that the specific exception was a
STATUS_ACCESS_VIOLATION
Parameter 2 indicates that the error occurred at memory address
bfa281bd so if you can trace the specific item (Device Driver, Windows
component, or application program) that is using that memory address
then this should help determine how to fix it. The following
procedure may be of some help in tracing this item:
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
"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."
