Annoying STOP message

[Brett Sabell]

I keep getting an annoying BSOD STOP message in Windows XP
SP1 that says the following:

DRIVER_IRQL_NOT_LESS_OR_EQUAL
....
*** STOP: 0x000000D1 (0x0000000C, 0x00000002, 0x00000000,
0xF80AFC00)
*** dne2000.sys - Address F80AFC00 base at F80A9000,
DateStamp 3C3CDBF4

This STOP message is intermittent; sometimes it appears
during a Scan Disk of C: (before I even log in to
Windows), sometimes several hours after using Windows.
Each time it appears, some of the Hex values differ
slightly.

I can start up successfully in Safe Mode (without
networking), but when I try to start Safe Mode with
networking support I get the same thing.

I believe that my problem is somehow being caused by my
wireless NIC, which is a D-Link DWL-520+. If I disable it
I can run Windows just fine, but as soon as I connect to a
WLAN I get the STOP message again. I have installed the
latest drivers for it, but alas, it makes no difference. I
also have an Ethernet card, which doesn't cause this
problem when I use it, so I don't think that it is a
generic network issue.

I searched for the file mentioned in the STOP message
(dne2000.sys), and it appears to be part of Deterministic
Networking in XP (or whatever its called), but I don't
know how this helps ms.

My PC is an Athlon XP 3000+, with 512MB RAM. I haven't
touched the guts of my PC recently, and I know that my RAM
is good because when I last loaded XP (with my wireless
NIC disabled) I played games and watched movies with no
problems at all. I have had my wireless NIC for over half
a year, with no problems at all. I tried moving the NIC to
another PCI slot, ensuring that it was inserted properly,
but this didn't help.

I have automatic IRQ assignment selected in my BIOS, so I
don't think its an IRQ issue, but I welcome any
suggestions. If the solution is as simple as reinstalling
XP, that isn't a problem, but I'd prefer a quicker and
less painful alternative if possible.

 

[dev]

Brett Sabell said:

I keep getting an annoying BSOD STOP message in Windows XP
SP1 that says the following:

DRIVER_IRQL_NOT_LESS_OR_EQUAL
...
*** STOP: 0x000000D1 (0x0000000C, 0x00000002, 0x00000000,
0xF80AFC00)
*** dne2000.sys - Address F80AFC00 base at F80A9000,
DateStamp 3C3CDBF4

This STOP message is intermittent; sometimes it appears
during a Scan Disk of C: (before I even log in to
Windows), sometimes several hours after using Windows.
Each time it appears, some of the Hex values differ
slightly.

I can start up successfully in Safe Mode (without
networking), but when I try to start Safe Mode with
networking support I get the same thing.

I believe that my problem is somehow being caused by my
wireless NIC, which is a D-Link DWL-520+. If I disable it
I can run Windows just fine, but as soon as I connect to a
WLAN I get the STOP message again. I have installed the
latest drivers for it, but alas, it makes no difference. I
also have an Ethernet card, which doesn't cause this
problem when I use it, so I don't think that it is a
generic network issue.

I searched for the file mentioned in the STOP message
(dne2000.sys), and it appears to be part of Deterministic
Networking in XP (or whatever its called), but I don't
know how this helps ms.

My PC is an Athlon XP 3000+, with 512MB RAM. I haven't
touched the guts of my PC recently, and I know that my RAM
is good because when I last loaded XP (with my wireless
NIC disabled) I played games and watched movies with no
problems at all. I have had my wireless NIC for over half
a year, with no problems at all. I tried moving the NIC to
another PCI slot, ensuring that it was inserted properly,
but this didn't help.

I have automatic IRQ assignment selected in my BIOS, so I
don't think its an IRQ issue, but I welcome any
suggestions. If the solution is as simple as reinstalling
XP, that isn't a problem, but I'd prefer a quicker and
less painful alternative if possible.

A good resource that might lead to a fix...
http://aumha.org/win5/kbestop.htm

 

[Rich Barry]

Brett, check here. http://aumha.org/win5/kbestop.htm
0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
(Click to consult the online Win XP Resource Kit article.)
The system attempted to access pageable memory using a kernel process IRQL
that was too high. The most typical cause is a bad device driver (one that
uses improper addresses). It can also be caused by caused by faulty or
mismatched RAM, or a damaged pagefile
a.. Error Message with RAM Problems or Damaged Virtual Memory Manager {KB
810093} Win XP Home (during restart)
b.. "STOP:0xD1" Error Message When You Start Your Win XP-Based Computer
{KB 316208} Win XP
c.. Stop 0x000000D1 Error Message When You Turn Your Computer Off {KB
317326} Win XP (with USB device(s) connected)
d.. "STOP 0x000000D1 IRQL_NOT_LESS_OR_EQUAL Kbdclass.sys" Error Message
When You Try to Shut Down the Computer {KB 810980} Win 2000, Win XP
(Logitech mouse with outdated MouseWare software)
e.. WRQ AtGuard Program Causes Error Message in Win XP {KB 319870} Win XP
(AtGuard version 3.22)

 

[Brett Sabell]

Thanks for your assistance, but alas, the suggestions at
http://aumha.org/win5/kbestop.htm didn't help.

I think it may be a hardware issue with my Wireless
network card, since I only get this problem when I use the
NIC, and I never get the problem when it is disabled.

The last time I re-installed Windows XP I made a backup
image of my C: partition using Norton Ghost. I have
restored this image several times since then (which
essentially re-creates an EXACT 1:1 replica of my original
C, with no problems at all. I restored that image once
again last night, but alas, I STILL get the STOP error
message. This suggests that it isn't a driver issue, since
I now have the EXACT same setup as I had pre-Ghost backup,
including drivers. I have not touched my hardware setup
since I originally made that Ghost image, so that isn't an
issue either.

I did some investigation and found that the driver
mentioned in the STOP message (dne2000.sys) is used by the
Deterministic Network Enhancer Mini Port (whatever that
is) for each of my network adapters (my D-Link DWL-520+
Wireless and my Realtek RTL8139 Ethernet). This driver
file is not corrupt though, since it must be used when I
use my Ethernet card, which works fine. And since I just
restored my Ghost image of XP (and hence the files are all
new again) the file couldn't possibly be corrupt.

I also don't believe that it is a problem with my RAM,
since it is only the dne2000.sys driver that is causing
this STOP message, and only for the DWL-520+. I have given
my RAM a thorough workout by watching movies, playing
games, even using my Ethernet NIC on my local LAN, but I
don't get the STOP message.

Please help!