EVGA

Evga X99 BIOS flash anomaly

Author
H-Emmanuel
New Member
  • Total Posts : 27
  • Reward points : 0
  • Joined: 2011/05/09 22:46:15
  • Status: offline
  • Ribbons : 0
2019/11/27 18:16:35 (permalink)
Hello everyone,
 
I'm experiencing a very weird issue with my Evga X99 Classified.
 
My 3 BIOS versions were:
#1 = 2.03
#2 = 2.03
#3 = 1.12
 
Within the BIOS, I flashed #1 to 2.07 and after that, the computer would no longer post, staying stuck at code 95 (sometimes 96) and eventually the CATERR LED would turn on.
 
Within the BIOS, I then tried to flash BIOS #3 to 2.06 and after that, same problem.
 
Using BIOS #2 to boot into Windows, I hot flashed #1 and #3 to version 2.03 and still the motherboard won't POST when the BIOS selector is set to them.
 
What could explain this weird behavior? At first I thought maybe there was something incompatible with my hardware in BIOS 2.07 and 2.06. But now that to the best of my knowledge, I've reverted back to 2.03 through the Windows flash app and they still don't work, I'm wondering what's wrong. There were no errors or power interruptions during the BIOS flash...
 
I reset the CMOS countless of times already.
 
Thanks!
#1

5 Replies Related Threads

    Cool GTX
    EVGA Forum Moderator
    • Total Posts : 21348
    • Reward points : 0
    • Joined: 2010/12/12 14:22:25
    • Location: Folding for the Greater Good
    • Status: offline
    • Ribbons : 116
    Re: Evga X99 BIOS flash anomaly 2019/11/27 18:23:53 (permalink)
    First -- Did you reset the BIOS to Default -- Before Flashing it ?

    Try rebooting 3 times ... when it locks just hold the power button till it restarts again ... it may work through the issue
     
    At least that is what I did to make my X99 Classy "work" after some heavy maintenance & mods on the custom loop

    RTX Project EVGA X99 FTWK-5930K,EVGA2080Ti EVGA-1200P2  Nibbler EVGA X99 3-GPU Water Loop 1600P2  AIO Folding  1080Ti FTW3 Hybrid, 1200P
    Thank You for Your Support


    #2
    H-Emmanuel
    New Member
    • Total Posts : 27
    • Reward points : 0
    • Joined: 2011/05/09 22:46:15
    • Status: offline
    • Ribbons : 0
    Re: Evga X99 BIOS flash anomaly 2019/11/27 19:01:33 (permalink)
    Thanks for the reply. Yes I did.
     
    Can you elaborate on your rebooting technique? What do you mean by "when it locks"?
     
    I was able to "revive" the two BIOS by flashing version 1.12 (what originally came with my board). However I'd like to update to the latest BIOS for the security/vulnerability fixes.
    #3
    Cool GTX
    EVGA Forum Moderator
    • Total Posts : 21348
    • Reward points : 0
    • Joined: 2010/12/12 14:22:25
    • Location: Folding for the Greater Good
    • Status: offline
    • Ribbons : 116
    Re: Evga X99 BIOS flash anomaly 2019/11/27 19:17:43 (permalink)
    I did Not Flash my BIOS
     
    After having the system down for a few weeks ... GPUs removed ... On first Reboot the MB failed at a code & just sat there several minutes.. before Win logon
     
    So, I forced reboot - by power button .. stuck again .. after 3 min. I force the PC to boot again with power button ... System worked - Full Boot

    RTX Project EVGA X99 FTWK-5930K,EVGA2080Ti EVGA-1200P2  Nibbler EVGA X99 3-GPU Water Loop 1600P2  AIO Folding  1080Ti FTW3 Hybrid, 1200P
    Thank You for Your Support


    #4
    bob16314
    CLASSIFIED ULTRA Member
    • Total Posts : 6412
    • Reward points : 0
    • Joined: 2008/11/07 22:33:22
    • Location: Planet of the Babes
    • Status: offline
    • Ribbons : 513
    Re: Evga X99 BIOS flash anomaly 2019/11/27 20:52:21 (permalink)
    Umm, version 2.09 is the latest for an X99 Classified in the EVGA Download Center..Any reason you're not flashing to that one?
     
     

    * Corsair Obsidian 450D Mid-Tower - Airflow Edition * ASUS ROG Maximus X Hero (Wi-Fi AC) * Intel i7-8700K (Delidded, TG Conductonaut) @ 5.2GHz* 16GB G.SKILL Trident Z 4133MHz * Crucial MX500 M.2 1TB * WD Black 500GB (x2) * Seasonic M12 II 750W * Corsair H80i V2 * EVGA GTX 760 SC * Dual-Boot Win7 Home 64-bit/Win10 Home 64-bit (Winver 1909) * 
     
    "Whatever it takes, as long as it works" - Me
     
     
     
    #5
    H-Emmanuel
    New Member
    • Total Posts : 27
    • Reward points : 0
    • Joined: 2011/05/09 22:46:15
    • Status: offline
    • Ribbons : 0
    Re: Evga X99 BIOS flash anomaly 2019/11/28 13:17:45 (permalink)
    Here's a little story :)
     
    The issues I described began after I flashed BIOS 2.09 so I tried downgrading to previous versions to see if the problem would go away.
     
    Before I started tinkering with BIOS updates and having boot problems, I had a 6850K running on 2.03. The night before swapping out to my current 5960X, I ran Memtest86 7.5 (UEFI) for 50 passes, 31 hours to make sure that if any issue arose, it wouldn't be RAM related.
     
    When I first installed the 5960X, it hung on post code 95 and sometimes 96. After a single CMOS reset, it finally booted on the same BIOS chip (2.03) as the 6850K. I got into Windows to do some testing and oddly enough, the computer would auto-restart within an hour of running Prime95 without any error or BSOD. The core temperatures were all around 50C, same thing for the motherboard VRMs. My PSU is a Evga Supernova 1200 P2 and just a few days earlier I was running my 4.3GHz 6850K for 24H+ in some custom AVX/FMA3 small FFT loops; that was pulling 200W vs the stock 140W 5960X.
     
    Doubting that my PSU or motherboard had suddenly died on me, I decided to check if any BIOS updates had been released in case they fixed some kind of compatibility issue. For security reasons (spectre etc.), I wanted to flash the latest version anyway.
     
    After I flashed 2.09 and every single BIOS down to 2.02, the computer would remain stuck at post code 95/96 regardless of CMOS resets and restarts. I had to flash 1.12 or 1.20 to get those BIOS chips bootable again, anything higher would bring back the problem. This whole thing started looking like some low-level software glitch more than a hardware problem, especially considering that 2.03 worked and then no longer worked when I reflashed it.
     
    Not wanting to take apart my 2 water loops, I did the next best thing. I disconnected literally everything that connects to the motherboard except for 1 stick of RAM, my GPU and the case power/reset/LED wires. I also flipped off all but 1 PCI-E switch.
     
    I then attempted a first boot on 2.09 which got stuck at the usual 95/96. I did a single CMOS reset and finally, it booted all the way into the BIOS. I repeated this procedure for the 2.03 BIOS chip and that worked too.
     
    I then reconnected everything I disconnected and still booted successfully into both BIOS (2.09 and 2.03). I just finished running a 2-hour loop of Prime95 FMA3, 112K in-place and the computer did not auto-restart. This specific test auto-restarted after like 20 minutes earlier.
     
    All in all, this leaves me with a few questions:
    1- it seems like the CPU and motherboard struggled with their initial "handshake". Does anyone have an idea of what could have gone wrong that got magically fixed after stripping the computer to barebones? No component other than the CPU was changed during this upgrade.
     
    2- although I haven't run Prime95 for more than 2 hours yet to completely verify that the computer no longer auto-restarts, if it is truly fixed then something weird was going on at a BIOS/CPU level. The computer would no longer boot even after reflashing the original bootable version (2.03). It's as if something at the BIOS level persisted from the 6850K to the 5960X which allowed the computer to boot but also made it unstable (auto-restart under heavy load). The moment I flashed a BIOS using the 5960X, that persistent information was gone and the computer would no longer boot until going barebone. When it did finally boot, the instability was gone. Anyone wants to speculate on this?
     
    3- one thing I did add during the upgrade was the Classified IO cover. In one thread, someone recommended removing it without mentioning why. Does anyone know why someone would recommend removing it? Does it pose some kind of risk? (it is made of metal)
     
    Thanks!
    post edited by H-Emmanuel - 2019/11/28 14:47:13
    #6
    Jump to:
  • Back to Mobile