The motherboard is the machine, so the typical manifestation of a fizzled motherboard is a totally dead framework. Fans, drives, and different peripherals may turn up if the motherboard is dead, yet all the more frequently nothing at all happens when you turn on the force. No beeps, no lights, no fans, nothing. On the off chance that you think you have a dead motherboard, reconsider. The probably reason for a dead framework is a blown wire or breaker at the divider repository. In case you’re sure the framework is getting force and you have quite recently introduced the motherboard, its substantially more probable that you’ve fail to unite a link or made some other essential lapse than that the motherboard itself is terrible, expecting obviously that the issue motherboard is a highquality item. In a working system, it’s very uncommon for a high-quality motherboard to fail other than from lightning damage or other severe abuse. In particular, it’s nearly unheard of for a motherboard to fail while it is running, as opposed to when you start the system. A dead system is more often caused by a dead power supply than a dead motherboard, so the first step to troubleshoot an apparently dead motherboard is to swap in a known-good power supply. If the system remains completely dead with a known-good power supply, it’s likely that the motherboard is defective and must be replaced. It’s not uncommon for a motherboard to fail partially. It’s possible to work around such partial failures; for example, by disabling the failed function in BIOS Setup and installing an expansion card to replace the failed embedded function. We recommend against this practice, however, because a partial motherboard failure is often soon followed by a complete failure.
Image by shutterstock.com