Memory fine tuning

Associate
Joined
18 Oct 2011
Posts
2,272
Last edited:
Ahh sorry about that

MB - Asrock z77 extreme 4

**Tryed (11-11-11-36 2T at 2133) got to bios and then PC rebooted

--------------

Also a quick question this might seem really stupid but when I put 2T it changed it to auto is this correct? Because I changed it again and only put 2 (Maybe why it rebooted not sure)
 
Last edited:
Lets try get the system to boot at 2133mhz DRAM speed first so set VTT 1.2 in the voltages and VCCSA the same.

Then down the DRAM page set the following :
11-11-11-31-2-16-260-7-7-7-30-9 Then all the settings down to TWWSR to 6 and try to boot.

Then we will tune from that.
 
hmmmmm I dont understand why really. Those settings should work fine at 2133mhz. They are very compatible.

What is the debug code the system is stopping on? this will help. Have you updated the boards Bios?? and have you tried with just one stick??
 
Extremely late reply, I upped my vcore a little and finally it boots at 2133Mhz (11-11-11-36)

So yeah you was right :). Is it worth trying to tune the timings more?

**Well I might of been able to boot but programs keep crashing (Failing to respond) I.E Skype/Team Speak/Rust <-- a game
 
Last edited:
Ahhh ok had a brain fart moment.

I now have:

Vcore (1.150v)
VTT (1.141v / auto)

VCCSA 1.107 <-- Could only choose between (0.925v - 1.016v - 1.107v - 1.200v)
TCKE 5
TWR 16
TFAW 26
TRRSR 5
TWWSR 5

**Game crashed and HWmonitor etc stopped responding
 
Last edited:
Gave it a try and while I was playing Arma2 the game crashed with the error (out of memory)

Maybe there is something else wrong with my CPU OC or voltage some where, i am not really sure

--------------------------------------------------------------

Not sure if this will help but a week or so ago after months of stability with no changes I did get a random blue screen with the error code (0xD1), not had one since. I do believe that code meant

*0xD1 = QPI/VTT, increase/decrease as necessary, can also be unstable Ram, raise Ram voltage

Could this be causing the issues? I have no idea.

---------------------------------------------------------------

I dug this out for you to check just incase it helps in anyway:

On Fri 08/11/2013 21:25:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\110813-11216-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xD1 (0xC350, 0x2, 0x8, 0xC350)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 08/11/2013 21:25:51 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xD1 (0xC350, 0x2, 0x8, 0xC350)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
 
Last edited:
Ok, so set everything to stock? (Default UEFI Bios)

Do I set the memory to 2133Mhz @ 11-11-11-36-2?
 
Last edited:
Back
Top Bottom