IRQ less Than or equal to Error

  • Thread starter Thread starter Dragon
  • Start date Start date
D

Dragon

My computer got blue screen "IRQ_LESS_THAN_OR_EQUAL_TO" Error when I run a
program.
below is the 64KB dump after running dumpchk.
How can I diagnose this dump check ???

Thank you..


----- 32 bit Kernel Mini Dump Analysis

DUMP_HEADER32:
MajorVersion 0000000f
MinorVersion 00000a28
DirectoryTableBase 007a6000
PfnDataBase 81000000
PsLoadedModuleList 8055d720
PsActiveProcessHead 805638b8
MachineImageType 0000014c
NumberProcessors 00000002
BugCheckCode 1000000a
BugCheckParameter1 00000000
BugCheckParameter2 00000002
BugCheckParameter3 00000000
BugCheckParameter4 80509943
PaeEnabled 00000001
KdDebuggerDataBlock 8054d2e0
MiniDumpFields 00000dff

TRIAGE_DUMP32:
ServicePackBuild 00000300
SizeOfDump 00010000
ValidOffset 0000fffc
ContextOffset 00000320
ExceptionOffset 000007d0
MmOffset 00001068
UnloadedDriversOffset 000010a0
PrcbOffset 00001878
ProcessOffset 000024c8
ThreadOffset 00002728
CallStackOffset 00002980
SizeOfCallStack 00000584
DriverListOffset 00003198
DriverCount 0000009f
StringPoolOffset 000060d0
StringPoolSize 00001610
BrokenDriverOffset 00000000
TriageOptions 00000041
TopOfStack ba4d3a7c
DebuggerDataOffset 00002f08
DebuggerDataSize 00000290
DataBlocksOffset 000076e0
DataBlocksCount 00000004


Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86
compatible
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Tue Jul 08 02:14:02 2008
System Uptime: 0 days 0:02:15
start end module name
804d7000 806e4000 nt Checksum: 001F442E Timestamp: Mon Apr 14
02:31:06 2008 (4802516A)

Unloaded modules:
a891e000 a8933000 naveng.sys Timestamp: unavailable (00000000)
a8933000 a8a03000 navex15.sys Timestamp: unavailable (00000000)
acae5000 acafa000 naveng.sys Timestamp: unavailable (00000000)
acafa000 acbca000 navex15.sys Timestamp: unavailable (00000000)
ba74e000 ba74f000 drmkaud.sys Timestamp: unavailable (00000000)
a9841000 a984e000 DMusic.sys Timestamp: unavailable (00000000)
a97a1000 a97c4000 aec.sys Timestamp: unavailable (00000000)
a9871000 a987f000 swmidi.sys Timestamp: unavailable (00000000)
ba66a000 ba66c000 splitter.sys Timestamp: unavailable (00000000)
b9b74000 b9b78000 kbdhid.sys Timestamp: unavailable (00000000)
ba318000 ba325000 i8042prt.SYS Timestamp: unavailable (00000000)
ba3f8000 ba3fd000 Cdaudio.SYS Timestamp: unavailable (00000000)
b9b7c000 b9b7f000 Sfloppy.SYS Timestamp: unavailable (00000000)

Finished dump check
 
Dragon said:
My computer got blue screen "IRQ_LESS_THAN_OR_EQUAL_TO" Error whenever I
run a program.
below is the 64KB dump after running dumpchk.
How can I diagnose this dump check ???

Thank you..
Click to expand...

Which program? Insufficient Data here.
I doubt if you can. Instead, go research (Google) just the error message
itself, (IRQ_LESS_THAN_OR_EQUAL_TO), with perhaps its STOP CODE number if
there was one (something like 000008E or whatever)
 
Dragon said:
My computer got blue screen "IRQ_LESS_THAN_OR_EQUAL_TO" Error when I run a
program.
below is the 64KB dump after running dumpchk.
How can I diagnose this dump check ???

Thank you..


----- 32 bit Kernel Mini Dump Analysis

DUMP_HEADER32:
MajorVersion 0000000f
MinorVersion 00000a28
DirectoryTableBase 007a6000
PfnDataBase 81000000
PsLoadedModuleList 8055d720
PsActiveProcessHead 805638b8
MachineImageType 0000014c
NumberProcessors 00000002
BugCheckCode 1000000a
BugCheckParameter1 00000000
BugCheckParameter2 00000002
BugCheckParameter3 00000000
BugCheckParameter4 80509943
PaeEnabled 00000001
KdDebuggerDataBlock 8054d2e0
MiniDumpFields 00000dff

TRIAGE_DUMP32:
ServicePackBuild 00000300
SizeOfDump 00010000
ValidOffset 0000fffc
ContextOffset 00000320
ExceptionOffset 000007d0
MmOffset 00001068
UnloadedDriversOffset 000010a0
PrcbOffset 00001878
ProcessOffset 000024c8
ThreadOffset 00002728
CallStackOffset 00002980
SizeOfCallStack 00000584
DriverListOffset 00003198
DriverCount 0000009f
StringPoolOffset 000060d0
StringPoolSize 00001610
BrokenDriverOffset 00000000
TriageOptions 00000041
TopOfStack ba4d3a7c
DebuggerDataOffset 00002f08
DebuggerDataSize 00000290
DataBlocksOffset 000076e0
DataBlocksCount 00000004


Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86
compatible
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Tue Jul 08 02:14:02 2008
System Uptime: 0 days 0:02:15
start end module name
804d7000 806e4000 nt Checksum: 001F442E Timestamp: Mon Apr 14
02:31:06 2008 (4802516A)

Unloaded modules:
a891e000 a8933000 naveng.sys Timestamp: unavailable (00000000)
a8933000 a8a03000 navex15.sys Timestamp: unavailable (00000000)
acae5000 acafa000 naveng.sys Timestamp: unavailable (00000000)
acafa000 acbca000 navex15.sys Timestamp: unavailable (00000000)
ba74e000 ba74f000 drmkaud.sys Timestamp: unavailable (00000000)
a9841000 a984e000 DMusic.sys Timestamp: unavailable (00000000)
a97a1000 a97c4000 aec.sys Timestamp: unavailable (00000000)
a9871000 a987f000 swmidi.sys Timestamp: unavailable (00000000)
ba66a000 ba66c000 splitter.sys Timestamp: unavailable (00000000)
b9b74000 b9b78000 kbdhid.sys Timestamp: unavailable (00000000)
ba318000 ba325000 i8042prt.SYS Timestamp: unavailable (00000000)
ba3f8000 ba3fd000 Cdaudio.SYS Timestamp: unavailable (00000000)
b9b7c000 b9b7f000 Sfloppy.SYS Timestamp: unavailable (00000000)

Finished dump check
Click to expand...

Stop codes are here. Look for "0A".

http://aumha.org/a/stop.htm

"Typically due to a bad driver, or faulty or incompatible hardware or
software. Technically, this error condition means that a kernel-mode
process or driver tried to access a memory location to which it did
not have permission, or at a kernel Interrupt ReQuest Level (IRQL)
that was too high. (A kernel-mode process can access only other
processes that have an IRQL lower than, or equal to, its own.)"

I don't know what to do with the rest of it. Not all those listed files
will have been at fault. The NAV ones could be Norton AntiVirus.

Paul
 
Background information on Stop Error message
http://msdn2.microsoft.com/en-us/library/ms793589.aspx

0x0000000A: IRQL_NOT_LESS_OR_EQUAL
Typically due to a bad driver, or faulty or incompatible hardware or
software. Use the General Troubleshooting of STOP Messages checklist
above. Technically, this error condition means that a kernel-mode
process or driver tried to access a memory location to which it did not
have permission, or at a kernel Interrupt ReQuest Level (IRQL) that was
too high. (A kernel-mode process can access only other processes that
have an IRQL lower than, or equal to, its own.)
Source: http://aumha.org/a/stop.htm

Please post copies of all Error and Warning Reports appearing in
the System and Application logs in Event Viewer for the last boot. No
Information Reports or Duplicates please. Indicate which also appear in
a previous boot.

You can access Event Viewer by selecting Start, Control Panel,
Administrative Tools, and Event Viewer.

A tip for posting copies of Error Reports! Run Event Viewer and double
click on the error you want to copy. In the window, which appears is a
button resembling two pages. Click the button and close Event
Viewer.Now start your message (email) and do a paste into the body of
the message. Make sure this is the first paste after exiting from
Event Viewer.

Are there any yellow question marks in Device Manager? Right click on
the My Computer icon on your Desktop and select Properties,
Hardware,Device Manager. If yes what is the Device Error code?

Try Start, Run, type "sigverif.exe" without quotes and hit OK. What
drivers are listed as unsigned? Disregard those which are not checked.

Remove any dust bunnies from inside the computer casing using an Air
Duster and check all fans are running.


--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
 
Back
Top