Extremely slow startup lasting over ten minutes using Grub, running either Windows or Linux on a dual-boot system.
Extremely slow startup lasting over ten minutes using Grub, running either Windows or Linux on a dual-boot system.
Hey there, a week back I slipped up and installed some harmful software that exploited a token logger to breach my Discord account. Once the news came in, I decided to completely overhaul my setup by swapping out my SSD and installing Debian. The week was packed with fixes, experimenting with Nvidia drivers, troubleshooting Steam issues, and more. There was a brief hiccup with grub, which probably contributed to the situation. When I power on, I quickly enter the BIOS splash screen and linger about eight minutes before it either jumps into BIOS via DEL or boots the chosen OS. Frustrated, I changed my boot sequence and made Windows the primary boot device, but the wait still lasted nearly ten minutes. Once inside the OS, everything felt normal—no odd behavior, no CPU/GPU strain. Then I thought about updating the BIOS on my motherboard, but that didn’t resolve anything. Now I’m really stuck and unsure what to do next.
PC Specs: Windows 10 Home 22H2 64 bit | Debian 12 Bookworm Alpha ASUS ROG STRIX X570-E Gaming (BIOS 4408, latest)
AMD Ryzen 7 5800X3D (stock) 4x16GB (64GB) G.Skill TridentZ DDR4-3200 (DOCP profile 1, 3200 MHz)
ASUS TUF NVidia RTX 3090 OC edition (stock) Seasonic TX-1000 (1000W PSU)
2TB XPG GAMMIX S5 NVMe (Windows Boot SSD) | 1TB Crucial P3 NVMe (Grub/Debian Boot SSD)
Using a single RAM stick and re-running the test. From what I've noticed, slow startup often points to RAM or the CPU placement, rather than the GPU.
I used a single RAM stick... nothing worked, even after running Memtest86+... The system boots normally but takes over ten minutes to start.
I believe I identified the issue, but fixing it beyond replacing the motherboard isn't clear. When starting up, the system remains stuck on A2 for eight minutes. The manual mentions "IDE Detect," indicating a potential bootloader problem. I could also attempt to install a fresh operating system to see if that resolves the matter.
I attempted to set up a fresh OS but faced repeated reboots, with one lasting nearly half an hour. Eventually, I returned to the original Windows installation. FanControl also encountered issues, only identifying 17 of the 40 sensors. It seems my motherboard is deteriorating. I’ve ordered a replacement and am hoping it resolves the problem.