I was putting together a new system w/ an ecs k7s5a (go figure) and after getting the main components installed and windows just installed, i thought everything was going dandy. I happened to have an extension for 2 extra usb ports (the little thing that just fills a slot in the back of the case) from my epox 8kha + and there was a header that matched on the ecs board so i figured i'd just plug it in. Well, as soon as I powered on the next time, i saw light coming from a circuit near the usb header. I couldn' tell if it was sparks or a small flame like on a match but I jumped for the power button. When it turned off and the smell of burnt PCB had cleared a little, I saw that a few of the circuits near the usb header were melted! I yanked out the usb extension and booted back up. Everything that had worked up to this point still works but now I've hit a bump and don't know if it's related. I can't get any sound from my speakers using the onboard audio. I'm using xp pro w/ the newest drivers for the sound and when i play a song like in windows media player, it tells me it's playing but i can't hear anything. Device manager says the sound is working fine. The onboard modem is disabled and the onboard lan is sharing the same irq (11) as the sound but I don't know if resource conflict would give me this kind of problem i.e. everything in windows says it's working fine. Here are some other stats if it helps:
256 mb of crucial pc 2100
visiontek 5632 geforce gts-v
duron 900
ibm 40 gb 7200 rpm hd
win xp pro
Also, any speculation on what kind of damage that little bit of spontaneous combustion did to my mobo and what part is affected?:Q:Q:|:Q
256 mb of crucial pc 2100
visiontek 5632 geforce gts-v
duron 900
ibm 40 gb 7200 rpm hd
win xp pro
Also, any speculation on what kind of damage that little bit of spontaneous combustion did to my mobo and what part is affected?:Q:Q:|:Q