F5F Stay Refreshed Hardware Desktop Transported build fails to show BIOS, remains on screen A2 error

Transported build fails to show BIOS, remains on screen A2 error

Transported build fails to show BIOS, remains on screen A2 error

D
Darek06
Junior Member
16
12-04-2016, 08:22 AM
#1
Problem description has been updated with additional details and clarifications.
D
Darek06
12-04-2016, 08:22 AM #1

Problem description has been updated with additional details and clarifications.

A
Abli
Junior Member
4
12-11-2016, 12:19 PM
#2
Welcome to the forums, newcomer!
Edit 2: CMOS error stopped after re-seating the button battery. A2 error still present.
You may want to try swapping in a fresh cell for the battery.
Corsair Vengeance LPX 32GB DDR4-3200
Do you have a link to this RAM kit? Which slots are being filled with RAM on the motherboard?
Resetting BIOS to PRIME X299-DELUXE II BIOS 3801. A2 code error persists.
Could you explain how you performed this?
Removing the GPU and using the built-in Display Port output.
This doesn't matter much since the processor lacks an integrated graphics unit.
What should I attempt next? Sadly, I can't replace other parts (besides new RAM sticks).
Troubleshooting involves systematically removing known working components or testing against a donor system to identify the faulty part, rather than assuming a specific failure point.
A
Abli
12-11-2016, 12:19 PM #2

Welcome to the forums, newcomer!
Edit 2: CMOS error stopped after re-seating the button battery. A2 error still present.
You may want to try swapping in a fresh cell for the battery.
Corsair Vengeance LPX 32GB DDR4-3200
Do you have a link to this RAM kit? Which slots are being filled with RAM on the motherboard?
Resetting BIOS to PRIME X299-DELUXE II BIOS 3801. A2 code error persists.
Could you explain how you performed this?
Removing the GPU and using the built-in Display Port output.
This doesn't matter much since the processor lacks an integrated graphics unit.
What should I attempt next? Sadly, I can't replace other parts (besides new RAM sticks).
Troubleshooting involves systematically removing known working components or testing against a donor system to identify the faulty part, rather than assuming a specific failure point.

P
PersieO
Posting Freak
786
12-13-2016, 12:18 PM
#3
Thank you! And your thoughtful response is appreciated. I’ll include this in my testing list.

The Amazon product page is here:
https://www.amazon.co.jp/CORSAIR-メモリモジュー...TNI2/?th=1

I think the official Cosair source is:
https://www.corsair.com/us/en/p/mem...00...m2e3200c16

EDIT: I should note my current RAM setup – presently only one stick in "DIMM_C1*", matching the instructions in the motherboard manual.

I saved the new BIOS file onto a USB drive and connected it to the system. While powered on, I activated the BIOS via the "BIOS_FLBK" button for about three seconds, which triggered a green light. After releasing the button, pressing the power button brought the machine online. It displayed some CPU codes and reset itself, then proceeded with VGA codes before encountering the same HDD A2 error and freezing again.

I considered checking the GPU display to see if any BIOS information appeared, wondering whether HDMI or DisplayPort would be better, but I suspect DP is the way to go.

EDIT 2: After installing the GPU, I connected my monitor to a DP output. The screen lit up briefly before switching to text advising against turning off the PC while the BIOS updates. The system rebooted once but failed to boot on subsequent attempts, consistently returning the A2 error code.

EDIT 3: With the GPU installed, I linked an Ubuntu USB into a DP port and pressed "DELETE" or "F2" during startup. The display appeared briefly before the screen froze at the A2 error again. I then accessed BIOS via F1, which functioned correctly – no errors, responsive keyboard/mouse. I navigated to the boot menu, selected the USB, and the PC restarted successfully, showing the same screen. I attempted to adjust the CPU fan settings but couldn’t locate them. The automatic fan detection took roughly two minutes and suggested minor speed changes. Temperatures stayed around 30°C, with the AIO fan running at about 2800 RPM. All cooling fans were active. When I re-entered BIOS, I chose a different option and managed to boot from the Ubuntu USB. Display and input devices worked properly.

I then decided to power down, assuming the slow USB or limited RAM (just one stick) was the cause. I added more RAM and connected the M.2 drive and HDD, hoping they would appear in BIOS. However, after restarting, I still couldn’t enter BIOS – the original problem remained: a black screen with no way to access the system. Disconnecting the M.2 and HDD, plus additional RAM, didn’t resolve the issue, and I’m left wondering if I’ll need professional help in my new city.
P
PersieO
12-13-2016, 12:18 PM #3

Thank you! And your thoughtful response is appreciated. I’ll include this in my testing list.

The Amazon product page is here:
https://www.amazon.co.jp/CORSAIR-メモリモジュー...TNI2/?th=1

I think the official Cosair source is:
https://www.corsair.com/us/en/p/mem...00...m2e3200c16

EDIT: I should note my current RAM setup – presently only one stick in "DIMM_C1*", matching the instructions in the motherboard manual.

I saved the new BIOS file onto a USB drive and connected it to the system. While powered on, I activated the BIOS via the "BIOS_FLBK" button for about three seconds, which triggered a green light. After releasing the button, pressing the power button brought the machine online. It displayed some CPU codes and reset itself, then proceeded with VGA codes before encountering the same HDD A2 error and freezing again.

I considered checking the GPU display to see if any BIOS information appeared, wondering whether HDMI or DisplayPort would be better, but I suspect DP is the way to go.

EDIT 2: After installing the GPU, I connected my monitor to a DP output. The screen lit up briefly before switching to text advising against turning off the PC while the BIOS updates. The system rebooted once but failed to boot on subsequent attempts, consistently returning the A2 error code.

EDIT 3: With the GPU installed, I linked an Ubuntu USB into a DP port and pressed "DELETE" or "F2" during startup. The display appeared briefly before the screen froze at the A2 error again. I then accessed BIOS via F1, which functioned correctly – no errors, responsive keyboard/mouse. I navigated to the boot menu, selected the USB, and the PC restarted successfully, showing the same screen. I attempted to adjust the CPU fan settings but couldn’t locate them. The automatic fan detection took roughly two minutes and suggested minor speed changes. Temperatures stayed around 30°C, with the AIO fan running at about 2800 RPM. All cooling fans were active. When I re-entered BIOS, I chose a different option and managed to boot from the Ubuntu USB. Display and input devices worked properly.

I then decided to power down, assuming the slow USB or limited RAM (just one stick) was the cause. I added more RAM and connected the M.2 drive and HDD, hoping they would appear in BIOS. However, after restarting, I still couldn’t enter BIOS – the original problem remained: a black screen with no way to access the system. Disconnecting the M.2 and HDD, plus additional RAM, didn’t resolve the issue, and I’m left wondering if I’ll need professional help in my new city.

T
travelelliott
Junior Member
46
01-02-2017, 06:34 PM
#4
Someone lent me a functional SSD to try, but the A2 error persisted. The same individual might be able to provide a 3.5" HDD to USB and M.2 to USB adapter for testing. This would help determine if the drives are functional. At this point, I believe they are, possibly due to a motherboard issue or incorrect setup. If useful, I can share photos of the current connections.
T
travelelliott
01-02-2017, 06:34 PM #4

Someone lent me a functional SSD to try, but the A2 error persisted. The same individual might be able to provide a 3.5" HDD to USB and M.2 to USB adapter for testing. This would help determine if the drives are functional. At this point, I believe they are, possibly due to a motherboard issue or incorrect setup. If useful, I can share photos of the current connections.