Problem with PC startup not resolved.
Problem with PC startup not resolved.
Hi all,
My pc had a cocacola spill after drying up. I turned it on and it booted, then shut it off and tried again later—it won’t boot now.
What happens: all fans spin, RGB is on, the ice cap is on, and the GPU spins. The light turns off quickly but keeps spinning. No post or booting.
What’s causing the issue? Why did it boot up but now it won’t? Thanks.
did you wipe it down or simply let it sit without baking to the motherboard and other components?
I allowed it to dry, then started it up. It booted but I saw a small amount of water on the top radiator fan. I turned it off. I cleaned everything with isopropyl alcohol and let it dry again. After turning it on, it still won’t boot. The AEorus X570 lights illuminate the board, all fans spin, then the lights turn off but everything keeps spinning. I moved the GPU to the 2nd PCIe slot and turned it on—beeps came out, then the PC shut down. After unplugging, I reconnected it and heard beeps, then the PC turned off again. Once I reinserted the GPU into the main slot, it didn’t work properly; the lights would turn on and off repeatedly, and the GPU behaved the same. I removed all memory, leaving only one active, but nothing happened. I really want it to function. I’ve invested a lot of time and effort, and it’s stored in those NVMe drives.
Hello, I attempted to clean everything again and the PC started up, though it doesn't recognize my NVM2 KC3000. The NVMe device gets warm but isn't visible in the BIOS. I updated the BIOS to the latest F38 for GIGABYTE Aeorus. I'm not sure if the NVMe is damaged—everything else on the PC functions normally, including RAM, GPU, etc.
Yes, the pc even started up a few hours after the spillage. However, I observed more water or coke condensing in the radiator, so I turned off the PSU by switching it off. After cleaning again and letting it dry, the pc wouldn't boot at all, no matter how much I tried. After days of inactivity, I began testing the RAM in the slots and it finally booted up. All components functioned properly, including my second NVME, though it still didn't recognize the KC3000. It's hard for me to believe that was the only part that got damaged while everything else remained operational.