Help! (IRQL_NOT_LESS_OR_EQUAL)

[TheWinter]

Hey guys... when I play some videos or start most games I get blue screen crash
with the message IRQL_NOT_LESS_OR_EQUAL and no specific error
Currently when I start my PC a program called atkkbservice.exe crashes
I'm not sure if that is relevant (don't think so)
When I start the videos that crash in VLC on WMP - I get audio and no video so perhaps that is an indication that it is not an audiio driver/hardware error.. Any help is appreciated
Thanks!

[JohnnyMalaria]

It is a driver error but what causes it could be a number of things including a bug in the driver or a fault with the hardware that the driver communicates with.

When you get the blue screen, there is a whole bunch of stuff that provides information about exactly what driver is crashing and where (within the driver's code). If you can make a note of it and post it here, it may give others some clues.

(What's happening is that the driver is running some of its functions at a time when it is prohibited. There a number of "levels" that software in the kernel can run in and they have different priorities. Many functions must only be performed when the "level" is below a certain priority - hence the name for the error.)

[Soopafresh]

atkkbservice.exe is Asus Keyboard service, but I'll bet it's your video drivers causing the IRQL error. Upgrade them.

[TheWinter]

0x0000000A(0x00000000, 0x0000001C, 0x00000000, 0x805022D7)
This?

[painkiller]

I have had similar messages in the past (but with a bit more data after that message).

Before trying other (above) suggestions, I would recommend you do the following:

Power down the computer, clean it out if needed (dust, what have you) with an air can.
Then reseat your memory.
Double check all electrical connections, that they are completely connected.

The first time this happened to me, I found I had a bad memory stick that needed replacing.
The second time, a different memory stick had come loose. (Or was never completely seated and worked loose.)

This might be your first, best solution.

If not, try updating drivers (but I suspect most times this message is telling you of a hardware problem).

Good luck.

[TheWinter]

All my hardware is like 2 months ols and spotless... I thought of bad memory and took out 2 / 4 of my 1 gig ram and problem persisted and i was too lazy to power down and try the other 2.. but I'll do that now and be embarassed if it works

[TheWinter]

No dice.

[painkiller]

Very well then. At least we know there isn't a hardware problem.

You will have to consider (remember) what your last piece of of software you installed.
It is likely your cause stems from that.
Whether it replaced/overwrote drivers or something.

YOu don't have a restore ability maybe?

[JohnnyMalaria]

Very well then. At least we know there isn't a hardware problem.

I'm not sure we can say that. Being 2 months old and spotless doesn't necessarily mean it is not faulty, though it is more likely that the driver is at fault.

The BSOD should provide more info than just the one line of information and can be retrieved via the Event Log to see what driver was responsible:

http://www.bleepingcomputer.com/forums/topic40108.html

[aedipuss]

the error you mention can be caused by a conflict between game copy protection and nero inCD.

[TheWinter]

Ok I used event viewer and the one with matching error code has the following DATA

IN WORDS:
0000: 74737953 45206d65 726f7272 72452020
0010: 20726f72 65646f63 30303120 30303030
0020: 50202061 6d617261 72657465 30302073
0030: 30303030 202c3030 30303030 63313030
0040: 3030202c 30303030 202c3030 30353038
0050: 37643232
IN BYTES:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 31 30 30 30 30 30 30 1000000
0020: 61 20 20 50 61 72 61 6d a Param
0028: 65 74 65 72 73 20 30 30 eters 00
0030: 30 30 30 30 30 30 2c 20 000000,
0038: 30 30 30 30 30 30 31 63 0000001c
0040: 2c 20 30 30 30 30 30 30 , 000000
0048: 30 30 2c 20 38 30 35 30 00, 8050
0050: 32 32 64 37 22d7

I hope this helps, thank a lot guys!

[TheWinter]

bump

[JohnnyMalaria]

Is the info in the event log all that was there? If so, you need to find the "mini dump" file that Windows creates whenever there is a bug check (a.k.a. BSOD).

The problem with the mini dump file is that you have to load it into a debugger - something most people don't have on their PCs - or a utility called dumpchk.exe (see later).

In C:\Windows\Minidump you will see .dmp files. On my Vista system they are typically ~135K in size. You can tell by the date the file was created which BSOD it corresponds to.

To get dumpchk for XP SP2, goto:

http://www.microsoft.com/downloads/details.aspx?familyid=49ae8576-9bb9-4126-9761-ba801...displaylang=en

Also, see http://support.microsoft.com/kb/315263 - this tells you have to configure the OS to generate minidump files if they aren't already. To use dumpchk, see the section "Tools to read the small memory dump file" in the same link.

If you manage to get any info, please post back.

[disturbed1]

IRQL not less or equal is 60% of the time corrupt RAM. (Usually bad RAM sticks) 40% of the time a overheating CPU. As soon as it BSOD's reboot and go directly into the BIOS and check your CPU temps. This same stop error can also be caused from too aggressive RAM timings, poor over clocking attempts, and other BIOS mucking around.

DRIVER_IRQL not less or equal is usually a bad driver, failing hardware IRQ sharing problems. With the DRIVER_IRQL stop error a foo.sys file is usually listed. This is the driver of the device that causes the issue(s).

You stated you removed 2 of 4 1gig ram sticks. 32bit OSes can not address more ~3.2GB of ram. Even many Motherboards have issues physically mapping this much RAM. Get a copy of memtest86+ and let it complete the test.

http://www.memtest.org/

Direct link for those that don't like to read http://www.memtest.org/#downiso You want the Download - Pre-Compiled Bootable ISO (.zip)

[JohnnyMalaria]

IRQL_NOT_LESS_OR_EQUAL is the most common STOP reason and can occur for any reason when any kernel mode code (including drivers) tries to access memory that it doesn't have access to at the current priority level. Bad memory is only one example. Buggy drivers are the most common cause. What is important is the STOP code provided with the BSOD information and the memory dump.

DRIVER_IRQL_NOT_LESS_OR_EQUAL is a much less common cause for STOP and are specific to drivers performing certain illegal operations.

[TheWinter]

Ok I installed the windows support tools but when I try to run dumpchk.exe the cmd window flashes open and nothing happens

[TheWinter]

Oooook I played around on the cmd and figured out how to do it manually.

C:\Documents and Settings\User>dumpchk C:\WINDOWS\Minidump\Mini010808-01.dmp
Loading dump file C:\WINDOWS\Minidump\Mini010808-01.dmp
----- 32 bit Kernel Mini Dump Analysis

DUMP_HEADER32:
MajorVersion 0000000f
MinorVersion 00000a28
DirectoryTableBase 0ad80460
PfnDataBase 81846000
PsLoadedModuleList 8055c700
PsActiveProcessHead 80562818
MachineImageType 0000014c
NumberProcessors 00000004
BugCheckCode 1000000a
BugCheckParameter1 000e6736
BugCheckParameter2 0000001c
BugCheckParameter3 00000000
BugCheckParameter4 804fa246
PaeEnabled 00000001
KdDebuggerDataBlock 8054c2e0
MiniDumpFields 00000dff

TRIAGE_DUMP32:
ServicePackBuild 00000200
SizeOfDump 00010000
ValidOffset 0000fffc
ContextOffset 00000320
ExceptionOffset 000007d0
MmOffset 00001068
UnloadedDriversOffset 000010a0
PrcbOffset 00001878
ProcessOffset 000024c8
ThreadOffset 00002728
CallStackOffset 00002980
SizeOfCallStack 0000080c
DriverListOffset 00003420
DriverCount 0000008b
StringPoolOffset 00005d68
StringPoolSize 00001338
BrokenDriverOffset 00000000
TriageOptions 00000041
TopOfStack ace1e7f4
DebuggerDataOffset 00003190
DebuggerDataSize 00000290
DataBlocksOffset 000070a0
DataBlocksCount 00000003


Windows XP Kernel Version 2600 (Service Pack 2) MP (4 procs) Free x86 compatible

Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Tue Jan 08 13:22:37 2008
System Uptime: 1 days 17:53:52
start end module name
804d7000 806e2000 nt Checksum: 001FB950 Timestamp: Wed Feb 28 01:
15:54 2007 (45E5484A)

Unloaded modules:
bac18000 bac1f000 USBSTOR.SYS Timestamp: unavailable (00000000)
aea72000 aea9d000 kmixer.sys Timestamp: unavailable (00000000)
b63a4000 b63b7000 naveng.sys Timestamp: unavailable (00000000)
b63b7000 b6489000 navex15.sys Timestamp: unavailable (00000000)
b5747000 b5772000 kmixer.sys Timestamp: unavailable (00000000)
baec2000 baec3000 drmkaud.sys Timestamp: unavailable (00000000)
b5772000 b5795000 aec.sys Timestamp: unavailable (00000000)
b5d8a000 b5d97000 DMusic.sys Timestamp: unavailable (00000000)
b598a000 b5998000 swmidi.sys Timestamp: unavailable (00000000)
bae5a000 bae5c000 splitter.sys Timestamp: unavailable (00000000)
ba968000 ba975000 i8042prt.sys Timestamp: unavailable (00000000)
bac90000 bac95000 Cdaudio.SYS Timestamp: unavailable (00000000)
b9c06000 b9c09000 Sfloppy.SYS Timestamp: unavailable (00000000)
bac50000 bac55000 Flpydisk.SYS Timestamp: unavailable (00000000)
bac40000 bac47000 Fdc.SYS Timestamp: unavailable (00000000)

Finished dump check


/prays

[JohnnyMalaria]

Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Tue Jan 08 13:22:37 2008
System Uptime: 1 days 17:53:52
start end module name
804d7000 806e2000 nt Checksum: 001FB950 Timestamp: Wed Feb 28 01:
15:54 2007 (45E5484A)

This part shows that the guilty module is "nt" which is a little odd since there is no standard module with Windows called "nt". There's ntdll.dll. Possibly, you have a rogue module (malware).

Try this from the cmd prompt:

dir c:\windows\nt*.* /b /s

This will list all files in the Windows folder (and subfolder) beginning with "nt" in a simple list format.

[TheWinter]

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\User>dir C:\windows\nt*.* /b /s
C:\windows\ntdtcsetup.log
C:\windows\$hf_mig$\KB930916\SP2QFE\ntfs.sys
C:\windows\$NtUninstallKB930916$\ntfs.sys
C:\windows\$NtUninstallKB931784$\ntkrnlpa.exe
C:\windows\$NtUninstallKB931784$\ntoskrnl.exe
C:\windows\Driver Cache\i386\ntkrnlmp.exe
C:\windows\Driver Cache\i386\ntkrnlpa.exe
C:\windows\Driver Cache\i386\ntkrpamp.exe
C:\windows\Driver Cache\i386\ntoskrnl.exe
C:\windows\Help\ntart.chm
C:\windows\Help\ntbackup.chm
C:\windows\Help\ntbackup.hlp
C:\windows\Help\ntchowto.chm
C:\windows\Help\ntcmds.chm
C:\windows\Help\ntdef.chm
C:\windows\Help\nthelp.chm
C:\windows\Help\ntshared.chm
C:\windows\Help\ntshrui.hlp
C:\windows\inf\ntapm.inf
C:\windows\inf\ntapm.PNF
C:\windows\inf\ntgrip.inf
C:\windows\inf\ntgrip.PNF
C:\windows\inf\ntprint.inf
C:\windows\inf\ntprint.PNF
C:\windows\Prefetch\NTOSBOOT-B00DFAAD.pf
C:\windows\system32\ntbackup.exe
C:\windows\system32\ntdll.dll
C:\windows\system32\ntdos.sys
C:\windows\system32\ntdos404.sys
C:\windows\system32\ntdos411.sys
C:\windows\system32\ntdos412.sys
C:\windows\system32\ntdos804.sys
C:\windows\system32\ntdsapi.dll
C:\windows\system32\ntdsbcli.dll
C:\windows\system32\ntimage.gif
C:\windows\system32\ntio.sys
C:\windows\system32\ntio404.sys
C:\windows\system32\ntio411.sys
C:\windows\system32\ntio412.sys
C:\windows\system32\ntio804.sys
C:\windows\system32\ntkrnlpa.exe
C:\windows\system32\ntlanman.dll
C:\windows\system32\ntlanui.dll
C:\windows\system32\ntlanui2.dll
C:\windows\system32\ntlsapi.dll
C:\windows\system32\ntmarta.dll
C:\windows\system32\ntmsapi.dll
C:\windows\system32\ntmsdba.dll
C:\windows\system32\ntmsevt.dll
C:\windows\system32\ntmsmgr.dll
C:\windows\system32\ntmsmgr.msc
C:\windows\system32\ntmsoprq.msc
C:\windows\system32\ntmssvc.dll
C:\windows\system32\ntoskrnl.exe
C:\windows\system32\ntprint.dll
C:\windows\system32\nts.dll
C:\windows\system32\ntsd.exe
C:\windows\system32\ntsdexts.dll
C:\windows\system32\ntshrui.dll
C:\windows\system32\ntvdm.exe
C:\windows\system32\ntvdmd.dll
C:\windows\system32\config\systemprofile\ntuser.da t
C:\windows\system32\dllcache\NT5.CAT
C:\windows\system32\dllcache\NT5IIS.CAT
C:\windows\system32\dllcache\NT5INF.CAT
C:\windows\system32\dllcache\ntbackup.exe
C:\windows\system32\dllcache\ntdll.dll
C:\windows\system32\dllcache\ntdos.sys
C:\windows\system32\dllcache\ntdos404.sys
C:\windows\system32\dllcache\ntdos411.sys
C:\windows\system32\dllcache\ntdos412.sys
C:\windows\system32\dllcache\ntdos804.sys
C:\windows\system32\dllcache\ntdsapi.dll
C:\windows\system32\dllcache\ntdsbcli.dll
C:\windows\system32\dllcache\ntevt.dll
C:\windows\system32\dllcache\ntfs.sys
C:\windows\system32\dllcache\ntio.sys
C:\windows\system32\dllcache\ntio404.sys
C:\windows\system32\dllcache\ntio411.sys
C:\windows\system32\dllcache\ntio412.sys
C:\windows\system32\dllcache\ntio804.sys
C:\windows\system32\dllcache\ntkrnlmp.exe
C:\windows\system32\dllcache\ntkrnlpa.exe
C:\windows\system32\dllcache\ntkrpamp.exe
C:\windows\system32\dllcache\ntlanman.dll
C:\windows\system32\dllcache\ntlanui.dll
C:\windows\system32\dllcache\ntlanui2.dll
C:\windows\system32\dllcache\ntlsapi.dll
C:\windows\system32\dllcache\ntmarta.dll
C:\windows\system32\dllcache\ntmsapi.dll
C:\windows\system32\dllcache\ntmsdba.dll
C:\windows\system32\dllcache\ntmsevt.dll
C:\windows\system32\dllcache\ntmsmgr.dll
C:\windows\system32\dllcache\ntmssvc.dll
C:\windows\system32\dllcache\ntoc.dll
C:\windows\system32\dllcache\ntoskrnl.exe
C:\windows\system32\dllcache\NTPRINT.CAT
C:\windows\system32\dllcache\ntprint.dll
C:\windows\system32\dllcache\ntsd.exe
C:\windows\system32\dllcache\ntsdexts.dll
C:\windows\system32\dllcache\ntshrui.dll
C:\windows\system32\dllcache\ntvdm.exe
C:\windows\system32\dllcache\ntvdmd.dll
C:\windows\system32\drivers\ntfs.sys
C:\windows\system32\Setup\ntoc.dll
C:\windows\system32\wbem\ntevt.dll
C:\windows\system32\wbem\ntevt.mfl
C:\windows\system32\wbem\ntevt.mof

C:\Documents and Settings\User>

[TheWinter]

buump

[TheWinter]

sigh am i actually not getting a resolution from this thread after going this far?

[Squash]

Have you tried this?

http://forums.techguy.org/windows-nt-2000-xp/666309-solved-windows-xp-crashes-when.html

[JohnnyMalaria]

sigh am i actually not getting a resolution from this thread after going this far?

Sorry - I have been trying to find out how you can get more information from the minidump (i.e., tell Windows to put more info in it at the time of the crash) - haven't managed to locate it yet.

In the meantime, you could try the following (it's rather tedious):

1. Boot in safe mode (press F8 during the boot and select Safe Mode) - use the PC as per usual and see if it still crashes. Note, there's a lot of stuff you won't be able to do and the screen will look ugly - it isn't permanent.

2. In normal mode, disable each piece of hardware one at a time. Use the PC as usual and see if it crashes. Only disable those items that you can safely - e.g., network adapter, sound card, any hardware you have added, FireWire interfaces etc. For any given disabled item, you may have to use the PC for a long time to be sure if it still crashes or not.

3. If you have more than one stick of RAM, remove all but one (if your motherboard permits just one) and see how the PC runs. Try each stick separately.

As I said, it's quite tedious but may help point you in the right direction.