Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1028
  • Last Modified:

IRQL NOT LESS OR EQUAL software cause

I am getting the blue screen with IRQL_NOT_LESS_OR_EQUAL but only when I run a communications utility within my application (a custom vb2005 and C++ graphics manipulation program). The communications feature uses an RS232 connection to a similar program on another computer to exchange information. Lower down the blue screen it says:
*** stop: 0x0000000A (0x0000BA33,0x00000002,0x00000001,0x806E6A8E)
The computers are Winows XP, SP3.
We currently use the motherboard RS232. I'll try an adaptor. Any other suggestions?
Thanks
0
focuser
Asked:
focuser
5 Solutions
 
akajohnCommented:
You will need to go into Device Manager or your Bios and check which hardware devices, (Hard disk Controller, Sound Card , Network Card, etc...) is using the same IRQ. (Make a list) You have a conflict and possibly some old interface card refuse to use IRQ numbers that are higher than 5 which restricts the choices. Ideally, run it on a machine with no external cards in the  slots!

Also see if you can change the IRQ of the COM 1 or COM 2 port. (RS 232) in the bios.

This is very annoying and We wish you good luck, It is trial and error until you find the right combination.

A>
0
 
signin_sivaCommented:
This is usually a memory fault (either faulty RAM or faulty sockets on the board). Grab memtest and see what it reports.
0
 
lordrtCommented:
usually a RAM fault, try remove one by one if you have more than 1 installed and switch on to know which one is causing this fault, and replace if needed with a new one
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
willcompCommented:
Contrary to the responses above, the BSOD in question is usually caused by a driver. Can you change the driver used? Attach a recent minidump (located in C:\windows\minidump folder) and we'll try to pinpoint the driver at fault.
0
 
focuserAuthor Commented:
Changing Com1;s IRQ, from 04 to 03, by changing the settings selection in Device Manager, did not help. When communications was turned on it happened again. I'm attaching the minidump log.

Mini031511-01.dmp
0
 
willcompCommented:
The faulting driver is serial.sys which is probably located here: c:\windows\system32\drivers\serial.sys

Try copying serial.sys from another PC with same version of Windows.

I've attached the complete dump analysis log. Analysis.log
0
 
focuserAuthor Commented:
copying serial.sys in from the neighboring xp computer didn't help. Could the pointer to serial.sys indicate the utility using serial.sys (communications)?
I'll try reloading my main application. Then I suppose I should try a USB to serial adaptor.
0
 
focuserAuthor Commented:
Using a PCIE board with 2 comports has solved my problem.
Thanks all.
0

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now