cancel
Showing results for 
Search instead for 
Did you mean: 

Need bios guidance to achieve non-oc stable boot...

VitBrevis
Level 7
Not looking to OC (yet) just trying to get stable.

Looking for any suggestions on where to start, I had this rig stable, upgraded my bios and lost my sweet spot.
I am now clouded by 'too much info', countless google searches has me chasing bios settings I probably should not be changing and wanted some fresh input if possible.


RVE bios 2001 (For NVME)
5960x
64gb Corsair Dominator Platinum 2666 8x8 2666 15-17-17-35
Samsung 950 Pro NVME boot (with a proper UEFI Win10 Install)
980ti
970gtx
Corsair AX1200I PSU

Primary use is a graphics workstation, occasional gaming.

My workflow when attempting to get stable:
Clear CMOS, load defaults,
Set memory timing & speed,
Set M.2,
Turn off Compatibility mode in boot, (UEFI),
Turn on 4g in BOOT (for 980ti 6gigs of memory),
Save settings & reboot...

Usually I do not even get a reboot from the bios.
The board restarts, it seems to get partially through the bios boot, hangs then shuts down.
Reset and power button at this point become useless requiring me to power down from the PSU.
Sometimes after trying a couple times I can get to boot and into windows, at this point everything seems to work fine unless I 'Sleep' or attempt a 'Restart' in Win10, then need to shut off power to the PSU.
When the board will not boot, I usually have a 00 code.
Hibernate & Fast Start are disabled in WIn10.

Is this a voltage issue since all ram slots are filled?

I would love to get my machine stock stable AND able to sleep (to conserve power) but I fear I am overthinking everything at this point and need a voice grounded in reality to lend a hand.

Any suggestions on where to start and what to try would be greatly appreciated.
4,592 Views
11 REPLIES 11

Qwinn
Level 11
What is "Turn on 4G in BOOT"? I never had to do that (or even heard of it) and I have two 980tis.

Also, what power supply are you using?

As for setting memory timings and speed, are you using XMP settings?

Minsekt
Level 7
afaik above 4g decoding has to be disabled for your primary gpu anyway, 4g decoding does only have an effect on tesla graphiccards if i remember correctly, praz mentioned this in another thread. i leave it always at default, no problems with sli or vram, i can use all of my vram. maybe thats your problem?
its either that or your ram i guess, might be tricky with 64gb. maybe you have to increase vccsa.
did you tried it without setting your timings? at stock 2133mhz?


i would try it like that,

clear cmos, disable csm support, increase dram voltage by 25mv above the rated voltage, save settings and reboot. if this doesnt work increase system agent voltage in 25mv steps until it does.
maybe your bios isnt perfectly flashed too. did you tried another pen drive? this helped me too in the past. ive got weird qcodes, reflashed and its working fine without issues.

btw what qcode does your board show if it gets stuck? only 00?

I do have the boot issue at stock memory speeds (2133mhz).
I have not been using XMP settings after reading many posts recommending to manually set memory.
The Boot 4g setting was an option I added in an attempt at stable, I was unaware it was only needed for the Titan, I worried it was part of my issue with the 980ti having 6g of memory
My power supply is a Corsair AX1200I PSU.

Appreciate the help!

Any thoughts on amounts I should be applying to vccsa?

Arne_Saknussemm
Level 40
What BIOS were you on? If it was one with NVMe support already 13xx onwards then if I were you I would simply flash that BIOS again. You might still have it on BIOS 2? if so swap over to BIOS 2 and see if that runs smooth.

How did you update BIOS...maybe that you have a bad flash...download fresh file and flash again...BIOS flashback method.

BIOS updates are only worth it if you have a problem that is specifically addressed in an update. Or for compatibility with new gear etc. if nothing is wrong and everything works don't bother...there will be no performance improvement if your system is already working well...

The error code I have seen the most is 00. I have seen others but I'm pretty sure those were from me travelling down paths exacerbating my true issue (that I am still unsure of).

Adding a boost to my memory voltage and sys agent has allowed me to restart cleanly from the bios (without the boosts the bios would attempt to restart then hang resulting in a 00 code with either a reset or holding down the power button for 10+ seconds).

While this is an improvement, I do still have serious issues with sleep mode:
I can not ever wake the machine, usually when I tell the machine to sleep, it appears windows is going to sleep properly but shortly after the machine goes dark, 10-20 seconds, the machine attempts to wake on its own only to hang, reset/hard power reset results in 00 requiring me to shut down from the psu power button until I hear all voltage drain (marked by a speaker/subwoofer pulse). At this point the machine can reboot normally when powered on.

I have found many threads of the RVE having issues with sleep mode, the rare posts that mention possible solutions do not seem to make sense (bios memtest disabling etc).
Most are running in Win10 'Performance' mode, avoiding sleep/wake all together it seems.
I would hate to run this machine full power all the time, and saving tons of work to spend 30 minutes opening everything again for a lunch break is counterproductive.
Are others successfully using Win10 sleep mode with no issues?
Should I use 'Hibernate' mode or not with 'Sleep'?

Being an artist I am in over my head, this is my 2nd attempt with an 'extreme' proc and Asus board in a weak attempt to avoid a $20k Xeon based workstation, both high end Asus boards have left me feeling I should have pursued electrical engineering instead of art school. 😞

Thanks again for the guidance, have not given up yet and I am slightly more confident I can get there eventually.
(Losing confidence in your own tools is soul crushing)

In regards to my bios, I am currently using the latest for the RVE = 2001. (My board is the USB 3.1 version tho)

When my system was the most stable it was the default pre-installed bios (I have changed my bios so many times now I can not remember the original at this point).

My original issue (back when sleep appeared to work etc) was an SSD Raid 0 Boot setup consisting of 2 Evo 850's.
After the 2nd scare of the Raid 0 failing(?), I was terrified of losing alot of work so I cloned the boot drive to a single 950 Pro NVME ssd.

There was definitely an issue with my original bios regarding raid so even if I could remember which one it was I would not feel comfortable going back to it.

Minsekt
Level 7
theres a sticker somewhere on the board with the preinstalled bios version. for me it was 1501. ive had many problems with the board at the beginning. i had a 2666/2800 ram kit just like you, and had many qcodes, reboots, failed boots etc. with bios 1901 somehow the xmp profile used a bclk of 100 instead of 125 like all the bios versions before. but that didnt help either, i got so pissed and just purchased a 2400mhz kit which worked perfectly right out of the box, all problems where gone, no boot problems anymore. ironically this 2400mhz kit runs fine overclocked to 3000mhz 15-17-17-35-T2 @1.35v and 3000-15-15-15-35-T1 at 1.4v.
but no matter what i tried with the old kit, it just didnt work

maybe another kit will do better for you too? g.skill kits seems to work fine

Sticker on the mobo says my pre-installed bios was 1302.

My wallet would hate to replace the 64gig mem kit, especially considering this is already the 2nd kit (first was a 32gig kit that had the same issues).

Is sleep mode in Win10 really a rare achievement?
Just wondering if I am undertaking an uphill battle here.

i never put my system to sleep because i have 4 virtual machines running almost 24/7. its either on or i shut it down completely. i still use intel speedstep and adaptive voltage even tho im running almost all the time on high performance power plan. windows fast boot /hibernation/sleep is disabled on my system. bios fastboot disabled too.