Unsolved

1 Rookie

 • 

6 Posts

1230

October 19th, 2022 06:00

Aurora R4, one beep code

Alienware Aurora R4

Alienware Aurora R4

Hi, our Alienware Aurora R4 isn’t getting past post.

We are running on windows 10 Alienware bios version A11 and it’s had a windows update which required the pc to be restarted.

gone ahead with the restart and it gets to the shut down point and won’t then get past post without giving us beep code 1.

It has happened previously (see image)

E93A6568-5D8D-4440-93E3-DC1AC79B7907.jpeg

 (don’t know why it thinks we have overclocked as we have never touched those settings)

and we have been able to get it started again by removing the mouse or keyboard and replacing them. But now there has been another windows update as explained above.


yesterday we tried removing hardware (removing the ram gave us the two beep code and returned to one beep code when we reinstalled the ram) so we power drained and removed the graphics card and CMOS battery and left it over night.

 

this morning we put the CMOS battery and graphics card back in and managed to get it past post to this screen:

83BFDC9E-7E99-421D-8C9B-4A15B9B34370.jpeg

posts online said to press F2 so we tried it and next it took us to the bios menu where it said to change the boot mode from UEFI to legacy. We did this and then the computer went to restart and went back to the post screen (one bios beep) and got stuck there again.

We just want to get to the OS so we can run system diagnostics as we believe it may be a windows update issue (parents have an Alienware R8 that just had a windows update and had misplaced personal settings but I managed to solve it with the windows onboard diagnostic software which fixed the misplaced files and I believe that may be our issue if it is a bios fault)

the computer has only been used for digital artwork with a drawing tablet and photoshop. No heavy hardcore gaming and there has been no issues with the computer when in use apart from being a bit slow on loading photoshop up.

hope you can help.

1 Rookie

 • 

6 Posts

October 19th, 2022 07:00

Update: just tried the ram sticks. Got 1 beep code in every slot tried, until we got to slot 4 where it started up with no beep codes but no video either so couldn’t tell if it was getting past post or not.

9 Legend

 • 

15.1K Posts

October 19th, 2022 11:00

I have seen that w my R4.  Mistake is to allow Windows 10 update which often messes up cmos settings.  In this relatively old model, disconnect all storage devices and replace cmos battery w a new one.  You may also try clear cmos settings by RTCRST jumper on motherboard.  Try to boot into bios without hdd/ssd to establish a good post first.  If successful then put a blank hdd in and do a clean OS Win 10 Pro latest ver install.  After install use gpedit.msc to disable auto Windows update for good.

1 Rookie

 • 

6 Posts

October 21st, 2022 06:00

Thank you for your help and apologies for the delayed response.

we tried booting with a new CMOS battery and did the jumper reset too and tried to boot without HDD/SSD as suggested but sadly it couldn’t get past the POST check and kept giving us the repeating one beep.

a few weeks prior I did manage to do a system hardware health check (sorry I tried to share a screenshot but it’s not working) that basically said the performance of everything is poor and needs replacing and also said ‘missing events in event log 44%’ not sure what that is about.

1 Rookie

 • 

6 Posts

October 21st, 2022 06:00

CCBB65FD-D8AB-46C9-862E-A1161628133C.jpeg

not sure why it keeps loading upside down from my phone and apologies for the poor quality but hopefully it can be read. If not I can write it out.

4 Operator

 • 

2.3K Posts

October 21st, 2022 06:00

00000Capture.JPG

 

1 Rookie

 • 

6 Posts

October 21st, 2022 21:00

Tried it again and managed to boot it up (sorry about the clutter, it’s a small room)

1CF570A1-FFB7-4C15-9CDC-6D7FAA436E66.jpeg

CD6F351D-87FD-46AA-BCD4-992B79F590FD.jpegwe then pressed F1 and got this:

380262E0-310D-458F-921A-F3E89F42B10B.jpegso we pressed F1 again and it booted and finished updating windows and shut down.

we tried to switch it on again but went back to the POST issue again. Will have another look later and try the rest of what you suggested (good job we had literally just ordered a new SSD and has arrived)

thank you for your help!

5 Practitioner

 • 

1.6K Posts

October 23rd, 2022 20:00

A 1 beep error is usually BIOS corruption and it can sometimes only happen occasionally or sometimes constantly with no boot to the OS.

I have repaired a few AW laptops with a 1 beep error but never tried it on a desktop. On the laptops it requires you to extract a file from the BIOS, put it on a bootable USB, and force the system to boot from the USB by holding down the END key while plugging the power in. I'm not sure if this process is possible on a desktop but it could be a last resort if you have no choice. 

8 Wizard

 • 

17.1K Posts

October 23rd, 2022 22:00


@HazelSwift wrote:

Tried it again and managed to boot it up (sorry about the clutter, it’s a small room)

we then pressed F1 and got this:

so we pressed F1 again and it booted and finished updating windows and shut down.

we tried to switch it on again but went back to the POST issue again. 


So, you dragged the Alien-monster out from under the desk huh? They are heavy and well built aren't they ? (I still have my working Aurora-R1).

It's really an Aurora-R4 ALX (very rare) because it has the extra LEDS and louvers on top. Be sure the 3 AA batteries for the extra ALX light are good-and-fresh (for some reason, IIRC, that causes some weird problems).

That display looks very messed up. Like you might want to try a spare PCIe video card? Maybe?

As far as the Over-Clocking message ... Correct ... it SHOULD NOT be Over-Clocked and if you can ever get into the BIOS, load BIOS defaults and be sure all OC is Off.

Between the unexpected OC messages and that weird split-screen-ish display at Post or around BIOS initialization ... it looks pretty jacked-up. I'm surprised you got it back into Windows.

 

1 Rookie

 • 

6 Posts

January 1st, 2023 10:00

Could it be an issue with A11?

found this on another forum:

windows-10-killed-my-dell-xps-2710-a-10.html 

Quote:

XPS 2710 won't boot up SOLUTION!!! FIX!!!

To all,

I had the same problem of not be able to boot up. Using Windows 10 and Dell BIOS A11. I read all the messages in various forums for their solutions. Basically, the problem is not been able to get the Dell logo so you can go into BIOS and/or Boot setup. I saw all kinds of responses and for some they work and for other it didn't. Many complicated steps for something that I found (it turn-out) to be simple.

Here's what I did:

1.Follow the CMOS reset, clear NVRAM, and BIOS procedure (steps)-- Make sure to disconnect power!!!
a. Take out the coin battery and press the power button for 10 seconds to clear the CMOS to totally discharge it. Put battery back.
b. Locate both the 2-pin jumper plug for the password connector (PSWD), and the CMOS (RTCRST)-- RealTimeClockReset (look at the XPS user manual PDF--download for free).
c. Move both plugs to the left.
d. Connect power, press power button, and wait at least for 10 seconds. Turn power off.
e. Put back both plugs where they were before.

2. Now, to force a Realtime Clock Power Failure (5 beeps in your computer at power up--power on!)
a. This will hopefully get you where you can make some changes to the BIOS entries.
b. At power up press F2 and/or F12 (BIOS access and/or Boot setup)
c. With F2 you can make sure the date/time is correct , the hard drives are recognized, and the booting sequence.
d. This is what you really want...F12...Boot setup!! Here I solved my problem...and hopefully yours. What I did is to change the Boot Mode Setting from Legacy Boot to UEFI Boot. This made the Windows Boot Loader (WBL) take over the booting process and....presto!! I got my system working back!!!
e. MAKE SURE YOU PUT THE BATTERY BACK BEFORE PRESSING ENTER TO SELECT UEFI BOOT!!!
f. I had DELL BIOS A11 so I updated to A12 while in Windows before I rebooted for second time to see if I really got it working. Know what? I DID!!!! 8-)

3. This is assuming you don't have a real hardware problem with the hard drives, memory, video card, etc., etc.

4. While I got it to force a Realtime Clock Power Failure I was able (within the BIOS options) to run hardware diagnostics...which they all turn out OK. So there were no hardware problems with my system...yours..who knows???

5. Hope this help since the XPS 2710 is awesome!!! I'll hate to see a good system go to waste for just a simple fix. For some of the user I read that bought a MOBO maybe it was not necessary...maybe! Give it a try and let us know if it works for you. If it does, please pass it along to other forums so everyone can benefit...thanks!

JC
Retired AF Civilian Systems Engineer

No Events found!

Top