Hi everyone,
I recently purchased a Ryzen 7 3700x CPU to replace my Ryzen 5 2600. After installing the new CPU, the PC gets stuck in POST for +40min (though there's no pattern, once it's 10min, another time 1 hour). After it boots to Windows and I authenticate, there are no issues whatsoever and everything runs properly. CPU-z also recognizes all of the components.
Specs:
Mobo Gigabyte B450 Aorus Pro
RAM Corsair Vengeance Pro RGB 16GB 3200MHz
SSD Crucial 500 GB
Sapphire Radeon RX5700 XT Nitro+
PSU Thermaltake 650W
My mobo was running F2 BIOS so I updated it all the way up to F51 following the instructions in the Gigabyte support page before installing the new CPU and the mobo chipset driver should also be updated to the latest version.
I just installed my old CPU back and the PC booted quickly, as usual.
I tried re-installing the new CPU but the issue is ongoing.
I tried different RAM sockets, nothing.
I also just noticed that the BIOS has reset itself to default values, meaning it's on F2 version again.
Any clue what could be the issue?
Thank you
I recently purchased a Ryzen 7 3700x CPU to replace my Ryzen 5 2600. After installing the new CPU, the PC gets stuck in POST for +40min (though there's no pattern, once it's 10min, another time 1 hour). After it boots to Windows and I authenticate, there are no issues whatsoever and everything runs properly. CPU-z also recognizes all of the components.
Specs:
Mobo Gigabyte B450 Aorus Pro
RAM Corsair Vengeance Pro RGB 16GB 3200MHz
SSD Crucial 500 GB
Sapphire Radeon RX5700 XT Nitro+
PSU Thermaltake 650W
My mobo was running F2 BIOS so I updated it all the way up to F51 following the instructions in the Gigabyte support page before installing the new CPU and the mobo chipset driver should also be updated to the latest version.
I just installed my old CPU back and the PC booted quickly, as usual.
I tried re-installing the new CPU but the issue is ongoing.
I tried different RAM sockets, nothing.
I also just noticed that the BIOS has reset itself to default values, meaning it's on F2 version again.
Any clue what could be the issue?
Thank you
Last edited: