M11x-R2 Overclocking Guide via SetFSB

I'm happy to report that SetFSB now works to change the FSB on the AW M11x-R2 to overclock further than the bios will limit and also underclock for additional battery life - W0000000T!!! Although I can push it further than what my bios would allow by 6mhz I still can't reach a full 166mhz although same may be able too, as always it's best to take this in small increments to avoid damage. I assume no liability in the event that something is damaged.

So far I have been able to overclock 6mhz than my bios would allow before throwing a BSOD error to 162mhz, and as low as 126mhz so far. I will do additional testing over the next day or two and post screenshots on differences in performance and battery life.

NOTES

This only works on the Registered version of Setfsb v2.3.157.112 or later (There's a donate button on their site and Abo will email you to arrange your keycode). Please be patient as he's an individual, not some big company. He probably needs to sleep sometimes too.

I need some more help in researching other machines as there is a possibility that there exists more than 1 pll in our machines, and my rig is an i7 so the i5's may also be different. In theory this guide should work for any of the machines as the PLL is part of the mother board so give it a try but also proceed at your own risk. I will update the guide as more info is found.

As always additional Overclocking results in additional heat so also make sure to monitor your temps with a reputable program.

The overclock does remain when you restart - just not if you turn off and then back on. It also causes problems with sleep and hibernate - short answer: overclock when you need, not as a general-use option. Use the bios if you want a permanant overclock and SetFSB for boosts on battery life or performance.

If there's anything else you think should be on these notes, please let me know!

SetFSB_HomePage

GUIDE

(edited version of Jstarnino's guide)

1. download SetFSB.

2. Donate.

3. he will then send u an e-mail asking you for some info that you will need to e-mail back to you.

"1. Could you tell me your SetFSB ID number?

2. The SetFSB informations
a. the motherboard(/PC) name ?
b. the chipset name ?
c. the clock generator name ? (If it is possible)"

4. When you get a reply, run SetFSB and skip the first dialog box ( just press ok for now)

5. select the clock generator to "ASUS G73JH".

6. click "Diagnosis" button.

7. click "Get FSB" button.

8. click "Capture" button.

9. send capture image to him by e-mail

10. He e-mails you back the activation key, and type it in the first dialog box that appears when you open setFSB.

After first putting in the code and setting the PLL, quit SetFSB to save the settings. From then on, you won't have to do anything fancy.

1: Click GetFSB
2: Move slider to desired level(stock 133.3 is 140)
3: Click SetFSB

Command line options

-w : Wait [00-99 sec] default=10sec
-s : Set FSB [000-999 MHz]
-i : Increment [00-99 MHz] default=max
-u : 0(default)=normal , 1=ultra
-b : 0(default)=normal , 1=background
-p : PCI-E [000-999 MHz] default=none
-cg[string] : Clock Generator default=none Maximum 15 characters

Thanks and credit for the layout of this guide go to MrPras the author of the M15x SetFSB overclocking guide.

As always I will update the guide as needed.

Thanks, PM me with any questions.

 

This is probably a dumb question, but all it does is let you change the FSB speed from within Windows, right? How can it change at which speeds one's M11xR2 is stable?

 

yes it is a software OC meaning it can do it within windows which means you change OC to nonOC without rebooting. I can report that my maximum stable OC is still 164FSB with using the bios OC and a setFSB OC. This may be more useful for those that are already stable at 166FSB and can push even further beyond what the bios can provide and for those that want to underclock less than 133FSB. There may also be cases where people see more stable software OC then bios OC but I think this will be a rare case.

I can also report that the instructions above worked for my i5 as well thanks for the write up!

 

Not a dumb question at all! I can't say I know for sure why myself, but what I did observe was there was one moment in the boot sequence that it threw a BSOD anytime I tried to go over 156 in the bios. There was 2 times it got past the boot sequence and when it did it ran great in Windows. So I think it must be the actual boot that does something to throw a BSOD.

 

bump just to let everyone know with all the talk of pinmodding that the R2 supports FSB out of box.

 

I think this belongs here. Anyway, I have figured out how to avoid paying for SetFSB by using the manual programming method.

Register 16 is used to control BCLK. I don't know what PLL I have, so I used the ICS9LPRS365, compatible with my M11x. Each step is ~3mhz.

In Register 16, the values accepted are hexadecimal, so the next increment after 39 is NOT 40 but 3A through to 3F and then it's 40.

I am awaiting AnonyMouse to update SetPLL to reflect this change.

 

Register 10 in your screenshot has a value of "03".
Are you sure you dont mean register 16 (the one highlighted in your screenshot)?

If you want I can create a custom PLL.lut file for you, I just need to know which register you want changed (10 or 16)?

 

Register 16 needs to be changed but the SetPLL program is not working. Here is what I mean:

 

I'll make a few changes and upload a copy for you, give me 10 mins.

 

Ok so first I added "U 520" in the CPUmulti.lut file.
I told it that your multiplier is 13 (I hope this is correct, otherwise need to change).

Then I also made a new file called icsunknown.lut, that is your PLL (icsunknown).

So yeah, read the "setpll.txt" file so you know how to use it, and test this version:
http://rapidshare.com/files/448219091/setpll.zip

Currently only one BCLK is possible, 178mhz.
So you would type:
setpll icsunknown 178

 

I'll be waiting patiently for someone to post a core i overclock that exceeds what is possible in the BIOS, with temperature data.

One other question, you say that this can augment a BIOS overclock- can it override a BIOS overclock? Say if I have a BIOS overclock but I want to underclock since I'm only doing word processing or the like?

Also, breadcrumb so I can find my way back.

 

Ok. This was possible for a long time now. I closed IntelBurnTest so I will rerun it tonight and post it tomorrow.

 

This is the greatest program ever made. I remember having my old AW m5550 and this was the only program I could use to overclock, the only other way to OC was to Pin mod (me being not very tech savvy) this program saved my a$$

 

I saw your earlier post, my concern is long term stability. I'm not familiar with IntelBurnTest, how long have you run it for?

Additionally, you probably posted before I ninja edited to cover underclocking. Have you tried that?

 

I ran it for 20 runs. IntelBurnTest uses LinPack and is more stressful then Prime95. I accidentally set it to 200 runs tonight. That means it'll take 16 hours, much longer and stressful then my standard Prime95 overnighter. I think that is long term enough. (Maths: (300s per run * 200runs) / 60 for minutes, then / 60 for hours)

I haven't tried underclocking but CSufy over at the Supercharge thread did.

 

I take it you were logging with throttlestop and that 81°C was the highest logged temperature? What was your BIOS overclock during this test?

 

Yes, 81C was max temp. My BIOS overclock was 166mhz.

 

Last question, is 177.7 the highest you tried or the highest stable overclock?

 

178 is the highest stable overclock I got. I think RAM ties into this- most R2 owners are topping out ~180mhz, whether they are i5 or i7.

 

Have you got setpll working now?

 

Yeah 182Mhz was the most far I can get. It's prime stable under full load, but when it goes idle and 17x multiplier the system freezes.

Lets buy better RAM

Edit: I think not RAM is the problem since it's only at 547Mhz @ 182Mhz BCLK

 

Wow, 3 Ghz? Starting to think I should have gotten an i7!

 

Ok, first off, the stability test:



I know it's incomplete but after 166 runs, you get the point.

I think RAM is a major factor in overclocking R1 and R2s. If you removed the 17x multiplier, say by using Orthos to load both cores at low priority, can you go any further?

The problem with the RAM is that we have it running at CL6 so we are effectively overclocking it once we are past the SPD entry for CL6, 457mhz. To run at 1066mhz, we need CL7 timings and nobody tried editing the SPD on an R2.

Yes I have but it's a mess between your code and nando4's. Check it out here.

 

Not sure if you need it, but I filled out your frequency table a bit:

Code:

:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

:::::::::::::::::::::::::::::::
:: PLL:    icsunknown
:: SYSTEM: Alienware M11xR2, U 520-1.7 (133-202 Bclk)
:: FREQS:  133-202Mhz
:: AUTHOR: DavyGT
:: BUGS:   NA
::         NA
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

:::::::::::::::::::::::::::::::
:: Initialisation strings
::
:: [setfsb diagnosis window OR r-w "Clock Generator" appearance ]
:: 00 01 02 03 04 05 06 07   08 09 0A 0B 0C 0D 0E 0F
:: 10 11 12 13 14 15 15 17   [      local3         ]
:: [      local4         ]   [      local5         ]
::
:: Converts to be in the following format below
::
:: set local0=0x0706050403020100
:: set local1=0x0f0e0d0c0b0a0908
:: set local2=0x1716151413121110
:: set local3=..................
:: set local4=..................
:: set local5=..................
::
:: The byte(s) that change during FSB changes is substituted with
:: the strings [PLL_B1], [PLL_B2], [PLL_B3], [PLL_B4] and [PLL_B5]
:: from the LUT below. Ensure localx is 64-bit (16 chars), 
:: pad with 00 if needed.
::
:: bytecount = number of bytes to be send to the PLL
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

::::::::::::::::::::::::::::::::

set bytecount=0x16
set local0=0x1100FFFFFFFFA529
set local1=0x98A5B71207032583
set local2=0x00008F8F0631D8[PLL_B1]
goto exit

:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

::::::::::::::::::::::::::::::::
:: This is a look up table only.. this code is never run as part of 

the batch file
:: LUT for ICS9LPRS397 PLL based on placing the two PLL byte that 

change in setfsb 
:: when move the slider noting the FSB they correspond to 
::
::[FSB], [PLL_B1] (byte 13), [PLL_B2] (byte 14) triple entries.


133, 33
136, 34
139, 35
142, 36
145, 37
148, 38
151, 39
154, 3A
157, 3B
160, 3C
163, 3D
166, 3E
169, 3F
172, 40
175, 41
178, 42
181, 43
184, 44
187, 45
190, 46
193, 47
196, 48
199, 49
202, 4A

:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

::::::::::::::::::::::::::::::::
:: Ensure the exit below is the last line

:exit  

Hope that's done correctly. If it is, I can add it to the table in the pll pinmod thread.

BTW thaiphoon burner should let you change the CAS, but I have found that no ram likes an 800mhz@CAS 7 entry.

Don't know what frequency your ram runs at.

 

I built my own table as each increment is 2.7mhz, meaning each step is not an even +3mhz (from rounding off).

Code:

::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: PLL:    m11xR2
:: SYSTEM: Alienware M11xR2, i5-520UM 
:: FREQS:  133-233Mhz bclk
:: AUTHOR: DavyGT@NBR
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
:: Initialisation strings
::
:: [setfsb diagnosis window OR r-w "Clock Generator" appearance ]
:: 00 01 02 03 04 05 06 07   08 09 0A 0B 0C 0D 0E 0F
:: 10 11 12 13 14 15 15 17   [      local3         ]
:: [      local4         ]   [      local5         ]
::
:: Converts to be in the following format below
::
:: set local0=0x0706050403020100
:: set local1=0x0f0e0d0c0b0a0908
:: set local2=0x1716151413121110
:: set local3=..................
:: set local4=..................
:: set local5=..................
::
:: The byte(s) that change during FSB changes is substituted with
:: the strings [PLL_B1], [PLL_B2], [PLL_B3], [PLL_B4] and [PLL_B5]
:: from the LUT below. Ensure localx is 64-bit (16 chars), 
:: pad with 00 if needed.
::
:: bytecount = number of bytes to be send to the PLL
:: ensure last line is "goto exit"
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

set bytecount=0x16
set local0=0x1100FFFFFFFFA529
set local1=0x98A5B71207032583
set local2=0x00008F8F0631D8[PLL_B1]
goto exit

::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: This is a look up table only.. this code is never run as part of the batch file
:: LUT for ICS9LPRS397 PLL based on placing the two PLL byte that change in setfsb 
:: when move the slider noting the FSB they correspond to 
::
::[FSB], [PLL_B1] (byte 13), [PLL_B2] (byte 14) triple entries.

135, 32
138, 33
140, 34
143, 35
146, 36
148, 37
151, 38
154, 39
156, 3A
159, 3B
162, 3C
164, 3D
167, 3E
170, 3F
172, 40
175, 41
178, 42
180, 43

::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: Ensure the exit below is the last line

:exit  

My RAM runs at 533mhz CL6 (Ratio is 1:3). I haven't got around to trying ThaiPhoonBurner again but in the past, when I did test it, it couldn't boot with 1066/1333mhz RAM with a minimum CL7 SPD entry.

 

3Ghz its only when the Multi jumps up to 17 when only one core is in use. Does this happen often and is then when the laptop will crash?

Also is the multi 14 on the i5 with single core use?

Cheers

 

Yes, the multiplier is 14 with a single core loaded.

 

Thanks DavyGT! The setpll worked like a charm on my i5. Testing stability now. Is there another thread about this? I kind of stumbled upon this by accident.

 

This thread details how you can modify the memory so you can further overclock, should memory be a barrier.

I can't think of anymore threads like this one. Maybe the benchmark thread if you can find it?

 

So I want to try this out, but how do I find out this information to send to him?


2. The SetFSB informations
a. the motherboard(/PC) name ?
b. the chipset name ?
c. the clock generator name ? (If it is possible)"


also, when overclocking in Setfsb, are you still overclocked in bios? My computer is stable at 166mhz, I want to see how high it could go.

 

Thanks Davy ~

Ironic thing is that I installed some 1333 memory from GSkill, and it performed worse than stock ram O.O;;

Is there any way to make the settings more permanent instead of running the script at startup?

 

a. the motherboard(/PC) name ? Alienware M11xR2
b. the chipset name ? Intel mobile QS57
c. the clock generator name ? (If it is possible)" I don't know. Looks like a 397 or 387. You'll have to pull apart the R2 to check.

Yes, I am overclocked in BIOS with SetPLL.

1333 RAM is already included with the M11x so unless you have upgraded to 8GB, it will perform similarly due to CL6 timings.

I don't think there is a way make it more permanent without the script.

 

Looks like I can't go over 166. Could I it be my memory holding me back? I got the stock 4gb

 

call me a noob but how would I add U 640 to CPUmulti.lut? when I'm in cd C:\setpll it tells me I have to add it.

 

New versions of SetPLL removed CPUmulti.lut so it should work without changing anything.

Possibly. Try taking one stick out and see if it's more stable.

 

Latest setpll is here:
http://forum.notebookreview.com/har...clocking-methods-examples-84.html#post7153216

 

First off. Hazard and Davy thanks for this (I was going to donate $10 but this way better)
I am getting 180 BCLK stable. How can I add more increments? I would like to go until I get a BSOD.

 

Here is a modified version of SetPLL with higher limit. Do note I haven't tested any speed greater then 180 so they maybe off by a few mhz + or -.

 

Thank you very very much.

 

Nope didnt make a difference. Guess my CPU just isnt meant to go above 166 lol. Itd great if I could somehow get it to go higher.

 

Honestly try the better RAM. Currently I can't get over 182 MHz but once I get 8GB RAM with 1333 MHz or something (I was thinking Corsair) I bet I can OC my i7 more. Currently I am happy with a 3.1 OC but its more stable at 3.0. I got one BSOD at 182 after a bit of playing around so 3.0 for now until I get the RAM

This thing is a total beast now... And also the setPLL seems to be making my cpu throttle less without TS on or I could just be noticing the higher clock speeds?

 

You can a RAM SPD mod to force slower timings right now if you have a 32bit OS. Getting a new set of 1333 RAM won't make too much of a difference when it is still running at CL6- DDR3-800 timings.

That 17x multiplier is a killer to the dual core clock speed though.

You are noticing higher clock speeds- SetPLL and Throttlestop have completely different applications but in this case, are essential together- SetPLL increases the clock speed, Throttlestop lets you keep it.

Try swapping for the other stick. That stick might just be limiting you.

First i7 to 200BCLK will beat an R3.

Hopefully.

 

I went out to microcenter and bought Crucial 1333 ram, 8gb total and now my OC isn't stable past 164.

Back to the store it goes tomorrow and I'll stick with this memory. Ill eat the 15% restocking lol. This is the one I had http://www.microcenter.com/single_product_results.phtml?product_id=0352108

Do you guys have any suggestions for memory that's proven good for oc?

 

Wait so you're saying that I won't notice OC difference from 4GB RAM to 8GB? I understand the 64 bit 800 mhz limit though.

 

It's pretty much luck of the draw. I found sets of stock 4GB Samsung RAM on the R1 to all overclock differently.

You should try an SPD edit using Thaiphoon Burner to force slower timings because you're pretty much banking on luck (ie: buying a good kit that can OC better) without changing the timings.

No, you won't notice a difference since the timings (CL6) are the same. You need to force it to run at slower timings if you want to improve OC, provided RAM is the factor causing instability, not core voltage or high frequency. You can have DDR3 1600 clocking similarly if the timings don't change.

There is no 64bit 800mhz limit...

 

I guess luck is not on my side lol.

I tried two different sets of 8gb memory (4gbx2 Corsair, and 4gbx2 Crucial) and I couldnt get it to boot stable at 166mhz.

Funny thing is, I could go 176mhz stable with just 2gb memory. Is it all luck of the draw? Should I try a different brand of memory? I want to be stable at 166 with 8gb lol.

 

I don't know how applicable desktop overclocking logic applies, but it could be that the motherboard can't sustain the additional load of two sticks. Have you tried just 1 4Gb stick?

I also lucked out ~ I can get around 185 stable on my i5 with 8GB of ram.

Edit -- I also noticed that I received different overclocking results when I used my SSD over my mechanical drive. I don't know how that happened.