IRQ not less or equal blue screen

August 19, 2007 at 19:26:22
Specs: XP Pro, amd 2ghz / 512
constantly getting the "irq not less or equal" BSOD. I've done everything including wiping my hard drive completely and doing a clean install. Everything worked great for about a month, and all of a sudden it's back.

Specs: asus a7v8x-x, nvidia geforce 4 mx440-8x 128M, 2x kingston 512 DDR sticks, belkin wireless G router and wireless USB (see this post regarding my bad memtest, which hasn't resolved anything: http://computing.net/windowsxp/wwwb...

I've tried updating and rolling back all drivers, running verifier, removing software that may cause the problem, etc.

There doesn't seem to be one universal solution to this problem. Hopefully someone here can help. thanks.


See More: IRQ not less or equal blue screen

Report •


#1
August 19, 2007 at 19:30:58
also get "page fault in non paged area" error

Report •

#2
August 19, 2007 at 20:20:00
The link to your previous thread/subject does not work - apparently it has a bracket at it's end it shouldn't have.

You probably have a problem with the connection of your ram to it's slots.

See response 1, starting at
Stop 0x00000050 error is PAGE_FAULT_NONPAGED_AREA
http://www.computing.net/hardware/w...

AND

If you run a ram test BEFORE you have checked whether the modules are properly seated AND before you have tried cleaning the contacts on the modules, any memory errors found may be invalid if you're having connection problems!
If you have onboard video and are using it, do not force the utility to test all the ram - test the amount it finds by default - or the test will find errors FOR SURE!

If you DO get ram errors after doing those things, THEN it MIGHT be bad, but it is more likely one or more modules is incompatible with your mboard - if it has ALWAYS given you problems since you last installed ram it probably IS incompatible. In your case, go to the Kingston web site and using your make and model number, look up which modules it lists. If the ID string on the modules you have is not on the list, there is no way of telling whether it will work with your mboard and chipset, and whether it will work properly is a crap shot.



Report •

#3
August 19, 2007 at 20:38:16
I am not using on board video, and everything worked fine for 5 years. Once the BSOD started, the only time everything woked smoothly was after I did a clean install of WinXp. That lasted about a month.

When I have just one RAM stick in, memtest passes all tests but I still get the BSOD.


Report •

Related Solutions

#4
August 19, 2007 at 21:09:20
See the info at the above link.
That should at least cure your ram errors.
If after doing that, if it doesn't cure the errors -
- make sure you have the ram installed in the right slots - see your mboard manual - e.g. if your ram is dual channel it is sold in matched pairs, the two modules must be identical, and it must be installed in specific pairs of slots; if it is single channel ram it may not matter where it is installed.
- if all your ram is on the Kingston list of modules, then the one that gives you errors is bad, if it gives errors when installed by itself in all the slots (it is remotely possible a ram slot is bad).
- if it isn't on the list of modules, if a module or modules is incompatible, sometimes one module will work fine, or both will work fine by themselves, but when two modules are installed something is incompatible and you get memory errors, or the total amount of ram detected is not what it actually is by a long shot (a difference of 1 mb if you are not using onboard video, or the amount of ram shared with onboard video possibly plus 1 more mb, is of no concern).

BSOD can be caused by zillions of things.

If it BLACK screens, that's probably a hardware problem. One of the things that can do that is a faulty power supply.Check your PS.
See response 4 in this:
http://www.computing.net/hardware/w...
If it is a BLUE screen , does it give any details, or is there anything to click on that does?
If it BLUE or BLACK screens then it reboots....

Win XP is often set to reboot when it encounters an unrecoverable error.

To have XP display possibly display an error message instead of rebooting:

1. Click Start, and then right-click My Computer.
2. Click Properties.
3. Click the Advanced tab, and then click Settings under Startup and Recovery.
4. Under System failure, click to clear the Automatically restart check box.
5. Click OK, and then click OK.


Report •

#5
August 20, 2007 at 02:16:10
Check ALL your cable connectors inside AND outside the case are properly (tightly) inserted in the slots. I faced your trouble after five years of running without ONE problem due to a loose parallel printer connection. I found the cause only when the printer refused eventually to work (and I run lots of mem and hard drive tests with no results).

Report •

#6
August 20, 2007 at 05:50:01
Is it possible that it could be a bad power supply? I unplugged all cd drives and am runnign on bare requirements. PC seems to be more stable, but the BSOD eventually appears - just not as quickly as before.

Report •

#7
August 20, 2007 at 06:16:51
Possibly - see the link in the middle of response 4 - but you must also have the ram producing no errors.

Report •

#8
August 20, 2007 at 06:40:46
..but you must also have the ram producing no errors.

See dombrorj's earlier thread posted same day as this thread

bad memtest86 results


i_Xp/VistaUser


Report •

#9
August 20, 2007 at 06:49:08
I've already seen it - see response 2 - I removed the bracket in order for the link to work.

Report •

#10
August 20, 2007 at 06:53:01
Hi Tubes - OOps I must have missed that :-( OK I guess I need to get another cup of black coffee :-)

i_Xp/VistaUser


Report •

#11
August 20, 2007 at 15:00:30
well . . I replaced the psu, and that seemed to solve all the issues. No more BSOD (crossing my fingers), and memtest is passing all tests. I can't believe after all of that it was just the power supply.

Report •

#12
August 20, 2007 at 20:25:12
Sounds good. It's quite possible the voltages were out of whack - that can make ram malfuncion but that's not common.

Report •


Ask Question