Overclock.net › Forums › Intel › Intel Motherboards › [Official] Asus Rampage IV Black Edition Owners Club!
New Posts  All Forums:Forum Nav:

[Official] Asus Rampage IV Black Edition Owners Club! - Page 576

post #5751 of 14864
Quote:
Originally Posted by LunaP View Post

@Cada

I'm starting to think my chip sucks IMC wise. Regardless I can't get 2400 stable on 1 kit , regardless of which kit. Been blue screen after blue screen after blue screen.

1333 is the only thing stable. 1866 crashes 1600 crashes 2133 crashes 2000 crashes 2333 crashes etc. I bumped VTT to match my vcore and bumped VSSCA to 1.15 as well heck even 1.25 for all and still as soon as I run an Aida64 bench it dies, either whole comp locks up or a get a blue screen.

Caught one blue screen

"A clock cycle was not received in a timely manner from a 2ndary processor..."

Any last suggestions.


Of course.

thumb.gif


I see you have CPU, DIMM and VCCSA current in DiGi+ set to 130%. Tsk, Tsk.

Extreme loadline on all?

Yeah, let's shove the current down everything, that'll fix it! rolleyes.gif


biggrin.gif

try 180% CPU, high or very high LLC. VCCSA to 130%, but high LLC. DRAM, 100%, optimized LLC.

Then, start at 1.05V VTT, and 0.900V VCCSA...try boot. increase VCCSA first, but try to maintain ratio between VTT and VCCSA. Think of it in steps..data goes from ram @ 1/2 ram voltage, to VCCSA, to VTT, to CPU. You need to maintain that relationship between those voltages as much as is possible.

Also, you should have cleared CMOS with optimized defaults, enabled XMP, then adjusted secondary timings to match what's in SPD tool in BIOS. A few timings will be off. At the same time, G.Skill uses very low tWCL, usually @ 7, and you might need 8 or 9, or maybe 10...check what the DIMMs request, and what the BIOS sets. Also, I feel all timings are adjusted to provide -1 tWCL, so 9 is like 8, 8 like 7, etc, etc.

Lastly, DRAM tREFI is not always set accurately. Some sticks ask for 7.8, some for 3.9....sometimes BIOS sets 7.3, or other weird stuff with 8 GB DIMMs. So play with tRFC and tREFI, try to get that 7.8us.

as a guide, for settings in BIOS,

2133 MHz = 8320
2400 MHz = 9360
2600 MHz = 10140
2666 MHz = 10400
2800 MHz = 10920

I know, by now, you're like "huh!?!".


biggrin.gif
post #5752 of 14864
Quote:
Originally Posted by MehlstaubtheCat View Post

Have you looked on HWBot Forum?

http://forum.hwbot.org/index.php
Great, iám looking forward ! thumb.gif

Quote:
Originally Posted by MehlstaubtheCat View Post

;(
I'm waiting too, since he posted he had it 5ghz stable in Ivy thread several weeks ago. wink.gif
This is all I see atm.


Edited by hotrod717 - 2/16/14 at 11:59am
    
CPUMotherboardGraphicsRAM
Intel 5820k Asrock x99 OCF V3.1 One of many Kingston HyperX Predator 
Hard DriveOptical DriveCoolingOS
Samsung 840 EVO Asus Bluray Custom Water Win7 Ultimate 
MonitorPowerCaseMouse
Asus VG248QE EVGA P1200 Mountain Mods Extended Custom U2-UFO  Mad Catz R.A.T 5 
Mouse PadAudio
steelseries M-Audio BX5a DLX 
  hide details  
Reply
    
CPUMotherboardGraphicsRAM
Intel 5820k Asrock x99 OCF V3.1 One of many Kingston HyperX Predator 
Hard DriveOptical DriveCoolingOS
Samsung 840 EVO Asus Bluray Custom Water Win7 Ultimate 
MonitorPowerCaseMouse
Asus VG248QE EVGA P1200 Mountain Mods Extended Custom U2-UFO  Mad Catz R.A.T 5 
Mouse PadAudio
steelseries M-Audio BX5a DLX 
  hide details  
Reply
post #5753 of 14864
Ok, one of so many, he won the lottery. smile.gif very unique !
I think it is not worth it to me to wait until for this one good chip
fourteen that must be more than enough to select !
Edited by MehlstaubtheCat - 2/16/14 at 12:11pm
post #5754 of 14864
Quote:
Originally Posted by hotrod717 View Post


I'm waiting too, since he posted he had it 5ghz stable in Ivy thread several weeks ago. wink.gif
This is all I see atm.



Soon my friend, almost done cleaning my loop smile.gif
LEGION
(15 items)
 
  
CPUMotherboardGraphicsRAM
I7 6700K ASUS Maximus VIII Impact EVGA GTX TITAN X G.skill 16gb 3200 ddr4 
Hard DriveHard DriveHard DriveCooling
Samsung 840 pro 250gb Samsung 840 evo 250gb Samsung 840 evo 250gb Ice kings magic. 
OSMonitorKeyboardPower
WIN 10 Wasabi Mango 42" 4k Corsair k70 EVGA 1000w P2 
CaseMouseAudio
Caselabs Mercury S3 Razer naga :( sennheiser HD 558 
  hide details  
Reply
LEGION
(15 items)
 
  
CPUMotherboardGraphicsRAM
I7 6700K ASUS Maximus VIII Impact EVGA GTX TITAN X G.skill 16gb 3200 ddr4 
Hard DriveHard DriveHard DriveCooling
Samsung 840 pro 250gb Samsung 840 evo 250gb Samsung 840 evo 250gb Ice kings magic. 
OSMonitorKeyboardPower
WIN 10 Wasabi Mango 42" 4k Corsair k70 EVGA 1000w P2 
CaseMouseAudio
Caselabs Mercury S3 Razer naga :( sennheiser HD 558 
  hide details  
Reply
post #5755 of 14864
He did link a CPU-Z @ some point a few weeks ago.
IT'S WHITE
(21 items)
 
 
CPUMotherboardGraphicsGraphics
4930k Rampage iv extreme Black Edition GTX Titan  GTX Titan 
GraphicsRAMHard DriveHard Drive
GTX Titan GskillZ Trident X Samsung EVO samsung 840 evo 
Optical DriveCoolingCoolingOS
Asus External Blue Ray drive 4x 480x60mm Swiftech MCP35x2 Win 8.1.2 
MonitorMonitorMonitorPower
AOC AOC AOC EVGA G2 1300w 
CaseMouseMouse PadAudio
STH10 RAT7 what is this?  Vali / Modi :(  
Other
Corsair HX850 
  hide details  
Reply
IT'S WHITE
(21 items)
 
 
CPUMotherboardGraphicsGraphics
4930k Rampage iv extreme Black Edition GTX Titan  GTX Titan 
GraphicsRAMHard DriveHard Drive
GTX Titan GskillZ Trident X Samsung EVO samsung 840 evo 
Optical DriveCoolingCoolingOS
Asus External Blue Ray drive 4x 480x60mm Swiftech MCP35x2 Win 8.1.2 
MonitorMonitorMonitorPower
AOC AOC AOC EVGA G2 1300w 
CaseMouseMouse PadAudio
STH10 RAT7 what is this?  Vali / Modi :(  
Other
Corsair HX850 
  hide details  
Reply
post #5756 of 14864
Hi skupples happy to see you here smile.gif

Has he a real prove Prime 95 for a few hours with CPU-Z Validation of something ?
post #5757 of 14864
The cpuz I linked was 5.1 it was somewhat stable but needed more voltage than I liked for 24/7, it can boot at 5.2 & 5.3 but the volts it needs aren't close to safe for water even in winter. I think I got a good chip, not golden exactly but still good and if it does eventuallybsod for me at 5.0 you guys would be the first to know tongue.gif
LEGION
(15 items)
 
  
CPUMotherboardGraphicsRAM
I7 6700K ASUS Maximus VIII Impact EVGA GTX TITAN X G.skill 16gb 3200 ddr4 
Hard DriveHard DriveHard DriveCooling
Samsung 840 pro 250gb Samsung 840 evo 250gb Samsung 840 evo 250gb Ice kings magic. 
OSMonitorKeyboardPower
WIN 10 Wasabi Mango 42" 4k Corsair k70 EVGA 1000w P2 
CaseMouseAudio
Caselabs Mercury S3 Razer naga :( sennheiser HD 558 
  hide details  
Reply
LEGION
(15 items)
 
  
CPUMotherboardGraphicsRAM
I7 6700K ASUS Maximus VIII Impact EVGA GTX TITAN X G.skill 16gb 3200 ddr4 
Hard DriveHard DriveHard DriveCooling
Samsung 840 pro 250gb Samsung 840 evo 250gb Samsung 840 evo 250gb Ice kings magic. 
OSMonitorKeyboardPower
WIN 10 Wasabi Mango 42" 4k Corsair k70 EVGA 1000w P2 
CaseMouseAudio
Caselabs Mercury S3 Razer naga :( sennheiser HD 558 
  hide details  
Reply
post #5758 of 14864
Quote:
Originally Posted by skupples View Post

He did link a CPU-Z @ some point a few weeks ago.
I'd be happy to see a R15 run. thumb.gif I can boot 5ghz.


Edited by hotrod717 - 2/16/14 at 1:06pm
    
CPUMotherboardGraphicsRAM
Intel 5820k Asrock x99 OCF V3.1 One of many Kingston HyperX Predator 
Hard DriveOptical DriveCoolingOS
Samsung 840 EVO Asus Bluray Custom Water Win7 Ultimate 
MonitorPowerCaseMouse
Asus VG248QE EVGA P1200 Mountain Mods Extended Custom U2-UFO  Mad Catz R.A.T 5 
Mouse PadAudio
steelseries M-Audio BX5a DLX 
  hide details  
Reply
    
CPUMotherboardGraphicsRAM
Intel 5820k Asrock x99 OCF V3.1 One of many Kingston HyperX Predator 
Hard DriveOptical DriveCoolingOS
Samsung 840 EVO Asus Bluray Custom Water Win7 Ultimate 
MonitorPowerCaseMouse
Asus VG248QE EVGA P1200 Mountain Mods Extended Custom U2-UFO  Mad Catz R.A.T 5 
Mouse PadAudio
steelseries M-Audio BX5a DLX 
  hide details  
Reply
post #5759 of 14864
Quote:
Originally Posted by LunaP View Post

Ah didn't know that.

and also was setting high VTT/VCCSA in hopes of working down but I"ll work the other way up .... so far 125 block seems to be the ticket.


Here's @ 2400 which loaded up seemingly fine w/ the DEC batch.



Here's the July batch on 2333 block 125 , surprisingly enough seems like 2333 is the sweet spot as 2400 you see a dip in the Write.
Warning: Spoiler! (Click to show)


Here's my settings thus far =w=;;
Warning: Spoiler! (Click to show)



After you do the CMOS reset and load defaults, take a picture of all the timings for the RAM under default. Then, when you overclock the RAM carefully compare the secondary and tertiary timings between the overclocked and standard values.

From my experience the tRDRD value when overclocking was being set to a value of 8 and it was giving me 50% less on write speed when benchmarking. I changed the tRDRD value to 4 (the stock value was 4) and the write speeds immediately matched the read and copy speeds.

Some background on the settings logic from ASUS:
Warning: Spoiler! (Click to show)
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.
Not Fast Enough
(17 items)
 
  
CPUMotherboardGraphicsRAM
Core i7-4770K @ 4.5GHz ASUS Maximus VI Hero GTX 980Ti 2 x 8GB 2400MHz Hynix MFR Corsair Vengeanace  
Hard DriveHard DriveHard DriveOptical Drive
Samsung 840 Pro 256GB SSD QNAP TS-670 HGST 5K4000 PLDS 16X DVD±RW 
CoolingCoolingOSMonitor
Two AP-13, two AP-14, one AP-15 Noctua NH-D15S Windows 10 Pro x64 Acer Predator XB271HU 
KeyboardPowerCaseMouse
Ducky Shine 3 TKL SS-860XP2 NZXT H630 Logitech G303 
  hide details  
Reply
Not Fast Enough
(17 items)
 
  
CPUMotherboardGraphicsRAM
Core i7-4770K @ 4.5GHz ASUS Maximus VI Hero GTX 980Ti 2 x 8GB 2400MHz Hynix MFR Corsair Vengeanace  
Hard DriveHard DriveHard DriveOptical Drive
Samsung 840 Pro 256GB SSD QNAP TS-670 HGST 5K4000 PLDS 16X DVD±RW 
CoolingCoolingOSMonitor
Two AP-13, two AP-14, one AP-15 Noctua NH-D15S Windows 10 Pro x64 Acer Predator XB271HU 
KeyboardPowerCaseMouse
Ducky Shine 3 TKL SS-860XP2 NZXT H630 Logitech G303 
  hide details  
Reply
post #5760 of 14864
Thread Starter 
Quote:
Originally Posted by cadaveca View Post

Of course.

thumb.gif


I see you have CPU, DIMM and VCCSA current in DiGi+ set to 130%. Tsk, Tsk.

Extreme loadline on all?

Yeah, let's shove the current down everything, that'll fix it! rolleyes.gif


biggrin.gif

try 180% CPU, high or very high LLC. VCCSA to 130%, but high LLC. DRAM, 100%, optimized LLC.

Then, start at 1.05V VTT, and 0.900V VCCSA...try boot. increase VCCSA first, but try to maintain ratio between VTT and VCCSA. Think of it in steps..data goes from ram @ 1/2 ram voltage, to VCCSA, to VTT, to CPU. You need to maintain that relationship between those voltages as much as is possible.

Also, you should have cleared CMOS with optimized defaults, enabled XMP, then adjusted secondary timings to match what's in SPD tool in BIOS. A few timings will be off. At the same time, G.Skill uses very low tWCL, usually @ 7, and you might need 8 or 9, or maybe 10...check what the DIMMs request, and what the BIOS sets. Also, I feel all timings are adjusted to provide -1 tWCL, so 9 is like 8, 8 like 7, etc, etc.

Lastly, DRAM tREFI is not always set accurately. Some sticks ask for 7.8, some for 3.9....sometimes BIOS sets 7.3, or other weird stuff with 8 GB DIMMs. So play with tRFC and tREFI, try to get that 7.8us.

as a guide, for settings in BIOS,

2133 MHz = 8320
2400 MHz = 9360
2600 MHz = 10140
2666 MHz = 10400
2800 MHz = 10920

I know, by now, you're like "huh!?!".


biggrin.gif

Lol hey trial and error right? biggrin.gif and no actually been reading up alot so I'm following pretty well, and I've been reading up on the diff stetings as well.


For TwCL did you mean tRRD?
Quote:
Originally Posted by iatacs19 View Post

After you do the CMOS reset and load defaults, take a picture of all the timings for the RAM under default. Then, when you overclock the RAM carefully compare the secondary and tertiary timings between the overclocked and standard values.

From my experience the tRDRD value when overclocking was being set to a value of 8 and it was giving me 50% less on write speed when benchmarking. I changed the tRDRD value to 4 (the stock value was 4) and the write speeds immediately matched the read and copy speeds.

Some background on the settings logic from ASUS:
Warning: Spoiler! (Click to show)
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.

you guys want me to do this with the 32 or with the 64? I wouldn't mind having the 64 on 2133.

also was messing more last night and got 2333 stable w/ 32gb by bumping dram voltage to 1.67

Also I can't find tRDRD in my settings for timings. Any chance that's a typo? Google isn't bringing up much either.




UPDATE

ok made the desired changes and here's the current shots of the Mobo, What the crap now windows loads w/ 2400... time to run aida..


While I do that here's the current settings.
Warning: Spoiler! (Click to show)












Ok so Read speeds were about 63343 , write was about 42455, when it got to copy it choked a bit then rebooted ( BSOD'd)

Bumping VSSCA to 1.05 if that works I'll drop it to 1 and retest.



Ok set to 1.05 but windows rebooted before getting in now. Interesting.




0.95 boots into windows but this time BSOD stays when it gets to the COPY test in Aida64

SYSTEM_SERVICE_EXCEPTION

msrpc.sys

gonna google this one(obviously due to the memory but curious anyways). Write speeds are still horrible, yet if I back down to 2133 or 2333 they're almost identical?




Update

Following the VTT : VSSCA ratio guide by cad

I'm now @ 1.1v for VTT
and 1v for VSSCA

Aida now completes successfully. Running it a few more times to make sure it wasn't a fluke.

Write speeds however are bad. 63 on copy and read but 43 on write. Still looking for this setting mentioned.

After this should I attempt w/ 64gb? Except @ 2133? Since I'm sure 2400 would be quite a load for my chip, and uneeded? Would be nice to make use of them.


None the less this is definitely progress!! and a good learning experience.


Edited by LunaP - 2/16/14 at 2:23pm
Sylphiel
(20 items)
 
Yuna
(18 items)
 
 
CPUMotherboardGraphicsRAM
Intel Core i7 Extreme 980X Gigabyte X58A-UD3R eVGA GTX TITAN Corsair 
RAMHard DriveOptical DriveCooling
Corsair  Corsair SSD Samsung BluRay R/W Corsair H90 
OSMonitorMonitorMonitor
Windows 7 Ultimate HP w2338h HP w2338h HP w2338h 
MonitorMonitorKeyboardPower
HP w2338h Samsung 46" TV ROCCAT Antex 1200W Silver 
CaseMouseMouse PadAudio
Cosmos Corsair m95 ALLSOP Onboard 
  hide details  
Reply
Sylphiel
(20 items)
 
Yuna
(18 items)
 
 
CPUMotherboardGraphicsRAM
Intel Core i7 Extreme 980X Gigabyte X58A-UD3R eVGA GTX TITAN Corsair 
RAMHard DriveOptical DriveCooling
Corsair  Corsair SSD Samsung BluRay R/W Corsair H90 
OSMonitorMonitorMonitor
Windows 7 Ultimate HP w2338h HP w2338h HP w2338h 
MonitorMonitorKeyboardPower
HP w2338h Samsung 46" TV ROCCAT Antex 1200W Silver 
CaseMouseMouse PadAudio
Cosmos Corsair m95 ALLSOP Onboard 
  hide details  
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Intel Motherboards
Overclock.net › Forums › Intel › Intel Motherboards › [Official] Asus Rampage IV Black Edition Owners Club!