IRQL_NOT_LESS_OR_EQUAL

[Guest]

Ive read articles and forum and the newsgroup regarding this message and id
gladly follow any instructions resolve my issue.

the problem is, I get the IRQL_NOT_LESS_OR_EQUAL screen whenever I try to go
into the Recovery Console in XP SP2

My original issue was regarding a missing or currupt SYSTEM file, I know how
to fix this. Problem is, I cant fix it cuz I get the IRQL_NOT_LESS_OR_EQUAL
error when i try to get into the RC or go into the XP install.

Same error when plugged into different PC systems.

Current system only has a CD-ROM, HDD, CPU, RAM and MB. No other hardware

anyone know what I can do?

 

[AJR]

The Stop Message indicatesa kernel-mode process or driver attempted toaccess
memory to which it did not have permission and is usually the result of
faulty or incompatible hardware or software (Just about anything!).
The complete message would have indicated the memory address, the IRQL
required and the type of access (OxOO-read or 0x01 - write).

The last parameter gives address of the bogus instruction and if it is a
driver at fault the parameter usually indicates the driver name.

1. Try the "Last Known Good Configuration" option - if successful
indicates a faulty driver, system service or BIOS.
2. Check System Log in Event Viewer.
3. Disable memory caching of the BIOS.
4. Run memory diagnostics.
5. Try removing all IDE devices except for the HD.

 

[Guest]

Well, options 1 & 2, I can't do seeing as how i can't get into Windows XP.

For option 5, I'll need to keep the CD-ROM connected if I want to use the
Recovery Console off the CD

Option 4, if i can find a memory diagnotic program that will boot on its
own, then i can try that.

option 3 looks to be the only option I can try right now.

 

[Guest]

I should also have mentioned that when I move the HDD to other systems, the
exact same thing happens.

 

[Rock]

I should also have mentioned that when I move the HDD to other systems, the
exact same thing happens.

What do you mean by move the HDD to another computer? Do you mean install
it as the boot drive or as a slave drive? If you haven't tried it as a
slave drive do that. In that situation you can perform the fix on the slave
drive for the registry problem without going into the recovery console.

Also you could put the drive in an external drive enclosure and attach it to
another computer.