IRQL_ Not_les_than_ equal, blue screens, and windows crashing
Expand Post »
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.
Here ya go bro, i got a link for ya that tells you excatly how to fix it. It is a problem with your NAT address pool is configured so that the start address is the same as the end address and the mask is 255.255.255.255.
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
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
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.
No one has posted to this discussion for at least three months. Please let old threads die and do not reply to them unless you feel you have something new and valuable to contribute that absolutely must be added to make the discussion complete. Otherwise, please start a new thread in this forum instead.
Previous Thread in Windows NT / 2000 / XP Forum Timeline:Debugg Error
Next Thread in Windows NT / 2000 / XP Forum Timeline:no windows xp