How an accident damages one motherboard and the damage affects another one?

[Oftoy]

The PC. Not a PC, just a setup of some parts left over from disused machines.
PC : Acer aspire M5700.
OS : No OS.
CPU: Intel Core2 Quad CPU.
RAM: DDR2 800 SDRAM 4G.
GPU: On board Intel G45，
PSU: Corsaire RM650.
MB : G45T AM2 V:1.0
HDD: WD600BEVS Scorpio 60GB
BIOS:American Megatrends V.02.16

This has nothing to do with Acer product.

This is something which I cannot understand and come to you professionals for advices.

Note: This has been posted in many forums and has not been answered reasonably.

Scenario 1.
The PC was a normal desktop PC. Had start up issues a few months ago, not started sometimes. Bought another MB, identical to the OEM one, and another PSU, Corsair RM651x. These two parts replaced the OEM MB & PSU. Set up properly. Had power on, "pa" a burst and smell and the HDD was burnt. The SATA power connector was a defective one and cause the damage. Had another HDD connected to another SATA power connector, the PC started normally. Tried to install OS on this HDD, when it came to select HDD, there was no any HDD data in the dialogue window and installer found no any hard drive drivers. Checked BIOS, there was no data of the HDD.

Scenario 2.
Removed CPU, RAM sticks, CR2032, PSU, DVD drive, keyboard, mouse, and the monitor from the above said PC. Note, the MB remained in the case of the above said PC. Had another identical MB laid on top of a wooden bench, and had all the parts from removed from the above said PC installed or connected to this MB properly, and another HDD installed properly, and started OS installation. When it came to the step of selecting HDD, there was no any HDD data in the dialogue window and installer found no any hard drive drivers. Checked BIOS, there was no data of the HDD.

Questions:
How the damage on one MB came over to another MB?
What part or parts transported the damage message?
No damage to the second MB, but why installer found the same damage on the second MB?
The installer remembered the damage and reacted the same response as it did previously to the first MB?
Or what?

 

[Joe C]

First thing you'll need to do is to get the board to recognize the hdd in the bios, without that first then nothing else will happen. Try a different sata cable on different sata ports, check that drive in a different pc to see if the bios will recognize it, if not then you may need to get another hdd. The likely hood of both boards being bad as to not recognize a hdd would be slim, I would first suspect sata cable, power supply molex or the drive itself.

 

[PP Mguire]

You need to return the PSU. Short in the line fried the HDDs. The second one might still spin but the controller board is probably toast.

 

[Joe C]

You need to return the PSU. Short in the line fried the HDDs. The second one might still spin but the controller board is probably toast.

Seeing as the OP is from the ROC we do not know if this could really be a Corsair PSU, or the actual age of this, The Op stated it was the sata power connector which would be very unusual for a quality Corsair psu to do

 

[Oftoy]

First thing you'll need to do is to get the board to recognize the hdd in the bios, without that first then nothing else will happen. Try a different sata cable on different sata ports, check that drive in a different pc to see if the bios will recognize it, if not then you may need to get another hdd. The likely hood of both boards being bad as to not recognize a hdd would be slim, I would first suspect sata cable, power supply molex or the drive itself.

Thank you.

Tried all what you said above.
The peculiar thing is it could run the OS from a hard drive but would not install OS onto the same hard drive and the reason for not installing was the same for both motherboards.

 

[Oftoy]

You need to return the PSU. Short in the line fried the HDDs. The second one might still spin but the controller board is probably toast.

Thank you.

But why and how one accident damaged two MBs?

 

[Oftoy]

Seeing as the OP is from the ROC we do not know if this could really be a Corsair PSU, or the actual age of this, The Op stated it was the sata power connector which would be very unusual for a quality Corsair psu to do

Thank you.

Thank you.

Great Lakes State. Ha, we were once neighbours. I lived in Dubuque for many years.
Corsair RM650x PSU caused the accident, but I do not care about that.
My concern is HOW AN ACCIDENT ON ONE MOTHERBOARD AFFECTS ANOTHER MOTHERBOARD?

 

[PP Mguire]

It's not the motherboards, it's the HDDs. The second drive was either browned or surged when the first was shorted. This is assuming that the second board you tested with was either a previously good working secondary or new. The fact that both will post and boot but not see the drives also says the drives have been shot.

Seeing as the OP is from the ROC we do not know if this could really be a Corsair PSU, or the actual age of this, The Op stated it was the sata power connector which would be very unusual for a quality Corsair psu to do

It's unlikely, but not impossible for it to be bad, but lack of info there. Could have been the PSU was fine but the cable pack that was loaded in the box was incorrect (again assuming it's new from the store, higher probability if used). 24 and 8 pins are usually never pinned/keyed different with same manufacturer but VGA and SATA/Molex can sometimes be pinned differently with same keying. If that's the case it would insta short and trip protection.

 

[DomniCruper]

Thanks for sharing!