IRQ channel conflicts

[Seamus]

I have a HP Omnibook XE3 running Windows XP (OEM) with
256Mb RAM. The laptop is factory-fitted with a Synaptics
ps/2 pointigng device.

The problem is that I have been getting the blue screen
of death for 2 years and no level of reading support or
re-installing Windows fixes the problem permanently. The
most common message I get when the laptop crashes is an
IRQ_NOT_LESS_OR_EQUAL. When booting the computer, it
regularly states that there is an error in
WINDOWS\SYSTEM32\CONFIG\SYSTEM and to press "r" to repair
in SETUP on reboot.

I have recently installed a wireless network at home
using a D-link wireless router DI-624+ distributing ADSL
from a D-link 302 ADSL modem to a D-link DWL-650+ PCMCIA
card on the laptop. The problem is now that the number of
blue screens of death and the booting problems still
occur, but are compounded by the PCMCIA card and
Synaptics pointing device/touchpad simultaneously
freezing. When the pointing device unfreezes, the
wireless PCMCIA card is no longer recognised by the
computer.

I have tried reading everything I can on IRQs and
everything points to XP handling IRQ assignment and that
only experienced computer professionals should reassign
this resource in Device Manager. This is too far beyond
my experience. HP say its nothing to do with their
computer. Synaptics says not to update the driver without
HP's OK, as it may have been customised. D-link support
site does not reference IRQ channel conflicts.

All I know is that as soon as I can afford a new laptop,
I'll throw the whole lot in the bin. Can anyone advise on
appropriate steps in the meantime?

 

[KevinK]

Do a search of the MSKB for the IRQ_NOT_Less...
I had the same issue with adesktop, and it had the
solution.

Unfortunately, had it with another machine, and it was a
out of date card, no current drivers. Upgraded the SCSI
card and I haven't had a problem.

KlK

 

[Tom]

WOW,sounds like an H/P problem to me,but what the hay,i'm
just a regular Joe!Ok can you check the system
information for me?start > all programs > accessories >
system tools > system information > click it > + next to
hardware > highlite IRQ's....list the device sharing the
IRQ with the touch pad...also check out (conflicts and
sharing) and (forced hardware).If you dont want to change
the IRQ's path,you can get you a USB mouse plug it in and
go to your hardware manager and the disable your touch
pad,then you'll have to use the mouse to navigate,and the
IRQ for the touch pad won't be in use.See if you had a
desktop would be easier for me to help you.Most IRQ's can
be fixed by switching PCI slots with something else.Not
sure of laptops if you can do this,but if you have more
than one slot try the card in a different slot so it
won't conflict with others.Sharing is not a bad thing in
IRQ's unless you get one that hogs it up.Well post back
to this tread with what is sharing your touchpad.

 

[Tcheukraki]

I had the exact problem on my desktop. I had deleted or
added driver files to the win32 driver folder and the
system didn't agree that they were supposed to be there.
Luckily I have 2 hard drives... I had to reinstall WinXP
on the other hard drive and delete to first install. Then
of course reinstalling all the drivers... very tedious,
but the IRQ_NOT_LESS_THEN... went away. If there is an
easier way, good luck.