:irql_not_less_not_equal - Help !

[UKDoms]

After updating my(works/dads) win2000 (prof.) to sp1, i getting the irql error. This happens after i have started up image editors or applications that use a lot of the memory. The message i recieve is:

code:
------------------------------------------------------------

STOP: 0x0000000A (0x0B2F0620, 0x00000002, 0x00000001, 0x80445D40)

IRQL_NOT_LESS_OR_EQUAL

Address 80445D40base at 80400000, Date Stamp 384d9b17 - ntoskrnl.exe

------------------------------------------------------------

I have recently uninstalled a lot of my applications and the update patch (hotfixes), though the problem still arises !
I have also looked at many sites, especially the microsoft support pages, and they say that its down to a 'buggy' driver? - in which case the driver should of been uninstalled when i unistalled the application as the system worked fine before !
I don't really want to install drivers or update patches just incase that it decides to crash half way through a install.
Is there a way to reinstall drivers from the CD ? And does anyone have any ideas on this?

Thanks,
Dom


code:
------------------------------------------------------------

SYSTEM:PIII - 1GHz
LG DVD
Adaptec Scsi card + HD
ATI Rage 128 expert (something like that)
MSI Motherboard - 694D Pro (MS-6321)
512mb SDRAM

[l0m4x]

Try using different RAM. or if you have more than 1 'stick' of ram try taking one or the other out.

[cleancut]

IRQ stop mess.
Check all scuzzy connections internally'
Try updating video drivers

[POBrien]

http://www.windows2000faq.com/Articles/Index.cfm?ArticleID=14562

Patrick (http://www.winguides.com/forums/sendprivate.php?Cat=&User=POBrien&Board=&Number=&what=online&page=&view=&sb=&part=&vc=><font)</font color=green> /images/forums/icons/smile.gif
<a target="_blank" href=http://www.winguides.com/subscribe/?guide=registry>WinGuides</a>

[Andy-S]

If the system was working fine before adding SP1, you could try removing SP1 or upgrading to SP2 to see if that helps any.

Cheers
Andy

[reghakr]

Can't emember where this came from:

Error Message:
STOP: 0x0000000A (parameter, parameter, parameter, parameter) IRQL_NOT_LESS_OR_EQUAL

Explanation:
This is a Windows 2000 Executive character-mode STOP message. It indicates an attempt was made to touch pageable memory at a process IRQL (interrupt request level) that is too high. This is usually caused by drivers using incorrect addresses. The fourth parameter in the message parameter list is the memory address at which the fault happened. The second parameter shows the IRQL. If the IRQL was not equal to 2, then the interrupt most likely came from a driver. Compare the memory address in the fourth parameter with the base addresses of the drivers in the driver table on the STOP screen to find the driver that is the problem. Note that the third parameter encodes read/write access (0 = read, 1= write).

User Action:
If this is the first time you have booted after installing new hardware, remove the hardware and boot again. Check the Microsoft Hardware Compatibility List to verify that the hardware and its drivers are compatible with Windows 2000. For information about the hardware, contact the supplier. If you are installing Windows 2000 for the first time, check the Windows 2000 system requirements, including the amount of RAM and disk space required to load the operating system. Also, check the Hardware Compatibility List to verify that the system can run Windows 2000. If Windows 2000 is loaded and no new hardware has been installed, reboot with recovery options set to create a dump file. If the message continues to appear, select the Last Known Good option when you reboot. If there is no Last Known Good configuration, try using the Emergency Repair Disk. If you do not have an Emergency Repair Disk, contact your technical support group.

reghakr

[gavsta]

used to get this problem on my laptop. it turned out it was a problem with the wireless networking components. Some little app that redirects the Wireless to IP I think, something called WinRT.

The problem occured once I updated my wireless drivers and didn't update the component software.