Memory fine tuning

Loxa

Loxa

Loxa

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:
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:
8 Pack said:
Yep!!!

Lets see whats going on!!!
Click to expand...

Seems to work fine, only thing I did notice was when I look in the bios with XMP profile enabled without a CPU OC on my memory voltage is 1.665v but when I had a CPU OC on and XMP profile it was 1.650v.
 
8 Pack said:
No issue with that. So XMP is fine, nothing wrong with memory then. maybe IMC is weak.
Click to expand...

Yeah I was thinking this after a bit of research the past week or so. I am guessing there is not much I can do now?

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

(got this after exiting a game)

Desktop windows manager has stopped working

Problem signature:
Problem Event Name: APPCRASH
Application Name: Dwm.exe
Application Version: 6.1.7600.16385
Application Timestamp: 4a5bc541
Fault Module Name: dwmcore.dll
Fault Module Version: 6.1.7601.17514
Fault Module Timestamp: 4ce7c62d
Exception Code: c000001d
Exception Offset: 0000000000001342
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 2057
Additional Information 1: 0079
Additional Information 2: 007959f892908690b4db8dc9699bd0ae
Additional Information 3: 3037
Additional Information 4: 30371cb2c58ba672f25d794b2c23a413

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
 
Last edited:
Its kind of annoying because I used to have 8gb of geil ram which after a few months went faulty and I had it swapped for 16gb of geil and now it seems this is not right some how..

-------------------------------
I do not know if this will affect anything but I think my Intel chipset driver is out of date, I found these two which are newer than the ones on my motherboard manufactures website. But I am not 100% sure if these are the correct ones for my board.

(ASrock Z77 extreme4 is my board)

https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=23061

https://downloadcenter.intel.com/De...22596&lang=eng&wapkw=management+engine+driver
 
Last edited:
Ok ill memtest with the XMP profile tonight, only problem I have is doing one stick at a time because I have the Prolimatech Genesis cooler and do not have the compound to keep removing it.. God damn lol
 
The weirdest thing happened yesterday. I went into my bios and set the XMP profile & changed the timing but when I entered the tab for the timings I glanced some voltages and on the way back out I noticed they had changed (hmm strange) but did not think anything of it. Booted into windows had multiple programs and was even gaming for hours with not one problem or program crash.. I just do not know how this is possible

2133mhz (11-11-11-36)
 
Ran memtest last night for 11 hours (5 passes) with no errors.

1.665v - Dram Voltage
2133mhz
11-11-11-36
1.141v - VTT
0.925 - VCCSA

I get know random program crashes but one of my games with just randomly turn off every 40 minutes or so, thinking IMC might be sucky..
 
Ok so I finally got the system stable at 2133mhz, the problem turned out to be a corrupt windows file and needed more VCore as you said in a previous post. Where is a realistic place for me to start with timings?
 
You must log in or register to reply here.
Back
Top Bottom