Jump to content

14" Dell Latitude E6430 - Performance Upgrades and System Mods


Recommended Posts

5 minutes ago, sefki21 said:

 

Yeah - tried A03/A07 and A12 with windows and freeDOS. Gave A09/A11/A12/A13/A14/A15 a chance via FreeDOS now - as i'm already dissambled my 6430 to unlock it. But still no update :-/

 

in FreeDos the Prompt comes up after executing the exe - if i'm sure. Then it prepares - wants to restart to intstall - but after coming up again it just normal boots...

 

I have no other ideas... Last resort would be to revert your ME FW from the original dump you made and see if it makes any difference (I doubt it)... Let us know how it goes.

 

Did you get this laptop with A16 or did you just updated?

 

Edited by timohour
Link to comment
Share on other sites

39 minutes ago, timohour said:

 

I have no other ideas... Last resort would be to revert your ME FW from the original dump you made and see if it makes any difference (I doubt it)... Let us know how it goes.

 

Did you get this laptop with A16 or did you just updated?

 

 

i thought the dump of bios includes the one for ME FW - my mistake as it doesnt... As i was able to use the modified ME FW of someone else, shouldn't i be able to flash a unmodifed ME FW of someone else too?

 

nope, i did update - and i was able to downgrade before, as i tried diffrent BIOS at the bery beginning .. 

Link to comment
Share on other sites

5 minutes ago, sefki21 said:

 

i thought the dump of bios includes the one for ME FW - my mistake as it doesnt... As i was able to use the modified ME FW of someone else, shouldn't i be able to flash a unmodifed ME FW of someone else too?

 

offcourse it does.. use the dump of your original BIOS to revert to «stock ME FW».

 

If I understand your question correctly, you will flash the old ME FW using the command you used to flash the OCed one.

 

Edited by timohour
Link to comment
Share on other sites

4 hours ago, sefki21 said:

feeling like a fool right now :-(

- reseted UEFI changes

- reseted Flash descriptor to original (locked)

- again applied power drain

--> still not able to down/upgrade BIOS

 

here i tried flashing BIOS Dump via "FPT -DESC -F"

 

1 hour ago, timohour said:

 

offcourse it does.. use the dump of your original BIOS to revert to «stock ME FW».

 

If I understand your question correctly, you will flash the old ME FW using the command you used to flash the OCed one.

 

 

Now after your comment i tried it with the modifed BIOS, where i left Flash Descriptor unlocked and locked ME

I used "FPT -ME -F" this time..

 

 

Tadaaa!!! working! so seems to be related to the OC ME FW

anyway many thanks for your help!!

IMG_5230.JPG

 

PS: back to A07 now - OS X: Glitches gone, almost twice as fast boot time! 

PS2: I just tried out A17 - Boot-Time still fast. but can't get rid of the glitches (tried out setting 0x1c7 to 0x01, 0x02 and 0x03)

Edited by sefki21
more Infos
Link to comment
Share on other sites

4 hours ago, sefki21 said:

Tadaaa!!! working! so seems to be related to the OC ME FW

anyway many thanks for your help!!

 

PS: back to A07 now - OS X: Glitches gone, almost twice as fast boot time! 

PS2: I just tried out A17 - Boot-Time still fast. but can't get rid of the glitches (tried out setting 0x1c7 to 0x01, 0x02 and 0x03)

 

Great news! I am happy that you finally did it.

I think that I might understood what caused the problem. The OC_ME region supplied by khenglish is based on an A13 (if memory serves) FTP dump.
This is probably why it didn't down/upgrade the BIOS when you tried. It seems like there was a mismatch between BIOS version and ME FW version.
 

So, from now on I recommend that everyone who wants to patch his ME FW in order to enable BCLK OC, to mod his  own ME FW version instead of using the one supplied.
This way we probably won't have such problem again.
 

What's the default value of 0x1c7 for the A07 version?

 

You can try all values with the A17 to see if anything changes...

Option: 32M, Value: 0x1
Option: 64M, Value: 0x2
Option: 96M, Value: 0x3
Option: 128M, Value: 0x4
Option: 160M, Value: 0x5
Option: 192M, Value: 0x6
Option: 224M, Value: 0x7
Option: 256M, Value: 0x8
Option: 288M, Value: 0x9
Option: 320M, Value: 0xA
Option: 352M, Value: 0xB
Option: 384M, Value: 0xC
Option: 416M, Value: 0xD
Option: 448M, Value: 0xE
Option: 480M, Value: 0xF
Option: 512M, Value: 0x10
Option: 1024M, Value: 0x11

It most probably won't have any difference but wouldn't hurt if you tried.

(I know it's a dirty job, but somebody's gotta do it)

 

Edited by timohour
Link to comment
Share on other sites

12 hours ago, timohour said:

What's the default value of 0x1c7 for the A07 version?

 

It's like on A12 and A17: 0x02

 

12 hours ago, timohour said:

You can try all values with the A17 to see if anything changes...

It most probably won't have any difference but wouldn't hurt if you tried.

(I know it's a dirty job, but somebody's gotta do it)

 

just tried all of them --> no luck

are you aware of any other variable to check? or method to try? 

Link to comment
Share on other sites

3 hours ago, sefki21 said:

 

It's like on A12 and A17: 0x02

 

 

just tried all of them --> no luck

are you aware of any other variable to check? or method to try? 

 

I looked on many hackintosh sites but I can't find the reason those glitches occur. It should be a BIOS setting not a hardware problem since it works with a BIOS revision but not with another.

Do  you have any other info that can help us narrow it down?

you can check other variables related to the iGPU... I can't tell which one could do the trick.

Setting: DVMT Total Gfx Mem, Variable: 0x1C8
Option: 128M, Value: 0x1
Option: 256M, Value: 0x2
Option: MAX, Value: 0x3
End of Options
Setting: Aperture Size, Variable: 0x17D
Option: 128MB, Value: 0x1 
Option: 256MB, Value: 0x2
Option: 512MB, Value: 0x3
End of Options
Setting: GTT Size, Variable: 0x17C
Option: 1MB, Value: 0x1
Option: 2MB, Value: 0x2
End of Options
Setting: Gfx Low Power Mode, Variable: 0x178
Option: Enabled, Value: 0x1
Option: Disabled, Value: 0x0
End of Options
Setting: Graphics Performance Analyzers, Variable: 0x179
Option: Enabled, Value: 0x1
Option: Disabled, Value: 0x0 
End of Options

keep a  note which was the default one before changing it. I have never touched any of the above settings so I don't know how your laptop will react.

 

Edited by timohour
Link to comment
Share on other sites

3 hours ago, timohour said:

you can check other variables related to the iGPU... I can't tell which one could do the trick.

 

Just checked those settings by comparing A07 to A17

 

Setting: DVMT Total Gfx Mem, Variable: 0x1C8
DEFAULT VALUE A17: 0x3
DEFAULT VALUE A07: 0x3

Setting: Aperture Size, Variable: 0x17D
DEFAULT VALUE A17: 0x2
DEFAULT VALUE A07: 0x2

Setting: GTT Size, Variable: 0x17C
DEFAULT VALUE A17: 0x2
DEFAULT VALUE A07: 0x2

Setting: Gfx Low Power Mode, Variable: 0x178
DEFAULT VALUE A17: 0x1
DEFAULT VALUE A07: 0x1

Setting: Graphics Performance Analyzers, Variable: 0x179
DEFAULT VALUE A17: 0x0
DEFAULT VALUE A07: 0x0

no difference there, if it comes to the Value

Link to comment
Share on other sites

Cooling Mod

So, some info about a little project of mine. Very similar to  timohour's, but with copper. It should be noted that the "tetris" position is the best one, with the space available. Temps are < 7/10° lower (but, after more seconds, it maxes to >99° anyway).

 

20160112_153950.jpg

20160112_155357.jpg

20160112_162247.jpg

20160112_165252.jpg

20160112_165309.jpg

20160112_165318.jpg

  • Thumbs Up 1
Link to comment
Share on other sites

16 minutes ago, Dewos said:

Cooling Mod

So, some info about a little project of mine. Very similar to  timohour's, but with copper. It should be noted that the "tetris" position is the best one, with the space available. Temps are < 7/10° lower (but, after more seconds, it maxes to >99° anyway).

 

 

Running the system without the bottom gives much better venting/airflow, as does using a notebook cooler. However, there's an innovation included in the latest TB3-equipped 15" HP ZBook Studio i7-quad ultrabook that might be of interest. Was for me.

 

They've enmeshed the complete bottom to keep the i7-quad temps down.
 

ZBook%20bottom-650-80.jpg

 

REF: http://www.techradar.com/au/reviews/pc-mac/laptops-portable-pcs/laptops-and-netbooks/hp-zbook-studio-1308737/review

  • Thumbs Up 2
Link to comment
Share on other sites

5 minutes ago, Tech Inferno Fan said:

 

Running the system without the bottom gives much better venting/airflow, as does using a notebook cooler. However, there's an innovation included in the latest TB3-equipped 15" HP ZBook Studio i7-quad ultrabook that might be of interest. Was for me.

 

They've enmeshed the complete bottom to keep the i7-quad temps down.
 

ZBook%20bottom-650-80.jpg

 

REF: http://www.techradar.com/au/reviews/pc-mac/laptops-portable-pcs/laptops-and-netbooks/hp-zbook-studio-1308737/review

 

 

Nice, but it's not worth (for me at least). I'm just waiting one year at most for the Thunderbolt3 eGPU to stabilize, before make the jump to a dell xps 15 or something.

Link to comment
Share on other sites

6 hours ago, sefki21 said:

 

Just checked those settings by comparing A07 to A17

no difference there, if it comes to the Value.


Seems like it is probably  not a setting, but a change in the iGPU vBIOS.

Nothing we can do unless someone is willing to mod the A17 BIOS with A07 vBIOS. Pretty useless, since it works OK with A07.

 

5 hours ago, Dewos said:

Cooling Mod

So, some info about a little project of mine. Very similar to  timohour's, but with copper. It should be noted that the "tetris" position is the best one, with the space available. Temps are < 7/10° lower (but, after more seconds, it maxes to >99° anyway).

 

Nicely done.. This was a great idea using smaller copper pieces.. 7-10° lower is a great advantage... i assume that your fan is kicking now less often when at idle..
And the only drawback seems to be the extra weigh :)

 

I assume that now you can't remove the extra copper pieces right?

Edited by timohour
Link to comment
Share on other sites

10 hours ago, timohour said:

Nicely done.. This was a great idea using smaller copper pieces.. 7-10° lower is a great advantage... i assume that your fan is kicking now less often when at idle..
And the only drawback seems to be the extra weigh :)

 

I assume that now you can't remove the extra copper pieces right?

 

The copper shims? I have already removed them (after test I can say they are useless now). The fan in idly almost never starts now (nice!). For the weight yeah, this thig is bulky as hell (not only for the new copper) :) 

Edited by Dewos
Link to comment
Share on other sites

7 minutes ago, Dewos said:

 

The copper shims? I have already removed them (after test I can say they are useless now). The fan in idly almost never starts now (nice!). For the weight yeah, this thig is bulky as hell (not only for the new copper) :) 

 

That's true... It is worse with the 9 cell battery too..

 

I was talking about the new copper heatsinks though... I saw that you used Alumina Adhesive, so they are no removable, right?

 

Edited by timohour
Link to comment
Share on other sites

On 15/1/2016 at 10:08 AM, timohour said:

 

That's true... It is worse with the 9 cell battery too..

 

I was talking about the new copper heatsinks though... I saw that you used Alumina Adhesive, so they are no removable, right?

 

 

I cannot separate the single pieces of copper from each other, but the "block" is stacked with a single drop of adesive to the laptop, hence mechanically could be separated with a little force.

Edited by Dewos
Link to comment
Share on other sites

1 hour ago, Dewos said:

@timohour can I change my 2x8GB 1600 RAM to 1800+ with just the UEFI variable? (without a XMP flashed profile, I mean).

 

I have initially tried but I finally used the XMP profiles to go to 1866 and then used some PnP Kingston modules to go to 2133.

 

There are two way to OC RAM. One is to use BCLK OC and gain 4,5% more meaning that your 1600MHz memory module will run @ 1672. This works following the guide to unlock your Descriptor and mod your ME FW to allow BCLK OCing.

 

The other is to run with a different multiplier meaning that you can run @ 1866MHz or even 2133MHz (I have seen my ram going @ 2000MHz sometimes when using 2133MHz XMP Profiles that had tight timings.) Some users reported that memory tweaking works, Khenglish though reported that

On 2/11/2014 at 5:43 PM, Khenglish said:

I tried overclocking memory too, but it's still walled at 1600MHz. Underclocking memory did work.

You can try for yourself and report back.
 

This post had everything regarding RAM tweaking variables  by kondilac but somehow are lost (he maybe deleted it?), I don't know why...

 

I am giving you some hints from the part of the IFR file that contains the most RAM tweaking variables.

 

Spoiler

Make sure you select here Custom profile. Otherwise non of your options below will apply Also make sure that you  set all the timing cause if a timing is wrong or missing this will may trigger the BIOS to revert to Default profile.

 

Setting: DIMM profile, Variable: 0x1EE
Option: Default DIMM profile, Value: 0x0
Option: Custom profile, Value: 0x1
Option: XMP profile 1, Value: 0x2
Option: XMP profile 2, Value: 0x3
End of Options

 

Select the Voltage DDR3 is 1,5V and DDR3L is 1,35V


Setting: DDR Selection, Variable: 0x1E9
Option: DDR3, Value: 0x0
Option: DDR3L, Value: 0x1
Option: Auto, Value: 0x2
End of Options


Numeric: DDR Reset Wait Time, Variable: 0x1EA
Default: 32 Bit, Value: 0x9A43D899
End

 

set 0x4 for 1866MHz speed.


Setting: Memory Frequency, Variable: 0x1E6
Option: Auto, Value: 0x0
Option: 1067, Value: 0x1
Option: 1333, Value: 0x2
Option: 1600, Value: 0x3
Option: 1867, Value: 0x4
Option: 2133, Value: 0x5
Option: 2400, Value: 0x6
Option: 2667, Value: 0x7
End of Options

 

This should be for the second channel (ignore this cause there is no second channel available)


Setting: Memory Frequency, Variable: 0x1E7
Option: 1067, Value: 0x42B
Option: 1333, Value: 0x535
Option: 1600, Value: 0x640
Option: 1867, Value: 0x74B
Option: 2133, Value: 0x855
Option: 2400, Value: 0x960
Option: 2667, Value: 0xA75
End of Options

 

Known as Command Rate (CR)


Setting: NMode Support, Variable: 0x1EF
Option: Auto, Value: 0x10
Option: 2N Mode, Value: 0x2
End of Options

 

CAS Latency


Numeric: tCL, Variable: 0x1FE
Default: 8 Bit, Value: 0x4
End

 

RAS to CAS delay


Numeric: tRCD, Variable: 0x1FF
Default: 8 Bit, Value: 0x3
End

 

RAS Prechange


Numeric: tRP, Variable: 0x200
Default: 8 Bit, Value: 0x3
End

 

Cycle Time


Numeric: tRAS, Variable: 0x201
Default: 16 Bit, Value: 0x9
End

 

WR


Numeric: tWR, Variable: 0x203
Default: 8 Bit, Value: 0x5
End

 

Row Refresh Cycle time


Numeric: tRFC, Variable: 0x204
Default: 16 Bit, Value: 0xF
End

 

RRD


Numeric: tRRD, Variable: 0x206
Default: 8 Bit, Value: 0x4
End

 

WTR


Numeric: tWTR, Variable: 0x207 {07 A6 F1 02 F2 02 28 04 02 00 07 02 14 10 00 FF 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00}
Default: 8 Bit, Value: 0x3
End

 

RTP


Numeric: tRTP, Variable: 0x208
Default: 8 Bit, Value: 0x4
End

 

RC


Numeric: tRC, Variable: 0x209
Default: 16 Bit, Value: 0xF
End

 

FAW


Numeric: tFAW, Variable: 0x20B
Default: 16 Bit, Value: 0xA
End

 

 

Even if you don't manage to alter your frequency you will definetely be able to tighten your timings and increse your performance.

 

Edited by timohour
  • Thumbs Up 1
Link to comment
Share on other sites

44 minutes ago, timohour said:

I have initially tried but I finally used the XMP profiles to go to 1866 and then used some PnP Kingston modules to go to 2133.

 

There are two way to OC RAM. One is to use BCLK OC and gain 4,5% more meaning that your 1600MHz memory module will run @ 1672. This works following the guide to unlock your Descriptor and mod your ME FW to allow BCLK OCing.

 

The other is to run with a different multiplier meaning that you can run @ 1866MHz or even 2133MHz (I have seen my ram going @ 2000MHz sometimes when using 2133MHz XMP Profiles that had tight timings.) Some users reported that memory tweaking works, Khenglish though reported that

 

You can try for yourself and report back.
 

This post had everything regarding RAM tweaking variables  by kondilac but somehow are lost (he maybe deleted it?), I don't know why...

 

I am giving you some hints from the part of the IFR file that contains the most RAM tweaking variables.

 

  Hide contents

Make sure you select here Custom profile. Otherwise non of your options below will apply Also make sure that you  set all the timing cause if a timing is wrong or missing this will may trigger the BIOS to revert to Default profile.

 

Setting: DIMM profile, Variable: 0x1EE
Option: Default DIMM profile, Value: 0x0
Option: Custom profile, Value: 0x1
Option: XMP profile 1, Value: 0x2
Option: XMP profile 2, Value: 0x3
End of Options

 

Select the Voltage DDR3 is 1,5V and DDR3L is 1,35V


Setting: DDR Selection, Variable: 0x1E9
Option: DDR3, Value: 0x0
Option: DDR3L, Value: 0x1
Option: Auto, Value: 0x2
End of Options


Numeric: DDR Reset Wait Time, Variable: 0x1EA
Default: 32 Bit, Value: 0x9A43D899
End

 

set 0x4 for 1866MHz speed.


Setting: Memory Frequency, Variable: 0x1E6
Option: Auto, Value: 0x0
Option: 1067, Value: 0x1
Option: 1333, Value: 0x2
Option: 1600, Value: 0x3
Option: 1867, Value: 0x4
Option: 2133, Value: 0x5
Option: 2400, Value: 0x6
Option: 2667, Value: 0x7
End of Options

 

This should be for the second channel (ignore this cause there is no second channel available)


Setting: Memory Frequency, Variable: 0x1E7
Option: 1067, Value: 0x42B
Option: 1333, Value: 0x535
Option: 1600, Value: 0x640
Option: 1867, Value: 0x74B
Option: 2133, Value: 0x855
Option: 2400, Value: 0x960
Option: 2667, Value: 0xA75
End of Options

 

Known as Command Rate (CR)


Setting: NMode Support, Variable: 0x1EF
Option: Auto, Value: 0x10
Option: 2N Mode, Value: 0x2
End of Options

 

CAS Latency


Numeric: tCL, Variable: 0x1FE
Default: 8 Bit, Value: 0x4
End

 

RAS to CAS delay


Numeric: tRCD, Variable: 0x1FF
Default: 8 Bit, Value: 0x3
End

 

RAS Prechange


Numeric: tRP, Variable: 0x200
Default: 8 Bit, Value: 0x3
End

 

Cycle Time


Numeric: tRAS, Variable: 0x201
Default: 16 Bit, Value: 0x9
End

 

WR


Numeric: tWR, Variable: 0x203
Default: 8 Bit, Value: 0x5
End

 

Row Refresh Cycle time


Numeric: tRFC, Variable: 0x204
Default: 16 Bit, Value: 0xF
End

 

RRD


Numeric: tRRD, Variable: 0x206
Default: 8 Bit, Value: 0x4
End

 

WTR


Numeric: tWTR, Variable: 0x207 {07 A6 F1 02 F2 02 28 04 02 00 07 02 14 10 00 FF 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00}
Default: 8 Bit, Value: 0x3
End

 

RTP


Numeric: tRTP, Variable: 0x208
Default: 8 Bit, Value: 0x4
End

 

RC


Numeric: tRC, Variable: 0x209
Default: 16 Bit, Value: 0xF
End

 

FAW


Numeric: tFAW, Variable: 0x20B
Default: 16 Bit, Value: 0xA
End

 

 

Even if you don't manage to alter your frequency you will definetely be able to tighten your timings and increse your performance.

 

 

Something like this one? Worth a try.

 

Setting: DIMM profile, Variable: 0x1EE
Option: Default DIMM profile, Value: 0x0
Option: Custom profile, Value: 0x1
Option: XMP profile 1, Value: 0x2
Option: XMP profile 2, Value: 0x3
End of Options

 

Setting: Memory Frequency, Variable: 0x1E6
Option: Auto, Value: 0x0
Option: 1067, Value: 0x1
Option: 1333, Value: 0x2
Option: 1600, Value: 0x3
Option: 1867, Value: 0x4
Option: 2133, Value: 0x5
Option: 2400, Value: 0x6
Option: 2667, Value: 0x7
End of Options

 

Setting: Memory Frequency, Variable: 0x1E7
Option: 1067, Value: 0x42B
Option: 1333, Value: 0x535
Option: 1600, Value: 0x640
Option: 1867, Value: 0x74B
Option: 2133, Value: 0x855
Option: 2400, Value: 0x960
Option: 2667, Value: 0xA75
End of Options

 

 

Link to comment
Share on other sites

10 minutes ago, Dewos said:

 

Something like this one? Worth a try.

 

Setting: DIMM profile, Variable: 0x1EE
Option: Default DIMM profile, Value: 0x0
Option: Custom profile, Value: 0x1
Option: XMP profile 1, Value: 0x2
Option: XMP profile 2, Value: 0x3
End of Options

 

Setting: Memory Frequency, Variable: 0x1E6
Option: Auto, Value: 0x0
Option: 1067, Value: 0x1
Option: 1333, Value: 0x2
Option: 1600, Value: 0x3
Option: 1867, Value: 0x4
Option: 2133, Value: 0x5
Option: 2400, Value: 0x6
Option: 2667, Value: 0x7
End of Options

 

Setting: Memory Frequency, Variable: 0x1E7
Option: 1067, Value: 0x42B
Option: 1333, Value: 0x535
Option: 1600, Value: 0x640
Option: 1867, Value: 0x74B
Option: 2133, Value: 0x855
Option: 2400, Value: 0x960
Option: 2667, Value: 0xA75
End of Options

 

 

 

Something like this... Don't touch the 0x1e7 variable... It is used for a second channel which is not available on the E6430 and it may cause problems with the stability of your system.

 

If it doesn't work try to set the timings (follow the guide on the previous post)

 

If you don't understand something ask

Link to comment
Share on other sites

2 hours ago, Dewos said:

0x1EE: 0x1 and  0x1E6: 0x4 tried: no changes in CPU-Z (mem freq 800x2) :logik:

 

5 hours ago, timohour said:

Some users reported that memory tweaking works

 

I realise now that all of them either used 1866MHz 2133MHz modules or used Thaiphoon Burner to add JEDEC or XMP timings to their existing RAM  as did Tempest here.

You can try though to set tighter timings to your 1600MHz modules let's say CL 7... It would interesting to test and benchmark with those timings (if applicable).

Try something like 1600 @ 8-8-8-21... or even lower 7-7-7-20...


Seems like there is no other way... Maybe there is some other variable that waits to be found, but I haven't found anything so far.

Link to comment
Share on other sites

  • 2 weeks later...
On 1/10/2016 at 10:10 PM, kondilac said:

The memory controller of this i7-3840QM can run my RAM sticks at factory timings @2133 with no problem, althrough only the slightest BCLK raise freezes the machine. No problem, i am fine @4Ghz 4C/8T

 

hi there! i've got also 3840QM and HX321LS11IB2K2/16 Ram Sticks, but my system doesn't boot. 

 

On 11/14/2015 at 6:48 PM, kondilac said:

UPDATE2: I was also able to boot into windows @2133 CL11-12-13(factory) , when manually setting EFI var 0x1EF (Nmode) to 2N instead of auto. Using 2N mode improves stability, but 1N offers the maximum performance. Memory bandwith R/W/C was around 28k/30k/28k Mb/s. Before running a GFX bench to check for iGPU instability, i've restarted the system. Tried to restart, to be exact, because this functionality is lost, but there are some other settings available in the bios at the memory section, so maybe this could work out better than loosening the timings. I will continue to experiment tomorrow, until then i've reverted back to 1866, which is stable with the factory (tight) timings.

 

is this still up to date? or did you change something else? to which Value should i change the 0x1EF?

 

Link to comment
Share on other sites

4 minutes ago, captnastro said:

 

hi there! i've got also 3840QM and HX321LS11IB2K2/16 Ram Sticks, but my system doesn't boot. 

 

is this still up to date? or did you change something else? to which Value should i change the 0x1EF?

 

You change this to 0x2.


This way you set CR (Command Rate) to 2. Try that and report if it works.

 

maybe you will have to tweak other settings too.

 

Edited by timohour
Link to comment
Share on other sites

2 hours ago, timohour said:

You change this to 0x2.


This way you set CR (Command Rate) to 2. Try that and report if it works.

 

maybe you will have to tweak other settings too.

 

 

Still not able to boot :-/ . Any advise? 

UPDATE: able to boot with 1 Stick, but not with 2.

Edited by captnastro
Link to comment
Share on other sites

16 hours ago, captnastro said:

 

Still not able to boot :-/ . Any advise? 

UPDATE: able to boot with 1 Stick, but not with 2.

 

I was able to boot with my i5-3210M @2133MHZ @CR2 (setting EFI var  0x1EF to 0x2), but reboot functionality was gone as described in my old post. If i recall correctly, i had also set custom ram setting using EFI var 0x1EE to 0x1, to the command rate setting be effective.

 

The 3840QM had no trouble at all booting @2133 with factory timings, I guess i got a better performing one, because other users also had trouble with 2133.

 

First, i would make sure that the BIOS is in factory state. Removing the main battery, and then the CMOS batery for a minute will revert everything to factory settings (also the SATA mode to RAID!!!)

 

And then try to boot with one stick only, and then 2. Please describe the behaviour (black screen only, or you can get into BIOS, etc.) If no success, try loosening the command rate to 2.

 

If 2133 @CR2 does not work at all, try setting  Memory Frequency, Variable: 0x1E6 to 0x4 (1867Mhz). You should be able to boot without problems, at factory timings. If this works out, and You would like to experiment, you should try setting the custom memory settings, esspecially loosening the CAS latency to 12 (I have no idea where did my post with the variables go BTW...)  For this, You have to enable custom ram setting using EFI var 0x1EE to 0x1, then tCL , Variable: 0x1FE to 0xC (=12)

 

EDIT: Maybe try setting EFI var "DDR Selection": 0x1E9 to 0x0, to set the voltage to 1.5V instead to 1.35. Maybe the stick internally regulate the VIN to 1.35 anyway, but if not then it could help. If i will have time, i will also try this, and check if i could raise the BCLK a bit. But most likely the memory controller of the CPU is the weak part of the system, and i guess only loosening the timings will help.

 

 

Edited by kondilac
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.