How to Use SetPLL to overclock your R2 over 166

Yea setpll is sweet

 

Can't wait to get mine so I can start playing round and OCing it!
With 8GB RAM is it X2 4gb sticks or x4 2GB? I guess if I have a bad stick I could stick with 4GB (On the best Stick) and a higher OC rather than a poor OC and 8GB of ram.

 

It will be 2x4GB. It depends on the difference between the sticks. If both sticks are 3-6mhz apart, just keep the 8GB RAM, you'll notice more of a performance boost with more RAM then insignificant clocks.

I should collecting RAM IC codes so we can get a rough idea of how much RAM modules can OC.

 

What a PITA there were loads of R2's on the outlet this morning. I check back 10 mins ago and there are non! Looks like i'll have to wait again for more voucher codes etc to come up.

I'll be doing HD video editing so the 8GB probably will be more use. Since i'm using powerdirector which can use CUDE to help with encoding I think it should work quite nicely.

 

Finally got around to doing this. I tested at 185 and was stable with 25 runs of Intel Burn Test. 188 shutdown the laptop after 7 runs or so, and anything higher than that messes up the picture and will turn off the laptop after a few seconds. Thanks again DavyGT for the easy to use guide. Oh, your "Flash the R2 BIOS to enable .95V and higher overclocking" link is broken, it has a line break command added to it when you click on it.

 

This isnt working for me. When I run the setpll m11xr2 command I get the error: "setPLL: No .lut for 'PLL 'm11xr2.' Please create one.

What am i doing wrong?

 

Use 'setPLL Alienware-m11xR1 [BCLK]' in the newer setPLL 1.0f version. The 1.0e version that DavyGT describes used 'setPLL m11xR1 [BCLK]'.

I renamed the .lut files in this newer version to include the system vendor.

 

*EDIT* I am tired and dumb. Thanks for the help.

 

The [BCLK] above means put in the value you want. Run it with 'setPLL Alienware-m11xR2' to see what [BCLK] values are defined.

 

^Yep, got it last night, thanks.

Had another question, though. I have the CPU OC in bios to 166. Im using this mod to OC to 170 and Im also using Throttlestop.

When I launch CPU-Z it shows my bus spd is always 167. Last night it was stuck at 133? Does this value continually fluctuate or is there something I am maybe doing wrong? I figured it would show 170.

 

Some M11x laptops have a problem where the overclock you set in the bios is sometimes ignored. It seems to happen randomly every second or third or fourth time you boot up so you will need to check what speed you are actually running at after you boot up. This is a bios issue and I don't think there is any solution for it yet.

 

Well that sucks. Ive done 4 reboots and its staying at 133 now. It reset on me last time when the machine went to sleep and now it seems to be stuck at 133. Way to go, Dell.

Even when it does work - any idea why it never shows more than 167 when I used setpll to go to 172?

 

Please ensure you've disabled UAC. Hit ALT+R, type 'cmd', then type the following and post the results:

Code:

cd \setPLL
setPLL -read
setPLL Alienware-m11xR2 170
setPLL -read
setPLL -report

 

Just did this and rebooted. Still stuck at 133.

Seems like the only way I can get it back to 167 is to reboot, toggle OC in the bios, then log in to windows. But it still never goes above 167.

Im running the custom A03 bios to flash the 335m voltage.

 

If it can't get above the bios-set 167Mhz OC then setPLL isn't setting your PLL for some unknown reason. Please post the output of the commands in my previous post to confirm.

 

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>cd \setpllv2d

C:\setpllv2d>setpll -read

SMBus Read: Mode=BLOCK, Address=0xD2, Start=0x00, End=0x11
00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 0123456789ABCDEF
00 21 A5 FF FF FF FF 00 11 83 25 03 07 12 B7 A5 D8 !........%......
10 31 D8 1.

C:\setpllv2d\myPLL.lut created with [INIT] containing this PLL data. Further
instructions to complete your PLL's definition are within myPLL.lut.

C:\setpllv2d>
C:\setpllv2d>setpll Alienware-m11xR2 170

setPLL: sending#1 BCLK@170=3F to the PLL via rw.

cpu.bat: CPU=U 640, CPU_BCLK=170Mhz. Full cpu details in C:\setpllv2d\cpuzinfo.t
xt.

C:\setpllv2d>
C:\setpllv2d>setpll -read

SMBus Read: Mode=BLOCK, Address=0xD2, Start=0x00, End=0x11
00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 0123456789ABCDEF
00 29 A5 FF FF FF FF 00 11 83 25 03 07 12 B7 A5 98 )........%......
10 3F D8 ?.

C:\setpllv2d\myPLL.lut created with [INIT] containing this PLL data. Further
instructions to complete your PLL's definition are within myPLL.lut.

C:\setpllv2d>
C:\setpllv2d>setpll -report

cpu.bat: CPU=U 640, CPU_BCLK=170Mhz. Full cpu details in C:\setpllv2d\cpuzinfo.t
xt.

C:\setpllv2d>

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

I set up a task in task scheduler to start running the setpll.bat file everytime i log in as well.

 

Looks good. 'setpll -report' parses cpu-z output to confirm the BCLK is 170Mhz as requested. The PLL dump from 'setpll -read' also confirm it's been set to 170Mhz.

So it's all good. You can run go to the \setpll\cpuz directory and run cpuz for a visual confirmation.

Do note that you'll need to run 'setPLL Alienware-m11xR2 170' on every reboot and resume-from-standby/hibernate to get it back to the 170Mhz BCLK OC state as the PLL state is reset after those activities.

 

Ah, gotcha. I think I see the issue now. When I run the cmd and check CPU-Z immediately after it DOES reflect the OC. I thought that by setting a task to run the setpll.bat file on reboot it would automatically run the process again and OC it?

 

I assume it would as well but I don't use that method. Instead I've modified the AC/DC lines in \setPLL\automated\resume-setpll.vbs and put a shortcut to it in my startup folder. That way I get an OC state on bootup and on resume-from-standby/hibernate.

 

Thanks again for all your help. I went ahead and just created a batch file to run the command line when i log in.

 

Hi guys,

you are all talking about overclocking with the stock-RAM...

Has anyone of you tested this kind of oc with 1600Mhz-Ram.
You have the possibility to go to 200Mhz FSB without (RAM)-Problems.
I think I will buy a set of them - but has anyone tested this?

(Maybe the CPU will limit the oc with this high fsb?!)

Greetz,
Michael

 

The R2 only needs the memory to go to 1200mhz for 200BCLK. (200x3= 600mhz DDR3. 600mhz = 1200mhz effective DDR3)

The problem with buying 1600mhz RAM is that the M11x R1 and R2 will try to use the lowest possible timings, in most cases, CL6. Running at 1600mhz DDR3 would require very high timings such as CL10 or CL11 and the R2 just won't boot with CL9 and higher. The M11x will instead run at the lowest timings supported by the 1600mhz memory, if it is under CL9.

 

Hi,


so 1333Mhz would be enaugh?!

In my opinion, the FSb between CPU an RAM is linked, isn't it?
So when I use a fsb of 170 Mhz, the ram will do the same.....!?

with 1333Mhz Ram you could go up to an fsb of 222 Mhz?!
Why isn't this possible? Chipset, cpu,....?

 

I'm so sorry.....
I didn't realy think about the "real Mhz" ;-)

I have the "stock" Ram (Samsung - 10600)...

so it can run up to 1333 Mhz - which means: 222Mhz FSB (?!)

I just make a check, and it still runs at 666,7 Mhz(=1333mhz effectiv) (which has the highst timing of CL9).



So why am I not able to set fsb higher 170Mhz...?
The ram is not limiting this, correct?

 

It's not about how fast the RAM is rated as timings will scale up to accommodate higher speeds. It's about the quality of the RAM itself and that can't be foreseen easily.

CPU and RAM is linked by a 3:1 ratio. So if you set 170mhz BCLK, RAM will be running at 510mhz, effectively 1020mhz.

1333mhz needs to be overclocked with CL8 timings to reach 222mhz as 1333mhz requires CL9 timings that the R2 does not support. If the SPD mod does not increase clocks then either the CPU or chipset doesn't have enough voltage.

 

I'm sorry again but i dont know where I am thinking in the wrong way....


My RAM is able to handle a speed of (effektiv) 1333Mhz (with CL9 timings) and (effektiv) 1066Mhz with CL7.

As I see with some tools: my Ram use CL6-timings (which means: 800Mhz effektiv and an FSB of 133Mhz.....

so it is possible to make him use the CL7-timings?

If yes - how?

 

It is possible to run the RAM at CL7 by using a 32bit OS and Thaiphoon Burner 6.3 attached to the first post here to edit the SPD.

 

Sometimes I think Davy is speaking another language... xD
I got no idea how RAM effects an overclock even though hes explained it a 100 times
Any literature you can suggest to help me better understand overclocking factors?

 

thanks so much used your gpu oc and about to start stress testing with this to see where I can get stable OC's.

 

Well, I am able to OC to 170 - but if I go to 172 I get a BSoD. I was going to flash the RAM but I couldnt figure it out at all. No guides that I could find which really explain how to use Thaiphoon.

 

OCed to 185 with TS. No problems for the past couple of days. Been playing crysis 2 just fine. temp stays below 80c.

 

Anyone that has overclocked beyond 166 MHz, can you try running WinTimerTester and post your results so I can see how this affects your Windows high performance system timer?

WinTimerTester 1.1
http://www.mediafire.com/?xzo9n84d8lze9nb
http://www.sendspace.com/file/xadvhe

Head over to this thread to find out more.

http://forum.notebookreview.com/gam...must-read-setfsb-o-c-game-problems-fixed.html

If this is also a problem for the M11x-R2 when using SetPLL then maybe DavyGT can add the above link to the first post in this thread.

 

I didn't run WinTimerTester, but I did OC my M11xR2 to 175, and experienced skipped dialog in Crysis 2. So the problem definitely exists.

 

Hi - I have the exact same problem:

I would make an "how -to" (if I know what to change where).
My only hope is DavyGT - He did it - can you please tell me how?! (see my own post about change the SPD).

THANKS !!!!

 

i believe there is a way to get 7-7-7-20
i think it was posted in a thread called "the real_b13_worklog"

 

Hi,

i just checked this thread - no hint how to change the the timings...

 

did you read through all the pages? i know theres some info lodged in there somewhere lol.

 

Hey Davy, very nice, but do it (SetPLL) reduces the CPU lifespan? And other question, how can I disable SetPLL after? Doing its instalations implies that I need to overclock always by SetPLL and not anymore by BIOS since it?

Other thing: I don't have a .lut for my m11x r2. How can I create one?

 

(Sorry about the double-post, but they are different subjects)

Ok, I just did the SetPLL, but I'm having BSOD on anything beyound 170 Mhz (and even on 170 Mhz I got a BSOD). This is normal right? Means that my CPU is not powerful enough to handle this frequency? I.e., I didn't had so much luck with my CPU chip?

Other thing: I added the setpll.bat on Startup folder. But everytime that Windows starts I need to confirm the overclock with a CMD pop-up appearing on desktop? Thanks.

 

Hi,

I just make my to 170Mhz - i cannot go any further, too....

@hadou:

How did you manage to get about 2900Mhz CPU frequenze.....
When I use 170Mhz FSB - i get about 2350-2400 Mhz.....

 

Using ThrottleStop (AC plugged always when using it), TPL 70/70, TDP/TDC at options 8.

 

I can't find anymore the PLL for the m11x R2 to download, where can I find it pliz?

 

http://forum.notebookreview.com/har...clocking-methods-examples-87.html#post7170384

 

Hi, do I have to first use the BIOS to overclock to 166 THEN use SetPLL to continue overclocking? Or can I begin my overclock with SetPLL?

 

Hi,

you can use both ;-)

The Bios-Option for overclocking and setpll send the same "information" to the chipset - so it doesnt matter what you use.....

you can do it all with setpll if you want to ;-)

Greetz,
Michael

 

Cool thanks. Which would you recommend? Does one create more stable overclocks than the other?

 

No - they do it both the Same way.....

Pro for BIOS:
- you don't have configure it every system boot.

Pro for setpll:
- you can Change FSB without reboot!
- you can oc FSB to more than 166Mhz

 

When you say I have to configure it every system boot, does that mean I need to overclock it again everytime I reboot my laptop?
I can do step 7 of DavyGT's first post to automate it right?

 

Hi,

the Bios sets the FSB automaticly on every boot.
If you want to change anything further, you have to do it by your own - every start!!

Setpll works only as long as you do not shut off your laptop.

Of course you can create some automatism to run setpll every systemstart ;-)

 

Can someone answer pliz? Thanks.