G50V - 9700m GT overclocking

Woot, but say for example, we were able to get our hands on a more powerful card, something like a 9800M GTX, would someone be able to mod the bios to support it? the only reason we couldn't swap out GPUs before was because they were soldered in right? Or do we have to take into concideration the size of the heatsink and the power usage?

I'm sooo excited we should probabbly contact some of the resellers

 

Before you go purchasing 9800m GTX (trust me I would give me more pleasure having that in my laptop too). Would the laptop boot? Since MOBO bios contorls the VC how are you about flashing it or even sporting off vendor board (Clearly Asus not going to sell em off)

Plus 9800m GTX runs REALLY hot, have you seen laptops heatsicks that has that card. That's why I think 9800GS OCed to something reasonable (500 3Dmark points would not kill me if it prevents literal melt down of my laptop).

Thing now is this, IF and IF we get 8800GS in the G50V and get our hands on the bios from G50VT, how are we about flushing it and making it work?

For this we need first 2 and then start trying. NOW... who has 8800GS and G50V with VC taken out? That's the starting point....

 

We should prob start a new "9800GS swap in G50V" thread

 

Except we don't even have a proof of concept. Can someone ask Asus if Asus will sell the 9800m GS?

 

no go from asus.

ripped the vbios, opened in NiBiTor (v4.6), but the core clock speed is read wrong (22884) for all three states and i dont have the balls to reflash it. perhaps if rivatuner were locked to the max 3d and the third step modded in the vbios it might work.

version 62.94.3C.00.15 attached

 

anyone else want to try this?

- install the 169.04 drivers (thanks leshcat) with the attached inf (xp32 only, just add the device id to the lv2g inf if youre using a different OS)
- install System Tools 6.03
- change the clocks by modifying the profile file (usually under ~/Local Setting/App Data/Nvidia Corp/nTune/Profiles/*.nsu or somthing like that) or the one i attached

if you use a new inf, the system locks up if you try going over even 1 step.



unless RivaTuner, GPU-Z and nvidias control panel are lieing to me, overclocking works. i'll see how high it can go, then if i have time, stock/OC results from CoD4 and CSS.

currently stable @ 780 / 1963 / 891, with some headroom.
css runs fine, 5~25% increase in frames (making sure that i was in around the same places on the same server, no reboots).

800/1900/891, temps hold at ~85C full load (CoD4).

 

holy crap!!! im praying that this really works.....do you have any before and after benchmark results to show if the gpu is really overclocked? Also would you be able to tell me the device/OS ID for Vista 64?

Thanks!

 

*jaw drops*...

I'm testing this out...

EDIT: What do you mean by new inf?

 

those score are based off XP our computer can get almost 10k on 3dmark in windows XP its all synthetic it doesn't mean much except to benchmark against yourself to see improvement in score

 

How did you get your shader so high if i go passed 1825 i start noticing artifacts....no programs show this as a error its just visible in the image it self the artifact scanning programs dont detect a error

EDIT somethings FISHY in those screenshots look at his CPU speeds 4100mhz and 5999mhz even if he upgraded his CPU to the 2.8ghz version 4.1ghz is a bit much let alone 6ghz

EDIT well i didn't even realize mine say the same thing go figure

 

system tools doesn't show the clock speed properly, but you can ovecrclock the fsb to get it to 2.8 instead of upgrading funky stuff sometimes happens with the lan card though.

1900 was a bit high, and there were artifacts (after an hour of css). looks good at 1850. redoing the overclocking, so these shots will have to do (no 3dmark06 til the weekend (stupid university inet)).

h.ttp://i137.photobucket.com/albums/q228/HoldFire/c4stock.jpg
h.ttp://i137.photobucket.com/albums/q228/HoldFire/c4shadersmem.jpg
h.ttp://i137.photobucket.com/albums/q228/HoldFire/c4highermem.jpg

^-- minus the .
1MB each (with an extra monitor),
113~119 FPS on stock 625/800/1650
141~145 with shaders at 1800, mem at 850
150~153 with mem at 900. (different server since the original had slay-on-twice-in-one-round on)

seems too much for a small overclock, but this is only my second OC'd card so idk

 

I cant get my clocks to change except shaders still.... i tried ur method it just defualts to no overclock factory defualts how are you getting these to apply at those speeds. Please list exact steps. i cant load any profiles

 

**IF YOU CAME TO LOOK AT THIS POST FROM GOOGLE, CHECK THE NEWER METHOD HERE: http://forum.notebookreview.com/showpost.php?p=4265412&postcount=111**

1) remove every trace of your current driver + system tools + profiles. everything.

2) download the 169.04 driver + 169.04 modded inf.

3) add all of the GPU's to the inf (both in the NVIDIA.Mfg and Strings sections).

4) install the drivers (i did it with the installer, but i guess both methods will work). if you get something like " target ***.dll is newer then the one being copied, continue?", you didn't remove the drivers fully -> back to step 1.

5) install System Tools 6.03 (google).

6) in the nv cpl Device Settings (under Performance), click Save, and save it somewhere easy to get to, eg. My Documents.

7) in that, change the
GPUCOREMHZ0=***
GPUMEMMHZ0=***
GPUSHADERMHZ0=****
lines to whatever you want to set the clocks to.

8.) save, double click to load the profile in nTune.


edit: YOU CANT OVERCLOCK IN RIVATUNER. it only does the third step, and it will hang the system even with a 1mhz oc.
i'm not a driver expert, but there is no difference in the inf's between 179.13 (cant overclock) and 169.04 (can) besides having the R&T lines split in the newer ones.

another edit: if it says the cuda dll is not found, just cancel and continue with the installation

and another: to have the OC apply when windows starts, save the code in a .reg file and replace "C:\\Users\\nv(700.1813.848).stable.nsu\" to where your profile is.

Code:

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run]
"NVIDIA nTune"="\"C:\\Program Files\\NVIDIA\\nTune\\nTuneCmd.exe\" boot \"C:\\Users\\nv(700.1813.848).stable.nsu\""

 

OK then i can confirm this doesn't work on vista 64bit cause that what i did and when i load profiles it does absolutely nothing only way i can change anything is in the portion where you can create a profile.

 

How exactly do I do step 3? I'm a bit confused, is there anyway you can post or upload your modded version?

 

@Singh31: i have the xp 32 bit inf on page 6 (post 52).

for other OS's,

-get the modded inf for a newer driver

-scroll to [NVIDIA.Mfg.****], it will have a bunch of
%NVIDIA_BR02.DEV_00F0.1% = nv_NV3x, PCI\VEN_10DE&DEV_00F0
%NVIDIA_BR02.DEV_00F1.1% = nv_NV3x, PCI\VEN_10DE&DEV_00F1
%NVIDIA_BR02.DEV_00F2.1% = nv_NV3x, PCI\VEN_10DE&DEV_00F2
%NVIDIA_BR02.DEV_00F3.1% = nv_NV3x, PCI\VEN_10DE&DEV_00F3
and so on.

-copy/paste those lines into the [NVIDIA.Mfg***] section in the 169.04 inf

-repeat the same thing with the bottom part of [Strings]
NVIDIA_BR02.DEV_00F0.1 = "NVIDIA Device ID 0x00F0"
NVIDIA_BR02.DEV_00F1.1 = "NVIDIA GeForce 6600 GT"
NVIDIA_BR02.DEV_00F2.1 = "NVIDIA GeForce 6600"

this is the lazy method of adding the 9700M gt id so the driver will recognize it.
up


@Errant33: if noting shows up in the Device Settings things besides save, thats how it was for me. the saving is just to get a default profile. and i have a feeling its because of not running it as admin

 

hey, can someone briefly walk me through making the 169.04 drivers work for vista 64? I modded the inf file according to your step 3 but I'm guessing I still have to mod something to change the OS to Vista 64 instead of XP.

Thanks

 

attached the vista x64 inf.

 

thanks for the file thalanix but I followed all the steps but couldn't get everything to work....after i installed and edited eveything I was suppose to, it seems gpuz and 3dmark couldn't find my gpu for some reason......i guess ill have to wait until someone with vista 64 perfects everything...thanks though you're probably on to something big

 

or you can try to be the one that makes it work on vista x64 errant33 seems to be on to something. or you can try with slightly older/newer drivers, perhaps it will change something.

ill try and find any differences in the inf, but on first glance it doesn't look too promising. besides the list of files, its mostly added physx to the new, and grouped R&T_common reg config in the old.

 

hahah...im about to reinstall my OS with XP....i really dont like vista anyways....well worth it if I'll be able to overclock my vid card....can't wait to see some real benchmark to see if the adjusted clocking are real!!!....

 

no i am in admin

I have been overclocked on my shaders for almost 8 days at 1800mhz......however cant change anything else if i use ur method it just resets defaults otherwise just says cannot do this operation

 

about a 25% increase on average in cod4 across the board.

clocks @ 740/1800/1050, core can still be OCd a bit more.

Settings:
ht.tp://i137.photobucket.com/albums/q228/HoldFire/cod4set1.jpg
ht.tp://i137.photobucket.com/albums/q228/HoldFire/cod4set2.jpg

i've never played the map, so i couldn't find where i was. settled for something close enough.

Stock:
ht.tp://i137.photobucket.com/albums/q228/HoldFire/c5cod1.jpg

OC:
ht.tp://i137.photobucket.com/albums/q228/HoldFire/c5cod2.jpg

temp holds at 86C


@Errant: can you try 169.09 (i dont have vista, but i remember reading something about those drivers)


edit: i managed to get the 3dmark06 trial, results are decent. 6036 on stock, 6829 on oc. 740/1800/950 clocks, because it crashed at the end of the last test three times. so from limited experience i would say something like 6900 is possible.

 

If Someone can do the magic and make it works completely with Vista64 it would be amazing! I tried it too but no luck

 

tried several drivers in all the desktop ranges, only 169.04 work (for xp 32). try out some 169.** drivers, perhaps youll get lucky. if not, xp might be the only method.

 

any update on this with Vista 64?
I tried every driver but no luck so far...

 

i wont be reinstalling vista just to try, but heres what i gathered from the webs:

- some 9600's, 8600's and probably a lot of other cards only overclock on 169.04 (or not at all), not just the 6xxx and 7xxx series.
- drivers from your manufacturer could work. all drivers newer than 169 from asus: 174.31(V), 176.23(V), 176.28(V/X), 177.26(V/X), 179.14 (V). if it were up to me, those would be the next to try.

 

I tried every dirver on Vista64 and only the shaders are overclockable so far...

 

Ok here are some interesting news about the VISTA64 with the latest drivers 180. installeds

I have found that

1) If you try to change the SHADERS clock value with the power charger plugged in you can raise and lower the values

2) If you try to change the SHADERS clock value with the power charger UNPLUGGED it wont let you change the values.

3) If you try to change the MEMORY or the CORE values with the power charger UNPLUGGED it wont let you change the values at all

4) if you try to change the MEMORY or the CORE values with the power charger PLUGGED IN it will LET YOU LOWER the values. But once lowered it wont let you raise them again.

At this point I think that the software and power management can be the main problem. It would nice to try uninstalling all the power managements softwares.

 

2 and 3 sound like powermizer. in 4, you should have been able to raise them back to stock (or close to stock).

edit: asus drivers dont overclock on xp as well.

 

I am actually using the 180.xx drivers from laptopvideo2go and they works to overclock the shaders but not the mem and core

 

I have been able to push the shaders to 2000. But it didn't made that big difference. Well I just tested with 3dMark Vantage and I reached 2300 without overclocking the cpu. All stock just the shaders at 2000.

 

no artifacts at 2000? i'm all out of ideas for vista.

 

Not stable at 2000. I couldn't complete the test. At 1950 no artifacts tho.
I am still tryng to my xp older-newer inf with vista64 older-newer but still not luck.

 

Keep overclocking

 

maybe an even older driver? something like 164.01. i'm fairly sure that besides a bios mod (which will have to wait until nibitor supports it), a specific driver is your last hope.

if anyone wants to nag Mavke, be my guest
i couldn't get my flash drive to boot (yes, i tried using HP's make bootable program, no luck), so i extracted it from the 205 bios and posted

mvktech.net/component/option,com_joomlaboard/Itemid,34/func,view/catid,13/id,52420/#52420

 

I think this thread deserve a small BUMP!
Any news?

 

no choice but to wait for someone to properly dump the vbios with nvflash, then some more for a nibitor update (or use 169.04 w/ XP)

 

There is another thing that I tried:
If I overclock the shaders I get nice results in games.
But I can't overclock with SETFSB or Iwill get almost immediately aritfacts. If I overclock the cpu to about 3k ghz ro abit more it happen the opposite. I get sitll very nice results in games but I can't overclock the shaders almost at all or I get artifacts.
I wodner where is the relation.
I should be able to overclock teh CPU AND THE SHADERS...

 

Reason being is overclocking the CPU with setfsb also overclocks all your bus speeds so its also affecting your pci-express slot which is most likely causing your artifacts.

 

hmmm what should I use to overclock the cpu then without overclocking the pci?

 

none. the board has no pci-e lock, so pci-e is raised with the fsb.

 

why would u need to OC the amply fast cpu anyway? X1 version?

 

nibitor works as it should, it just doesn't read the proper offsets (eg. the clock speed for 3d is at 0xCEF3 and not 0xCEF1, the 22884 value could be an identifier (im no bios expert) since it precedes the first three steps, but not extra (the one it doesn't see)). if all nibitor does is change the values, then its still within possibility.

for anyone interested, i found the fourth step -> 0xCF68 (core), 0xCF6A (shaders), 0xCF6C (mem). i uploaded a few modded bios' below.

**FLASH ONLY IF YOU HAVE BALLS OF STEEL**
**I TAKE NO RESPONSIBILITY FOR WHAT IS DONE WITH THESE BIOS**

note: removed since ill add some 209's

flashed with the 720/1800/1050, no bsod yet. reinstalling nvidia drivers, ill post my results soon.

 

imo this deserves its own post.

modded bios 209. SUCCESS. no bsod, all good.



THIS IS FOR THE G50V-A1/2, NOT THE G50Vt.

BIOS 205:
720/1800/1050: http://www.zshare.net/download/5239770146d4bcd7/
680/1750/954: http://www.zshare.net/download/52397751a1576d7d/
650/1650/864: http://www.zshare.net/download/523978994d7f676e/

BIOS 209:
720/1800/1050: http://www.zshare.net/download/52415855a69b27eb/
680/1750/954: http://www.zshare.net/download/5241584404eaa585/
650/1650/864: http://www.zshare.net/download/52415826635ee715/

**I TAKE NO RESPONSIBILITY FOR ANY DAMAGE DONE BECUASE OF THE USE OR MISUSE OF THE ABOVE BIOS FILES**
**IF YOU WANT TO EDIT THE VBIOS TO YOUR OWN LIKING, READ THE PREVIOUS POST**
**IT WOULD BE A GOOD IDEA TO FIND YOUR CARDS MAX WITH THE 169.04 DRIVERS BEFORE FLASHING**

depending on my free time (exams ftl), if you dont know how to mod ami bios, you can request the clocks here and myself or someone else capable can do it for you.

AFTER A FEW RESTARTS, THE SYSTEM BSOD'S WITH A "NV4_DISP HAS ENTERED AN INFINITE LOOP" ERROR. THEN THE SOUND OF DOOM CAME BACK. USE AT YOUR OWN RISK. REFLASHING BACK TO THE ORIGINAL, NO BSOD, NO PROBLEM.
(it seems to bsod as soon as the card enters the oc'd speed when windows starts (explorer, after logging in)

can a card degrade itself over time? i ask since it started happening recently even with the 169.04 drivers. went strong for 2 weeks, temps never rose above 85.

 

That's your memory going, clocked too high. That infinite loop error is ONLY from overheating or fried memory. I am curious though, did you have to hex edit or did NiBiTor take care of it for you?

 

hex edit. but if it were fried memory, wouldnt the stock clocks die as well? reinstalling the drivers fixes it for restart or two.

hmm... stock bios, this happens when attempting to overclock with ntune (during crashing time, 169.04)



something isn't right... reset to stock and launching gw



is installing xp pro 64 worth it? i ask since last time i did that, BIOS stopped seeing SATA ports 1 & 4, and then just stopped POSTing alltogether (easy RMA though, 3 days total)



sata/lan/wifi/sound slipstreamed quite nicely almost no drivers to install. 5 reboots, all good with 720/1800/1050.

 

That's interesting but I suspect that it's from the memory being relieved of processing while your drivers aren't using the chips. I am positive your problem is due to memory errors. Sorry to be the bearer of bad news

 

all seems well on x64 though. an hour of cod4, no glitches/artifacts, nothing.

 

Yea, you may not be out of luck, but some of your memory has gotten hurt, I would be very careful, let us know how your stability turns out. Good luck!

Edit: can you try running furmark? That'll beat your memory into a pulp and give a good indication of stability.

http://www.ozone3d.net/benchmarks/fur/