IRQ Conflict question...

By boxfiddler Moderator ·
PC: Acer Aspire 9300 (notebook)
OS: WinXP (came with Vista)
CPU: AMD 64 bit (not sure which one)
MOBO: Unknown

Have been working to resolve regular BSOD's and come up with the following:

Hardware Resources
I/O Port 0x00000000-0x00000CF7 PCI bus
I/O Port 0x00000000-0x00000CF7 Direct memory access controller

IRQ7 Texas Instruments PCIxx12 Cardbus Controller
IRQ7 Texas Instruments PCIxx12 Integrated FlashMedia Controller

IRQ 18 NVIDIAnForce 430/410 SerialATA Controller
IRQ 18 Microsoft UAA Bus Driver for High Definition Audio

Memory Address 0xA0000-0xBFFFF PCI bus
Memory Address 0xA0000-0xBFFFF NVIDIA GeForce Go 6100

I am pretty certain that IRQ 18 is a problem here, but don't know about IRQ 7. I also don't know about the other entries, but think they are probably related.

What please can be done to resolve these conflicts?

Thank you!

edit: IRQ 18 to MS AAU driver line

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Answers

Collapse -

Nobody's answered yet box???

by The Scummy One In reply to IRQ Conflict question...

Ok, here is a question. What is the BSOD?

the 3 parts (if they are avail) that I like to get are
The second part is the exception code
0x000000FA (and the ones in parenthesis)
and if avail which file caused the fault

Ok, as for IRQ's, many are shared these days, it is not uncommon to see them as shared. In device manager, are there any actual conflicts?
Also, what errors are showing in the SW and system event viewer logs?

Collapse -


by boxfiddler Moderator In reply to Nobody's answered yet box ...

(0xE1900DE8, 0xC0000185, 0xBF9B4E48,0x0E8ADB60)

Research yielded the following:
"0xC0000185, or STATUS_IO_DEVICE_ERROR, is caused by improper termination or defective cabling on SCSI devices, or two devices attempting to use the same IRQ.

Another common cause of this error message is defective hardware or failing RAM.

This bug check can also be caused by a virus infection.


Virus has been ruled out as XP has been loaded 3 times now with continuing consistent BSOD's. SCSi ruled because, well there was no need to load SCSi drivers at install. 1 bad stick of RAM has been removed, providing for smoother running and SIGNIFICANTLY fewer BSOD's. Client hasn't the money at the moment to purchase another stick in order to fully rule out RAM.

Yes I do know that often IRQ's are shared. There are few of them on my own systems that don't appear to be troublesome in the least.

"In device manager, are there any actual conflicts?" If by this you mean are there any yellow question marks or other notation on the opening device manager page, the answer is no. If you mean something else, please advise exactly what you mean. I'm ok, but a lightweight in many regards.

I should have noted that the MS AAU driver is sharing IRQ 18 (if I didn't - it disappeared from the document I have been copying this stuff to)? That is the one that bugs me, primarily because MS doesn't always know what it is doing - not becuase I know much when it gets this deep!

Will have to get back to you on the logs. Client machine... My backyard labor client - can't lose that one!

Thanks for the help Oh Scummy One! Will post further info in response to your questions as soon as I get it.

PS: I miss Pond Scum somehow. Must be the Mets thing...

EDIT TO AD File this time is win32k.sys (don't know about other times). Sorry, can't read the address, base, or datestamp.

Collapse -

Sorry BoxFiddler

by The Scummy One In reply to BSOD...

I ran into these a few times, including this morning, so all I read so far was up to the 7A error at the time of this post.

This error is likely a faulty HDD, or drive controller. Most likely your HDD is going out on you.
First, backup your data to another location.
2nd, try the drive as a USB drive and run a chkdsk on it. Likely it will find bad clusters, or it may have a hard time reading the drive.

I will look at the rest of the post in a minute.

Collapse -

Nothing to be sorry about...

by boxfiddler Moderator In reply to Sorry BoxFiddler

you're a doll!

But I promise not to tell!

Collapse -

More info

by The Scummy One In reply to BSOD...

Although tMS KB says SCSI drives, the error can pop up with other errors including both the 0x00000077 and 0x000000FA (or AF or something). Anyway, these are all related to the same general items, and are usually HDD failures. For one of the other 2 errors it mentions that it is not detected as a master drive, and to change the setting, or that the cable is bad. However, it is likely the read head or chipset on the HDD that is faltering.

To test the RAM, boot to memtest86 and let it run a bunch of cycles (with the HDD removed). I usually let it run for 24 hours, but if in a hurry, overnight or just a few hours should pick up a problem.

Collapse -

Is a laptop Scummy, still under warranty...

by boxfiddler Moderator In reply to More info

so I'm not going to take her apart. Though I wouldn't take a laptop apart if it wasn't under warranty... My fingers are kind of big and klutsy in small spaces.

Thanks, though for the input. I have really been trying to get this guy to restore Vista and return it, but he is fighting that like nuts because he likes the 17" screen. So get another one with a 17" screen! Sheesh.

I learn a lot fighting with this one (person that is), though. I get pushed into researching things I wouldn't if it were my machine. I would have returned mine months ago if it gave me the fits this one is giving him.

Collapse -

Oh, somethign else to try

by The Scummy One In reply to BSOD...

while it may not be the issue, you can try deleting pagefile.sys, as it can trigger memory errors as well.

Collapse -

Would clearing it at shutdown have the same effect?

by boxfiddler Moderator In reply to Oh, somethign else to try

What effect might that have on performance? This guy is heavy into photo and graphics editing and creation.

Collapse -

Blowing away the pagefile.sys file

by The Scummy One In reply to Would clearing it at shut ...

will hit performance once. When Windows does not find it, it re-creates it.

It is not the same as clearing on shutdown, as if there is something wrong with the file itself, just removing the cached info will not correct it. Not to mention, clearing it at shutdown gives a small performance hit much more often.

Collapse -

Okee-dokee then.

by boxfiddler Moderator In reply to Blowing away the pagefile ...

Thank you. I will be looking into the above suggestions...

Man if things get up and running, I owe you a 5th of whatever you drink in addition to a couple more thumbs.

edit because I can...

Related Discussions

Related Forums