IRQL_NOT_LESS_OR_EQUAL - Vista and XP

Soldato
Joined
17 Dec 2006
Posts
8,245
Been having the above BSOD on both Vista and XP now. I thought it might have been a Vista issue, so I've just formatted today and put Windows XP Professional back on. Went great, the installed SP2, rebooted and got the BSOD. Then it automatically rebooted itself, only number I caught was 0xc000005 and something about "subsystem". When it started back up, I entered my XP password, got into Windows desktop and after about 5 seconds, got the BSOD again. So it automatically rebooted, as I never had a chance to turn off the auto-reboot thing. Couldn't catch any info as it rebooted too fast.

Booted back up this time in safe mode, and undid a few things that I had done, which was create a start-up shortcut for Core Temp and placed it in the Startup folder in the start menu and uninstalled Firefox which was all I added. Then went back into Windows normal mode, and it didn't reboot.

I also had this problem with Vista over the past week, and it seemed to have started when I put my overclock back on. Although not as high as I was at 3.2 Ghz before, then took the overclock off due to overheating, and decided to put 2.8 Ghz back on when I sorted temperatures and heat issues. Vista was a bit different however, it didn't give the IRQL_NOT_LESS_OR_EQUAL BSOD, also it only seemed to happen from a cold boot, such as if I turned the PC off over night and back on in the morning, it would boot up, BSOD, then automatically reboot and the 2nd time around it always worked. Last step was when I decided to error scan the drive, went away to make a cuppa, came back and PC was at the Vista logon screen, and when I logged on I got the pop up about windows shutting down unexpectidly (press "Find a solution" made the box search, then it just closed).

Things I've seen/done:
  • I've ran Orthos on the Vista build for a little over 8 hours and no errors at all.
  • I've error checked both of my hard drives and no errors have been found.
  • I've defragged both the hard drives.
  • It happens on XP and Vista, both 32bit versions
  • Only appeared to happen when I put my overclock back on.
  • Shifted RAM timings to 5-5-5-15.

Overclock settings are:
  • CPU @ 2.8ghz (stock: 2.13ghz), 350 x 8, default voltage.
  • RAM @ 700 Mhz 4-4-4-12 forced timings (stock: 667mhz, 4-4-4-12??), default voltage.
  • PCI-E: 100Mhz locked.
  • EIST/C1E set to off.

Read a few articles on Google suggesting that it could happen when something is not getting enough volts/power. CPU won't need more as it's a very mild overclock, RAM however it wasn't sure. The memory is listed as 4-4-4-12 timings but when you set it to "Normal" in the BIOS it shows 5-5-5-15 in CPU-Z, so confused about that, but I shifted the timings down to 5-5-5-15 forced, from 4-4-4-12 forced and it's not BSODed yet, but I only tend to get them after a cold boot when the PC has been off for a while. Will know more tomorrow morning.

Anything else I should try that people can recommend, or know more on this BSOD? I've done a check on the forums and found some stuff but a lot of it didn't really match in with mine.
 
Last edited:
I had this problem for a while, i got the exact same error, when i went to stock it wasnt as bad but was still there, I got the same bsod but only when running 3d apps, so maybe yours is a faulty component but maybe ram-cpu-mobo?
 
Thanks for the post, will keep that in mind.

Think I'll run a memtest86+ overnight tonight, then a 10 hour Orthos tomorrow and a 3D Mark looped run overnight again. If it doesn't trip up on either of those, I'm going to be a bit baffled.
 
Sorry, my post made no sense, was i drunk? :p

What i meant to say was that i discovered mine was a faulty gpu, rma'd it and now it's fine
 
It could be any number of things, the fact it's happening on vista and on a fresh install of xp points to it being hardware. Do a memtest, swap out as many components as you can.
 
ShakenNstirred said:
9 out of 10 times IRQL_NOT_LESS_OR_EQUAL is a driver problem
Burnsey2023 said:
Indeed, installed any new ones recently?

Burnsy

But on two operating systems? This has happened on Vista, and with a brand new fresh install of XP. The only things I had installed on the XP operating system when it happened was my LAN driver, which was a brand new driver from the site and a different one to the Vista driver. Other than that, everything was just as it would be when you install XP + SP2.

Did some tests overnight...

Orthos: 9.5 hrs, Blend - Stress CPU and RAM, priority 7
ATi Tool: 9.5 hrs, artifact test

Both passed fine, not one error. Graphics card never went about 48c and CPU never went above 45c. Took a screenshot below, sorry about the bad quality - ms paint sucks - stopped both benchmarks about 20 mins after the screenshot (made breakfast :P).

Not really sure what else to do now :confused:

9hrs_new.gif
 
First thing to remember about these faults is that when reference is made to memory/ram it doesnt always mean the two stick of pc6400 sitting in the mobo. The CPU cache, memory controller and ram can cause this to be memory related. Try running everything at stock for a bit.
Other than that, make a completely clean install of the Windows of your choice and see how it goes, installing a single driver at a time.
 
First thing to remember about these faults is that when reference is made to memory/ram it doesnt always mean the two stick of pc6400 sitting in the mobo. The CPU cache, memory controller and ram can cause this to be memory related. Try running everything at stock for a bit.
Other than that, make a completely clean install of the Windows of your choice and see how it goes, installing a single driver at a time.
Yeah if I can't get this sorted, I think I'll drop it back down to stock CPU speeds, as this only seemed to happen (coincidently?) since I put my CPU overclock back on.

HangTime said:
I'd try running Memtest.
Maybe bump up your vdimm a bit.
Thanks, will run a memtest86+ tonight. Was gonna do it last night but couldn't get it booted off my USB stick :) Worth upping the vdimm though? It's only 33 Mhz over stock settings, and the timings are relaxed to 5-5-5-15 as they are apparantly meant to be 4-4-4-12.

lay-z-boy said:
Is you memory the crucial pc5300 stuff?
Nah, it's PQI Turbo PC5400.
 
Just remembered about the .dmp files, doh. Inspected both of them that I have for Windows XP, and they both are pretty much identical in errors. Here is one of them if any tech people can made anything of it :) Both of them were just after I had installed Service Pack 2 for Windows, and this was on the boot up after I pressed the "Restart Now" button after install.

Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C000021A, {e19dd3f8, c0000005, 75e9ad23, 52f240}

Probably caused by : ntkrnlmp.exe ( nt!KiFastCallEntry+fc )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WINLOGON_FATAL_ERROR (c000021a)
The Winlogon process terminated unexpectedly.
Arguments:
Arg1: e19dd3f8, String that identifies the problem.
Arg2: c0000005, Error Code.
Arg3: 75e9ad23
Arg4: 0052f240

Debugging Details:
------------------


ERROR_CODE: (NTSTATUS) 0xc000021a - {Fatal System Error}  The %hs system process terminated unexpectedly with a status of 0x%08x (0x%08x 0x%08x).  The system has been shut down.

ADDITIONAL_DEBUG_TEXT:  Windows SubSystem

BUGCHECK_STR:  0xc000021a_csrss.exe_c0000005

CUSTOMER_CRASH_COUNT:  2

DEFAULT_BUCKET_ID:  DRIVER_FAULT

PROCESS_NAME:  csrss.exe

LAST_CONTROL_TRANSFER:  from 80632f2b to 80537832

STACK_TEXT:  
b3d98934 80632f2b 0000004c c000021a b3d989b0 nt!KeBugCheckEx+0x1b
b3d98970 8066554c 00000001 0000004c c000021a nt!PoShutdownBugCheck+0x5c
b3d98b28 806135ba c000021a 00000004 00000001 nt!ExpSystemErrorHandler+0x511
b3d98cd4 8064f585 c000021a 00000004 00000001 nt!ExpRaiseHardError+0x9a
b3d98d44 804ddf0f c000021a 00000004 00000001 nt!NtRaiseHardError+0x16b
b3d98d44 7c90eb94 c000021a 00000004 00000001 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0052f0b0 7c90e273 75b432b7 c000021a 00000004 0x7c90eb94
0052f108 75b44aea 0052f130 75b468b1 0052f138 0x7c90e273
0052fff4 00000000 00000088 00000000 00000000 0x75b44aea


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiFastCallEntry+fc
804ddf0f 8be5            mov     esp,ebp

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  nt!KiFastCallEntry+fc

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  41107faa

FAILURE_BUCKET_ID:  0xc000021a_csrss.exe_c0000005_nt!KiFastCallEntry+fc

BUCKET_ID:  0xc000021a_csrss.exe_c0000005_nt!KiFastCallEntry+fc

Followup: MachineOwner
---------
 
I had this before with a CPU which had ended up getting electromigration from too much voltage over a period of time. There was no rhyme or reason to the BSODs, they would just happen randomly even if the computer was idle.

Unfortunately generic BSODs like that one are difficult to pinpoint. Might be worth downloading the Debugging Tools for Windows and loading up one of your minidumps in it, you might be able to find out which process caused it.
 
flibby said:
Just remembered about the .dmp files, doh. Inspected both of them that I have for Windows XP, and they both are pretty much identical in errors. Here is one of them if any tech people can made anything of it :) Both of them were just after I had installed Service Pack 2 for Windows, and this was on the boot up after I pressed the "Restart Now" button after install.

Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C000021A, {e19dd3f8, c0000005, 75e9ad23, 52f240}

Probably caused by : ntkrnlmp.exe ( nt!KiFastCallEntry+fc )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WINLOGON_FATAL_ERROR (c000021a)
The Winlogon process terminated unexpectedly.
Arguments:
Arg1: e19dd3f8, String that identifies the problem.
Arg2: c0000005, Error Code.
Arg3: 75e9ad23
Arg4: 0052f240

Debugging Details:
------------------


ERROR_CODE: (NTSTATUS) 0xc000021a - {Fatal System Error}  The %hs system process terminated unexpectedly with a status of 0x%08x (0x%08x 0x%08x).  The system has been shut down.

ADDITIONAL_DEBUG_TEXT:  Windows SubSystem

BUGCHECK_STR:  0xc000021a_csrss.exe_c0000005

CUSTOMER_CRASH_COUNT:  2

DEFAULT_BUCKET_ID:  DRIVER_FAULT

PROCESS_NAME:  csrss.exe

LAST_CONTROL_TRANSFER:  from 80632f2b to 80537832

STACK_TEXT:  
b3d98934 80632f2b 0000004c c000021a b3d989b0 nt!KeBugCheckEx+0x1b
b3d98970 8066554c 00000001 0000004c c000021a nt!PoShutdownBugCheck+0x5c
b3d98b28 806135ba c000021a 00000004 00000001 nt!ExpSystemErrorHandler+0x511
b3d98cd4 8064f585 c000021a 00000004 00000001 nt!ExpRaiseHardError+0x9a
b3d98d44 804ddf0f c000021a 00000004 00000001 nt!NtRaiseHardError+0x16b
b3d98d44 7c90eb94 c000021a 00000004 00000001 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0052f0b0 7c90e273 75b432b7 c000021a 00000004 0x7c90eb94
0052f108 75b44aea 0052f130 75b468b1 0052f138 0x7c90e273
0052fff4 00000000 00000088 00000000 00000000 0x75b44aea


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiFastCallEntry+fc
804ddf0f 8be5            mov     esp,ebp

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  nt!KiFastCallEntry+fc

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  41107faa

FAILURE_BUCKET_ID:  0xc000021a_csrss.exe_c0000005_nt!KiFastCallEntry+fc

BUCKET_ID:  0xc000021a_csrss.exe_c0000005_nt!KiFastCallEntry+fc

Followup: MachineOwner
---------

after reading that, it looks like a driver error in the graphics, as csrss.exe is to do with graphic subsystems
found this
"csrss.exe is the main executable for the Microsoft Client/Server Runtime Server Subsystem. This process manages most graphical commands in Windows. This program is important for the stable and secure running of your computer and should not be terminated."
 
ShakenNstirred said:
after reading that, it looks like a driver error in the graphics, as csrss.exe is to do with graphic subsystems
found this
"csrss.exe is the main executable for the Microsoft Client/Server Runtime Server Subsystem. This process manages most graphical commands in Windows. This program is important for the stable and secure running of your computer and should not be terminated."
Thanks for the reply :)

Not really sure what to make of the errors though, I mean, I was using 2 completely difference versions of the Nvidia drivers in Windows XP and Vista. XP I'm using 94.24 I think it is (the official ones from the nvidia site for 7 services + XP) and then another for Vista which was around 157.xx. Going to reformat again and put Windows XP back on, incase it's just coincidence that I'm getting the BSODs for two operating systems and confusing the situation. So at least I can rule out a dodgy Windows XP installation if I BSOD with a second install.

Thanks everyone for the replies so far, appreciate the help
icon14.gif
 
I get this when trying to use the VX-6000 on vista with vista drivers if I try to take screenshots at higher than 640x480 or use the video at higher than 640x480. Its very annoying.
 
Just an update:

Reformatted (full write to zero format), created a new partition etc. Went swimmingly, got into Windows and had no BSOD's at all. However I was having trouble with my Internet Connection (was my ISP rather than the machine I found out eventually) and after fiddling around I managed to make it BSOD. I did that by right clicking on the "Local Area Connection" in "Network Connections" in the Control Panel and disabling it. About 5 seconds after I did that, the machine locked, and about 20 seconds after that it gave a BSOD, with the details:

STOP: 0x000000F4 (0x00000003, random, random, random).

Although the randoms always seem to be in the "80" range, such as 0x86293847. I logged back into Windows from the BSOD and tried it again, and sure enough it locked straight after I did the thing with the Local Area Connection, then BSOD'd 20 or so seconds later with the same STOP hex codes. I took out 1 stick of RAM, tried it again and it did the same BSOD. Removed the other stick, and replaced it with the one I took out and it BSOD'd the same. Then tried a stick in a memory slot I don't normally use, and yep it BSOD'd again. Did this in case it was accessing a bad section on the RAM, but it happened for both sticks and didn't matter which channel it was in.

Guessing it's not a memory issue then?

Thinking it could be one of my hard drives, as I have 2 identical drives (Maxtor 6V3 Sata Drive) and I'm busy reinstalling Windows again on the other drive (using dads computer at the moment). Will see what happens with that one. If a piece of hardware is knackered (such as mobo/cpu/ram) then it's not so bad as I can replace it in about 1.5 weeks, just need to know which the failing part :) If it's the hard drive then I'll probably be glad, been looking for an excuse to get rid of them as I hate them with a passion!

But I think I'm going to rule out:

  • CPU - Because it passed around 20 hours worth of Orthos
  • RAM - Because it BSOD's no matter which stick was in or which slot, plus it passed a Blend on Orthos for 9.5 hrs
Would that be a correct assumption or should I not rule them out yet even with what I experienced today as written above?
 
Back
Top Bottom