Windows Forum

Ask something
Discussion Locked

IRQL error message

0 helpful
9 replies

by mike o

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Heya folks,

I'm getting an odd error message while installing Windows XP. I have ten machines I've built from scratch, all identical. On two of the first three, however, I'm running into a strange error message.

I boot from the CD to install, it runs through the boot routine, gets to the point where it asks if I want to install XP or repair a current install, then suddenly goes to a blue screen with the following error message:

IRQL_NOT_EQUAL_OR_LESS

It suggests some BIOS tweaks, which either don't work or are irrelevant to this board. I tried using a different installation CD just for kicks and I'm getting the same problem.

Any ideas?

Take care,
Mike

9 replies

by quintar51

What are the hardware specs for one of the machines? Is all the hardware compatible with XP?
I don't think it's the cds that are bad in this case, but try copying the contents of the cd to the hard drive and installing from there. Just a thought.

by mike o

It's not the CD's, I've got it working on other machines. I'm up to three out seven getting the same problem. They're AMD Duron 1.7 machines with Gigabyte boards, AGP video cards, and D-Link NICs. On the machines where the install DOES work, I never have to install a single driver, Windows XP takes care of everything.

by wcp

Most likely the D-Link NIC is the bad guy.

Take it out. Install Windows from scratch again.
If it works, try to put the NIC into a diffeerent slot.

If you get the same error without the NIC, it must be the video card.

by mike o

No luck with the NIC... I've tried it in different slots and tried removing it completely, but I still get the same error messages. I don't have a spare video card to try, but of 10 machines -- all using the same NIC's and same video cards in the same slots with the same BIOS settings -- I only get the error in five of the machines. Thanks for the suggestion, though.

by walesobo

Specific Trouble Shooting
1. Stop 0x0000000A or IRQL_NOT _LESS_OR_EQUAL ---This error is typically caused by faulty or incompatible harware or software attempting to access a memory location without authorization. Suspect an incompatilbe driver, system service, virus scanner, or backup program.
2. Stop 0x0000001E or KMODE_EXCEPTION_NOT_HANDLED---The XP kernel detected an illegal or unknown processor instruction. This is often caused by faulty drivers or hardware devices.
5. Stop 0x0000003F or NO_MORE_SYSTEM_PTES---This occurs when your system runs out of page table entries (PTEs). Consult Knowledge Base article Q256004.
6. Stop 0x00000050 or PAGE_FAULT_IN_NONPAGED_AREA---This may be caused by defective physical memory or incompatile software which caused a hardware driver or service request for data that was not in memory. If the error occured after installing a device driver or application, try using Safe Mode and removing the driver or program.
7.Stop 0x00000077 or KERNEL_STACK_INPAGE_ERROR---This error can be caused by defective memory, a malfunctioning HD, an improperly configured disk controller or cable, corrupted data, or a virus infection when an attempt was made to read kernel data from virtual memory and failed to find the data at the memory address.
9. Stop 0x0000007A or KERNEL_DATA_INPAGE_ERROR---This error may be due to an incompatible disk or controller drivers or hardware problems. Run the windows XP check disk utility or use a more comprehensive disk utility obtained from the disk manufacturer.

by mike o

I've found these on the MS Knowledge Base as well, only they didn't do me much good. Just recently (today) I hit on the Page Fault in Nonpaged Area problem. It's kind of driving me nuts because I've got ten machines, all identical as far asparts and configuration, and I'm only getting the problem on half the machines.

by walesobo

Specific Trouble Shooting
1. Stop 0x0000000A or IRQL_NOT _LESS_OR_EQUAL ---This error is typically caused by faulty or incompatible harware or software attempting to access a memory location without authorization. Suspect an incompatilbe driver, system service, virus scanner, or backup program.
2. Stop 0x0000001E or KMODE_EXCEPTION_NOT_HANDLED---The XP kernel detected an illegal or unknown processor instruction. This is often caused by faulty drivers or hardware devices.
5. Stop 0x0000003F or NO_MORE_SYSTEM_PTES---This occurs when your system runs out of page table entries (PTEs). Consult Knowledge Base article Q256004.
6. Stop 0x00000050 or PAGE_FAULT_IN_NONPAGED_AREA---This may be caused by defective physical memory or incompatile software which caused a hardware driver or service request for data that was not in memory. If the error occured after installing a device driver or application, try using Safe Mode and removing the driver or program.
7.Stop 0x00000077 or KERNEL_STACK_INPAGE_ERROR---This error can be caused by defective memory, a malfunctioning HD, an improperly configured disk controller or cable, corrupted data, or a virus infection when an attempt was made to read kernel data from virtual memory and failed to find the data at the memory address.
9. Stop 0x0000007A or KERNEL_DATA_INPAGE_ERROR---This error may be due to an incompatible disk or controller drivers or hardware problems. Run the windows XP check disk utility or use a more comprehensive disk utility obtained from the disk manufacturer.

This discussion is closed to new replies.