Crosshair VI Hero: UEFI build update thread

[Syaoran]

@Syaoran - what helped me finally iron out the ram timings was the departure of using any of the presets or using the ram calculator. Left all the voltages as before and only changed all the ram timings to Auto. With the ram speed still at its desired setting, only changed the first four ram timings to their desired setting (for me 15-15-15-15) for Tras and Trc, I referred to the XMP settings as stated by Typhoon Burner in ns. Tras was listed at 19.876ns. My BCLK is set to 100.4. Therefore Tras calculated to ((1733x100.4) x .019875)/100 = 34.5878 so 35 was the new setting. Those were the only two ram timings that XMP was used as reference. The rest were provided by the bios except for TrdrdScl and TwrwrScl which I referred to the Stilt's values of 2. I may have lost a nit picky amount of bandwidth according to Aida64 but the latency went down from 65.6 (when using the presets) to 65.3 (using the new values). You may want to give this a try with the 3560 speed you were able to use before.

EDIT: After all was said and done, switched all the timing values, aside from the ones mentioned above, off of Auto to what the bios trained the ram at.

The BIOS training the RAM isn't so much of the issue. It's stability. I can boot into Windows at the old settings I used and even at 3,501 with things on auto. When testing the RAM though, it doesn't pass and in games that use a lot of memory, the system will blue screen.

[Red Core]

The BIOS training the RAM isn't so much of the issue. It's stability. I can boot into Windows at the old settings I used and even at 3,501 with things on auto. When testing the RAM though, it doesn't pass and in games that use a lot of memory, the system will blue screen.

I think you have to wait for the next stable bios release, so far i know companys, they fix problems for the most people first.
Means.. Ram which is above 3200 will be cared later than stability issues, misreading of temps, fix of OC bugs etc.
If you are lucky, they might work on it but as you can read on the Asus support page of the C6H under-> specs its unsupported by the mainboard.
So the priority of higher ram above 3200 is low, likely kindness if they fix it.

[Clouseau]

The BIOS training the RAM isn't so much of the issue. It's stability. I can boot into Windows at the old settings I used and even at 3,501 with things on auto. When testing the RAM though, it doesn't pass and in games that use a lot of memory, the system will blue screen.

The reason for the post was what ended up being a different approach that has garnered more stability than I had in the past. CLDO_VDDP along with the CAD Bus settings are all on Auto. The one thing that I noticed about all the timings, the most stable ones for me all shared the same tertiary timings except they all had Twrrd wrong. The bios provided the correct value. The slightly looser Trfc timings also added to needed stability; Tfaw as well. Was sharing what finally ironed out all the kinks in regards to stability for me in hopes the method may work for you and others as well. The only conversions needed was for Tras and Trc from the XMP profile unique to the flavor of ram being used. Keeping the timing in ns the same in regards to the desired operating speed.

[Waxinator]

Interesting indeed! Now thinking about additional heatsink 4 the chip. Maybe, it'll be useful.
By the way, which chip exactly? Currently too lazy 4 opening the case and searching fan area - evening...

It's the SUPER I/O chip in this picture. The chip is hidden under the plastic cover just bellow the graphic card slot.
A heatsink can't be fitted here, but a fan can ventilate the chip.

[mito1172]

3008 BIOS is not doing a cold boot ram 3200 MHz very good

[Red Core]

3008 BIOS is not doing a cold boot ram 3200 MHz very good

You can set the trc manually to 48.
Mine works at 3200 CL14 but each restart now it has problems with it, set it again up and it works.
Since thats annoying, i ve set it to 3140 CL14 and now it doesnt complain each start.

[mito1172]

You can set the trc manually to 48.
Mine works at 3200 CL14 but each restart now it has problems with it, set it again up and it works.
Since thats annoying, i ve set it to 3140 CL14 and now it doesnt complain each start.

standard ram profile no need to make any adjustments for me. no problem when you restart

[dAlexis]

It's the SUPER I/O chip in this picture. The chip is hidden under the plastic cover just bellow the graphic card slot.
A heatsink can't be fitted here, but a fan can ventilate the chip.

[Eaten by mice]

Thanks! Looking on the images, I understood, why the MB is working 4 me. CPU & GPU are liquid cooled, case is large, and it's not too hot in the area. But something with regular cooling...

By the way! The plastic can be easily cut after warranty period. Not steel indeed (I already made a large hole in metal, when moving a PSU in Fractal Design Node 304 NAS case) After hole in the plastic - thermal glue and heatsink is installed. The area is hot, but self-made heatsink may be long; 5-10 cm upper and the chip will be cool. Required piece of aluminium is not a problem 2 find.

P.S. placing such chip under plastic is NOT good indeed. It should be somewhere near post codes indicator.

[Waxinator]

Thanks! Looking on the images, I understood, why the MB is working 4 me. CPU & GPU are liquid cooled, case is large, and it's not too hot in the area. But something with regular cooling...

...[eaten by my cats]...

P.S. placing such chip under plastic is NOT good indeed. It should be somewhere near post codes indicator.

Thank you dAlexis for your feedback and comments about my findings !

[Red Core]

standard ram profile no need to make any adjustments for me. no problem when you restart

The XMP profile of my ram show CL14 @3000mhz 1.35V but i went above it.
It can reach 3200 with CL14 but at each restart it makes problems and need to set it up again.
So it works without any problems at 3140 CL14 which is above its max XMP clocks.
Also your ram is 8gb each ram stick, mine is 16gb each ram stick, of course your ram is made to reach higher clocks above 3200mhz.