Overclock.net › Forums › Components › Memory › BSOD 101 Tight RAM Timings
New Posts  All Forums:Forum Nav:

BSOD 101 Tight RAM Timings

post #1 of 63
Thread Starter 
Can tightening RAM timings produce a BSOD 101?
post #2 of 63
I think 101 is a clock interrupt cycle. Potentially additional Vcore is need, or VTT for the IMC (if I remember it right, I am doubting myself now.)

Better question is, have you Prime95 stable tested on Custom with 90% of your memory successfully?
Snowdevil
(16 items)
 
ASUS G750JM
(9 items)
 
 
CPUMotherboardGraphicsGraphics
[i7 4790K @ 4.4 GHz (1.186v)] [Asus Sabertooth Z97 Mark S] [nVidia Geforce GTX 1080] [nVidia Geforce GTX 1080] 
RAMHard DriveCoolingOS
[G.Skill 32GB DDR3 2133 MHz] [Crucial MX100 256GB] [Phanteks PH-TC12DX] [Win 10.1 Pro] 
MonitorMonitorKeyboardPower
[LG 29UM65 (2560x1080)] [QNIX Evo II LED (2560x1440)] [WASD v2 Tenkeyless] [NZXT Hale90 v2 ] 
CaseMouseMouse PadAudio
[ThermalTake GT10 Snow Edition] [Razer Mamba - Chroma] [Razer Kabuto] [Razer Man O' War] 
CPUMotherboardGraphicsRAM
i7 4770HQ Intel HM87 Express Chipset Geforce GTX 860M 8GB DDR3L 1600 MHz 
Hard DriveOptical DriveCoolingOS
Samsung SSD EVO DVD-RW Stock Windows 8.1 
Monitor
1920x1080 TN 
  hide details  
Reply
Snowdevil
(16 items)
 
ASUS G750JM
(9 items)
 
 
CPUMotherboardGraphicsGraphics
[i7 4790K @ 4.4 GHz (1.186v)] [Asus Sabertooth Z97 Mark S] [nVidia Geforce GTX 1080] [nVidia Geforce GTX 1080] 
RAMHard DriveCoolingOS
[G.Skill 32GB DDR3 2133 MHz] [Crucial MX100 256GB] [Phanteks PH-TC12DX] [Win 10.1 Pro] 
MonitorMonitorKeyboardPower
[LG 29UM65 (2560x1080)] [QNIX Evo II LED (2560x1440)] [WASD v2 Tenkeyless] [NZXT Hale90 v2 ] 
CaseMouseMouse PadAudio
[ThermalTake GT10 Snow Edition] [Razer Mamba - Chroma] [Razer Kabuto] [Razer Man O' War] 
CPUMotherboardGraphicsRAM
i7 4770HQ Intel HM87 Express Chipset Geforce GTX 860M 8GB DDR3L 1600 MHz 
Hard DriveOptical DriveCoolingOS
Samsung SSD EVO DVD-RW Stock Windows 8.1 
Monitor
1920x1080 TN 
  hide details  
Reply
post #3 of 63
101 in ivy\sandy is due to vcore .... raise \ lower accordingly ... typically ... you do not have enough vcore for your OC
Desktop Toaster
(19 items)
 
ThinClient
(5 items)
 
 
CPURAMHard DriveOS
Celeron N2930 G.Skill 8gb 204 pin Seagate 500gb 2.5" Win 10 Pro 
Case
Zotac Zbox CI320 Nano 
  hide details  
Reply
Desktop Toaster
(19 items)
 
ThinClient
(5 items)
 
 
CPURAMHard DriveOS
Celeron N2930 G.Skill 8gb 204 pin Seagate 500gb 2.5" Win 10 Pro 
Case
Zotac Zbox CI320 Nano 
  hide details  
Reply
post #4 of 63
Thread Starter 
Quote:
Originally Posted by RagingCain View Post

I think 101 is a clock interrupt cycle. Potentially additional Vcore is need, or VTT for the IMC (if I remember it right, I am doubting myself now.)

Better question is, have you Prime95 stable tested on Custom with 90% of your memory successfully?

Quote:
Originally Posted by HardheadedMurphy View Post

101 in ivy\sandy is due to vcore .... raise \ lower accordingly ... typically ... you do not have enough vcore for your OC

Yes I did. I am already 24hr Prime95 custom blend (90% RAM) and 100passes IBT (6500MB RAM) stable with loose timings and low clock RAM. I'm trying to overclock my RAM now. I'm 100passes IBT stable while lowering the RAM timings at 1866MHz but as when I tried 8-10-6-24-2T, I got a BSOD 101 in the middle of my IBT test. Does that mean that the RAM timings were the cause? Or is my CPU OC not yet stable?
Edited by kevindd992002 - 3/1/13 at 12:13am
post #5 of 63
Quote:
Originally Posted by kevindd992002 View Post

Quote:
Originally Posted by RagingCain View Post

I think 101 is a clock interrupt cycle. Potentially additional Vcore is need, or VTT for the IMC (if I remember it right, I am doubting myself now.)

Better question is, have you Prime95 stable tested on Custom with 90% of your memory successfully?

Quote:
Originally Posted by HardheadedMurphy View Post

101 in ivy\sandy is due to vcore .... raise \ lower accordingly ... typically ... you do not have enough vcore for your OC

Yes I did. I am already 24hr Prime95 custom blend (90% RAM) and 100passes IBT (6500MB RAM) stable with loose timings and low clock RAM. I'm trying to overclock my RAM now. I'm 100passes IBT stable while lowering the RAM timings at 1866MHz but as when I tried 8-6-8-24-2T, I got a BSOD 101 in the middle of my IBT test. Does that mean that the RAM timings were the cause? Or is my CPU OC not yet stable?

If it was stable, and you changed something, and its not stable, that is usually the cause. Not every device will allow itself to be overclocked.

Even memory benchmarks don't change that much with tighter timings on Intel, if I recall it's the AMD side that thrives on tight timings of memory. Anyways, to continue forward, you are going to have to add more voltage. Try keeping the timings locked and then overclocking the RAM speed. I have never found memory sticks to be perfectly stable with forced tighter timings but I am not a great RAM clocker. My thing is CPUs and GPUs.

CPU Vcore, then I think VTT for IMC, and potentially DRAM Voltage too.
Edited by RagingCain - 2/28/13 at 10:51am
Snowdevil
(16 items)
 
ASUS G750JM
(9 items)
 
 
CPUMotherboardGraphicsGraphics
[i7 4790K @ 4.4 GHz (1.186v)] [Asus Sabertooth Z97 Mark S] [nVidia Geforce GTX 1080] [nVidia Geforce GTX 1080] 
RAMHard DriveCoolingOS
[G.Skill 32GB DDR3 2133 MHz] [Crucial MX100 256GB] [Phanteks PH-TC12DX] [Win 10.1 Pro] 
MonitorMonitorKeyboardPower
[LG 29UM65 (2560x1080)] [QNIX Evo II LED (2560x1440)] [WASD v2 Tenkeyless] [NZXT Hale90 v2 ] 
CaseMouseMouse PadAudio
[ThermalTake GT10 Snow Edition] [Razer Mamba - Chroma] [Razer Kabuto] [Razer Man O' War] 
CPUMotherboardGraphicsRAM
i7 4770HQ Intel HM87 Express Chipset Geforce GTX 860M 8GB DDR3L 1600 MHz 
Hard DriveOptical DriveCoolingOS
Samsung SSD EVO DVD-RW Stock Windows 8.1 
Monitor
1920x1080 TN 
  hide details  
Reply
Snowdevil
(16 items)
 
ASUS G750JM
(9 items)
 
 
CPUMotherboardGraphicsGraphics
[i7 4790K @ 4.4 GHz (1.186v)] [Asus Sabertooth Z97 Mark S] [nVidia Geforce GTX 1080] [nVidia Geforce GTX 1080] 
RAMHard DriveCoolingOS
[G.Skill 32GB DDR3 2133 MHz] [Crucial MX100 256GB] [Phanteks PH-TC12DX] [Win 10.1 Pro] 
MonitorMonitorKeyboardPower
[LG 29UM65 (2560x1080)] [QNIX Evo II LED (2560x1440)] [WASD v2 Tenkeyless] [NZXT Hale90 v2 ] 
CaseMouseMouse PadAudio
[ThermalTake GT10 Snow Edition] [Razer Mamba - Chroma] [Razer Kabuto] [Razer Man O' War] 
CPUMotherboardGraphicsRAM
i7 4770HQ Intel HM87 Express Chipset Geforce GTX 860M 8GB DDR3L 1600 MHz 
Hard DriveOptical DriveCoolingOS
Samsung SSD EVO DVD-RW Stock Windows 8.1 
Monitor
1920x1080 TN 
  hide details  
Reply
post #6 of 63
Thread Starter 
Quote:
Originally Posted by RagingCain View Post

If it was stable, and you changed something, and its not stable, that is usually the cause. Not every device will allow itself to be overclocked.

Even memory benchmarks don't change that much with tighter timings on Intel, if I recall it's the AMD side that thrives on tight timings of memory. Anyways, to continue forward, you are going to have to add more voltage. Try keeping the timings locked and then overclocking the RAM speed. I have never found memory sticks to be perfectly stable with forced tighter timings but I am not a great RAM clocker. My thing is CPUs and GPUs.

CPU Vcore, then I think VTT for IMC, and potentially DRAM Voltage too.

Yeah but I'm wondering why would timings produce a BSOD 101, can't find anything on google that relates the two. VCCIO and DRAM voltage are already at 1.2V and 1.7V, respectively so no worries on those. The highest speed I can get without failing HyperPi/SuperPi/IBT is 1866MHz. I was able to determine that by locking the timings at 11-11-11-30-2T. Now my goal is to tighten those timings to the extreme, I don't care about how little it affects the system, it's just I overclock what I can smile.gif

My system can only boot with these ultimate tight timings 8-10-6-24-2T at any given speed. But that doesn't mean it is already stable at those timings, it can only boot. Lowering any of those timings from those minimum boot settings, will render the system in a non-bootable state.
post #7 of 63
Quote:
Originally Posted by kevindd992002 View Post

Quote:
Originally Posted by RagingCain View Post

If it was stable, and you changed something, and its not stable, that is usually the cause. Not every device will allow itself to be overclocked.

Even memory benchmarks don't change that much with tighter timings on Intel, if I recall it's the AMD side that thrives on tight timings of memory. Anyways, to continue forward, you are going to have to add more voltage. Try keeping the timings locked and then overclocking the RAM speed. I have never found memory sticks to be perfectly stable with forced tighter timings but I am not a great RAM clocker. My thing is CPUs and GPUs.

CPU Vcore, then I think VTT for IMC, and potentially DRAM Voltage too.

Yeah but I'm wondering why would timings produce a BSOD 101, can't find anything on google that relates the two. VCCIO and DRAM voltage are already at 1.2V and 1.7V, respectively so no worries on those. The highest speed I can get without failing HyperPi/SuperPi/IBT is 1866MHz. I was able to determine that by locking the timings at 11-11-11-30-2T. Now my goal is to tighten those timings to the extreme, I don't care about how little it affects the system, it's just I overclock what I can smile.gif

My system can only boot with these ultimate tight timings 8-10-6-24-2T at any given speed. But that doesn't mean it is already stable at those timings, it can only boot. Lowering any of those timings from those minimum boot settings, will render the system in a non-bootable state.

I can respect that. In my opinion, I think its best to start from scratch CPU included, and determined each components individual maximum first.

Here is a pretty thorough guide on the subject:
http://www.masterslair.com/memory-ram-overclocking-guide-ddr3

To answer an early question I was still trying to get a consensus on, yes, making the RAM overclocked can essentially destabilize what you thought was a stable CPU OC.

Best of luck to you. The voltages look within reason for what you are trying to do, and don't forget, RAM is way harder to OC than a Sandy CPU. You may not even physically be able to, even with all that voltage, but I totally understand why you would try.
Snowdevil
(16 items)
 
ASUS G750JM
(9 items)
 
 
CPUMotherboardGraphicsGraphics
[i7 4790K @ 4.4 GHz (1.186v)] [Asus Sabertooth Z97 Mark S] [nVidia Geforce GTX 1080] [nVidia Geforce GTX 1080] 
RAMHard DriveCoolingOS
[G.Skill 32GB DDR3 2133 MHz] [Crucial MX100 256GB] [Phanteks PH-TC12DX] [Win 10.1 Pro] 
MonitorMonitorKeyboardPower
[LG 29UM65 (2560x1080)] [QNIX Evo II LED (2560x1440)] [WASD v2 Tenkeyless] [NZXT Hale90 v2 ] 
CaseMouseMouse PadAudio
[ThermalTake GT10 Snow Edition] [Razer Mamba - Chroma] [Razer Kabuto] [Razer Man O' War] 
CPUMotherboardGraphicsRAM
i7 4770HQ Intel HM87 Express Chipset Geforce GTX 860M 8GB DDR3L 1600 MHz 
Hard DriveOptical DriveCoolingOS
Samsung SSD EVO DVD-RW Stock Windows 8.1 
Monitor
1920x1080 TN 
  hide details  
Reply
Snowdevil
(16 items)
 
ASUS G750JM
(9 items)
 
 
CPUMotherboardGraphicsGraphics
[i7 4790K @ 4.4 GHz (1.186v)] [Asus Sabertooth Z97 Mark S] [nVidia Geforce GTX 1080] [nVidia Geforce GTX 1080] 
RAMHard DriveCoolingOS
[G.Skill 32GB DDR3 2133 MHz] [Crucial MX100 256GB] [Phanteks PH-TC12DX] [Win 10.1 Pro] 
MonitorMonitorKeyboardPower
[LG 29UM65 (2560x1080)] [QNIX Evo II LED (2560x1440)] [WASD v2 Tenkeyless] [NZXT Hale90 v2 ] 
CaseMouseMouse PadAudio
[ThermalTake GT10 Snow Edition] [Razer Mamba - Chroma] [Razer Kabuto] [Razer Man O' War] 
CPUMotherboardGraphicsRAM
i7 4770HQ Intel HM87 Express Chipset Geforce GTX 860M 8GB DDR3L 1600 MHz 
Hard DriveOptical DriveCoolingOS
Samsung SSD EVO DVD-RW Stock Windows 8.1 
Monitor
1920x1080 TN 
  hide details  
Reply
post #8 of 63
Thread Starter 
Quote:
Originally Posted by RagingCain View Post

I can respect that. In my opinion, I think its best to start from scratch CPU included, and determined each components individual maximum first.

Here is a pretty thorough guide on the subject:
http://www.masterslair.com/memory-ram-overclocking-guide-ddr3

To answer an early question I was still trying to get a consensus on, yes, making the RAM overclocked can essentially destabilize what you thought was a stable CPU OC.

Best of luck to you. The voltages look within reason for what you are trying to do, and don't forget, RAM is way harder to OC than a Sandy CPU. You may not even physically be able to, even with all that voltage, but I totally understand why you would try.

Thanks but that article was focused on changing BCLK also which obviously can destabilize your stable CPU OC easily. Mine is set to 100 as the default value.
post #9 of 63
Sometimes when overclocking RAM you'll reach a point where you need more vcore even if you have thoroughly stressed your CPU beforehand and it appeared stable. I don't know why exactly, but it's not unheard of.
Beestje 2.0
(20 items)
 
Beestje 1.5
(16 items)
 
 
CPUMotherboardGraphicsGraphics
Intel Core i7 3820 Sabertooth X79 ASUS GeForce GTX 680 ASUS GeForce GTX 680 
RAMHard DriveHard DriveHard Drive
Samsung low profile x4 OCZ Vertex 3 Crucial M4 Samsung HD103SJ 
Optical DriveCoolingCoolingOS
Lite-On BD drive Megahalems rev. B Cooler Master Excalibur Windows 7 home premium x64 
MonitorKeyboardPowerCase
ASUS VG278H Logitech G710+ Corsair TX750 Silverstone Raven 2 Evolution 
MouseMouse PadAudioAudio
Corsair M60 Razer Kabuto Echo Audiofire 2 Sennheiser HD515 
CPUMotherboardGraphicsRAM
i7 920 Asus P6T Club3d HD7870 royalKing Corsair Dominator 3x4GB 
Hard DriveHard DriveOptical DriveCooling
Crucial V4 128GB Seagate Barracuda LP 2TB LG GH22LS Scythe Mugen 2b 
CoolingCoolingMonitorKeyboard
CM Excalibur x2 CM R4 x3 Samsung BX2450 Microsoft Sidewinder X6 
PowerCaseMouseMouse Pad
Seasonic M12 II 520 Antec 600 Microsoft Intellimouse Razer Kabuto 
  hide details  
Reply
Beestje 2.0
(20 items)
 
Beestje 1.5
(16 items)
 
 
CPUMotherboardGraphicsGraphics
Intel Core i7 3820 Sabertooth X79 ASUS GeForce GTX 680 ASUS GeForce GTX 680 
RAMHard DriveHard DriveHard Drive
Samsung low profile x4 OCZ Vertex 3 Crucial M4 Samsung HD103SJ 
Optical DriveCoolingCoolingOS
Lite-On BD drive Megahalems rev. B Cooler Master Excalibur Windows 7 home premium x64 
MonitorKeyboardPowerCase
ASUS VG278H Logitech G710+ Corsair TX750 Silverstone Raven 2 Evolution 
MouseMouse PadAudioAudio
Corsair M60 Razer Kabuto Echo Audiofire 2 Sennheiser HD515 
CPUMotherboardGraphicsRAM
i7 920 Asus P6T Club3d HD7870 royalKing Corsair Dominator 3x4GB 
Hard DriveHard DriveOptical DriveCooling
Crucial V4 128GB Seagate Barracuda LP 2TB LG GH22LS Scythe Mugen 2b 
CoolingCoolingMonitorKeyboard
CM Excalibur x2 CM R4 x3 Samsung BX2450 Microsoft Sidewinder X6 
PowerCaseMouseMouse Pad
Seasonic M12 II 520 Antec 600 Microsoft Intellimouse Razer Kabuto 
  hide details  
Reply
post #10 of 63
Thread Starter 
Quote:
Originally Posted by Vonnis View Post

Sometimes when overclocking RAM you'll reach a point where you need more vcore even if you have thoroughly stressed your CPU beforehand and it appeared stable. I don't know why exactly, but it's not unheard of.

Hmmm, ok. And one notch above your known stable vcore is enough?

Is 1.7V for DRAM voltage safe?
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Memory
Overclock.net › Forums › Components › Memory › BSOD 101 Tight RAM Timings