Member Avatar for frogeye

Hello
I have a problem with a laptop. it hangs on something and then when i try to reboot, it wont reboot except in safe mode. the first time that it happened was just after i had updated windows, and i thought that the update had caused it. this is a hp pavilion with scan to web software and there were problems with one of ( or several ) of the updates from Microsoft. anyway the problem resolved itself and i thought that everything was ok, but now it is starting up again only this time it isnt resolving itself.
the stop screen has the following info:
DRIVER_IRQL_NOT_LESS_OR_EQUAL
STOP 0x000000D1 (0x00000000,0x00000002,0x00000001,0xF83CD67D)


I have uninstalled all spyware/antivirus software, and have tried selecting the no paging file option under performance options in system information. also looked through the eventlogs, but I didn't really know what to look for and i didn't see anything that looked obvious.

I have been to the troubleshooting guide for windows stop errors at aumha.org and went through several things that may have been close , but i haven't been able to resolve the issue.

I would be very grateful for any suggestions
thanks in advance
frogeye

  • 2 Contributors
  • 3 Replies
  • 95 Views
  • 18 Hours Discussion Span
  • Latest Post Latest Post by Chaky

Dani AI

Generated

Good troubleshooting by and useful direction from — that combination (confirming a reproducible STOP code and focusing on drivers) is exactly the right approach for a STOP 0xD1. The official definition is that a kernel‑mode driver tried to access pageable memory at too high an IRQL; that points the investigation at kernel drivers rather than user apps. See Microsoft’s explanation for the bug check here: .

Next steps that make the fix durable and help find root cause:

  • Replace or update the suspect network stack drivers from the laptop OEM or the NIC vendor, and also keep chipset and platform drivers current. Vendor-supplied drivers are less likely to introduce kernel mismatches than very old or generic drivers.
  • Look for third‑party kernel network filters (VPN clients, packet capture libraries, firewall/NDIS filter drivers) — these are common contributors to network-related D1 crashes. Remove or update any non‑Microsoft network filter software.
  • If the crash recurs, enable Driver Verifier for third‑party drivers to force a diagnostic failure and create a reliable dump for analysis. Microsoft’s Driver Verifier guide explains how to run it safely: Driver Verifier.

For deeper diagnosis, collect minidump files and analyze them with WinDbg (or provide them to the vendor). The dumps will show the faulting module and call stack, which is the definitive evidence for which driver failed. If problems persist after driver updates, also check OEM BIOS/firmware updates and run a memory test to rule out hardware corruption.

Recommended Answers

All 3 Replies

Member Avatar for Chaky

You have driver issue on your hands. (kind of, obvious)
Try disableing display driver in your device manager. (in safe mode).

If it manages to reboot, uninstall the disabled driver and re-install it.
If not, reenable the driver and take a look in event viewer (will have to enable administrative tools in "taskbar and start menu" settings) where you can see a log of things that failed on your system.
Even better way is to look under "problem devices" in Programs/Accessories/system tools/system information to see the list of drivers that failed to start.

Please, post your findings.

Member Avatar for frogeye

gott it!
I had noticed that the problem seemed ot occur when i was tryingot access the internet, so i disabled the network adapter. bingo, it booted right up so i uninstalled the adapter and scanned for new hardware. everytihgn seems to be working great.

Member Avatar for Chaky

That went painless.

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.