driver_irql_not_less_or_equal

[skylt8]

Recently I purchased 1GB PC3200 DDR memory for my computer. After I installed the new hardware my computer began to crash showing a blue error screen with the words:

DRIVER_IRQL_NOT_LESS_OR_EQUAL and,

PAGE_FAULT_IN_NON_PAGED_AREA

I assumed this was a result of the new memory module I had assigned to my computer so I removed the new module and replaced it again with the 512MB that I had had originally. Unfortunately, the problem has persisted even after removing the new hardware. How can I rectify this problem?

Regards

rob

[N1K]

I had similiar problems with older SDRAM memory modules..

I cleaned the memory slots with compressed air, and have cleaned pins on the memory itself..

After that it was working like a charm..

Also, try to use different memory slot for a start..

[jftuga]

I had the a similar problem come up after I installed Windows Updates last month on a Dell PowerEdge 2850. I did not even touch the hardware. To fix it, I upgraded the PowerEdge BIOS firmware, ESM, and PERC firmware. Once this was done, the system rebooted back into Windows and no blue screens. Next I went ahead and updated the Windows SCSI-RAID PERC 4 driver that I downloaded from Dell's web site.

Good Luck,

-John

Edited April 12, 2006 by jftuga

[Mordac85]

When you get the BSOD it will have some other information like so:

Stop: 0x0000000A (item1, item2, item3, item4) IRQL_NOT_LESS_OR_EQUAL

acpi.sys - Address FC406663 base at FC3FC000 Datestamp 3b7d8550

The other pieces of information refer to exactly what is involved:

Item 1 - The address that was referenced improperly

Item 2 - IRQL that attempted to access the memory

Item 3 - Type of access (0 is a read, 1 is a write)

Item 4 - Address of the instruction that referenced memory in item 1

Now the IRQL_NOT_LESS_OR_EQUAL is sooooo ambiguous that it could be RAM, hardware, a driver, your BIOS, just about anything. However, since you're also getting the Page Fault error I'd start looking at a bad, or buggy, driver. The filename(s) listed on the BSOD should get you pointed in the right direction.