If the PC does not shut down after step 3, then you can start adding components back to the PC - one at a time. Don't try to boot, but let it sit at the BIOS screen each time. The idea is to see if an increased load on the power supply or MB is causing the issue. You can try replacing the PS, but it's more likely that the issue is on the MB.ĥ. On the circuit board, they are part of bus voltage regulation, clock timing circuits, and so on. In a power supply, for example, they might lose the ability to regulate the voltage, causing it to drop below spec and cause the machine to reset or shutdown. This throws whatever circuit they were part of out of spec. The paste-like electrolyte inside them contains water. After time or in high temps, they will out-gas eventually, they dry out and lose their value. This is typical of electrolytic capacitors that have dried out. If the PC still shuts down after step 3, then it's likely a component is changing value over time. If that creates a hotspot on the chip, it could make it shutdown. Clean the surfaces and apply the correct amount of new thermal paste. At that point, I would remove and re-seat the CPU. Download the Dell manual. If it shutdown there, you have eliminated all the components still not connected. Boot to the BIOS setup screen and let it sit. Put only the minimum memory back in and anything you need to get to the BIOS setup.ģ. Pay attention to the insides of the power supply (through the slots) and the heat sink on the CPU. Really get in and under everything you can. Next step would be to remove everything removable (hard drives, large flat cables, expansion cards) and blow the chassis/mother board out with high-pressure air. At work, I have a small compressor. In my experience, "sudden shutdowns" are usually heat-related - typically, the CPU. The heat/cool cycle of operating a PC can lead to "thermal creep" where components work themselves loose.Ģ. First diagnostic step is to remove and reseat all connectors and components (not the CPU). Assume some common problems and try to address them one-by-one.ġ. You've done a lot of testing and haven't been able to isolate the problem to a single large component.
0 kommentar(er)
