Hi,
The specification of my desktop computer is as
Processor: AMD FX-8320,
Motherboard: ASUS M5A97 (AMD 970 Chipset),
RAM: 16GB Kingston HyperX Fury,
HD: 1TB WD Black and
SMPS: CoolerMaster 650W
Due to some issue, the processor was replaced by the AMD. After installing the new processor (FX-8320), I see an error message during POST:
New CPU installed! Please enter setup to configure your system. Press F1 to Run SETUPAfter pressing
F1, I press
F8 for Boot Menu, then I select
P3:WDC.. (Hard Drive)
I saved booting priority by F10.
Then Windows login screen appears.
After every restart, I need to follow these steps after pressing
F1.
To find the solution, I have gone through the links
https://www.techsupportforum.com/forums/f15/solved-new-cpu-installed-on-boot-615569.htmlhttp://www.tomshardware.com/forum/174348-28-help-reinstalls-bootWhat I did to fix this issue.
1. Cleared CMOS using jumper,
2. Restored the BIOS to default,
3. Reconfigured the BIOS (Selected Hard Drive in the 1st Boot Priority and saved settings with F10.)
4. Checked the jumper pins,
5. Replaced the onboard battery.
To clear CMOS, “I did as Removed the onboard battery and moved the jumper again to clear the CMOS RTC RAM data. After clearing the CMOS, reinstalled the battery.”
6. Removed Processor and re-seated the Processor,
7. As per the link
https://www.asus.com/in/Motherboards/M5A97/HelpDesk_Download the latest BIOS version is 1605 (released on 31.10.2012). Already motherboard BIOS was updated and latest (1605). However, I re-flashed. After re-flashing, loaded default settings. In default settings mode, I selected Hard Drive in the 1st Boot Priority and saved settings with F10.
At the end, issue not resolved and I see the same message
New CPU installed! Please enter setup to configure your system. Press F1 to Run SETUPI discussed with ASUS. ASUS says, there is some issue in the motherboard. That’s why it’s not saving the settings. And ASUS suggested, disable
Wait for 'F1' If Error and continue to use.
Now please let me know what new steps should I go through to resolved this issue or
let me know, if I continue to use after disabling
Wait for 'F1' If Error, is there any possibility or risk of further hardware issue?