Odd 'irq less than equal' BSOD

AgedIdiot

AgedIdiot

AgedIdiot

Soldato
Joined
31 Oct 2007
Posts
2,560
Location
Gods County(Allegedly)
Hopefully I remember correctly that it is 'Irq less ...' that I've now seen twice.(in a couple of months)

Not in itself unusual but the timing ...

I've hit the (start) Turn off button and it's just about (if not immediately after) windows shuts down that I get this.- Very odd (to me anyway)

Anyone had a similar experience ? and the reason?

Do not think it's anything to worry about but ......

Running xp 32bit - Msi PA67 -65 + i2500k+ 2 x 2gb G-skill @ 1600 + wd 750 black.
(Would mention that I moved from P45 & Q9650 and did not need to re-install windows so may be odds and sods still about from old days)
 
Could be an issue with your RAM. Either the modules are faulty or timings incorrect. Run memtest and see what it shows.

If you change the mobo and cpu you really should do a fresh install of the OS. It is possible it is a driver issue causing the BSOD, where you have been a lil lazy and not done a fresh install ;)
 
AgedIdiot said:
(Would mention that I moved from P45 & Q9650 and did not need to re-install windows so may be odds and sods still about from old days)
Click to expand...
Yeah you're pushing it there. If all else fails, try reformatting (annoying, I know)

However, the only time I've had IRQL_LESS_THAN_OR_EQUAL is when I've gone too far on my overclocking and it's overheated. I don't know if your machine's OC'd at the moment?
 
The motherboard has its own mem test program which did not show any errors ,but will run mem test when I get home just in case!
I believe that it's more to do with the fact that I did not go the clean install route (lazy I know!) but if that is all it is I can live with the issue until I finally get around to installing ssd and windows 7.
 
That BSOD is either a hardware or software fault.

Seeing as we have ruled out RAM a fresh install is the next step. I wouldnt rush till you have a copy of Win 7 64bit
 
Almost certainly a fault with the OS if it gets triggered in particular instances. I was receiving this error message on my old Win 7 partition although it was happening very randomly. Fresh install sorted it.

You should look into getting Win 7 mate, it is a nice OS.
 
Yeah i phrased that a bit silly to be fair, getting tired. Saying 99.9% of the time it's the RAM is basically saying it's a hardware error code, which it isn't....although to be fair that was my first suggestion to check.

Why can't troubleshooting be easy hey :P
 
This Stop message indicates that a kernel-mode process or driver attempted to access a memory address to which it did not have permission to access. The most common cause of this error is an incorrect or corrupted pointer that references an incorrect location in memory. A pointer is a variable used by a program to refer to a block of memory. If the variable has an incorrect value in it, the program tries to access memory that it should not. When this occurs in a user-mode application, it generates an access violation. When it occurs in kernel mode, it generates a STOP 0x0000000A message. If you encounter this error while upgrading to a newer version of Windows, it might be caused by a device driver, a system service, a virus scanner, or a backup tool that is incompatible with the new version.
 
You must log in or register to reply here.
Back
Top Bottom