New Pornstar Interviews - [more]
Tiny Khloe: 2026 Exxxotica Interview

"I’m attracted to people’s intelligence. I like some substance. I want to be able to hold a conversation."
All Forums > Tech Talk > Tech Talk Forum Page 58 > IRQL_NOT_LESS_OR_EQUAL?
AuthorPost
Harri Patel
Senior Member


#SDNY he's all yours. -- Michael Steele
5110 Posts
3/03
Posted - Mar 25 2004 : 11:41PM
I'm getting random reboots in a computer running XP Pro with all the latest updates, into which i've just installed a TV tuner/capture card. I finally saw if happen tonight; the thing went BSOD on me after recording a program for 10 or 15 minutes; the error message read "IRQL_NOT_LESS_OR_EQUAL."

The machine has a Soyo M/B, a few years old, micro-ATX form factor, on-board graphics (disabled in BIOS), no AGP slot, a video card in one PCI slot, and the new card in the other. AMD Athlon XP1600+, 512K RAM.

Any suggestions?

daviangel
Member

Only time I would buy a girl flowers is if she was in the hospital
455 Posts
1/04
Posted - Mar 26 2004 : 12:13AM
Unfortunately this is the most useless error message ever by MS!
I mean it can pretty much be caused by anything as the following says from MS(in my own words did you use your computer today? Yeah that could've caused your problem. Okay now just tell me how to fix it):
Stop hex 0000000A or IRQL_NOT_LESS_OR_EQUAL
The Stop hex A message indicates that a kernel-mode process or driver attempted 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. This Stop message is typically due to faulty or incompatible hardware or software.
Personally the way I get rid of this message is to reboot and hope it goes away.
If it returns then I start thinking really hard if I installed any new software,driver updates maybe,games could be just about anything really? Most often I've seen it caused on my own hardware by installing some drivers for a raid controller that wasn't compatible with my hardware.Using a different driver version fixed it. Other times I have seen it randomly popup with a machine that had bad memory.
Another machine I never did figure it out and just reloaded windows and that fixed it.
"I'm getting random reboots in a computer running XP Pro with all the latest updates, into which i've just installed a TV tuner/capture card."
That sounds like the smoking gun to me so I'd try 2 different things in your case.
1. Find latest drivers for your tv tuner card and install them
2. If above doesn't work/help take card out and try it in a different pci slot.
sorry to say that without actually being there firsthand to check it out can't really say much else about this other than I'd recommend finding some local computer guru to help you out if you can.
Anyways if I really had time to mess with it and try to fix it I usually check out the microsoft knowledge base to see if I can find and answer there and that's the first thing most other techs will do if it's not an obvious problem.

p.s.
Resolving the Problem
The following suggestions are specific to Stop hex A errors. A Stop hex A message might occur after installing a faulty device driver, system service, or firmware. If a Stop message lists a driver by name, disable, remove, or roll back the driver to correct the problem. If disabling or removing drivers resolves the issues, contact the manufacturer about a possible update. Using updated software is especially important for multimedia applications, antivirus scanners, and CD mastering tools.
A Stop hex A message might also be due to failing or defective hardware. If a Stop message points to a category of devices (video or disk adapters, for example), try removing or replacing the hardware to determine if it is causing the problem.
If you encounter a Stop hex A message while upgrading to Windows XP Professional, the problem might be due to an incompatible driver, system service, virus scanner, or backup. To avoid problems while upgrading, simplify your hardware configuration and remove all third-party device drivers and system services (including virus scanners) prior to running setup. After you have successfully installed Windows XP Professional, contact the hardware manufacturer to obtain compatible updates.
For more information about Stop hex A messages, see the Microsoft Knowledge Base link on the Web Resources page at http://www.microsoft.com/windows/reskits/webresources. Search using keywords winnt, hex 0000000A, and hex A.


Unicorn
Member

156 Posts
4/04
Posted - Apr 10 2004 : 5:15PM
It's an IRQ conflict. Think channels on your tv.
Swapping the card to another PCI slot should fix it.
Most motherboards "share" IRQ on certain slots.
Some hardware does not like this.

Try it. Mail me if this doesn't help.

Unicorn

jamesn
Senior Member

Cambridge, MA
750 Posts
1/04
Posted - Apr 11 2004 : 2:55PM
Do you know which chipset you've got? I remember the via KT133A, which seems like you might have based on your cpu and its age, was a fiasco for my roomate a few years ago and he wasn't alone. it had signifigant problems with both IDE/PCI, which is why a few chipsets later, via hasn't caught up to the nforce2. I think soyo sells a lot of via stuff, the newer ones aren't supposed to be bad, but that one had uncorrectable problems with pci soundcards in particular, it wouldn't be suprising if this is related. definetly try another slot, motherboards are weird with pci slots sometimes(there's one slot where creative soundcards basically don't work on a lot of asus boards, for example), before you mess around with drivers, poke around in your bios a little to see if there's anything glaring, and then set it to "fail-safe defaults" and try booting windows in safe mode and progressively enable more stuff on each boot if it works. sorry to hear about that, good luck-james
Harri Patel
Senior Member

#SDNY he's all yours. -- Michael Steele
5110 Posts
3/03
Posted - Apr 13 2004 : 1:39AM
I ended up buying a new motherboard. Thanks for the suggestions.
 
Evil_Rip
Senior Member

Power overwhelming
1117 Posts
12/99
Posted - Apr 14 2004 : 2:13AM
I've had that problem before.
And for me it was because the hard drive failed.
The hard drive was inside one of those removeable cases
matrixman
Member

148 Posts
8/03
Posted - Apr 16 2004 : 3:36AM
Mine was because of bad capacitors. There was a huge batch of these used for motherboards and they cause the capacitors to bulge from the tops.

I had a guy replace all the caps on my MB and it worked perfect since then.




Jump To: