Sign in with
Sign up | Sign in
Your question

Asus Maximus Ranger Vii - Qcode FE - No POST

Tags:
  • Asus
  • BIOS
  • Motherboards
  • Physical Memory
Last response: in Motherboards
Share
September 3, 2014 12:35:05 PM

Hi All,

This is my first post to you fine folks, please if you can help i would greatly appreciate it.

Specs
Asus Ranger Vii Maximus
Core i5 Haswell
16GB Vengance DDR3 2133
256 SSD coursier
H80i cooler
780Ti 3GB
Raven3 Silverstone case

I recently took delivery of my new PC components, as excited as a kid at christmass :) .

The build went well, usual precaution taken with a anti static wristband to keep me grounded. Once the PC was built. Great care taken in the placing of everything

Time came for the first power on test which all the LEDS fans powered up and ran without issue but no POST screen...

The Qcode sequence runs as follows

00 (not used says manual)
14 (Pre Memory initialization started)
15 (Pre Memory System agent initialization started)
FE (Cannot find this at all, not in the manual nor online. This could mean Fatal Error? or F***ing excellent i just do not know)

After this i thought ah must be a dud mem module, but i do not think this is the case as i test each module individually and aslo with none at all.

After this i thought it could have shipped with a dead cmos battery and tested it with two new ones. No joy.

I have tried clear CMOS button and restarts but nothing.

I thought i might be shorting the mobo somehow so i reseated every component, i mean down to the risers.

Once back together i did the following

Created a Flashback USB formatted to Fat16 with 64KB allocated with the following BIOS's (one at a time of course ^.^)

- MAXIMUS-VII-RANGER-ASUS-0601
- MAXIMUS-VII-RANGER-ASUS-0904
- MAXIMUS-VII-RANGER-ASUS-1003
- MAXIMUS-VII-RANGER-ASUS-1104

Renaming to "M7R.cap"..

Once inserted i pressed the flashback button for 3 seconds, it picks up the drive and flashes until complete. On restart it returns to FE qcode.

Damn FE what the hell are you!!!!.

Can anyone shed some light on this, I may end up having to send it back to be replaced but i want to exhaust every troubleshooting options prior so i do not have a repeat with a new board. This could well be a problem between keyboard and chair or i cant see the forest for the trees if you get me.

I appreciate your time.

Thank you.



More about : asus maximus ranger vii qcode post

a b V Motherboard
September 3, 2014 12:38:26 PM

FE : Flash ROM programing was successful.Next, restarting the system bios.

try ClrCmos, Pull out battery, power on without anything plug in (cpu, ram, hdd)
m
1
l
September 3, 2014 12:39:28 PM

carlo_bigtunes said:
FE : Flash ROM programing was successful.Next, restarting the system bios.

try ClrCmos, Pull out battery, power on without anything plug in (cpu, ram, hdd)


Trying this now, just to note i was getting FE prior to any flashing. Cheers i report back in a moment.
m
0
l
Related resources
September 3, 2014 12:41:26 PM

carlo_bigtunes said:
FE : Flash ROM programing was successful.Next, restarting the system bios.

try ClrCmos, Pull out battery, power on without anything plug in (cpu, ram, hdd)


No Ram, No HDD, Cleared CMOS it restart still on FE.

Also tried without the CMOS battery inserted for the craic.
m
0
l
a b V Motherboard
September 3, 2014 12:49:46 PM

i think corrupted bios or cpu not seated correctly in pin.
m
1
l
September 3, 2014 1:06:45 PM

carlo_bigtunes said:
i think corrupted bios or cpu not seated correctly in pin.


Thank you kindly for your help mate. I figured it out. The thing that threw me about this board was the ram slot only had one clip on the right side so i put the ram in and push until i met resistance as to not damage the mobo or chip. I had to actually push through on the lef side without an actual clip for it to sit in properly which i never did.

It was reaally hard to tell that they were not fully seated.

so that was it two days of troubleshooting 8+years working in IT support and that was extent of the issue ^,^ uuughhh im just going to tell the guys in work something waaaay more complex went wrong hah.
m
0
l
!