Does anyone have the PLL number for this notebook so i can overclock it with setfsb?
-
jacobxaviermason Notebook Consultant
Yep, it's ics9lpr604aglf. I've got my G50VT-X1 up to 2.95 ghz so far. Not sure if the crashes beyond that are due to a lack of sufficient voltage or because the ram is clocked too high...must experiment.
Somebody was claiming that when you raise the fsb the pci-e speed increases to and affects the graphics card clocks, but this is certainly not the case with my 9800M GS, because I can still overclock it the same amount for 3dmark06.
Pretty awesome CPU score for a P8400.Attached Files:
-
-
Wow, that's really good. What's your CPU temps?
-
jacobxaviermason Notebook Consultant
Better yet, try ICS9LPR363DGLF. This one even displays the right FSB, and is more reliable for changing the pci-e speeds.
At 2.9ghz, the 3dmark06 cpu tests got one of the cores up to 58C and the other to 67C, so I'm nowhere near dangerous temps. Before overclocking, though, I don't think I ever saw it hit 60C. I am currently in a 60F basement though, but I think this is also due to the 45nm, 25 watt processor along with Asus' generous notebook fans.
I'm thinking my ram may be the bottleneck--it's up from 800 to 1023mhz... -
Thats not fair!!! lol
I got a T9400 @ 2.53 and i cant even use the directconsole to overclock to the highest level... My video starts to crash in games... I am in guess its the RAM cant handle the clocks... The PCI-E buss does not change based on what setfsb shows... Now only if my darn RAM would let me at least OC to the factory max from asus, lol -
Well, somehow I managed to break my lappy...I tried out setFSB using the recommended PLL, got the 2.7GHz, and then it reset. Now ANY amount of overclock at all from either setFSB or Direct Console results in, oddly enough, my ethernet port not working. I'm confused.
-
Well here is an odd one on mine... I thought the memory is what made my video go nuts during a game while I was overclock... Well I ran a few 2 hour long memory test from windows that also max the CPU and no errors... So i dont know whats up... Maybe SetFSB does something else its not reporting that it shouldn't?
In your case CA36GTP, I would say that the stress may have pushed your network card to its death... It is possible to damage things overclocking, even if not changing voltage... Its not common but can happen. I dont ever use my wired port, always wireless so I wouldnt know. -
Strangely, it works at stock 2.26GHz, but even setting it to the second setting in Direct Console makes it die.
-
Have you just been rebooting or have you tried a full shut down?
It was nice to see how far you got on a 2.26...
I am going to get the p9600 which is 2.66 @ 25w 6mb 1066 when they come out in the next few weeks... Less power, less heat and faster... In your case maybe you should think about doing the same? CPU prices are dropping and when these new models come out in the next month you will find great deals to upgrade yours. -
Yea, didn't make it near where jacob did with the same CPU, though. And he didn't kill anything. Guess that's just the unpredictability of overclocking =(
I'm following the P9600 as well. -
You can actually find some eng. samples on eBay very cheap right now... They got a crap load of them listed... I was almost going to buy one but right at checkout decided to just wait.
I dont get the network being dead though even with a little overclock. Maybe its something software messed up... Try to get one of them bootable CDs and get one with network drivers to try...
Or you can reinstall, but we all know how fun that is, haha
I myself think I am done with SetFSB.. I dont trust it. Its not even really for our chipset so who knows what else can happen. I just miss it because using this other LCD mod cant overclock because no direct console. That and cant control the back lights than also... I hope they get the drivers for the lights done soon for the touchpad and the lid. -
jacobxaviermason Notebook Consultant
I wish I could offer more productive advice, but I will note that you guys are right that the system needs a full reboot to return to default settings--unplug, remove battery, press power button...
I did find that creeping up slowly on the higher frequencies worked much better than just trying to jump to them from stock. going straight to 2.9ghz just gives me a BSOD. The best I've hit so far is 2.994--temptingly close to 3ghz.
I haven't done any detailed work with it yet, but if you think that "underclocking" your ram might help you could try memset ( http://www.tweakers.fr/memset.html). It doesn't seem to allow reducing the frequency, but you can at least relax your memory timings. -
Hey guys this looks like the right thread to put this in (if its not forgive me im new here lol) Anyway I have been trying for a few days now using various programs to oc my g50v-x1 first gen (t5750 processor, orange and black). I tried to use both of the pll's found in this thread but both times my laptop simply freezes once i hit set fsb in the setfsb program. I just updated to bios 210 and i do have the old 202-yes 202 even though asus said that the first bios was 203. I cracked open the case today and couldnt find my specific pll so I'm at a loss as to what I can try.
Any help would be appreciated, thanks
ps The values that I tried to use for the fsb speed was the same that is used in the direct console extreme mode which is 183.x mhz - I figured I knew that everything worked at this speed so I would try it first. I increased the pci speed (the second slider in the program) by the same percentage that the first was increased -
jacobxaviermason Notebook Consultant
Quadrunner, if you have a T5750, then you probably have an older Santa Rosa mobo, so I'm not sure that the same pll's would work in the first place (though the fact that you are crashing your system is an indication that something is happening).
Anyway, don't rely on setfsb to display the proper fsb, pci, or even cpu speed--definitely get CPU-Z for that.
Also, you shouldn't try touching the PCI slider at all while you're just trying to OC the processor (the PCI speed on most laptops can't really be changed in any event).
You should: 1. select the correct pll. 2. click get fsb. 3. move the fsb slider up a few clicks. 4. click set fsb 5. check CPU-Z to see if you are really affecting the fsb (and hence the cpu).
If neither of the pll's we've been talking about here work, you might just go through the list and try every one--that's what I had to do in the first place.
On a side note, if your laptop is a Santa Rosa (instead of the newer Montevina) you probably have 667mhz RAM.
The limiting factor for overclocking most newer G50's is that the RAM is already at 800mhz and when you OC the fsb, the RAM increases proportionally leading ultimately to memory errors and BSOD. But you can't buy faster DDR2 RAM.
In your case, if you RAM is preventing a higher overclock you could upgrade to 800mhz RAM and potentially push your fsb and cpu a lot higher.
Hope this is helpful. Let us know if you get it to work. -
Wow awesome response time!
According to Everest ultimate the following is my mobo:
Motherboard ID 64-0100-000001-00101111-010809-Cantiga$G50V0100_BIOS DATE: 01/08/09 VER: 210
Correct me if im wrong but I would believe that since I have a Cantiga board I would have the newer Montevina setup?
Regardless of everything else I am 100% certain I have 4 gigs of 667mhz ram.
Thanks for the advice and I'll give not touching the pci slider a try and cross my fingers.
Thanks again, and please keep me updated if anything pops into your head. -
Using the ics9lpr604aglf pll I was able to get to a tick over 2.3ghz before the laptop bsod. The bsod error was DRIVER_IRQL_NOT_LESS_OR_EQUAL. Also, after restart after the bsod none of the settings stuck-I'm assuming it's because of the bsod. I'm going to try the other pll again and see how that goes.
Update:
I tried the other pll and it instantly freezes and bsod's
Went to Windows 7 (dual booted with Vista) and tried the aglf pll there. I got to 2.3, then bsod. Same error as before. Unlike last bsod, the laptop auto-restarted after this one and when going back into Windows 7-my settings stuck! Next I got it up to 2.4. Bsod, error in system32.sys. Auto restart and then I got it 2.5ghz!! Then i figured, (after hitting capture of course), that I should restart and see if the settings stuck-they didn't. Tried again and I made it to 2.3xx and then it bsod with the very first error with auto restart. Booted up both os's no new clocks all back to default. I'm really not sure what to do to get these better settings to stick-IF I can even get back up that high.
Upadate:
Back in Vista I tried again and it didnt quite make it to 2.3ghz before it bsod and said that it had lost a critical process or something like that. It dumped and then failed to auto restart (exactly the same as before it seemed).
*** STOP: 0x0000000F4 (0x0000000000000003, 0xFFFFFFA800A72A040, 0xFFFFFA800A72A278, 0xFFFFF80002CFCE10)
One of the other errors-I cant remember which(somewhere in the middle), had both of these
*** STOP: 0x000000D1 (0x00000000326963C8, 0x0000000000000002, 0x0000000000000000, 0xFFFFFA6002F4E391)
*** usbehci.sys - Address FFFFFA6002F4E391 base at FFFFFA6002F4D000, Datestamp 479199d5
After googling I found that thats a usb driver error. I dont think that I have gotten this error before now. I have plugged in my mouse and usb chill pad.
Update again:
Replicated IRQL error again at 2.3ish ghz in Vista.
*** STOP: 0x0000000A (0x00000000000000DA, 0x0000000000000002, 0x0000000000000000,0xFFFFF80002A6667)
Ran Prime 95 at 2.25 and 2.243 got fatal error specified as a hardware error right away at 2.25 and it took about 3 minutes for that error to show up at 2.243. Ran again at 2.2 (same as the extreme setting in the direct console) and it was steady as a rock -
what is PLL??
-
jacobxaviermason Notebook Consultant
One popular way to overclock is the raise the front side bus (fsb) of the motherboard, causing the processor, memory, and sometimes pci speeds. This is especially common in overclocking laptops because it's easier to overclock the entire motherboard than to raise the processor multiplier (that's actually impossible on most laptops).
You're right, Quadrunner, that is a Montevina board, sorry about the misinformation. And the fact that you can OC at all means that you are using the right plls.
A usb driver error, though, probably means that your overclock is messing with the pci link speed, so if there's another pll that works, I would try that one. (On my G50VT for instance the 363 pll overclocks the pci-e link, causing video card crashes at lower overclocks, whereas the 604 just affects RAM and CPU.)
I'm not sure what you're running into to prevent a higher overclock--it could be the cpu or the ram (or some pci device if you have a faulty pll number). My max overclock on the RAM is about 32%, though I can only run games and whatnot at a 21% overclock. If you're at 2.5, you may be limited by the RAM then.
The IRLQ error, I believe, means that your page file (i.e. hard disk space used as ram) was accessed too fast, and failed. Not sure if that means anything special though.
Good luck. -
-
Update:
I tried all the pll's in the program-some of them actually just froze the program up forcing me to restart anyway...
The new data from today (all in Vista)is:
ICS952505AF - froze at 2.10ghz
ICS954127BFLF - crashed at 2.25ghz error Reference by pointer
*** STOP: 0x0000018 (0xFFFFF900C00879(6? 0?)0, 0xFFFFFA60069A9710, 0x0000000000000002, 0xFFFFF900C00225697)
ICS9LPR604AGLF - bsod at 2.252ghz
DRIVER_IRQL_NOT_LESS_OR_EQUAL
***STOP: 0x00000001 (0xFFFFF5001186A838, 0x000000000000000A, 0x0000000000000000, 0xFFFFFA6003C2209E)
*** dxgkrnl.sys - address FFFFFA6003C2209E base at FFFFFFA6003C08000, (maybe an extra f in the base) datestamp 4893b63f
I also updated the video card and audio drivers because after I googled around I learned that if these drivers are outdated it could cause a couple of the errors that I've mentioned. -
The PLL numbers listed by Quadrunner...are those just for theG50Vt model or are they the same for the G50Vm? If not, does anyone know the PLL number for this model?
-
Ray,
Looking at your signature I have the exact same laptop that you do, g50vm-x1 with the same t5750 processor.
As you can tell I'm not having much luck overclocking this machine. I'm really hoping that someone can translate the errors into something I can understand so hopefully I'll be able to fix them. If you have any luck, let me know.
Ps. Is there anything that I need to do special to make the settings from setfsb stick or do I need to use it every time I want to oc?
pss. I got windows 7 (build 7022 now vs 7000) to a hair shy of 2.3ghz where it runs but prime 95 encounters a hardware error within the first few minutes of running. It bsod'd because I didnt catch prime 95 in time to stop it. I rebooted, the 2.3ghz stuck, I re-ran prime 95 and caught it when it failed. My current rated fsb is 764.4-765.2mhz. If this is what my ram is I'm wondering if there's a way to alter the ram timing to make the ram go slower just to check and see if that is indeed whats causing the problem.
If anyone can recommend a program and a timing profile that I could try that would be great. Thanks. -
jacobxaviermason Notebook Consultant
Once you have that, select clock generator ICS9LPR604AGLF, click get FSB, move the top slider up a little, click set fsb. Your new cpu speed will appear in the bottom right hand corner. I've been able to get as high as 3.05Ghz, but can only run stably at ~2.75ghz. This will overclock your RAM in the same proportion as your cpu because you are raising the whole system bus speed.
Quadrunner, you might be able to get the setfsb autotool to work. I couldn't, but I didn't put much time into it either. The thread is here: http://forum.notebookreview.com/showthread.php?t=330419 -
ok do both of these notebooks use the same pll number?
Board: ASUSTeK Computer Inc. G50VT 1.0
that's my mobo... and i'm thinking by that every g50vt uses the same mobo which means i shouldb e able to use the same pll as what i've seen in this thread correct?
asus g50vt- x1 PLL number for setFSB?
Discussion in 'Asus' started by naticus, Dec 24, 2008.