Member Avatar for F083153WM

While booting up I got the blue screen.
It started off with DRIVER_IRQL_NOT_LESS_OR_EQUAL
Then gave the talk about going in safemode to disable cache etc.
Further down on the screen it said
STOP 0x000000d1 (0XFE3E5E30,0X00000002,0X00000000,0XF99DADD3)
NDIS.SYS - Address F99DADD3 base at F99C4000 DATESTAMP 41107ecs


Start of physical dump -


Where should I go from here ??
It rebooted ok, does this mean that there is not a problem??
Should I do something else ??

  • 2 Contributors
  • 2 Replies
  • 110 Views
  • 8 Hours Discussion Span
  • Latest Post Latest Post by F083153WM

Dani AI

Generated

reported a Windows XP blue screen showing NDIS.SYS and a 0xD1 stop; correctly suggested the network stack. A 0xD1 (DRIVER_IRQL_NOT_LESS_OR_EQUAL) usually means a kernel driver tried to access memory at the wrong IRQL. NDIS.SYS is the network subsystem, but the root cause is commonly a third‑party NIC driver, a network filter driver (antivirus, VPN, firewall), or failing NIC hardware. A single successful reboot does not guarantee the problem is solved.

Immediate diagnostics and quick checks:

  • Confirm kernel minidumps are being written to C:\Windows\Minidump and examine the latest .dmp with a dump viewer such as BlueScreenView or with WinDbg. The dump will usually point to the offending .sys.
  • Inspect the System log in Event Viewer for errors at the crash time.
  • Update or roll back the network adapter driver from the Dell support page or the NIC vendor. Remove any Linksys utility or extra network software that was installed when the router was added.
  • Check for third‑party network filters (antivirus, VPN clients, firewall drivers) and update or temporarily uninstall them.

Suggested troubleshooting order:

  • Boot Safe Mode to see if the crash reproduces.
  • Do a clean boot (msconfig) to isolate non‑Microsoft services and drivers.
  • If crashes continue, run a memory test (see MemTest86) to rule out RAM faults.
  • If the dump names a specific third‑party .sys, update or uninstall that driver. If needed, try a different NIC (USB/PCI) to rule out hardware.

Background note: NDIS.SYS frequently appears in these dumps but is often the victim, not the cause. If the problem repeats, focus on the exact .sys file shown in the minidump. For technical reference see Microsoft’s bug check documentation: .

Caution: create a restore point and back up important data before updating or changing drivers.

Member Avatar for thunderace1k

Hmmm, you don't say a lot about your system...

Is it Windows 2000?

Your problem seems related to your network card / driver.

Maybe this article will help you:

Member Avatar for F083153WM

my mistake,
I am on windows XP on a Dell PC, I also added a router a couple weeks back.
Its a Linksys wireless -g 2.4 router. Everything with the router seemed fine since install.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.