Member Avatar for kermie

I keepo getting my Xp computer crashing oin me and going to the blue screen. Commonestr error message is aklong the lines of IRQL_ Not_les_than_ equal-To or similar to this and often blames miscellaneuos drivers although removal of these drivers mnakes no difference and scanning of valaidity of drivers shows no problems. Other blames include memory inconsiostenies or video apater although all the MS troubleshootinh has resulted in lions 1 christians nil and i am pulling out my hair.

My event viewer gives error mesages for systyems after crashes stating that "NAt was unable to request an operation of the Kernel mode translation module". During the use, get mouse freezing and other peculiar problem. Friend suggested that an update if using wrong memory and correpting drivers and Microsoft trouble shooting has been uselsss,

Problem gets worse until crashing every minute. Reload Windows XP, problem is gone for while but eventual;ly starts to occur again and again with increasing frequency until autoi save on woird set to 1 nminute.

Any ideas guys and thanks

Kermie:sad: :sad:

  • 2 Contributors
  • 6 Replies
  • 298 Views
  • 1 Day Discussion Span
  • Latest Post Latest Post by kermie

Dani AI

Generated

Short expert summary and context: reported repeated XP blue‑screen crashes with the IRQL_NOT_LESS_OR_EQUAL stop and an Event Viewer entry referencing NAT/kernel translation; ’s TCP/IP change helped briefly. The 0xA IRQL stop normally means kernel‑mode code tried to access pageable or invalid memory at an elevated IRQL — most often a buggy driver or kernel component. Kernel pool corruption (drivers writing outside their allocation) can also produce seemingly unrelated, rapidly‑worsening BSODs. (learn.microsoft.com)

Practical, prioritized troubleshooting (perform in order):

  • Collect a minidump and analyze it with WinDbg using !analyze -v; a minidump lists loaded drivers and the kernel call stack and is usually the fastest way to point to the offending module. (learn.microsoft.com)

  • Run a full bootable memory test (MemTest86) for multiple full passes to rule out RAM errors; intermittent RAM faults often behave exactly like the symptoms described. (memtest86.com)

  • Use Driver Verifier to stress suspect drivers (start with network, video, and any third‑party filter drivers). Driver Verifier will provoke a controlled crash that makes the bad driver obvious; keep a plan to disable Verifier (verifier /reset) from Safe Mode if the system becomes unbootable. (learn.microsoft.com)

Useful commands (from an administrative prompt):

verifier               (launch Driver Verifier GUI)
verifier /query
verifier /reset
windbg -y srv*C:\Symbols*https://msdl.microsoft.com/download/symbols -z C:\Windows\Minidump\minidump.dmp

Hardware and service checks to close the loop: verify that ICS/NAT or any virtual‑network adapters (VMware, VirtualBox, Hamachi, VPN clients) are not present or are disabled — the Windows NAT driver (ipnat.sys) is tied to ICS/RRAS and problematic network filter drivers can trigger the Event Viewer NAT errors seen in the thread. Reseat/test RAM one DIMM at a time, restore default BIOS timings (disable overclock/XMP), check PSU/temps, and update chipset/video drivers and BIOS. (flylib.com)

Recommended sequence: gather at least one usable minidump, run MemTest86, then run Driver Verifier targeted at likely drivers; disabling ICS/virtual NICs and testing with minimal hardware will quickly distinguish driver/software causes from failing memory or other hardware. Analysis of a crash dump is the most direct way to identify the guilty driver. (learn.microsoft.com)

Recommended Answers

All 6 Replies

Member Avatar for kermie

thanks for the help...err Im a bit of as virgin at this, how do i access the mask???
thanks for the help

Member Avatar for kermie

PS my computer is running stasndalone XP, no lan or netwrok. Does this make a difference??

Member Avatar for Monte

Yes, go to the Control Panel, then Network Connections, Right Click Local Area Connection, go to properties, then Select Internet Protocol (TCP/IP) and to to Properties. Make sure that Obtain IP is selected for both the DNS and IP and hit apply :)

Member Avatar for kermie

Yes, go to the Control Panel, then Network Connections, Right Click Local Area Connection, go to properties, then Select Internet Protocol (TCP/IP) and to to Properties. Make sure that Obtain IP is selected for both the DNS and IP and hit apply :)

thanks mate

this seems to have fixed the problem

hope ya had a good one ofr chrissie

Member Avatar for kermie

Arrrrrgghhhhh!!!!!
spoke too soon.

systemjust dropped out again although took longer time with the changes monte suggested.

Have been told that iot could be "pool damage" by a freidn who sent me this piece of microgarble:
Pool damage is caused when a kernel-mode component writes to memory outside of its allocated pool area. By writing to memory beyond the boundary of its allocated area, it is likely that another area of allocated memory, possibly owned by another component, is overwritten. This damage can cause problems such as blue screens in completely unrelated areas of code. A kernel-mode component reading beyond its allocated area can also cause problem.

Any further suggestions on how to cure this.

thanks

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.