STOP: 0x0D1 Error - difficult one

[Chris]

We have a computer that is currently receiving the
infamous STOP: 0x000000D1 error whenever we attempt to
boot into Windows XP Home edition. This is of course
accompanied by DRIVER_IRQL_NOT_LESS_OR_EQUAL. The full
error,
STOP: 0x000000D1 (<somewhat random address>, 0x00000002,
0x00000001, <somewhat random address>).

The 'somewhat random addresses' change with each
occurrance. We can boot into safemode, but every attempt
to boot into normal mode results in the above error. I
have checked the Event Log, and there are no events
listed that could pertain to this problem. In fact, the
only critical errors listed are those that correspond to
entering safe mode. I have run memtest,
which found no fault with the memory, and I have updated
all drivers I could find to their most recent versions.
I have also attempted the fix involving the virtual
memory manager (http://support.microsoft.com/default.aspx?
scid=kb;en-us;810093), with no cure. This computer has
a Pentium 3 1.3 ghz processor, and 128 Mb of RDRAM. The
error does not specify any particular driver or file
name, nor give any other indication of what is causing
this problem. We have attempted all of the fixes
suggested off of http://aumha.org/win5/kbestop.php#0xd1
as well, and every possibility listed either does not
solve this problem, or is not applicable to this
situation. That is, except for the possibility of the
hotfix regarding the apci and a bios with multiple
tables. Unfortunately, I do not know if that is the case
here or not. This computer's bios is:
Phoenix Bios Core Version 4.0, Release 6.0
Bios Revision 2.08 07/17/01 .
Unfortunately, browsing Phoenix' website has not provided
me with any enlightenment so far.

I have tried uninstalling all drivers for the video card
and all associated software, and replacing it with a
known good video card, yet the error persists. I have
tried uninstalling and later reinstalling drivers for any
device I feel may be remotely related to this issue. So
far, I am at a complete and total loss. Interestingly
enough, I can boot it with Knoppix with no apparent
issues.

So, does anyone have any suggestions as to what next
steps may be taken at this point? Is there another way
without paying for Microsoft support to get a hold of
this hotfix, or at least verify if it is the solution or
not? Thanks...

-Chris

 

[Kelly]

Hi Chris,

Maybe there is something different offered here: http://tinyurl.com/2dr5k

 

[Plato]

We have a computer that is currently receiving the
infamous STOP: 0x000000D1 error whenever we attempt to

http://www.microsoft.com/technet/tr...prodtechnol/winxppro/reskit/prmd_stp_tnvo.asp

http://aumha.org/win5/kbestop.htm

http://www.updatexp.com/stop-messages.html

 

[Chris]

Though I appreciate the attempt to help, as stated in my
request, I have already tried all of that. In fact, the
second URL that you list, I have already mentioned
specifically in my post....

-Chris

 

[Chris]

Thanks, but I do not see anything new there, I'm afraid.
At this rate, this computer is quickly heading to being a
Linux box. Lower TCO, indeed.....

-Chris

 

[R. McCarty]

Download the latest BIOS firmware update and apply.
Then go into BIOS and disable any on-board peripherals
that aren't required. Sometimes, you can set BIOS to
operate at a "Failsafe" mode ( Conservative Memory
timing, etc). Also, try switching Memory modules from
a working similar machine.

Thanks, but I do not see anything new there, I'm afraid.
At this rate, this computer is quickly heading to being a
Linux box. Lower TCO, indeed.....

-Chris

 

[Malke]

Download the latest BIOS firmware update and apply.
Then go into BIOS and disable any on-board peripherals
that aren't required. Sometimes, you can set BIOS to
operate at a "Failsafe" mode ( Conservative Memory
timing, etc). Also, try switching Memory modules from
a working similar machine.

Thanks, but I do not see anything new there, I'm afraid.
At this rate, this computer is quickly heading to being a
Linux box. Lower TCO, indeed.....

-Chris

Chris - Forgive me for jumping in here so late, but here are a few
ideas. 1) You don't have enough RAM and it is probably older RAM. I
know you said you did a Memtest86, but I'd swap out that RAM for 256MB
of something else and see. 2) If you want to test whether problems are
operating system-related and not hardware, boot your computer with
Knoppix. Knoppix is a Linux distro that runs from cd. With so little
RAM, your computer won't be a speed demon, but it should run. Get the
latest .iso at www.knoppix.net. Be sure to rtfinem. Run using Knoppix
for a while and if you still get errors, then you know it is hardware.
3) You may be having some subtle electrical shorts that are very hard
to diagnose - I had a box do something similar with Win98 and it turned
out to be a faulty CD-ROM drive that eventually shorted out the power
supply and motherboard.

Good luck,

Malke

 

[James T]

Though I appreciate the attempt to help, as stated in my
request, I have already tried all of that. In fact, the
second URL that you list, I have already mentioned
specifically in my post....

-Chris

I'm having the same problem. I've wiped the hardrive, reinstalled XP,
and still the BSOD with everything out & known good video card. I
have 2 RAM sticks, which I've swapped out and into each of the three
DIMMs. Still the BSOD & STOP 0xD1. This system has been running fine
for months, but then this (*&! started, so compatibility doesn't seem
a likely issue. I'm thinking something on the main board has failed,
but I wish I knew for certain before spending $ on new hardware. Good
luck with yours. Frustrating as hell, isn't it.

 

[Malke]

James T wrote:

I'm having the same problem. I've wiped the hardrive, reinstalled XP,
and still the BSOD with everything out & known good video card. I
have 2 RAM sticks, which I've swapped out and into each of the three
DIMMs. Still the BSOD & STOP 0xD1. This system has been running fine
for months, but then this (*&! started, so compatibility doesn't seem
a likely issue. I'm thinking something on the main board has failed,
but I wish I knew for certain before spending $ on new hardware. Good
luck with yours. Frustrating as hell, isn't it.

As I suggested earlier, boot with Knoppix and run for a while (if it
will run). This will help answer your question about whether it is your
motherboard or Windows.

Malke