c'mon

You guys still can't figure it out eh? A user from another forum site told me to look at this http://www.file.net/process/cmuda.sys.html
Then told me to download a sound driver.

Lets see if this helps.

 

It's an IRQ conflict. Try moving the card to a different pci slot,

Also in bios, under pci configuration, there should be an entry to allow reconfiguration or re-enumeration, depending on your bios.

 

http://aumha.org/win5/kbestop.php

0x0000000A: IRQL_NOT_LESS_OR_EQUAL
(Click to consult the online Win XP Resource Kit article, or see Windows 2000 Professional Resource Kit, p. 1539.)
Typically due to a bad driver, or faulty or incompatible hardware or software. Use the General Troubleshooting of STOP Messages checklist above. Technically, this error condition means that a kernel-mode process or driver tried 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.)

The general thing to do if it lists a specific file such as cmuda.sys is to look up what device uses this file and then download updated drivers.
Now the next thing to consider is that sound cards tend to be really particular about resources. It is possible that your firewire card with the camcorder attached is using a resource the sound card needs to function and when the sound card tries to use alternate resources it fails.
You could try in device manager to change the firewire card to a secondary resource setting (under properties/ resources) . You may need to do this with the camcorder if the error only occurs when it is attached.
You could try changing the sound card to its alternate resource settings.

Something about is not very helpful. As you can see by the referenced site, there is a specific meaning for each hexadecimal entry in the stop message and without them we really cannot do much more.
You should also go to admin tools/ event viewer and check your error logs and see if you can find more information about this error.