Unsolved
This post is more than 5 years old
5 Posts
0
26642
December 7th, 2012 18:00
AlienwarenAurora-R4 Bios A07 information
Chris/Dell/Alienware,
I recentely purchased a Aurora R4, I love the computer, however, it shipped with bios a06, and there were issues. If I had the cpu overclocked, sometimes when it was booting it would throw a "no bootable drive" error. The pc shipped with a micron(crucial) c400 512ggb ssd. I first thought maybe the ssd was bad, but after much testing, It came down to weather or not I had the cpu set for overclock....if I did, it was just a matter of time till it through that error.
So, I have updated my bios to a07, and everything has seemed good, I have the cpu overclocked, and have not had a "no bootable drive" error on bootup. My question to you guys is, did a07 fix that issue? or did it just enable overclocking?? Because if it isnt fixed, it will turn up, and I just want you all to know about it, cus it sucks to have problems like this out of the box.....
Thanks,
-Tim
Aurora A4 specs: i7-3930K, 32gb 1600mhz ram, nvidia gtx 690, 512gb ssd + 1tb 7200 storage drive
T-Hefner
5 Posts
0
December 8th, 2012 04:00
Has anyone else seen the above mentioned issue? The computer hangs, and before windows boots it throws a "no bootable drive issue" - For me it didnt happen all the time...It was usually on a cold boot, or every 6-10 boot ups. Basically, the way I fixed it with bios a06, was to turn off the overclocking in the bios, and set bios to optimum defaults. No more boot errors.
Does anyone else have the dell stock micro c400 ssd drive and see the same thing? I read somewhere someone was having similar problems with bios a06, overclocking, no boootable drive.
Currently running a07, keeping fingers crossed, no bootable drive errors ......*yet*
Johnmcl7
1 Rookie
•
75 Posts
0
December 8th, 2012 11:00
There is a topic about A06 on this forum and I believe there were problems with this bios version with the cpu overclocking and Crucial SSD's which A07 was meant to resolve so it sounds like it is has done that.
I skipped straight fro A05 to A07 and initially had a problem with booting at all but since switching the bios back to Legacy from UEFI and rebuilding the SSD (also a Crucial) it's been working fine.
John
T-Hefner
5 Posts
0
December 8th, 2012 15:00
John,
Yea, I have seen the posts regarding the overclocking and the fixes for it in bios a07, but I havent seen where dell has said they were addressing the crucial ssd issues in a07 also. Kinda wanted to hear from Dell/Alienware on weather or not this was addressed in A07 also.
In my case, I have UEFI boot, because that was the way it shipped. Upgrading to a07, from a06, I made sure it was still set to UEFI, so that was never my problem. It had to do with the overclocking of the cpu, on cold boots, would throw a "no bootable drive found" error. For some reason, it wont detect the crucial c400 ssd, when it throws that error. Once, I set bios back to optimized defaults in a06 bios, the no bootable drive error would go away. Optimized defaults basically disables the overclocking, to stock clocks.
Keeping fingers crossed with bios a07, running overclocked cpu with no bootable drive errors on A07......*yet*
daddyz
71 Posts
0
December 8th, 2012 21:00
T-Hefner
5 Posts
0
December 9th, 2012 03:00
daddyz,
Exactly, Thats my point, there is no details in the release of A07, except, core multiplier fix. I wanted to know from dell/alienware if there was more then just that in a07? I have noticed the bios load bar with alienhead, on startup, now loads the full bar, where before I only ever saw it go half way on A06. Not sure if it means anything. But I know for sure, that on A06, if you had the cpu overclocked, eventually it would throw the no bootable drive found, and wouldnt see the crucial c400 ssd. Turn off overclocking, no more bootable drive problems on a06.
I am happy with A07 so far, no bootable drive found errors.
-Tim
In_Finite
3 Posts
0
April 4th, 2013 11:00
I've loaded A07 from A05 on an R4 and receive a BSOD every day. Never the same bugcheck either.
0a,
d1,
deaddead
The least one is a bugcheck that should never occur, but it has happened 3 times
-Dan