0x000000D1 (0x90766606, 0x00000002, 0x00000000, 0xF70C10AF)

E

e8.mccall

I have a DELL Latitude D820 laptop which operates off of XP.
Recently I have been receiving the following stop error
0x000000D1 (0x90766606, 0x00000002, 0x00000000, 0xF70C10AF)

I have download the Update for Windows XP (KB916595).
I have ran a couple of diagnostic test -- All show that the system
device PASS
I have replaced the the memory stick, think it was defective.
I tried downloading the lastest driver updates from Microsoft.

Also does any one know what the additional parameters (0x90766606,
0x00000002, 0x00000000, 0xF70C10AF) represent ?

Please help :(
 
R

Ron Martell

I have a DELL Latitude D820 laptop which operates off of XP.
Recently I have been receiving the following stop error
0x000000D1 (0x90766606, 0x00000002, 0x00000000, 0xF70C10AF)

I have download the Update for Windows XP (KB916595).
I have ran a couple of diagnostic test -- All show that the system
device PASS
I have replaced the the memory stick, think it was defective.
I tried downloading the lastest driver updates from Microsoft.

Also does any one know what the additional parameters (0x90766606,
0x00000002, 0x00000000, 0xF70C10AF) represent ?

Please help :(

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

Bug Check 0xD1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
The DRIVER_IRQL_NOT_LESS_OR_EQUAL bug check has a value of 0x000000D1.
This indicates that a kernel-mode driver attempted to access pageable
memory at a process IRQL that was too high.

Parameters
The following parameters are displayed on the blue screen.

Parameter Description
1 Memory referenced
2 IRQL at time of reference
3 0: Read
1: Write
4 Address that referenced memory

******

What you need to do is to identify which driver is using memory
address 0xF70C10AF as that is the most likely culprit.

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."
 

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

Top