Question about FSB wall, CPU multiplier for OC'ing

I had a couple of questions about OC'ing the G73JH. I'm able to get to 159 on SetFSB and thought that I was able to get higher on 211 than I was on 213. So I flashed back to 211, realized that there was no difference and jumped back to 213.

After flashing back I went to attempt to go to 161 and I BSOD'ed. I've been talking with j00zl33t and he said he was able to jump over his last OC and is testing now with Prime95. So I took the jump from 159-170 expecting BSOD, but it worked fine (FSB Wall?). After testing with prime95 I got alot of errors and jumped back to 165 and tested fine.

Problem I'm seeing is when I test with TS Bench in Throttlestop I'm able to see that my multiplier is at 13, but when I test with prime its at 12. Is there a reason for this?

Here are some pics:
TS Bench

Prime

 

I just got through wprime with no issues. Still running Throttlestop 1024M right now. About 65% done and yes the multipliers are still about 13.0 with the lowest dip ive seen at 12.77.

So right after this, its safe to say 175pll is stable for me. Still, like i told you and kurtcocaine, I dont know what the hell caused me to break my OC limit. I used to insta-BSOD @ 166+ PLL and now I was able to creep up to 179 PLL without a crash. Im not going to say the BIOS has something to do with your max OC capabilities but.....oh wait....the BIOS DOES have something to do with max OC capabilities!

almost forgot:
http://i.imgur.com/h6acv.jpg

 

Try with Prime95 and see what the multiplier does. I just did it after a reset of the computer and it seems to dip to 12.45-12.65 on stock clocks.

 

Just got through prime95 w/ no errors...phew. CPU temps went the highest I've ever seen @ 78C.

And yes, accdng to TS, multipliers locked at 12.0 during prime95

 

Ok, So I'm guessing that is normal. That is good to hear. I had a freeze on 169 after playing The Witcher 2 for a bit. I'm back down to 165. I'll see if there are any errors on that.

Checking Everest it is showing that my memory is running at 1200, not to bad for 1066.

 

Sigh i'm a greedy moron..

I was happily able to OC to FSB-156 on bios 213 after applying the timing fix. I could do that in 1 jump btw,not small increments, i had a shortcut setup in startup to OC to fsb-155 on startup..

Then j00zl33t told me how he was able to reach pll 175 on bios 209 (not blaming him) so tried downflashing to 209, it froze and rebooted on my usual fsb-155 so i tried small increments and it would go upto pll-158, then i go back to bios 213 (tried both asus site and chastity's page - zip file md5 diff but bios file's same) and now i cant OC like before!! getting stuck at 157, and rebootes on direct jump to 170s

I tried disabling and re-enabling the fix, no joy..

now am on bios 211 to see if its any different, if it isnt will just go back to 213 and settle for 142 fsb.. serves me right for being greedy i guess
BTW TS bench rerorts that setfsb OC to fsb-142 is faster than twinturbo OC to 142, even though in both instances it was running at x13 multiplier

Update : on bios 211 i'm somehow being able to OC again to pll 175ish but anything above 172 and its giving errors in TSbench.. havent tested stability in anything else.. What the hell is up with these bios(s)??? Anyway since i have a disease, i can rest in peace till i go back to bios 213 and try this so get ready to here more ranting as to how i'm a greedy moron

 

Oh joy! More to add into the pile of bad news!

So as mentioned I was at 175PLL stable. Well before when my max oc setting was only up the low 160's, i used to get back to stock clocks (usually when im about to go idle)by enabling and then disabling twin turbo, or just disabling twin turbo if I used setFSB while on twin turbo mode.

Anyway, I wanted to make sure that I can go back and forth from stock to 175pll no problems. ANd guess what? There is a problem. For some reason, I CANNOT get back to stock clocks. Looking at CPU-Z, im stuck with bus speeds of about 142 mhz, which if i remember correctly, are twin turbo values. The value doesn't change even after disabling twin turbo.

So I go into setfsb and choose 'get FSB' and find out the sliders are at 153pll by default. So im like "okay get back up to 175 buddy!". Well, after I set it to a desired pll and click getfsb, it just resets back to 153 pll. No changes made, i.e. no OC.

Been messing with it for 15 minutes now and it wont OC at all. Even after a restart and shutdown, I cannot get back down to stock CPU clocks....

oh boyyyyyyyyyyyyyyyyy

 

That sux. Sorry to hear.

That is crazy though. I KNEW I was able to get higher on 211 before I flashed to 213, and then when I tried, I wasn't able to. According to Chastity, the 209-213 bios's are pretty much the same. Once you get to a place you are happy I would suggest you stick to that BIOS. Somehow, when I flashed back i was able to pull 6 more on SetFSB. I think since you have the same mem as I do we are just hitting a mem wall.

 

Well I got to 175 stable on this BIOS, so im definitely sticking with this one until I find out how the hell i'll get back to stock clocks and OC again. In the meantime Im going to take a break from this OC fiasco and hit up some Witcher 2.

 

yea its completely random.. i got high OC on 213 then changed and got back to it, its gone..
then i got it on 211,changed and got back to it, gone...

now just going back to 213 with 144fsb

Well flashed back 213,now I can go stable to pll 162 but gonna use pll 159(fsb 146) for daily use...
I can believe how unbelievably random and inexplicable this phenomenon is..
If someone has an explanation for it, I'd sure like to hear it..

 

+1
10 char

 

Guys, you need to remember that overclocking is unpredicatable and does not yield the same results for everyone for several reasons.

The RAM you use maybe not necessarily making a difference but it is a factor.

The amount of RAM you use is a factor I can push 10 more PLL by using 6GB RAM than I can with 8GB but less with 4GB.

The voltage the CPU is set to is always going to restrict the amount you can overclock along with the Thermal capacity which plays a big part in the CPU's throttling, lowers temps might not = a higher o/c but overall its better.

Most important the CHIP itself as explained on several posts and by me here is that when testing is done on the I7's before they leave intel into the production line the QM models are only tested to make sure that they pass all required tests and that under maximum stress they can handle being pushed maybe 10% maybe slightly more over their stock capacity which is pretty much what the JH twin turbo button produces from the FSB. The chips are not tested to produce the 20%+ that most of us are getting so around 155-160PLL mark that you are all finding is your highest overclock. Yes some of us can hit higher and that is just pure luck of the draw in a very similiar way 'kurtcocaine' to how obscenely high your GPU can overclock when you have it hanging around 850/1150 which for me locks up without even a cough.

Testing is the best way, pull a RAM stick, try new BIOS as you have done and try to get your temps as low as they can go. At the end of the day if you have some spare cash cough it up for a 920/940XM because then you can push 3.2Ghz with ease over all 4 cores.

Make sure you have applied the Windows 7 timing fix most importantly.

Mine shows 12x at full load also:

 

^ no the inexplicable part here is..
I had pll 175 on bios213 > I went back to bios 209(coz i'm greedy for mhz), it wouldnt go beyond 157> then i come back to 213 and i cant go beyond 160..
Then i go back to 211 i'm getting 170> i go back to 213 and then again back to 211 and now i'm not getting 170..

The part which i dont understand is how the same machine can have diff OC performance on same bios..
I mean i was running 175 stable for a couple of days on 213 and then a bios change and back to 213 i cant get above 160.. just dont understand

 

Did you use the BIOS 213 from exactly the same location that you used in the first place? settings might have been changed or are different from when you first flashed.

Also if you flashed have you reapplied the W7 timing fix??

 

yes and yes

tried every variant of the bios 213 to be sure
btw i see you're running bios 211, how come..?

 

It was a long time ago, on a hot summer's night that I decided it was time and with a firm hand inserted the Flash drive to complete the BIOS flash on my ACER 6920G when it confirmed. CORRUPTION!!!

Took 2 weeks for me to get my laptop back (which for me is like hell on earth) and I vowed from that day to never flash again unless god himself commanded it!

In other words im just happy with 211 and knowing my luck moving up to 213 when there are only minor changes would only result in a curse for me. I stick by my motto to only flash if I have no other option.

This evening dear sir you have proved me correct I will be keeping my lovely overclock ability firmly in place with 211!

 

You guys are a superstitious lot.

@kurt: try resetting your BIOS to defaults to clear out your CMOS.

 

Tried that already, no joy..

I still cant understand what happened there but i'm over it...
Made my 10k vantage run and the higher clocks didnt make any difference in games anyway so happy with 146fsb for now..

 

OH i know that ram speed has an effect on OC, as does CPU and crap luck. I just don't understand how flashing the BIOS to a different one would cause it to allow you to OC more or less.

I didn't reapply the Win timing fix, but did test and it was still correct when I went from 213-211-213. I'm able to get higher now than I was before.

I just wish we could unlink our ram and set clock in BIOS like with the mini.