Should I resolve IRQ Conflict--sound card and USB Universal Host Controller

Hi Chris.  Model, OS, and BSOD details are always helpful :) .

 

Someone else may jump in with better ideas, but here's my 2c for what it's worth: 

 

Shared doesn't necessarily mean conflict - after all, your ethernet seems to be getting along OK with your hard drive. I've got 6 devices on PCI 16.  But if you do want to change it,  usually XP won't let you (resources tab in driver properties almost always has changes disabled), and then you'd have to figure out what to change it to.  Easier just to try a different PCI slot or just uninstall and reinstall the driver to see if XP will reassign it automatically.  

 

Another possibility:  when you installed the new sound card, did you get rid of all the old sound drivers and and disable the integrated audio in the BIOS (assuming that's what you were using before)?  If not that can cause all kinds of weird problems.

Sometimes also you can change the IRQ just by changing the PCI slot your card is connected to. Might be worth a try.

HI,
Sorry for not including that information. I have a Dell Dimension E510 with 4GB of RAM and it's running Media Center XP SP3. (At least I think I'm still running the Media Center edition; after the SP3 upgrade I'm not sure. Different parts of the system give me different info on what OS I'm running, but that's another story.)

 

I only had onboard sound before I installed this sound card. I'm not sure where those drivers are. But after I got your message, I disabled onboard sound in the BIOS. That seemed to resolve the problem, but today it occurred again. Both today and the last time it occurred I had BSODs in pairs. So I had one followed by another one within a matter of minutes. Reproducing it is hard although it always happens when media player classic and windows media player are both open.

 

The latest BSOD errors are:

First:

 The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000007f (0x00000000, 0x00000000, 0x00000000, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini062608-01.dmp.

According to Microsoft if the first parameter is 0x00000000, then it's a divide-by-zero error, which can be caused by Memory corruption (or other hardware problems) or software failures.)

 

 

Later: 

The computer has rebooted from a bugcheck.  The bugcheck was: 0x1000008e (0xc0000005, 0x00568000, 0xb2fbbc14, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini062608-02.dmp. 

 

Thanks,

Chris 

info on the first error code...

http://support.microsoft.com/kb/137539