Overclock.net - An Overclocking Community

Overclock.net - An Overclocking Community (https://www.overclock.net/forum/)
-   Intel CPUs (https://www.overclock.net/forum/5-intel-cpus/)
-   -   *Official* Intel DDR4 24/7 Memory Stability Thread (https://www.overclock.net/forum/5-intel-cpus/1569364-official-intel-ddr4-24-7-memory-stability-thread.html)

Silent Scone 08-13-2015 09:30 AM

*Official* Intel DDR4 24/7 Memory Stability Thread
Quote:
[UPDATE JAN 2018]

This thread now accepts Ram Test entries


Quote:
HOW TO USE

Get it from here, 9.99 euros / lifetime license:

https://www.karhusoftware.com/ramtest/

Configure the settings to your preference in the graphical user interface and
click the start button to begin testing. To stop testing, just click the same
button again.

It is recommended to run the test for at least 10 minutes before drawing any
conclusions about the stability of your system memory.


To detect intermittent memory errors you should let the test run for at least one hour.

Quote:
[UPDATE JAN 2017]

This thread will now also include results posted for the Z270 platform. However please try to remember the rules below to keep the discussion from becoming confusing, as what may work on one platform may not be viable on the other.



Quote:
[UPDATE JAN 2016]

This thread will now also include results posted for the X99 platform. However please try to remember the following to keep the discussion from becoming confusing, as what may work on one platform may not be viable on the other.



Please try to remember the following



Clarify what platform and CPU you are speaking about when asking a particular question or speaking about your experience.

Quote the user you are replying to when replying.

When posting stability results, be sure to include the CPU as described in the posting results instructions.

Happy posting! thumb.gif
Overview
This thread is dedicated to showing the various memory configurations of users with DDR4 on Z170/Z270 and X99 chipsets.
There is no strict criteria here, all things Z170/X99 memory overclocking welcome. However to enter the stability chart certain criteria is to be met as this is generally speaking dedicated to showing what is obtainable on both platforms at an operational level.


If using ASUS within North America you can post here:

ASUS North America Z170 Support / Q&A Thread
ASUS North America X99 Support / Q&A Thread
ASUS North America Z270 Support / Q&A Thread

Broadwell-E info:


Checkout the thermal control tool especially, this will be a god send for those who really want to push things.

How to get the best performance from Broadwell-E
http://edgeup.asus.com/2016/05/get-best-performance-broadwell-e-processors-asus-thermal-control-tool/


X99-Deluxe II build:
http://edgeup.asus.com/2016/05/x99-deluxe-ii-powers-prosumer-workstation-build/


X99-A II build:
http://edgeup.asus.com/2016/05/x99-ii-motherboard-sweet-spot-broadwell-e-vr-builds/


X99-Strix:
http://edgeup.asus.com/2016/05/the-rog-strix-x99-gaming-motherboard-illuminates-a-broadwell-e-gaming-build/


Rampage V Extreme Edition 10:
http://edgeup.asus.com/2016/05/introducing-rampage-v-edition-10/

Z270 info:
http://edgeup.asus.com/2017/01/03/z270-motherboard-guide/










ROG DRAM Timing Control Guide

Warning: Spoiler! (Click to show)
Quote:
Memory Presets: This is the place to start when overclocking memory. Identify the ICs used on the memory modules and select the relevant profile. We’ve put a tremendous amount of time configuring settings to get the most from each memory type. Once the profile is selected, various parameters in the DRAM timing section will be applied for you. From there, manual tweaking is possible as required.



Maximus Tweak: Leave on auto unless experiencing instability. Mode 1 may allow more compatibility, while Mode 2 is better for performance and some memory modules. Auto defaults to Mode 2.


Memory timings will automatically be offset according to memory module SPD and memory frequency. Should you wish to make manual adjustments, the primary settings and third timings are the most important for overall memory performance. Most timings are set in DRAM clock cycles, hence a lower value results in a more aggressive setting (unless otherwise stated).

As always, performance increases from memory tuning are marginal and are generally only noticeable during synthetic benchmarks. Either way, voltage adjustments to VDIMM, VCCIO-D, Cache Voltage and to a lesser extent CPU Core Voltage & VCCIO-A may be necessary to facilitate tighter timings.



Primary Timings

CAS: Column Address Strobe, defines the time it takes for data to be ready for burst after a read command is issued. As CAS factors in more transactions than other primary timings, it is considered to be the most important in relation to random memory read performance. (See third timing section for further info on important timings).

To calculate the actual time period denoted by the number of clock cycles set for CAS we can use the following formula:


tCAS in Nano seconds=(CAS*2000)/Memory Frequency


This same formula can be applied to all memory timings that are set in DRAM clock cycles.




DRAM RAS TO CAS Latency: Also known as tRCD. Defines the time it takes to complete a row access after an activate command is issued to a rank of memory. This timing is of secondary importance behind CAS as memory is divided into rows and columns (each row contains 1024 column addresses). Once a row has been accessed, multiple CAS requests can be sent to the row the read or write data. While a row is “open” it is referred to as an open page. Up to eight pages can be open at any one time on a rank (a rank is one side of a memory module) of memory.





DRAM RAS# PRE Time: Also known as tRP. Defines the number of DRAM clock cycles it takes to precharge a row after a page close command is issued in preparation for the next row access to the same physical bank. As multiple pages can be open on a rank before a page close command is issued the impact of tRP towards memory performance is not as prevalent as CAS or tRCD - although the impact does increase if multiple page open and close requests are sent to the same memory IC and to a lesser extent rank (there are 8 physical ICs per rank and only one page can be open per IC at a time, making up the total of 8 open pages per rank simultaneously).





DRAM RAS Active Time: Also known as tRAS. This setting defines the number of DRAM cycles that elapse before a precharge command can be issued. The minimum clock cycles tRAS should be set to is the sum of CAS+tRCD+tRTP.




DRAM Command Mode: Also known as Command Rate. Specifies the number of DRAM clock cycles that elapse between issuing commands to the DIMMs after a chip select. The impact of Command Rate on performance can vary. For example, if most of the data requested by the CPU is in the same row, the impact of Command Rate becomes negligible. If however the banks in a rank have no open pages, and multiple banks need to be opened on that rank or across ranks, the impact of Command Rate increases.


Most DRAM module densities will operate fine with a 1N Command Rate. Memory modules containing older DRAM IC types may however need a 2N Command Rate.

Latency Boundary A sets timings for the main set of Third timings, lower is faster and tighter.
Latency Boundary B sets timings for the secondary set of Third timings, lower is faster and tighter.

Manipulating Latency Boundary A and B, negates the need for setting third timings manually, unless granular control of an individual setting is required. For most users, we recommend tuning via the Latency Boundary settings. Advanced users who are tuning for Super Pi 32M may wish to set timings manually instead.

Latency Compensator when enabled tries to make opportunistic latency compensation that may increase performance or smoothen out the Memory training process. So try and compare overclocking and performance with it enabled and disabled. You can also trying enabling it when the whole system hangs at ‘55’ or ‘03’ or ‘69’ when pushing tight timings with high frequencies.





Secondary Timings



DRAM RAS to RAS Delay:Also known as tRRD (activate to activate delay). Specifies the number of DRAM clock cycles between consecutive Activate (ACT) commands to different banks of memory on the same physical rank. The minimum spacing allowed at the chipset level is 4 DRAM clocks.

DRAM Ref Cycle Time: Also known as tRFC. Specifies the number of DRAM clocks that must elapse before a command can be issued to the DIMMs after a DRAM cell refresh.


DRAM Refresh Interval: The charge stored in DRAM cells diminishes over time and must be refreshed to avoid losing data. tREFI specifies the maximum time that can elapse before all DRAM cells are refreshed. The value for tREFI is calculated according to module density. A higher number than default is more aggressive as the cells will be refreshed less frequently.

During a refresh, the memory is not available for read or write transactions. Setting the memory to refresh more often than required can impact scores negatively in memory sensitive benchmarks. It can be worth tweaking the refresh interval to a larger value for improved performance. For 24/7 use, this setting is best left at default, as real world applications do not benefit to a noticeable degree by increasing this value.








DRAM Write Recovery Time: Defines the number of clock cycles that must elapse between a memory write operation and a precharge command. Most DRAM configurations will operate with a setting of 9 clocks up to DDR3-2500. Change to 12~16 clocks if experiencing instability.


DRAM Read to Precharge Time: Also known as tRTP. Specifies the spacing between the issuing of a read command and tRP (Precharge) when a read is followed by a page close request. The minimum possible spacing is limited by DDR3 burst length which is 4 DRAM clocks.

Most 2GB memory modules will operate fine with a setting of 4~6 clocks up to speeds of DDR3-2000 (depending upon the number of DIMMs used in tandem). High performance 4GB DIMMs (DDR3-2000+) can handle a setting of 4 clocks provided you are running 8GB of memory in total and that the processor memory controller is capable.

If running 8GB DIMMs a setting below 6 clocks at speeds higher than DDR3-1600 may be unstable so increase as required.

DRAM Four Activate Window: Also known as tFAW. This timing specifies the number of DRAM clocks that must elapse before more than four Activate commands can be sent to the same rank. The minimum spacing is tRRD*4, and since we know that the minimum value of tRRD is 4 clocks, we know that the minimum internal value for tFAW at the chipset level is 16 DRAM clocks.


As the effects of tFAW spacing are only realised after four Activates to the same DIMM, the overall performance impact of tFAW is not large, however, benchmarks like Super Pi 32m can benefit by setting tFAW to the minimum possible value.


As with tRRD, setting tFAW below its lowest possible value will result in the memory controller reverting to the lowest possible value (16 DRAM clocks or tRRD * 4).


DRAM Write to Read Delay: Also known as tWTR. Sets the number of DRAM clocks to wait before issuing a read command after a write command. The minimum internal spacing is 4 clocks. As with tRTP this value may need to be increased according to memory density and memory frequency.


DRAM CKE Minimum Pulse width: This setting can be left on Auto for all overclocking. CKE defines the minimum number of clocks that must elapse before the system can transition from normal operating to low power state and vice versa.


CAS Write Latency: CWL is column access time for write commands to the DIMMs. Typically, CWL is needs to be set at or +1 over the read CAS value. High performance DIMMs can run CWL equal to or up to 3 clocks below read CAS for benchmarking (within functional limits of the DIMMs and chipset).
Quote:
Third Timings


On modern architectures like Haswell, page access is optimized such that back to back read timings in the third timing section can have a bigger impact on performance than primary settings. Memory interleaving and addressing optimization leads to the possibility of lots back to back read and writes (page hits) rather than random access (page misses).

In layman terms, the best way to describe this is to use the analogy of a hard drive. If data is fragmented, the head needs to move back and forth over the platter reading small bits of data. Similarly on memory, this would mean that CAS, wCL, tRCD, tRP and tRAS would factor more often - opening and closing memory pages across the DIMMs to read or write parts of data.


If data is not fragmented, the head can seek an area of the disc and read the data without needed to move back and forth. On a crude level, memory interleaving works in a similar way, ensuring that data is arranged into rows across ICs so that pages don't have to be open and closed as often to access it - this saves on excessive primary timing command requirements. That's why some of the back to back read and write timings in the third timing section of UEFI have a bigger impact on performance than the primary timings which were more important on older platforms.

If the required data is in sequence, CAS can be performed to access it and subsequent requests can be spaced by tRDRD (as low as 4 clocks). A lot of these requests can be sent before a page close request is required - which relies on the primary timing set (tRAS then tRP (tRC must elapse) followed by tRCD and then CAS). That's why the third timing spacing has more impact in memory sensitive benchmarks (memory frequency and other factors aside).


tRDRD: Sets the delay between consecutive read requests to the same page. From a performance perspective, this setting is best kept at 4 clocks. Relax only if the memory is not stable or the system will not POST. Very few memory modules can handle a setting of 4 clocks at speeds above DDR3-2400 so you may need to relax accordingly, although the performance hit may negate any gains in frequency.

tRDRD_dr: Sets the delay between consecutive read requests where the subsequent read is on a different rank. A setting of 6 clocks or higher is required for most DIMMs.

tRDRD (dd): Sets the delay between consecutive read requests where the subsequent read is on a different DIMM. A setting of 6 clocks or higher is required for most DIMMs.

tWRRD: Sets the delay between a write transaction and read command. The minimum value we recommend is tWCL+tWTR.

Auto is preferred from a stability perspective, while setting as close to the minimum value as possible is best from a performance perspective. For Super Pi 32m, try tWCl+tWTR+2 as a starting point. If that is stable, then try -1 clock, if not, add+1 and repeat until stable.

tWRRD_dr: Sets the delay between a write transaction and read command where the subsequent read is on a different rank. Keeping this setting as close to 4 clocks as possible is advised, although it will need to be relaxed to 6+ clocks at high operating frequency or when using high density memory configurations.

tWRRD_dd: Sets the delay between a write transaction and read command where the subsequent read is on a different DIMM. Keeping this setting as close to 4 clocks as possible is advised, although it will need to be relaxed to 6+ clocks at high operating frequency or when using high density memory configurations.








Dec_WRD: May give a small performance increase at speeds lower than DDR3-1600 with CAS 6. Can be left on Auto for all other use.

The following timings have a minimum spacing of Read CAS. The default rules space these settings well, so adjustment should not be required unless as a last resort. Setting equal to CAS is stressful on the DIMMs and IMC. Voltages may need to be increased to run the minimum value that POSTs.

tRDWR: Sets the delay from a read to a write transaction.

tRDWR_dr: Sets the delay from a read to a write transaction where the write is on a different rank.

tRDWR_dd: Sets the delay from a read to a write transaction where the write is on a different DIMM.


MISC

MRC Fast BOOT: When enabled, bypasses memory retraining on warm resets. Disabled retrains memory to counter any drift due to thermal changes. At higher memory frequencies the retraining process can interfere with system stability, hence this setting is enabled with auto by default. Should not need changing from Auto unless the system becomes unstable.

DRAM CLK Period: Allows the application of different memory timing settings than default for the operating frequency. Each number in the scale corresponds to a DRAM divider. The lowest setting being DDR3-800. Ordinarily, the timing set applied automatically tracks the DRAM ratio selected. This setting allows us to force timing sets from different dividers to be used with the selected DRAM ratio.

A setting of 14 is recommended for high DRAM operating frequencies. For all other use, leave on Auto.


Scrambler Setting: Alternates data patterns to minimize the impact of load transients and noise on the memory bus. A setting of optimized is recommended for most configurations.


DQ, DQS and CMD Sense Amplifier: Alters the bias on signal lines to avoid mis-reads. The Sense Amplifiers work good at Auto which lets BIOS decide the best for each. Reducing usually is better. Reducing DQ Sense and CMD Sense to -1~ -6 may stabilize things further when high VDIMM is used (2.2+v for example)




DRAM Swizzling Bit 0, 1 ,2, 3:

Enable Bit 0 for best OC most times, but disabling may help uncommon DRAM setups.

Enable Bit 1 for best OC most times, but disabling may sometimes help some 4GB DRAM modules.

Disabling Bit 2 helps high frequency overclocking at the expense of performance. Enabling improves performance but may need several tries to boot when frequencies are high and timings are tight. You can retry training when the system hangs at ‘55’ or ‘03’ or ‘69’ by pressing reset here and waiting for the rig to complete a full reset.
Enabling Bit 3 usually helps overclocking and stability unless the IMC is unstable at cold temperatures (Ln2 cooling) in which case try disabling.








RAW MHz Aid: May help to improve stability when using DRAM ratios above DDR3-3100 at the expense of performance.

IC Optimizer: IC Optimizer sets background invisible tweaks for the various DRAM ICs. Note that these were fine-tuned with specific DRAM and CPUs so it may help or harm depending on the likeness of the ones on your hands. So try with Auto first, then try with the one for your ICs and compare. These will get updated over time in future BIOSes.


For stability results, using the recommendations from [email protected] found below and in the overview seem the most requisite on recent platforms:

Quote:
Google stressapp test via Linux Mint (or another compatible Linux disti) is the best memory
stress test available. Google use this stress test to evaluate memory stability of their servers
– nothing more needs to be said about how valid that makes this as a stress test tool.


To bring up system info within Mint Terminal, type: sudo dmidecode type 17 and scroll to the relevant info.

For those who do not wish to install Mint to run Stressapp test:

HCI Memtest can be run via DOS or Windows. http://hcidesign.com/memtest/

An instance needs to be opened for each individual thread, covering a total of 90-95% of memory, giving the OS a little breathing room.

As an example i5 6600K - 8GB RAM

4 instances with 1750MB per instance.
Warning: Spoiler! (Click to show)

NOTE: Version 5.0 notes state that it's 30% faster than previous versions. For testing densities beyond 16GB - it's recommended you use 5.0 Pro.

http://hcidesign.com/memtest/




Stability Results

Please submit results with the following format.

GSAT Results
For sake of simplicity submitted results will only record primary timing sets, but feel free to show subsequent secondary and terts within screenshot.
Linux Mint's Stressapp test needs to be run for a minimum of 1 hour by typing stressapptest -W -s 3600 in the Terminal.
To take a screenshot in Terminal type: gnome-screenshot

HCI
HCI consider 1000% to be the 'golden standard' however for larger densities this can be time consuming. A minimal coverage of two laps (200%) is required to be added to the table for HCI for density over 16GB. 16GB or less requires a minimum of 4 laps (400%)


Example:

Silent Scone--i56600K @4.6/4.3---3000Mhz-C15-16-16-39-2T----1.37v---SA 1.05v---Stressapptest----1 Hour
Or
Silent Scone--i56600K @4.6/4.3---3000Mhz-C15-16-16-39-2T----1.37v---SA 1.05v---HCI 1500%

NOTE: This is not a leaderboard, as it is not a benchmark. This threads main purpose is to both discuss information and various results and to gauge what is possible between different configurations, DIMM capabilities and CPU samples. Results are welcome all the way up the frequency spectrum. If it's obtainable, it should be posted! smile.gif.

Should go without staying that general system and CPU stability should be gauged via the suggested means before attempting an outright memory stability test.

I will organise the results at some point (as well as post some of my own) this weekend and update whenever I get time smile.gif.






Have fun!

Shadowdane 08-13-2015 10:02 AM

Will have to keep an eye on this thread... looking to upgrade to Skylake, but haven't decided on a memory kit yet.

Sin0822 08-13-2015 10:12 AM

NVM, i saw it said memory stability thread! haha Memtest makes sense then.

Silent Scone 08-13-2015 10:31 AM

Quote:
Originally Posted by Sin0822 View Post

NVM, i saw it said memory stability thread! haha Memtest makes sense then.

Indeed lol. This is for people who've already established a reasonably stable overclock already via other suites such as Realbench, OCT and AIDA64 smile.gif

Z0eff 08-13-2015 11:45 PM

Subscribed, will be interesting to see what kind of results we end up with. smile.gif

Silent Scone 08-14-2015 07:54 AM

Silent Scone---6600K @4.6/4.3---3000Mhz-C15-16-16-39-1T----1.37v---SA 1.05v---HCI 1000%


llantant 08-14-2015 10:25 AM

Subbed. Will post when my stuff gets here biggrin.gif

Silent Scone 08-20-2015 03:43 AM

Guess there really is a stock shortage currently. redface.gif

[email protected] 08-20-2015 03:56 AM

GSkill Ripjaws V DDR4-3600 2 X 4GB kit at XMP defaults on Maximus VIII Hero:


2 hours of Stressapp pass:

llantant 08-20-2015 11:25 AM

Quote:
Originally Posted by [email protected] View Post

GSkill Ripjaws V DDR4-3600 2 X 4GB kit at XMP defaults on Maximus VIII Hero:


2 hours of Stressapp pass:

Nice nice. I cant wait to try this board out!

[email protected] 08-21-2015 01:44 AM

GSkill Ripjaws V DDR4-3600 2 X 4GB kit at XMP but CR1 set manually on Maximus VIII Hero (all default voltages):





Silent Scone 08-21-2015 02:23 AM

thumb.gif

[email protected] 08-21-2015 09:24 AM

Raja--i5-6700K @4.2/4.1---DDR4-3733-C18-19-47-1T----1.40v---SA Auto & IO Auto ---Stressapptest----2 Hours


Deders 08-27-2015 01:06 AM

Quote:
Originally Posted by [email protected] View Post

Raja--i5-6700K @4.2/4.1---DDR4-3733-C18-19-47-1T----1.40v---SA Auto & IO Auto ---Stressapptest----2 Hours

Does the SA and IO auto adjust on these boards like vcore? Wondering the same for LLC, someone said they got best results from leaving it on auto. I'm using the z170 Deluxe.

[email protected] 08-27-2015 01:07 AM

Quote:
Originally Posted by Deders View Post

Does the SA and IO auto adjust on these boards like vcore? Wondering the same for LLC, someone said they got best results from leaving it on auto. I'm using the z170 Deluxe.

Yep, Auto is "automatic".

Silent Scone 08-27-2015 02:19 AM

Quote:
Originally Posted by Deders View Post

Does the SA and IO auto adjust on these boards like vcore? Wondering the same for LLC, someone said they got best results from leaving it on auto. I'm using the z170 Deluxe.


I had no trouble dialling in 3000 and 3200 with auto, I set a lower manual system agent to see what I could get away with. If there's no instability whilst in auto there is no real reason to change this. Might need to play with it above these speeds though on some cpus, I've yet to try

seechay 08-27-2015 06:15 AM

I'm having issues posting on the stock XMP of my RAM. On reboots I sometimes get d0, but just restarting again I'll come boot fine after "Resetting my overclock settings by pressing F1." I haven't begun to overclock yet, because of this. Additionally my boot time is incredibly slow going through post. Anyone have any ideas? @[email protected]? I'm using 2 sets of F4-3000C15D-16GVR and the rest of my info is in my sig. When letting my bios auto adjust my ram, it sets it to 2133 with 1.2v. I just updated my bios to 0508 using the EZUpdate last night and it didn't change anything.

[email protected] 08-27-2015 06:20 AM

Quote:
Originally Posted by seechay View Post

I'm having issues posting on the stock XMP of my RAM. On reboots I sometimes get d0, but just restarting again I'll come boot fine after "Resetting my overclock settings by pressing F1." I haven't begun to overclock yet, because of this. Additionally my boot time is incredibly slow going through post. Anyone have any ideas? @[email protected]? I'm using 2 sets of F4-3000C15D-16GVR and the rest of my info is in my sig. When letting my bios auto adjust my ram, it sets it to 2133 with 1.2v. I just updated my bios to 0508 using the EZUpdate last night and it didn't change anything.


Two sets of DRAM is likely the issue. Remove one set. XMP is not made for two sets, it is made for one.

seechay 08-27-2015 06:54 AM

I'll try that out when I get home. If that's the case, can I just manually set the speed, timings and voltage to get it to work? Or do I need to get a quad channel kit?

[email protected] 08-27-2015 06:59 AM

Quote:
Originally Posted by seechay View Post

I'll try that out when I get home. If that's the case, can I just manually set the speed, timings and voltage to get it to work? Or do I need to get a quad channel kit?

You can try, but there are no promises it will work at the rated timings, frequency and voltage of a single kit. You may need to tune a lot to get both kits stable.

I would avoid 4 DIMM kits binned for X99 for similar purpose - look for a Z170 4 DIMM memory kit if you want a single kit.

Rubashka 08-27-2015 06:59 AM

sub

seechay 08-27-2015 07:07 AM

Quote:
Originally Posted by [email protected] View Post

You can try, but there are no promises it will work at the rated timings, frequency and voltage of a single kit. You may need to tune a lot to get both kits stable.

I would avoid 4 DIMM kits binned for X99 for similar purpose - look for a Z170 4 DIMM memory kit if you want a single kit.

Do you think this one would be fine? It's not in the QVL, but according to Newegg it's for Z170.

http://www.newegg.com/Product/Product.aspx?Item=N82E16820231903

[email protected] 08-27-2015 07:13 AM

Quote:
Originally Posted by seechay View Post

Do you think this one would be fine? It's not in the QVL, but according to Newegg it's for Z170.

http://www.newegg.com/Product/Product.aspx?Item=N82E16820231903

Difficult to say - at that type of density/freq it may not be plug and play. I dont have a kit like that here but will ask.

Strife21 08-27-2015 08:49 AM

Question on memory I am running some 2x8gb G.Skill Rip Jaws 4 (3000mhz) 15-15-15-35 @ 1.35v Model F4-3000C15D-16GRK. So memory works as advertised with command rate at 2 but won't post if I set it to 1. Is it worth it to change timings to try and get it to post at 1T? If so any suggestions what timings I should try? Or should I try and increase voltage instead? If so how how high is it to increase on skylake?

[email protected] 08-27-2015 08:53 AM

Not really an ASRock support guy - but you will likely need to set higher DRAM voltage and possibly VCCSA and IO.

Strife21 08-27-2015 09:03 AM

Quote:
Originally Posted by [email protected] View Post

Not really an ASRock support guy - but you will likely need to set higher DRAM voltage and possibly VCCSA and IO.

Yea I know haha. Just curious if you had any tips. I have always run my memory at stock so just a bit curious. Has a safe max voltage for dram been determined on skylake?

Silent Scone 08-27-2015 09:28 AM

Quote:
Originally Posted by [email protected] View Post

Not really an ASRock support guy - but you will likely need to set higher DRAM voltage and possibly VCCSA and IO.


How come?

biggrin.gif

[email protected] 08-27-2015 09:29 AM

M....u....s....t.....r...e...s...i...s....t....

Silent Scone 08-27-2015 10:52 AM

LOL, as my mother used to say if it's true one shouldn't take offence.

Someone has to keep food on the table in the fatal1ty house hold biggrin.gif

(Just kidding Asrock)

[email protected] 08-27-2015 11:48 PM

Quote:
Originally Posted by seechay View Post

Do you think this one would be fine? It's not in the QVL, but according to Newegg it's for Z170.

http://www.newegg.com/Product/Product.aspx?Item=N82E16820231903


GSKill tells me they have validated the kit on the Z170 DELUXE, MAXIMUS VIII HERO, and MAXIMUS VIII GENE

seechay 08-28-2015 05:14 AM

Quote:
Originally Posted by [email protected] View Post

GSKill tells me they have validated the kit on the Z170 DELUXE, MAXIMUS VIII HERO, and MAXIMUS VIII GENE

Thanks for the update smile.gif If I have issues I'll pick that kit up, but I've manually set the timings to 15-15-15-35-2N @ 1.35v and I haven't had any issues at all. I've been playing around with my OC and I'm stable at 4.6ghz with 1.3v adaptive. I'm working on cranking it up to 4.7 (but so far the temps are 75c, so more likely going to just lower the voltage on my 4.6). As far as the RAM goes, do you think I should attempt to drop my command rate to 1N? I haven't tried it yet, so not sure how it'll behave.

[email protected] 08-28-2015 05:20 AM

You can try that. May need to increase DRAM voltage and SA/IO voltages to get it stable.

Strife21 08-31-2015 10:24 AM

Raja,

I took back my ASrock z170 extreme 6 and purchased a Asus Asus MAximus VIII Hero. I am having some trouble with my memory thought. If I try and put my RAM G.Skill F4-3000C15D-16GRK 2x8gb at its xmp settings the computer fails to post. This memory is on the approved listed of RAM for the board. It does post at lower speeds though.

This ram worked perfectly fine in the Asrock board at its XMP and rated timings. Do you have any suggestions or know why it would not work?

[email protected] 08-31-2015 10:27 AM

Quote:
Originally Posted by Strife21 View Post

Raja,

I took back my ASrock z170 extreme 6 and purchased a Asus Asus MAximus VIII Hero. I am having some trouble with my memory thought. If I try and put my RAM G.Skill F4-3000C15D-16GRK 2x8gb at its xmp settings the computer fails to post. This memory is on the approved listed of RAM for the board. It does post at lower speeds though.

This ram worked perfectly fine in the Asrock board at its XMP and rated timings. Do you have any suggestions or know why it would not work?

Increase SA and IO voltage.

Praz 08-31-2015 10:28 AM

Quote:
Originally Posted by Strife21 View Post

Raja,

I took back my ASrock z170 extreme 6 and purchased a Asus Asus MAximus VIII Hero. I am having some trouble with my memory thought. If I try and put my RAM G.Skill F4-3000C15D-16GRK 2x8gb at its xmp settings the computer fails to post. This memory is on the approved listed of RAM for the board. It does post at lower speeds though.

This ram worked perfectly fine in the Asrock board at its XMP and rated timings. Do you have any suggestions or know why it would not work?

Hello

X99 memory will most times need tuning by hand for XMP settings. Try increasing memory, SA and/or IO voltage a bit. If that fails Instead of XMP try setting the 4 primary timings, speed and voltage manually.

Strife21 08-31-2015 10:30 AM

Quote:
Originally Posted by [email protected] View Post

Increase SA and IO voltage.

Can you recommend a safe voltage to use for these two settings?

[email protected] 08-31-2015 10:32 AM

Quote:
Originally Posted by Strife21 View Post

Can you recommend a safe voltage to use for these two settings?

There is a 6700K OC overview in the ASUS Z170 Q&A thread. I use up to 1.30V for both - tho you should not need that much at the clocks you are running.

Strife21 08-31-2015 10:35 AM

Do you have a link to that thread by any chance?

[email protected] 08-31-2015 10:38 AM

Will do one better and teach you how to fish: Click on the down arrow next to my user name then "threads started", that will list them all

Strife21 08-31-2015 10:59 AM

So I increased the system agent to 1.20 and the VCCIO to 1.15 and it seems to have done the trick.

Strife21 08-31-2015 11:00 AM

Quote:
Originally Posted by [email protected] View Post

Will do one better and teach you how to fish: Click on the down arrow next to my user name then "threads started", that will list them all

Thanks for the tip, kinda new to the forums. Didn't realize you could do that. The quality of this board is fantastic.

[email protected] 08-31-2015 11:02 AM

Quote:
Originally Posted by Strife21 View Post

So I increased the system agent to 1.20 and the VCCIO to 1.15 and it seems to have done the trick.

Nice.

Scoundrel 08-31-2015 01:06 PM

It would be extremely helpfull if someone could make an ISO availabe with NIC drivers embedded and maybe even the stressapp test installed as well.
I got as far as booting mint from an USB drive...but no internet connectivity and no Linux knowledge makes this a bit hard to deal with. redface.gif

[email protected] 08-31-2015 01:35 PM

Mint has embedded drivers that work on the Intel NICs of ASUS boards - works fine on my side.

Scoundrel 08-31-2015 01:47 PM

Quote:
Originally Posted by [email protected] View Post

Mint has embedded drivers that work on the Intel NICs of ASUS boards - works fine on my side.

I have a Hero VIII, so i should be fine i guess....wierdly i dont see any NIC's and it says "no internet connection" maybe just using rufus to create a bootable USB of the Cinnamon 64 bit ISO is not the right way to do it?

[email protected] 08-31-2015 02:20 PM

Quote:
Originally Posted by Scoundrel View Post

I have a Hero VIII, so i should be fine i guess....wierdly i dont see any NIC's and it says "no internet connection" maybe just using rufus to create a bootable USB of the Cinnamon 64 bit ISO is not the right way to do it?

I install to a hard drive and plug in the ethernet cable. That works for me.

AndreK 08-31-2015 02:25 PM

I also have problems with the internet connection, i used linux 17.2 cinnamon and mate.
Edit: MIII Ranger

There are not so many testresults here.
Should i test my Kingston HyperX Fury DDR4 2666 8GB?
I was reading it has Hynix chips.
I'm planning to overclock it to 3000MHz with 1,35V but i'm not in a hurry myself smile.gif

Scoundrel 08-31-2015 02:28 PM

Quote:
Originally Posted by [email protected] View Post

I install to a hard drive and plug in the ethernet cable. That works for me.

Ahh ok thanks thumb.gif,
I thought everybody just USB or DVD booted these Linux OS'es...I'll try installing it on a harddrive then.smile.gif

[email protected] 08-31-2015 02:38 PM

If you can't get it to work use Windows and HCI instead.

Strife21 08-31-2015 03:46 PM

So I spoke too soon the the voltages seemed to help it post for a bit then got failed posts again. Dropped it down to 2800 from 3000 everything works fine.

I tried Dram voltage from 1.36v to 1.38v
VCCIO from 1.12v-1.20v
SysAgent from 1.12v-1.25v

Manually entered the timings and stuff too. I guess as good as I am going to get on this kit is 2800 even though it was working another board find at 3000. However this board is much better so, I'll take it.

NerfedZombie 08-31-2015 06:37 PM

Why not include some undervolted DDR3 sticks?

Shadowdane 08-31-2015 07:27 PM

Quote:
Originally Posted by Strife21 View Post

So I spoke too soon the the voltages seemed to help it post for a bit then got failed posts again. Dropped it down to 2800 from 3000 everything works fine.

I tried Dram voltage from 1.36v to 1.38v
VCCIO from 1.12v-1.20v
SysAgent from 1.12v-1.25v

Manually entered the timings and stuff too. I guess as good as I am going to get on this kit is 2800 even though it was working another board find at 3000. However this board is much better so, I'll take it.


What timings are you running for DDR4-2800?
I bought a G.Skill kit which runs at 15-15-15-35 @ 1.25v, I'm hoping I can tighten the timings to Cas 13 or 14 if I run them at 1.3 to 1.35v.

Still waiting on my CPU to arrive, so no idea when I'll be able to test that.

[email protected] 09-01-2015 01:26 AM

Quote:
Originally Posted by Strife21 View Post

So I spoke too soon the the voltages seemed to help it post for a bit then got failed posts again. Dropped it down to 2800 from 3000 everything works fine.

I tried Dram voltage from 1.36v to 1.38v
VCCIO from 1.12v-1.20v
SysAgent from 1.12v-1.25v

Manually entered the timings and stuff too. I guess as good as I am going to get on this kit is 2800 even though it was working another board find at 3000. However this board is much better so, I'll take it.


Try Maximus Tweak Mode 1 in the DRAM timing page with the elevated SA and IO voltages.

Strife21 09-01-2015 08:18 PM

Quote:
Originally Posted by [email protected] View Post

Try Maximus Tweak Mode 1 in the DRAM timing page with the elevated SA and IO voltages.

Well this has worked after extensive testing before I posted. Mode 1 in the dram timings page has let this memory run at its rated speeds and timings with no issues. With it enabled I can even leave the vccio and sys agent on auto and still have stability.

Thanks man.

Strife21 09-01-2015 08:19 PM

Quote:
Originally Posted by Shadowdane View Post

What timings are you running for DDR4-2800?
I bought a G.Skill kit which runs at 15-15-15-35 @ 1.25v, I'm hoping I can tighten the timings to Cas 13 or 14 if I run them at 1.3 to 1.35v.

Still waiting on my CPU to arrive, so no idea when I'll be able to test that.

I was running the timings you have listed but at 1.35v. tweak settings mode 1 has resolved my issues tho.

[email protected] 09-02-2015 12:49 AM

Tweak Mode 1 uses a less aggressive set of memory sub-timings.

Scoundrel 09-02-2015 01:42 AM

Quote:
Originally Posted by [email protected] View Post

Tweak Mode 1 uses a less aggressive set of memory sub-timings.

Would you also recommend these ASUS Tweak Modes when overclocking memory, lets say overclocking DDR4 3200 to reach 3600mhz, or is VCCIO and SA more relevant if the memory works fine at XMP settings on their default rated speeds?

[email protected] 09-02-2015 01:49 AM

Quote:
Originally Posted by Scoundrel View Post

Would you also recommend these ASUS Tweak Modes when overclocking memory, lets say overclocking DDR4 3200 to reach 3600mhz, or is VCCIO and SA more relevant if the memory works fine at XMP settings on their default rated speeds?

You will need to experiment to find out what helps more to stabilize the system. Could be one, the other, or both.

Scoundrel 09-02-2015 02:02 AM

Quote:
Originally Posted by [email protected] View Post

You will need to experiment to find out what helps more to stabilize the system. Could be one, the other, or both.

I was just thinking that increasing the crazy-confusing sub-timings below the more common 16-18-18-36 -T2 timings would be nessesary pretty fast after increasing the clock speeds just a little bit.
I have tried just tinkering with speed by increasing DRAM Voltage @ 1.4v VCCIO @ 1.3v and SA @1.25v but my memory crapped out shortly after 3333mhz so i didnt bother at all after that. These Tweak modes might just be what takes me beyond 3500mhz.

cookiesowns 09-02-2015 02:08 AM

Where's the one for X99 confused.gif

[email protected] 09-02-2015 02:10 AM

Feel free to start one, the info in the first post is not proprietary. However, there are only two of us on the forum that understand memory timings and we cannot be in all places at once or answer everything as people would like us to.

Silent Scone 09-02-2015 02:39 AM

Quote:
Originally Posted by cookiesowns View Post

Where's the one for X99 confused.gif


I didn't feel the thread would serve it's purpose as well if it was platform agnostic, it would have been possible to add in other platforms but then that could have created congestion with results and confusion. Maybe we can add in X99..., but I draw the line at DDR4 smile.gif

Praz 09-02-2015 06:42 AM

Hello

Based on the first post, quoted below, Skylake only would be keeping with the intent of the thread. The DDR4 architecture is the only common link between X99 and Skylake. There is no comparison value as far as what may be optimal regarding obtainable speeds, timings or performance across the two platforms.

Quote:
Originally Posted by Silent Scone View Post

This threads main purpose is to both discuss information and various results and to gauge what is possible between different configurations, DIMM capabilities and CPU samples. Results are welcome all the way up the frequency spectrum. If it's obtainable, it should be posted! smile.gif.

Silent Scone 09-02-2015 06:55 AM

Yes, even with the use of a separate sheet I do not think there would be much benefit for X99 at this stage in the platforms life given there are plenty of results for people to gauge what is reasonable. Keeping the thread proprietary means that all discussion is kept to Skylake which hopefully will make it easier for people to digest looking for information

sauced 09-02-2015 09:18 AM

So I've had some interesting findings with trying to get XMP working on my DD4 3200 corsair set with a Asus Z170-A motherboard.

When I first built the PC I had to up the SA and IO voltage to get it to post with XMP to 1.25 SA and 1.20 IO.

After awhile I tried lowering the voltages after seeing someone killed their 6700k somehow and it seemed to be memory controller related.

It would be unstable with auto/lower voltage than 1.25SA and 1.20IO with the XMP profile enabled.

Though the system was stable at higher voltages, my USB sound DAC was dropping sound like crazy. Every three seconds in games the audio would cut out and distort, come back and cut out and distort again. If I switched to onboard realtek sound I would get loud popping and extreme distortion after about 30 minutes of gaming.

I found last night when I lowered the SA and IO voltages the system wasn't stable but the USB DAC sound issues were gone and played all sound without a hitch. Turned the voltage back up and the cutting out and distorted sound came right back.

I found a beta bios update for my board yesterday that I upgraded to and it seems to have fixed all the problems.

Z170-A BIOS 0901
1.Update Intel ME version to 1168
2.Enhance DDR4 compatibility

After the upgrade I was able to turn SA and IO voltage back to Auto and I passed 4 hours of realbench and 4 hours of HCI memtest flawlessly with XMP on. Before the bios update the system would crash with XMP on at auto voltage. Sound is perfect now too.

So if you're getting audio issues and have added voltage to SA or IO that could be your issue.

Silent Scone 09-02-2015 09:34 AM

Quote:
Originally Posted by sauced View Post

So I've had some interesting findings with trying to get XMP working on my DD4 3200 corsair set with a Asus Z170-A motherboard.

When I first built the PC I had to up the SA and IO voltage to get it to post with XMP to 1.25 SA and 1.20 IO.

After awhile I tried lowering the voltages after seeing someone killed their 6700k somehow and it seemed to be memory controller related.

The System Agent voltage should be fine within 1.3v. I'd be interested to see how someone managed to conclude the CPU failure was memory controller related, and how much voltage was being applied throughout the system. Can't really comment on the audio issues vicariously, seems odd

Derp 09-02-2015 11:02 AM

Can anyone comment on how much better the Google Stress App is at detecting instability compared to HCI memtest? I have used the free version of HCI for years and found it much better than memtest86. I don't have anything to boot Linux from atm but I can go pick something up if this test is clearly superior.

[email protected] 09-02-2015 11:27 AM

Quote:
Originally Posted by Derp View Post

Can anyone comment on how much better the Google Stress App is at detecting instability compared to HCI memtest? I have used the free version of HCI for years and found it much better than memtest86. I don't have anything to boot Linux from atm but I can go pick something up if this test is clearly superior.

Stressapp is more stressful than HCI for testing memory alone. HCI's load is a bit more spread to the cache, while Stressapp is more memory bus isolating. They both have their use, but if testing memory alone, then Stressapp is a quicker way of finding errors.

Silent Scone 09-02-2015 11:58 AM

Yep, around 1500% pass will take you substantially longer than running stressapp

[email protected] 09-03-2015 08:10 AM

Maximus VIII Extreme

Raja--6700K @4.8/4.8---DDR4-3733-C18-19-47-1T----1.40v---SA Auto & IO Auto ---Stressapptest----2 Hours and 1000% HCI pass:

14C water temp.





Silent Scone 09-03-2015 08:16 AM

mmm. Appetising biggrin.gif.

[EDIT]

Ignore previous, I read that as 1.4V SA lol. Will have some different results to post later in the week

FiShBuRn 09-05-2015 06:33 PM

FiShBuRn--i7-6700K @4.6/4.2---3200Mhz-C15-17-17-35-1T----1.35v---SA Auto & IO Auto---HCI 2900%


Silent Scone 09-06-2015 09:58 AM

thumb.gif

Shadowdane 09-06-2015 12:56 PM

i7-6700K @ 4.4Ghz (~1.23v) - DDR4-2800 14-14-14-34-1T @ 1.35v






I bet I can get the timings lower on these, will have to see if they can do Cas 13. smile.gif

Silent Scone 09-06-2015 02:24 PM

Quote:
Originally Posted by Shadowdane View Post

i7-6700K @ 4.4Ghz (~1.23v) - DDR4-2800 14-14-14-34-1T @ 1.35v






I bet I can get the timings lower on these, will have to see if they can do Cas 13. smile.gif

You've got a bit of headroom voltage wise so shouldn't be too difficult smile.gif. Only 600% coverage in the screenshot though wink.gif

Praz 09-06-2015 02:34 PM

Quote:
Originally Posted by Shadowdane View Post

i7-6700K @ 4.4Ghz (~1.23v) - DDR4-2800 14-14-14-34-1T @ 1.35v
Warning: Spoiler! (Click to show)




I bet I can get the timings lower on these, will have to see if they can do Cas 13. smile.gif

Hello

For 16GB the amount of memory being used per instance needs to be increased. Total memory allocated for HCI between 90% and 95% of available memory.

Silent Scone 09-06-2015 03:27 PM

Well spotted, this too. No point in only allocating half available memory to test. Defeats the very purpose

Silent Scone 09-08-2015 04:42 AM

https://www.overclockers.co.uk/showproduct.php?prodid=MY-457-CS&groupid=701&catid=8&subcat=2556

Reasonably priced LPX kit.

http://www.corsair.com/en-us/vengeance-lpx-8gb-2x4gb-ddr4-dram-3600mhz-c18-memory-kit-black-cmk8gx4m2b3600c18

Advil000 09-08-2015 09:37 PM

Raja,

As you may not be monitoring all threads here, I just noticed the Maximus Ranger VIII doesn't the Maximus Tweak option in Dram Timings. No "Mode 1" option.

[email protected] 09-09-2015 01:35 AM

Quote:
Originally Posted by Advil000 View Post

Raja,

As you may not be monitoring all threads here, I just noticed the Maximus Ranger VIII doesn't the Maximus Tweak option in Dram Timings. No "Mode 1" option.

Set tRFC to 390 manually and see if that helps.

If not set the following:

trdrd_dr 7
trdwr_dr 11
twrrd_dr 9
twrrd_dd 9


-Raja

[email protected] 09-09-2015 07:05 AM

Maximus VIII Extreme i7-6700K DDR4-3200 4 DIMM (16GB) Corsair Vengeance LPX at XMP (default settings)





Silent Scone 09-09-2015 07:23 AM

https://www.overclockers.co.uk/showproduct.php?prodid=MY-067-TG

These might be worth a look

Advil000 09-10-2015 08:54 PM

Quote:
Originally Posted by [email protected] View Post

Set tRFC to 390 manually and see if that helps.

If not set the following:

trdrd_dr 7
trdwr_dr 11
twrrd_dr 9
twrrd_dd 9


-Raja

Still no dice. Still no post at all above 2700. Didn't improve anything. But it was something to try. Any more ideas?

[email protected] 09-11-2015 12:29 AM

Quote:
Originally Posted by Advil000 View Post

Still no dice. Still no post at all above 2700. Didn't improve anything. But it was something to try. Any more ideas?

Keep all settings above and increase SA and IO voltage.

Silent Scone 09-12-2015 02:50 AM

Would we (royal we, Raja Praz) say that Stressapp is strained more with or without software rendering mode? Or maybe closer to the truth it really doesn't matter

cookiesowns 09-12-2015 03:10 AM

Quote:
Originally Posted by Silent Scone View Post

Would we (royal we, Raja Praz) say that Stressapp is strained more with or without software rendering mode? Or maybe closer to the truth it really doesn't matter

If anything its less strained due to software rendering mode hogging CPU cycles to allow stressapp to run my calculations.. But what do I know.

All I know is, if I have nvidia drivers I can browse da web while stressapping.

[email protected] 09-12-2015 04:43 AM

Quote:
Originally Posted by Silent Scone View Post

Would we (royal we, Raja Praz) say that Stressapp is strained more with or without software rendering mode? Or maybe closer to the truth it really doesn't matter

I would not be too concerned about this either way.

Silent Scone 09-12-2015 04:58 AM

That was my feeling on it but being pretty much alien to the OS thought best to ask

Praz 09-12-2015 06:52 AM

Quote:
Originally Posted by Silent Scone View Post

Would we (royal we, Raja Praz) say that Stressapp is strained more with or without software rendering mode? Or maybe closer to the truth it really doesn't matter

Hello

I have not seen any difference either way. I think this is both due to a minimal graphics load with the default Mint install as well as how good the stress test is at isolating the memory testing from the other subcomponents

cookiesowns 09-12-2015 07:53 PM

Quote:
Originally Posted by Praz View Post

Hello

I have not seen any difference either way. I think this is both due to a minimal graphics load with the default Mint install as well as how good the stress test is at isolating the memory testing from the other subcomponents


For comparison, I get around 20-30% graphics load, if I had a stressapp terminal window open, htop running, as well as xsensors open. If the nvidia drivers are loaded, its only 2-5%.

llantant 09-14-2015 02:23 AM

I ran hci memtest at Xmp settings 3200 16 16 18 2t.

It passed about 800% when I went to sleep but I woke up and it had crashed sometime during the night.

I take it that it's not stable.

I upped vccio and SA from auto (1.16 In bios) to 1.16 1 notch from 1.15 (showing 1.2 in bios) and am testing again.

Is this correct?

What I also notice is even thought I have ram set to 1.35 in bios it is showing next to it as 1.344. If I up the voltage to 1.36v it shows as 1.36v

llantant 09-14-2015 02:45 AM

also is it possible for memtest to crash from not enough vcore?

Also I tried to download Linux mint to use googlestressapp. I downloaded cinnamon the top one in the list but when I boot into it I cannot get online?? My internet won't work. How do I set up a network connection?

Silent Scone 09-14-2015 03:04 AM

Quote:
Originally Posted by llantant View Post

also is it possible for memtest to crash from not enough vcore?

Also I tried to download Linux mint to use googlestressapp. I downloaded cinnamon the top one in the list but when I boot into it I cannot get online?? My internet won't work. How do I set up a network connection?


it's possible to get an exception code with HCI, but if it's memory related it should happen really before 800% coverage. As mentioned in OP make sure to test general system stability before attempting HCI pass - leave uncore at defaults and either decrease your core multiplier by 10 or increase vcore by 20mv. System Agent and IO voltages should be fine in auto on most CPU at that DRAM frequency.

Use bluescreen viewer to see what exception code occurred:

http://www.nirsoft.net/utils/blue_screen_view.html

llantant 09-14-2015 03:27 AM

Quote:
Originally Posted by Silent Scone View Post

it's possible to get an exception code with HCI, but if it's memory related it should happen really before 800% coverage. As mentioned in OP make sure to test general system stability before attempting HCI pass - leave uncore at defaults and either decrease your core multiplier by 10 or increase vcore by 20mv. System Agent and IO voltages should be fine in auto on most CPU at that DRAM frequency.

Use bluescreen viewer to see what exception code occurred:

http://www.nirsoft.net/utils/blue_screen_view.html

Brilliant will try when I get back.

I've passed real bench 8 hours and 4 hours of aida64, 30 loops of x264, plus multiple x275 4k encodes on overkill x4 at 4.7 core and 4.4 core at 1.335v. I do however need 1.365v in order to pass the latest version prime small fft.

Anything lower results in rounding error on thread 3 every time.

I left it with the former vcore 1.335 as I figured prime seemed a bit too stressful and hci memtest was one of my final runs.

I'll download the bsod viewer later because windows 10 doesn't pop the code when it reboots mad.gif

Core multiplier is at 47.

I had Xmp enabled. Am I ok just to input the timings and voltage myself?

Silent Scone 09-14-2015 04:56 AM

Quote:
Originally Posted by llantant View Post

Brilliant will try when I get back.

I've passed real bench 8 hours and 4 hours of aida64, 30 loops of x264, plus multiple x275 4k encodes on overkill x4 at 4.7 core and 4.4 core at 1.335v. I do however need 1.365v in order to pass the latest version prime small fft.

Anything lower results in rounding error on thread 3 every time.

I left it with the former vcore 1.335 as I figured prime seemed a bit too stressful and hci memtest was one of my final runs.

I'll download the bsod viewer later because windows 10 doesn't pop the code when it reboots mad.gif

Core multiplier is at 47.

I had Xmp enabled. Am I ok just to input the timings and voltage myself?

I would have thought 8 hours RB to be enough. Make sure you don't have more than one monitoring application open, and if on NVIDIA close Afterburner if using this. When running HCI this can cause a polling collision of sorts which can cause instability

llantant 09-14-2015 05:44 AM

Quote:
Originally Posted by Silent Scone View Post

i WOULD HAVE
I would have thought 8 hours RB to be enough. Make sure you don't have more than one monitoring application open, and if on NVIDIA close Afterburner if using this. When running HCI this can cause a polling collision of sorts which can cause instability

Closed steam, precision x etc. I will retry tonight. thumb.gif

Is the setting in bios that's showing 1.344v still ok even though I have 1.35 set. The first skylake I built said ram was at 1.36 even though it was exact same ram and mobo and set at 1.35




It crashed at 6.25! That means it would have been going for 10 Hours. So can I ignore it?

Silent Scone 09-14-2015 06:17 AM

No, not ignore. Likely still caused by instability. Retest and see if you can replicate it. This code implies the memory is probably unstable. Do as suggested in my first post regarding reducing multiplier or increasing vcore, come back if you receive the code again at any point.

Too early in my own experience to know whether System Agent might be to blame, but auto ruling has worked perfectly fine on my sample so far.

seechay 09-14-2015 08:23 PM

Quote:
Originally Posted by seechay View Post

Thanks for the update smile.gif If I have issues I'll pick that kit up, but I've manually set the timings to 15-15-15-35-2N @ 1.35v and I haven't had any issues at all. I've been playing around with my OC and I'm stable at 4.6ghz with 1.3v adaptive. I'm working on cranking it up to 4.7 (but so far the temps are 75c, so more likely going to just lower the voltage on my 4.6). As far as the RAM goes, do you think I should attempt to drop my command rate to 1N? I haven't tried it yet, so not sure how it'll behave.

@[email protected] I got my ram issues fixed. I just updated my bios to 802 and enabled XMP. Now I have both dual channel stable at XMP biggrin.gif

llantant 09-15-2015 08:54 AM

Copied from my post on the overclock thread:

I am still getting issue with my ram on XMP settings, I know my core/cache voltage is fine. What is happening is im failing memtest around the 1000% percent mark. I have ram at 3200 16 18 18 36 2T and 1.35v as it says in XMP.

I do notice that my dram voltage in bios says 1.344 instead of 1.35. Are there any other things I can do to stabilize this ram. I knew i shouldn't have got corsair. Sooner I can find some G Skill in the uk the better.

Im getting these http://www.gskill.com/en/product/f4-3200c16d-16gvk as soon as I can find some. Never liked corsair ram, just had no choice.

Also how the hell do i run linux mint. I flashed to usb and booted in but I have no internet to download the stressapp. Id rather use that over 2 hours before doing another memtest for 8 hours!!!!

Also I have ram dram capability set to 130%

Silent Scone 09-15-2015 09:16 AM

The voltage variation is normal, all software polling should be taken with many a granule of salt. Increase DRAM voltage to 1.37v and see if the problem persists.

As for Mint, try typing this into terminal: sudo apt-get install stressapptest


All times are GMT -7. The time now is 01:23 PM.

Powered by vBulletin® Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.

User Alert System provided by Advanced User Tagging (Pro) - vBulletin Mods & Addons Copyright © 2020 DragonByte Technologies Ltd.
vBulletin Security provided by vBSecurity (Pro) - vBulletin Mods & Addons Copyright © 2020 DragonByte Technologies Ltd.

vBulletin Optimisation provided by vB Optimise (Pro) - vBulletin Mods & Addons Copyright © 2020 DragonByte Technologies Ltd.