POST hang on new build VGA_LED

Toggle sidebar Toggle sidebar
P

pentdragon

Honorable
Nov 30, 2013
18
0
10,510
I recently built a new PC, here is a list of the hardwares I used. pcpartpicker

Symptoms: Worked for about an hour after FIRST POST with windows 10 home installed, then got a blue screen then everything went to hell after with POST hangs, fans and pump working, Motherboard restarts a 2-3 times before getting stuck with Asus Q-code 62 ("installation of the pch runtime services" according to manual, no idea what that means). VGA_LED also on.

for the past 2 weeks, I have tried everything to fix my build, and yes I also know about the sticky on this forum, have tried it but didn't work. I am now in the process of replacing everything one by one.

Have replaced:

  • PSU - replaced with Corsair CX850M
    Motherboard - Was previously Asus Z170-Deluxe
    RAM - went from 2 stick(2 x 8 gb) to (4 x 4 gb) of the same same ram

I am bread-boarding with only the PSU, CPU, Motherboard, and Ram. Still the same issue. My new CPU (only thing left to test) will be here in a few days but something else hit me, and pardon me if this is going to sound stupid but, can a bad monitor cause the post to hang?. I did some googling but couldn't find anything on this matter. I connected my laptop to my new monitor and couldn't get a display, so it might be faulty. But would that make my new build to fail it's POST? I think my mobo will give me a error code when there is no video output connected but that Q-code is not 62.
 
Solution
ko888
It's true that you can't rule out the CPU. Most builders don't have a spare CPU to troubleshoot with and the CPU is usually the most reliable component.
Sort by date Sort by votes


yes, I have tried plugging the DisplayPort cable into the motherboard. Removed both GPU(also have tested using single GPU in different pcie x16 slots), but still the same error. Are you saying this is probably a motherboard issue? I have gone through two motherboard with the same exact issue. Is there any chance of it being a CPU causing this or even the possibility of the monitor interfering with the POST sequence?
 
Upvote 0 Downvote
Are you sure the Q-Code is 62? Could it possibly be b2? The difference between a 6 and a lowercase b is with the top LED segment being lit or unlit.

A monitor/display is not even necessary for the POST process.

If the Q-Code is indeed 62 then one of the connected peripherals may be halting POST (e.g. faulty/incompatible keyboard).

Did you leave it at Q-Code 62 for several minutes to see if POST will continue? Sometimes bad firmware in the keyboard will cause the problem.
 
Upvote 0 Downvote


yes I am sure it is q-code 62, the top line is lit up. I have left it at that for probably over 10mins before hoping and praying it would go past it, but my prayers were not answered. I have been testing on top of the Mobo cardboard box with only:

  • -Motherboard
    -PSU
    -Ram
    -CPU
    -CPU Cooler
    -monitor

No keyboard or mouse connect, no extra fans or USB

-------------------
a little more detail of the symptom that I been getting while troubleshooting :

Sometimes after clearing CMOS I would get stuck on Q-code 79 (VGA_LED also still solid white) code according to manual; 79 is "CSM initialization". It would too be stuck here and not move on. I would then restart and I would be back to getting stuck at 62. On top of all that If I restart too many times without clearing the CMOS the MOBO would just not turn on until I clear CMOS again... Which I really don't understand.
 
Upvote 0 Downvote
Upvote 0 Downvote


bought a speaker last night, should be coming tomorrow, hopefully that will shed some light on this.

Thanks for your help by the way. I really appreciated it, as I am at my wits end with this build. After getting it to work for an hour I was very excited that my first build had absolutely no problems only to have it all ripped out from under me.
 
Upvote 0 Downvote
Speaker came and pluged in. Still the same thing, Q-code 62 VGA_LED, however I learned that there is no beep from the speaker(most of the time). I was able to get it to Beep once after turning LN2 mode on and it went to q-code b6 and VGA_LED turn off and switched to BOOT_DEVICE_LED (solid orange). So I quickly inserted my samsung m.2 Nvme ssd and restarted after clearing CMOS. However we are now back to Q-code 62 and VGA_LED solid white and NO beep from speaker. I have tried removing the SSD but could not replicate the same again.
 
Upvote 0 Downvote


0907 on sticker of the motherboard, I have also tried flashing it to the lastest Bios.

Also after many restarts I got the splash page to appear. AMI bios splash screen and the bios version on it is 0907. After a restart, I am back to square one with Q-code 62 and no display, no beep.

 
Upvote 0 Downvote
MORE updates: So after restart after restart I learn that it could sometimes finish boot just fine and put me into the UEFI BIOS. further more I decided to get out my Geforce GTX 980 TI and put one of those in and noticed the chance of a successful boot went from like 1 out of 30 to like 1 out of 10? Q-code 62 is still the most frequent probably 8 of out 10 times it gets stuck on that, sometime it gets stuck on Q-code 79(CSM initialization) and sometime 99 ( super IO initialization). When I do manage to get into the BIOS I noticed a few times it may freeze up and i'm forced to restart again, also it does not detect my m.2 SSD.

Edit #2: Q-code 79(CSM initialization) no longer appears after I disable CSM in the BIOS when using BIOS 1 ( the only one that I can get it to boot into UEFI at all). when switched to BIOS 2 It constantly hangs at 62 and 79 and 96.

When using BIOS 1 and after getting past POST when the screen freezes the Q-code on the Mobo changes to 04 PCH initialization before microcode loading.


Update #3, no longer hanging on 62 or 79 anymore. been getting a good POST almost every restart with a few Q-code 99 hangs but overall a huge improvement. Not even sure what I did different. However a new problems has arose... Windows OS keeps crashing, even crashing from the Installation disc have also tried booting from a USB. As soon as the POST is finished and it starts booting into my Operating System it will Blue screen and auto restart my computer.

update #4, BAD news we are back to square 1 with constant hangs on Q-code 62. Just suddenly decided to get stuck again after some restarts from windows BSODs. I also noticed that the PCIe led indicator for my GPU isn't on. Another Q-code that is often getting stuck at is Q-code 04 PCH ("pch initialization before microcode loading")

I hope this new information will give you more clues on what is wrong.
 
Upvote 0 Downvote


Windows 10 Home x64, and I believe it is partitioned to use a GPT on my m.2 SSD. However even when I disable all my SSD and only boot from the installation disc or USB it will Blue screen before even displaying the installation menu.
 
Upvote 0 Downvote


It vary between 04, 62, and 79

04 - pch initialization before microcode loading
62 - installation of pch runtime services
79 - csm initialization
 
Upvote 0 Downvote
Looks like my Problem child was the CPU after all. After the new CPU got installed it booted up without a problem on the first try. Got windows reinstalled without any BSODs too. For all future troubleshooters... don't rule out a CPU that only last a hour of usage.

Anyone way to close out this post with a solution? if not... Ko888 please say something like "It sounds like your CPU is defective and i'll pick you as the solution. I just want this post to be around for future people who might have the same issue as what I ran into. 2 weeks of nightmare finally over hopefully. :bounce:
 
Upvote 0 Downvote


Hi I have EXACTLY the same problem.
2nd Motherboard Rog VIII Hero Alpha to DeLuxe.
Just ordered a 2nd CPU.
Successful Win 10 install to Samsung M.2 950 drive.
1 hour Prime95 CPU (torture internal CPU) test on my Intel 6700K overclocked to 4.5Ghz & 1.35V
Reached 93 degrees (Noctuna NH-D15S)
Blue screen of death.
Could re-enter bios for 50+ reboots.
Windows would always hang.
Did everything, switch memory (Corsair LPX DDR4 3200 Vengence 2x8Gb)
Eventually reached code 4D in bios & no further.
Same CPU, different MB. Code 62 using on-board graphics & hdmi from MB.
Insert known working GTX 760 . No change.
Conclusion, CPU fried!
Will know this afternoon when I replace it.
€700 for 2nd MB & 2nd CPU.
Skylake is fragile. Forget 105 degrees shutdown temperature, 4.4Ghz safe overclock & 1.4V max for
Core voltage. This chip can die with a lot less than that.

For comparison, this is what is possible (I think they avoided the torture)
http://www.digitaltrends.com/computing/overclocking-intel-core-i7-6700k/

No torture test ever again!
Do not run the PRIME95 CPU Torture test, do not exceed 90 degrees::fou:

Here is a 6700K cooled by a Noctuna NH-D15 OC to 4.8Ghz reaching 90 degrees
http://www.techspot.com/review/1041-intel-core-i7-6700k-skylake/page12.html
 
Upvote 0 Downvote
Hello you just saved my sanity. I've had the exact same issues. I'm two nother boards and 2 different sets of ram into troubleshooting, and I come across this post. I've literally had this exact same experience. Thank you so much for posting. Ordering a new 7700k now.
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom