Overclock.net › Forums › Intel › Intel CPUs › *Official* Intel DDR4 24/7 Memory Stability Thread
New Posts  All Forums:Forum Nav:

*Official* Intel DDR4 24/7 Memory Stability Thread - Page 40

post #391 of 4906
Thread Starter 
Quote:
Originally Posted by JnLoader View Post

Thats it for tweaking mem timings for me!

I just started Ocing my GPU (GTX 970) after what I though was a stable CPU overclock. When starting Ocing the gpu it wouldent take much to have it fail, say 50 mhz over stock = 100hz as it's DDR in XXX
And Ocing the mem was a no deal. So after thinking what a crappy GPU, I just for teh sake of it set my CPU Oc to stock, and voila it would overclock like crazy, on bothe the Core and Memory!

So guess what, it was the damn memory timings that was the problem, I mean the RAM of course. I set it back to the loose stock timings 16 - 18 -18 - 36. And voila again.
I even tried give the Ram more Voltage, and let the mobo take care of it. Even set my IO / SA at Auto.

Nothing was helping, only just loosing up the ram timings. And in every stresstest program it went smooth, but when Ocing the GPU it wen staight ot he..!
I am very disapointed. I have never heard of how that could make Ocing the GPU almost impossible.

So if I want to be able to O/C my GPU I just have to use very loose timings mad.gif

I guess many would have though, well first we o/c the cpu/ram and when it's stable you go on to the GPU, thats what I have allways done before.
This seems really crazy dont you think ?

It would be really good if Raija@Asus could helt us with a Memory Timings Guide or something smile.gif


Honestly no idea where you went wrong there. Depends on what stress tests you used to test the memory, likely wasn't ever stable. Unstable cache and memory can cause TDR events
post #392 of 4906
Quote:
Originally Posted by Silent Scone View Post

Honestly no idea where you went wrong there. Depends on what stress tests you used to test the memory, likely wasn't ever stable. Unstable cache and memory can cause TDR events

I see, and I have not o/c the cache, it set at 100hz. I even lowered the SA to 800Hz, it doesent help eaiter!

Well I dont know what to do, I guess I have to keep trying and learning guys.

And as allways, thanks for your input thumb.gif
JxLoader
(15 items)
 
  
CPUMotherboardGraphicsRAM
Intel i5-6600K @4.5ghz ASUS Z170 PRO GAMING ASUS GeForce GTX 970 4GB TURBO HyperX Fury DDR4 2133MHz - 2X8GB 
Hard DriveCoolingOSMonitor
Kingston SSDNow V300 240GB Be Quiet Pure Rock Win10 - Pro Acer Predator XB270HUDbmiprz TN 27 - 1440P G-Sync 
KeyboardPowerCaseMouse
Roccat - Isku Corsair RM750X Fractal Design R5 ROCCAT Kova 2016 
Mouse PadAudioOther
ROCCAT - Taito 2017 Integrated FX crap - For now :) Kingston HyperX Cloud II - USB Audio 
  hide details  
Reply
JxLoader
(15 items)
 
  
CPUMotherboardGraphicsRAM
Intel i5-6600K @4.5ghz ASUS Z170 PRO GAMING ASUS GeForce GTX 970 4GB TURBO HyperX Fury DDR4 2133MHz - 2X8GB 
Hard DriveCoolingOSMonitor
Kingston SSDNow V300 240GB Be Quiet Pure Rock Win10 - Pro Acer Predator XB270HUDbmiprz TN 27 - 1440P G-Sync 
KeyboardPowerCaseMouse
Roccat - Isku Corsair RM750X Fractal Design R5 ROCCAT Kova 2016 
Mouse PadAudioOther
ROCCAT - Taito 2017 Integrated FX crap - For now :) Kingston HyperX Cloud II - USB Audio 
  hide details  
Reply
post #393 of 4906


It worked, BCLK being weird, going to jump into the BIOS to fix that. How acceptable is this?

*If you're trying to do this stuff in a VM, make sure to leave a few gigs free for the host OS, otherwise you end up getting segmentation faults.
post #394 of 4906
Thread Starter 
Quote:
Originally Posted by JnLoader View Post

I see, and I have not o/c the cache, it set at 100hz. I even lowered the SA to 800Hz, it doesent help eaiter!

Well I dont know what to do, I guess I have to keep trying and learning guys.

And as allways, thanks for your input thumb.gif
No worrries.

SA and IO voltages (Z170) scale pretty well in auto for the most part. If you're stable at the timings used now then the memory wasn't stable before. Using the test methods provided in the OP will get you closer to being stable before encountering the issues you were seeing when playing games.
Quote:
Originally Posted by Desolutional View Post



It worked, BCLK being weird, going to jump into the BIOS to fix that. How acceptable is this?

*If you're trying to do this stuff in a VM, make sure to leave a few gigs free for the host OS, otherwise you end up getting segmentation faults.

Therein lies the issue, allocating less memory effectively makes it a less efficient test. This is really only a convenience thing smile.gif
Edited by Silent Scone - 1/20/16 at 1:14pm
post #395 of 4906
I've figured out what's causing my BCLK issue. Hyper-V ends up messing up timer measurements so BCLK appears lower than it actually is. I guess for "verification" purposes, it will be impossible to show the true OC as the apparent bus speed is fluctuating so much, so VM is a no go. Oh well, its only an hour I'd have to go without my rig. Yeah I'm lazy lol.
post #396 of 4906
Quote:
Originally Posted by Jpmboy View Post


EDIT: running gsat ATM 75% done and okay so far. When you tightened things up did you manually set a dram clock period? I believe this might hold things a bit more constsnt between boots. Just a guess, but seems empirically true on x99 and z170, today. redface.gif

I've left dram clock period on auto. Have you noticed something specific when setting this to a value? I don't seem to have any problems posting or difference in performance whenever I boot till now.

EDIT:Also just for the records I used 1.42 initial and 1.39 eventual in the past. I also noticed that these DIMMs don't like 1.4 eventual with the specific configuration (I get bd even with 1.42 initial) while they sit happily with 1.39 and pass the tests I have already mentioned. I tested 1.39v initial too and in the end they seem to love it. So I am running 1.39 from boot and in OS. This RAM is very picky.

Also I would like to ask you guys how well does mint handle your cache overclock. In order for me to run cache at 4200 without problems in windows I have disabled c6 state and I am sitting at 1.22v currently stable. Without disabling c6 I get shut downs starting from 40x uncore and up no matter the voltage(windows). I understand why this is happening but I would like to ask how are things for you in mint since when I tried to boot through a live USB to run GSAT, I get a shutdown a while after before I put CPU under load. I had to dial down my cache overclock to test RAM with GSAT. Mint doesn't handle c-states the same as windows or what?
Edited by NYD117 - 1/20/16 at 1:21pm
Alloy
(11 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core i7 5930K 4.2/4.2 Asus Deluxe x99 Gigabyte GeForce GTX 970 G1 Gaming @1.6GHz/8.2G... Corsair Dominator Platinum DDR4 2666c15@3200c16 
Hard DriveHard DriveCoolingOS
Samsung SSD 850 PRO 256GB WD Caviar Black 1TB NZXT Kraken x60 Windows 8.1 Pro Build 9600 
MonitorPowerCase
LG 27ud68-W Corsair AX 1200i Corsair Graphite 760T 
  hide details  
Reply
Alloy
(11 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core i7 5930K 4.2/4.2 Asus Deluxe x99 Gigabyte GeForce GTX 970 G1 Gaming @1.6GHz/8.2G... Corsair Dominator Platinum DDR4 2666c15@3200c16 
Hard DriveHard DriveCoolingOS
Samsung SSD 850 PRO 256GB WD Caviar Black 1TB NZXT Kraken x60 Windows 8.1 Pro Build 9600 
MonitorPowerCase
LG 27ud68-W Corsair AX 1200i Corsair Graphite 760T 
  hide details  
Reply
post #397 of 4906
Thread Starter 
Quote:
Originally Posted by NYD117 View Post

I've left dram clock period on auto. Have you noticed something specific when setting this to a value? I don't seem to have any problems posting or difference in performance whenever I boot till now.


Also I would like to ask you guys how well does mint handle your cache overclock. In order for me to run cache at 4200 without problems in windows I have disabled c6 state and I am sitting at 1.22v currently stable. Without disabling c6 I get shut downs starting from 40x uncore and up no matter the voltage(windows). I understand why this is happening but I would like to ask how are things for you in mint since when I tried to boot through a live USB to run GSAT, I get a shutdown a while after before I put CPU under load. I had to dial down my cache overclock to test RAM with GSAT. Mint doesn't handle c-states the same as windows or what?

Mint requires a fraction more stability than Windows in general, it's possible that lower power states in Mint could unearth instability with cache where Windows does not. I say this as I've experienced it myself.

Stress app however as a memory stresser does not stress cache in any meaningful sense, it's possible to run the test with fairly unstable cache in tow and have no problems.
post #398 of 4906
Quote:
Originally Posted by Silent Scone View Post

Mint requires a fraction more stability than Windows in general, it's possible that lower power states in Mint could unearth instability with cache where Windows does not. I say this as I've experienced it myself.

Stress app however as a memory stresser does not stress cache in any meaningful sense, it's possible to run the test with fairly unstable cache in tow and have no problems.

This seems pretty weird because In windows I have not found a way to make uncore show me any stability problems with stress testing, gaming or daily usage. And in mint it wasn't just unstable it committed suicide. biggrin.gif

I'll try to actually install mint on a drive and see how it goes though I doubt this should make a difference.
Alloy
(11 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core i7 5930K 4.2/4.2 Asus Deluxe x99 Gigabyte GeForce GTX 970 G1 Gaming @1.6GHz/8.2G... Corsair Dominator Platinum DDR4 2666c15@3200c16 
Hard DriveHard DriveCoolingOS
Samsung SSD 850 PRO 256GB WD Caviar Black 1TB NZXT Kraken x60 Windows 8.1 Pro Build 9600 
MonitorPowerCase
LG 27ud68-W Corsair AX 1200i Corsair Graphite 760T 
  hide details  
Reply
Alloy
(11 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core i7 5930K 4.2/4.2 Asus Deluxe x99 Gigabyte GeForce GTX 970 G1 Gaming @1.6GHz/8.2G... Corsair Dominator Platinum DDR4 2666c15@3200c16 
Hard DriveHard DriveCoolingOS
Samsung SSD 850 PRO 256GB WD Caviar Black 1TB NZXT Kraken x60 Windows 8.1 Pro Build 9600 
MonitorPowerCase
LG 27ud68-W Corsair AX 1200i Corsair Graphite 760T 
  hide details  
Reply
post #399 of 4906
Thread Starter 
Quote:
Originally Posted by NYD117 View Post

This seems pretty weird because In windows I have not found a way to make uncore show me any stability problems with stress testing, gaming or daily usage. And in mint it wasn't just unstable it committed suicide. biggrin.gif

I'll try to actually install mint on a drive and see how it goes though I doubt this should make a difference.

If it's only at idle there's not a lot else it could be. You can try disabling C3 reporting, or more drastically reduce the uncore overclock or increase your offset. The sudden shut down is a trait of FIVR as far as I'm aware, the first time I experienced it I too thought it seemed fairly ominous
Edited by Silent Scone - 1/20/16 at 1:42pm
post #400 of 4906
Quote:
Originally Posted by Silent Scone View Post

If it's only at idle there's not a lot else it could be. You can try disabling C3 reporting, or more drastically reduce the uncore overclock or increase your offset.

I'll give it a shot with disabled c-states to check this issue further when I install Mint on a drive.

I wanted to ask you guys your uncore and c-state configurations when you're using a linux distro, like in this case Mint, just for reference. Thanks thumb.gif
Edited by NYD117 - 1/20/16 at 1:46pm
Alloy
(11 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core i7 5930K 4.2/4.2 Asus Deluxe x99 Gigabyte GeForce GTX 970 G1 Gaming @1.6GHz/8.2G... Corsair Dominator Platinum DDR4 2666c15@3200c16 
Hard DriveHard DriveCoolingOS
Samsung SSD 850 PRO 256GB WD Caviar Black 1TB NZXT Kraken x60 Windows 8.1 Pro Build 9600 
MonitorPowerCase
LG 27ud68-W Corsair AX 1200i Corsair Graphite 760T 
  hide details  
Reply
Alloy
(11 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core i7 5930K 4.2/4.2 Asus Deluxe x99 Gigabyte GeForce GTX 970 G1 Gaming @1.6GHz/8.2G... Corsair Dominator Platinum DDR4 2666c15@3200c16 
Hard DriveHard DriveCoolingOS
Samsung SSD 850 PRO 256GB WD Caviar Black 1TB NZXT Kraken x60 Windows 8.1 Pro Build 9600 
MonitorPowerCase
LG 27ud68-W Corsair AX 1200i Corsair Graphite 760T 
  hide details  
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Intel CPUs
Overclock.net › Forums › Intel › Intel CPUs › *Official* Intel DDR4 24/7 Memory Stability Thread