Re: Error: "IRQL_NOT_LESS_EQUAL" help

From: David Candy (.)
Date: 01/11/05


Date: Tue, 11 Jan 2005 15:54:21 +1100


Bug Check 0xA: IRQL_NOT_LESS_OR_EQUAL
The IRQL_NOT_LESS_OR_EQUAL bug check has a value of 0x0000000A. This indicates that Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.

Parameters
The following parameters are displayed on the blue screen.

      Parameter Description
      1 Memory referenced
      2 IRQL at time of reference
      3 0: Read
      1: Write
     
      4 Address which referenced memory

Cause
This bug check is issued if paged memory (or invalid memory) is accessed when the IRQL is too high.

The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS.

If you encounter bug check 0xA while upgrading to a later version of Microsoft® Windows®, this error might be caused by a device driver, a system service, a virus scanner, or a backup tool that is incompatible with the new version.

Resolving the Problem
If a kernel debugger is available, obtain a stack trace.

To resolve an error caused by a faulty device driver, system service, or BIOS

  1.. Restart your computer.
  2.. Press F8 at the character-based menu that displays the operating system choices.
  3.. Select the Last Known Good Configuration option from the Windows Advanced Options menu. This option is most effective when only one driver or service is added at a time.
To resolve an error caused by an incompatible device driver, system service, virus scanner, or backup tool

  1.. Check the System Log in Event Viewer for error messages that might identify the device or driver that caused the error.
  2.. Try disabling memory caching of the BIOS.
  3.. Run the hardware diagnostics supplied by the system manufacturer, especially the memory scanner. For details on these procedures, see the owner’s manual for your computer.
  4.. Make sure the latest Service Pack is installed.
  5.. If your system has small computer system interface (SCSI) adapters, contact the adapter manufacturer to obtain updated Windows drivers. Try disabling sync negotiation in the SCSI BIOS, checking the cabling and the SCSI IDs of each device, and confirming proper termination.
  6.. For integrated device electronics (IDE) devices, define the onboard IDE port as Primary only. Also, check each IDE device for the proper master/slave/stand-alone setting. Try removing all IDE devices except for hard disks.
If the message appears during an installation of Windows, make sure that the computer and all installed peripherals are listed on the Microsoft Windows Hardware Compatibility List (HCL).

http://oca.microsoft.com/en/windiag.asp

http://www.google.com.au/search?hl=en&q=site%3Amicrosoft.com+IRQL_NOT_LESS_OR_EQUAL&btnG=Google+Search&meta=

-- 
----------------------------------------------------------
http://www.uscricket.com
"Caturn" <Caturn@discussions.microsoft.com> wrote in message news:42763CA2-87EA-44C0-AD32-E4818224B341@microsoft.com...
> These past couple of weeks I've been getting the blue screen with 
> IRQL_NOT_LESS_EQUAL error. I'm at a total loss on what to do about this 
> error. If anyone could help me that would be great because windows won't let 
> me e-mail them for some reason. I've included the technical information found 
> at the bottom of the screen. Thanks to all those that help.
> 
> Technical Information
> 0x0000000A (0x00000004, 0x00000002, 0x00000000, 0x804E339C)


wedge.gif

Relevant Pages

  • Re: Please help!
    ... This bug check is issued if paged memory is accessed ... installation of a faulty device driver, system service, or BIOS. ...
    (microsoft.public.windowsxp.help_and_support)
  • RE: Win 2000 Blue Screen
    ... > Physical memory dump complete. ... Microsoft® Windows®, this error might be caused by a device driver, a system ... To resolve an error caused by a faulty device driver, system service, or BIOS ... Select the Last Known Good Configuration option from the Windows Advanced ...
    (microsoft.public.win2000.general)
  • Re: error signature
    ... memory, maybe some other application was the cause or you have a bad RAM ... device driver, a general hardware problem, and incompatible software. ... This bug check is issued if paged memory is accessed ...
    (microsoft.public.windowsxp.general)
  • Re: Forth as an operating system
    ... Suppose that bug results in failure to yield. ... Or what happens on a memory leak? ... E.g. how to deal with idiots who ... defined interface or architectures, either, and even good programmers tend ...
    (comp.lang.forth)
  • Re: MyString Class
    ... > I compiled your program and run it under the debugger. ... > The first crash happens in ... ... > memory is flawed. ... First bug fixed. ...
    (comp.lang.cpp)