If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
The fire is out . . .
The good news is that the fire is out. The better news is that I was
sitting at our PC when it "smoked." It shut down normally! Whew! More good news - my son's old PC hasn't sold yet, so I'm able to reach out for help. The bad news is that the fire was on the motherboard. It appears to have started at the Firewire connector on the motherboard that goes to the adapter card. The connector cable (mobo end) is pretty well destroyed, and the one of the pins on the mobo is gone (stuck in the connector I suppose). There is some smoke residue on other components, but hopefully nothing else is damaged. System details: The motherboard is a DFI NFII Ultra Infinity. Generic Firewire adapter card (COMAX brand?). I don't think anything else is pertinent, but can supply more details if needed. I haven't tried powering it on again. Do you think that's a logical thing to do (under close scrutiny, of course)? Or should I just write it off and get a new mobo? Anyone else had problems with PC faults like this? Thanks, Craig [to reply directly, change the VERB to a NUMERAL] |
#2
|
|||
|
|||
"Craig Williams" wrote in message ... The good news is that the fire is out. The better news is that I was sitting at our PC when it "smoked." It shut down normally! Whew! More good news - my son's old PC hasn't sold yet, so I'm able to reach out for help. The bad news is that the fire was on the motherboard. It appears to have started at the Firewire connector on the motherboard that goes to the adapter card. The connector cable (mobo end) is pretty well destroyed, and the one of the pins on the mobo is gone (stuck in the connector I suppose). There is some smoke residue on other components, but hopefully nothing else is damaged. System details: The motherboard is a DFI NFII Ultra Infinity. Generic Firewire adapter card (COMAX brand?). I don't think anything else is pertinent, but can supply more details if needed. I haven't tried powering it on again. Do you think that's a logical thing to do (under close scrutiny, of course)? Or should I just write it off and get a new mobo? Anyone else had problems with PC faults like this? i sure would not use it if it smoked! just odd that it was the firewire connector that burned up! |
#3
|
|||
|
|||
A few weeks back, I installed an extra 256 MB of brand name (Kingston) DDR
333 RAM in bank #2. I had used it for a few minutes the day before with out any problem. When I powered on, there was a snapping or popping sound followed by the smell of burning plastic...oops! Two of the gold RAM contacts, one near each end of the module, were charred black. I removed the bad module and tried a reboot. The long repetative beep tones indicated that the mobo did not recognize any of the remaining memory. The remaining memory did just fine when tested in my other computer. After clearing the cmos on the injured mobo, I tried again with the original 512 MB RAM in bank #1. It would go to he startup BIOS screen and display the BIOS logo, processor type and amount of memory correctly and stop there....no access to the BIOS setup or OS. Don't know what happened to my Soyo KT 400 Platinum, but the board is obviously land fill now. Kingston replaced the 256 MB of RAM. "Craig Williams" wrote in message ... The good news is that the fire is out. The better news is that I was sitting at our PC when it "smoked." It shut down normally! Whew! More good news - my son's old PC hasn't sold yet, so I'm able to reach out for help. The bad news is that the fire was on the motherboard. It appears to have started at the Firewire connector on the motherboard that goes to the adapter card. The connector cable (mobo end) is pretty well destroyed, and the one of the pins on the mobo is gone (stuck in the connector I suppose). There is some smoke residue on other components, but hopefully nothing else is damaged. System details: The motherboard is a DFI NFII Ultra Infinity. Generic Firewire adapter card (COMAX brand?). I don't think anything else is pertinent, but can supply more details if needed. I haven't tried powering it on again. Do you think that's a logical thing to do (under close scrutiny, of course)? Or should I just write it off and get a new mobo? Anyone else had problems with PC faults like this? Thanks, Craig [to reply directly, change the VERB to a NUMERAL] |
#4
|
|||
|
|||
Misery loves company, so they say. Sorry to hear about your problem. I'll
post the results of my power-on test later. Craig "Andrew K" wrote in message ... A few weeks back, I installed an extra 256 MB of brand name (Kingston) DDR 333 RAM in bank #2. I had used it for a few minutes the day before with out any problem. When I powered on, there was a snapping or popping sound followed by the smell of burning plastic...oops! Two of the gold RAM contacts, one near each end of the module, were charred black. I removed the bad module and tried a reboot. The long repetative beep tones indicated that the mobo did not recognize any of the remaining memory. The remaining memory did just fine when tested in my other computer. After clearing the cmos on the injured mobo, I tried again with the original 512 MB RAM in bank #1. It would go to he startup BIOS screen and display the BIOS logo, processor type and amount of memory correctly and stop there....no access to the BIOS setup or OS. Don't know what happened to my Soyo KT 400 Platinum, but the board is obviously land fill now. Kingston replaced the 256 MB of RAM. "Craig Williams" wrote in message ... The good news is that the fire is out. The better news is that I was sitting at our PC when it "smoked." It shut down normally! Whew! More good news - my son's old PC hasn't sold yet, so I'm able to reach out for help. The bad news is that the fire was on the motherboard. It appears to have started at the Firewire connector on the motherboard that goes to the adapter card. The connector cable (mobo end) is pretty well destroyed, and the one of the pins on the mobo is gone (stuck in the connector I suppose). There is some smoke residue on other components, but hopefully nothing else is damaged. System details: The motherboard is a DFI NFII Ultra Infinity. Generic Firewire adapter card (COMAX brand?). I don't think anything else is pertinent, but can supply more details if needed. I haven't tried powering it on again. Do you think that's a logical thing to do (under close scrutiny, of course)? Or should I just write it off and get a new mobo? Anyone else had problems with PC faults like this? Thanks, Craig [to reply directly, change the VERB to a NUMERAL] |
#5
|
|||
|
|||
I cleaned up as much as I could of the sooty residue, and of course removed
the offending adapter cable, and "fired it up" (so to speak). No problems so far, but I'm not leaving the room with the PC on. Craig "Craig Williams" wrote in message ... Misery loves company, so they say. Sorry to hear about your problem. I'll post the results of my power-on test later. Craig "Andrew K" wrote in message ... A few weeks back, I installed an extra 256 MB of brand name (Kingston) DDR 333 RAM in bank #2. I had used it for a few minutes the day before with out any problem. When I powered on, there was a snapping or popping sound followed by the smell of burning plastic...oops! Two of the gold RAM contacts, one near each end of the module, were charred black. I removed the bad module and tried a reboot. The long repetative beep tones indicated that the mobo did not recognize any of the remaining memory. The remaining memory did just fine when tested in my other computer. After clearing the cmos on the injured mobo, I tried again with the original 512 MB RAM in bank #1. It would go to he startup BIOS screen and display the BIOS logo, processor type and amount of memory correctly and stop there....no access to the BIOS setup or OS. Don't know what happened to my Soyo KT 400 Platinum, but the board is obviously land fill now. Kingston replaced the 256 MB of RAM. "Craig Williams" wrote in message ... The good news is that the fire is out. The better news is that I was sitting at our PC when it "smoked." It shut down normally! Whew! More good news - my son's old PC hasn't sold yet, so I'm able to reach out for help. The bad news is that the fire was on the motherboard. It appears to have started at the Firewire connector on the motherboard that goes to the adapter card. The connector cable (mobo end) is pretty well destroyed, and the one of the pins on the mobo is gone (stuck in the connector I suppose). There is some smoke residue on other components, but hopefully nothing else is damaged. System details: The motherboard is a DFI NFII Ultra Infinity. Generic Firewire adapter card (COMAX brand?). I don't think anything else is pertinent, but can supply more details if needed. I haven't tried powering it on again. Do you think that's a logical thing to do (under close scrutiny, of course)? Or should I just write it off and get a new mobo? Anyone else had problems with PC faults like this? Thanks, Craig [to reply directly, change the VERB to a NUMERAL] |
#6
|
|||
|
|||
"Craig Williams" wrote in message
... .. The bad news is that the fire was on the motherboard. It appears to have started at the Firewire connector on the motherboard that goes to the adapter card. The connector cable (mobo end) is pretty well destroyed, and the one of the pins on the mobo is gone (stuck in the connector I suppose). You'd better check what was plugged into the Firewire connector, too. -- James T. White |
#7
|
|||
|
|||
That would be the Nikon CoolScan III film scanner. I turned it on and it
seems to function OK, but without the Firewire connection I don't know for sure. Craig "James T. White" wrote in message ... "Craig Williams" wrote in message ... . The bad news is that the fire was on the motherboard. It appears to have started at the Firewire connector on the motherboard that goes to the adapter card. The connector cable (mobo end) is pretty well destroyed, and the one of the pins on the mobo is gone (stuck in the connector I suppose). You'd better check what was plugged into the Firewire connector, too. -- James T. White |
#8
|
|||
|
|||
Noooo, I didn't mean the Nikon scanner. The firewire is for our digital
camcorder, which was NOT connected at the time - hooray! "Craig Williams" wrote in message ... That would be the Nikon CoolScan III film scanner. I turned it on and it seems to function OK, but without the Firewire connection I don't know for sure. Craig "James T. White" wrote in message ... "Craig Williams" wrote in message ... . The bad news is that the fire was on the motherboard. It appears to have started at the Firewire connector on the motherboard that goes to the adapter card. The connector cable (mobo end) is pretty well destroyed, and the one of the pins on the mobo is gone (stuck in the connector I suppose). You'd better check what was plugged into the Firewire connector, too. -- James T. White |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Change DVI resolution on ati fire gl t2 128 | Kai | Ati Videocards | 0 | February 20th 05 11:32 AM |
PCI Express guys: Anyone try the new(?) ATI Fire cards? | pw | Ati Videocards | 4 | January 19th 05 03:33 AM |
9500 Pro catches fire! | Faustus | Homebuilt PC's | 4 | November 30th 04 02:37 PM |
What's good to put out a cpu fire? | leigon. | Homebuilt PC's | 26 | November 28th 04 04:50 AM |
P4P800 on caught on fire? | ron | Asus Motherboards | 10 | October 28th 04 10:23 PM |