Stop 0*000000d1 error

[robert austin]

I recently up graded to Win 2000. When I boot my computer
it locks up after 10-15 minutes. I get a blue screen with
a "stop 0*0000000D1" error It says it's beginning dump of
memory. How can I fix it?

 

[Guest]

Sounds like you have a memory error. If you have more than one stick of memory, swap them out and try them one at a time. If you still have the error with both memories, than I don't know.

 

[Jason Hall [MSFT]]

--------------------

From: =?Utf-8?B?RnJhbmsgQ2FzdGxl?= <[email protected]>
References: <[email protected]>
Subject: RE: Stop 0*000000d1 error
Date: Thu, 6 May 2004 10:31:05 -0700

Sounds like you have a memory error. If you have more than one stick of

memory, swap them out and try them one at a time. If you still have the
error with both memories, than I don't know.--------------------

This issue is not caused by a problem with memory, but in how one of your
drivers is using it.
One of your drivers is making an illegal memory operation (either read or
write).

To find out which driver is causing the issue, you can obtain a memory dump
and analyze it.
OR
You can try to deduce the problem driver....
a) Looking at unsigned drivers, and disable the associated programs (or
rename the driver file and reboot).
Trial and error should eventually land you the culprit
Q259283: "How to Use the File Signature Verification Tool to Find
Third-Party..."
b) Disable all start-up items and systematically enable them
(this will only work if the driver is associated with an app, if
it's for hardware, this won't help)
c) Update all the drivers you can think of: video, audio, printer,
network card, etc.

--
~~ JASON HALL ~~
~ Performance Support Specialist,
~ Microsoft Enterprise Platforms Support
~ This posting is provided "AS IS" with no warranties, and confers no
rights.
~ Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
~ Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.

 

[Hans-Jochen Trost]

Jason,

[snip]

This issue is not caused by a problem with memory, but in how one of your
drivers is using it.

I'm hunting one of these as well, and from what I have read in this
forum, many STOP 0x000000D1 crashes, if not most or all of them, do
report the, or a, driver supposeldy involved.

One of your drivers is making an illegal memory operation (either read or
write).

To find out which driver is causing the issue, you can obtain a memory dump
and analyze it.
OR
You can try to deduce the problem driver....
a) Looking at unsigned drivers, and disable the associated programs (or
rename the driver file and reboot).
Trial and error should eventually land you the culprit
Q259283: "How to Use the File Signature Verification Tool to Find
Third-Party..."
b) Disable all start-up items and systematically enable them
(this will only work if the driver is associated with an app, if
it's for hardware, this won't help)
c) Update all the drivers you can think of: video, audio, printer,
network card, etc.

In my case, it is serial.sys according to the blue screen, while
Robert does not say if there is a driver reported. From listings of
possible incarnations of the D1 error, I take it that usually a
Microsoft driver is involved. The disconcertingthing is that for
serial.sys a fix has been applied in SP2, but apparently it is not
thoroughly successful - it has reduced the number of occurrences a
lot, sort of from one per hour to one per day. There is no information
anywhere what else could be causing this error.

To Robert I would suggest to check at what service pack level he is,
update to the newest one (SP4 if I am not mistaken), and apply
additional critical updates (everyone but IE6 SP1) as some of them
affect some of the D1 errors. This may help him but I would not bet
on it.

Cheers, Jochen
hjtrost at microfab dot com


Nil nimium studeo, Caesar, tibi velle placere,
nec scire ut an sis albus an ater homo.
Catullus