Stop Error 0x000000D1

[Shashank]

I constantly receive the stop error 0x000000D1(0x00000009,
0x00000002, 0x00000000, 0x00000009). Sometimes the error
appears with 11 in place of 9 in the parameters. There is
no specific environment that this error occurs in, and it
happens frequently. I have tried clean booting, with only
microsoft services running, and startup services and
programs turned off, and I have also tried safe mode, but
the blue screen still appears. I have the latest drivers
and BIOS updates, and I've tried rolling back drivers as
well. I have tested the RAM with memtest86 and it checks
out. I'd appreciate any help anyone can give me on this
issue. Thanks.
Shashank

System Specs:
ABIT KR7A-133R
AMD Athlon 2000+
768 MB Kingston DDR RAM
Creative Labs Audigy Platinum
ATI Radeon 8500

 

[Jacek Czerwonka [MSFT]]

I constantly receive the stop error 0x000000D1(0x00000009,
0x00000002, 0x00000000, 0x00000009). Sometimes the error
appears with 11 in place of 9 in the parameters. There is
no specific environment that this error occurs in, and it
happens frequently. I have tried clean booting, with only
microsoft services running, and startup services and
programs turned off, and I have also tried safe mode, but
the blue screen still appears. I have the latest drivers
and BIOS updates, and I've tried rolling back drivers as
well. I have tested the RAM with memtest86 and it checks
out. I'd appreciate any help anyone can give me on this
issue. Thanks.

Shashank,

Look for 0x000000D1at http://support.microsoft.com and see if there are any
cases that could apply to your configuration. Faulty memory can be one
possible explanation and swapping memory sticks may help verifying this.
Stop 0xD1 is also quite often caused by a misbehaving driver. You may want
to examine your hardware by removing all the non-essential pieces and having
your machine running for some time. If it's OK then you should start adding
hardware one by one making sure it's still fine after each addition.
Whichever addition gives you 0xD1 is your potential culprit. Obviously this
will not work for all the cases.

If you're running WinXP you may want to submit your memory dump to Microsoft
after the machine recovers from crash. If there were cases like yours
before, there may already be some solution to your problem.

If anything else fails you may want to load that memory dump into the
debugger (http://www.microsoft.com/whdc/ddk/debugging/default.mspx) yourself
and find out the exact name of the driver that gives you problems. Let me
know if you need more info to get you started.