zxello

just wondering if this makes sense to anyone, this is what I got on the error report after recovering from an IRQ Error....

BCCode : 4e BCP1 : 0000008F BCP2 : 0002A93D BCP3 : 0002143D
BCP4 : 00000000 OSVer : 5_1_2600 SP : 2_0 Product : 256_1

__________________
Old signature just wasn't doing it for me anymore, so now I have this new one. It's equally as stupid but at least it looks really long. I'm probably just going to keep typing until I run out of things to babble about and see how many people actually read this. I once ran down a hill, fell down and hurt my elbow; my mom said I would be ok, she kissed it and made it all better. I've run out of things to say now, so if you have read this whole thing, congratulations you get a gold star!

sashime76

Which IRQ, there are 15 I think, a couple of them shared. What Windows flavor do you have? Service pack(s)?

bendsley

A typical PC has a total of 16 IRQs, numbered 0 to 15.

According to what zxello pasted:
OSVer : 5_1_2600 SP : 2_0 OS version 5 is Windows XP, build 2600. SP 2.0

So, you're running XP SP2. Did this just start happening after you installed SP2?

__________________
"You hear the one about the fella who died, went to the pearly gates? St. Peter let him in. Sees a guy in a suit making a closing argument. Says, "Who's that?" St. Peter says, "Oh, that's God. Thinks he's Denny Crane."

Eric640

If this happened after a major system change (New OS... new piece of hardware... etc...) then you have the cause right there.

If it didn't I'd say reinstall windows and hope for the best. Also test your powersupply and make sure it isn't failing on you. I have seen that cause blue screen IRQ errors before (especially on boot up or if it feels COMPLETELY random).


Does it say which IRQ is in conflict? If it does you need to check that in Device Manager and remap stuff around it (it may take a reinstall to do this anyways... windows sucks if stuff doesnt PnP correctly... you'll have to switch the entire OS over to non PnP to change the settings at all.)

JohnnyRoyale

I've seen that a few of these before. Mostly, in the cases I've sen, it relates to XP's Service Pack 2 being incompatible with a system driver(in my case, some older SCSI card drivers). What you can do is: Check your hardware manufacturers for updated drivers, especially post-service pack 2 drivers, or, if they're reporting problems with SP2. In the case I had, I had to remove the SCSI cards' drivers, re-install SP2, THEN install the drivers for the SCSI cards again.

__________________
I'm gonna be rich and famous, as soon I invent a device that lets you stab people in the face over the internet.

zxello

i dont know which IRQ it is =/

__________________
Old signature just wasn't doing it for me anymore, so now I have this new one. It's equally as stupid but at least it looks really long. I'm probably just going to keep typing until I run out of things to babble about and see how many people actually read this. I once ran down a hill, fell down and hurt my elbow; my mom said I would be ok, she kissed it and made it all better. I've run out of things to say now, so if you have read this whole thing, congratulations you get a gold star!