Observations of the Official Beta VBios

I've been experimenting with different clock speeds for the official beta vBios.

Steam - Really problematic. Steam seems to make the HD5870M believe it's in 2D mode and at 3D mode at the same time. At least that's my impression. Whenever the memory clock speeds change, the taskbar flashes. This is not noticeable usually since you would only see a very quick flicker on the taskbar when going into 3D or 2D mode.
- I found that if you use OverDrive and lock in the memory clock permanently at a specific speed, this goes away.
- It also seems to have something to do with Enable Desktop Composition, what allows you to preview the application on the taskbar.
- What this tells me, Valve still sucks at programming Steam. It doesn't appear to be a flaw of the vBios, but a Valve failure.

Taskbar Flashing with Steam fail:
- If you use the mode for best performance, no taskbar flashing (Enable Desktop Composition)
- If you use the Windows 7 Basic, no flashing (Enable Desktop Composition)
- Disable Enable Desktop Composition: System Properties -> Performance Options (where you choose best performance, let windows choose, best appearance) -> Enable Desktop Composition
- For the most part, using Steam in window mode seems to improve (not in full screen view).

Taskbar AC Mode vs Battery
- Yes, this only happens in AC mode
- No issues on battery with 100/150. I can't figure out why

I have now flashed my vBios to these settings and are stable.
Plugged In
- 2D (200/300)
- UVD, Video (200/300) (.90v)
- 3D (700/1000) (1.05v) (.90v)
- OverDrive (800/1000) (1.05v)
On Battery
- 2D (100/150) (.90v)
- Load (400/600) (.90v)

PowerPlay and OverDrive
- PowerPlay functions as it should
- If you want PowerPlay to work with Overdrive, then don't touch memory. Both core and memory will dynamically change and OC when in 3D mode.
- If you already touched the memory. Then just click defaults. And then just change the core speed.
- As above, changing the memory speed will cause the memory clock speed to be fixed at all times.

Battery to AC Mode
- No issues. Downclocks to 100/150 on battery. Clocks back up to 200/300 on AC. And then 800/1000 in 3D mode.

This has been stable with all my games.
Games tested:
- Starcraft II (High Everything, Ultra just a drag with no visual improvement)
- Crysis (High Settings)
- Dirt 2 (Ultra Settings, No AA)
- Batman Arkham (High Everything)
- Mass Effect 2 (Highest Settings)

UVD Settings, Mine vs Asus
- There is no reason I can find why Asus has it at 500/1000.
- Video Playback is not related to Stream Processors or Memory clock speeds. UVD is separate, this is what processes video. Doesn't matter what speed the core or memory is. They could be zero and it would still work I believe.
- On battery 100/150, no audio video sync problems, no screen tearing or stuttering. Perfect playback.
Video Testing
- 1080p videos: Akira (11 mbps), EVA 2.2 (15 mbps)
- As you can see with such massive bitrate 1080p videos, 100/150 clock speeds are of no issue.

My Windows 7 Settings:
- I have latest drivers for just about everything.
- I have all updates from Windows Update

Download (At your risk. I take no responsibility if you brick your G73)
- MD5 Hash: CE1549E3AAF66C876C74BB53DAEB3A40
- http://www.megaupload.com/?d=2V896N86

Bricked your G73? Blind flash, courtesy of IceDragon7
How to blindflash on G73.

 

Does changing the voltages reverse the changes of the new vBios? As in will in bring back the GSODs? I do note that you've 'certified' it stable in the listed games, so the voltage amount isn't the cause for GSODs I take it.

FWIW, I've used your previously modded vBios (for when I was less familar with RBE) without issue and am one of the users that hasn't experienced GSODs in games.

Agreed and I've set UVD to 250/500. Although anything lower than 200/500 seems to hard-freeze MPC with DXVA. But that's just me. Similar testing boundaries with high-bitrate videos.

 

I really do think the reason why my TaskBar is flickering is because the vBios thinks Steam is 3D then 2D, then 3D.

OverDrive will tell you what the current clocks are. After flicking through Steam, I see OverDrive jumping from 700/1000 to 200/300. Using OverDrive and keeping the memory clock fixed resolves that issue.

So it has something to do with the memory clock changing and something to do with PowerPlay being confused, is it 2D or 3D. That's what I conclude from observing this.

 

I've had the 2D-3D-2D behaviour in steam...but also when Dirt2 is first loading. It flickers at the top for me though.

 

So I shouldn't bother flashing then?

 

Before you attempt to flash Ziddy's, or anyone else's bios, you should test the clocks on your machine using AMD GPU Tool. If your machine doesn't like the voltages/clocks that are incorporated into the VBios, then don't use it. Everyone's machine is different and your mileage will vary.

 

It's up to you. It may be just mine that has taskbar flickering not sure. If you can flash it yourself and test would be great.

But on mine, yes I can have down to 100/150 on battery and then A/C it jumps right back to AC mode clocks. The PowerPlay works fine with the directions I have above for using OverDrive.

Also, TweakForce released mobile Catalyst 10.5 which run really nice, even for StarCraft II. I don't use AA so the 10.7a update really doesn't mean much to me.

http://tweakforce.com/

 

Ziddy,
this looks pretty exciting. Thanks for sharing your hard work.
Quick question, so if I flash to this BIOS the clocks listed above will happen automatically right? Is that true for Overdrive too or do I have to set that manually? I just downloaded the 10.5a Extreme-G driver set. I used to love their nVidia work so I'm excited to see how these are.
What kind of battery life are you seeing on your machine?

 

I would say let it be. Just install the latest vBios Gary released. But from what I've seen so far, just means there is still some work to be done and this does not seem to be the final, but a beta still.

 

its needs some work.. the downclocking is not enough.. i need more as i'm going to use it in university for lectures and CAD etc.. anyways , Shadow, its worth doing the flash.. i'm rock stable in BC2 with 10.8 drivers.

 

Updated with the edited vBios I'm using.
- 3D or A/C remains unchanged with same clock settings and volt.
- Battery changed to 100/150 for 2D and 3D to 400/600 @ .9v
- OverDrive unlocked at 900/1250

So far everything is stable. No taskbar flickering. Steam problems not existing, but Steam still messes with the GPU causing it to believe it is constantly switching from 2D and 3D. But because the memory doesn't downclock, no taskbar flickering. Something Valve should fix, but they are probably too dumb.

Stability is great. No problem in any game. No game flickering, stuttering or GSOD etc.

Battery mode excellent. Downclocks to 100/150 @ .9v and once plug in, ramps back up to 405/1000 as the default A/C 2D clocks without any issue, no flickering no hiccups or anything.

 

Your vbios always seems to be 'temporarily unavailable' at megaupload?

 

I don't think that is specific to Steam, and it's highly unlikely an app like the Steam client has code that directly programs the video adapter.

Any of the graphics-intensive apps I write (WPF and Silverlight apps specifically) will cause up and down clocking with PowerPlay regardless of any 2D or 3D graphics usage. Same with the Aero UI and even graphics on web pages viewed in FF or IE.

The whole "2D or 3D mode" thing doesn't really exist any more since Vista. It's all 3D mode - the old 2D APIs are all rerouted through Direct3D.

From my observations, the PowerPlay switching algorithm used just seems a little too sensitive at times. Like really, you needed to up-clock to render that bitmap?

 

MegaUpload works fine.

Maybe MarkS. But for me the only time I see PowerPlay getting confused is Steam. None of my other programs do this.

 

can someone try this... i need more battery life and i'm willing to do it but just in case.. also ziddy how the hell do u have such a massive OC? Its almost as good as moos...

 

What do you mean by "confused"?

I see upclock when certain graphics are rendered in Steam, like when the featured items images are rendered. It also can happen just resizing the Steam client window (or any other window). That's not confusion to me - that's just upclocking when it's sensed that more intensive graphics operations are being performed - expected and desired behavior.

(FWIW, I'm observing on beta VBIOS with no clock changes)

 

ziddy,

What's the deal with only two clock info modes being used for a given PowerPlay state? Does this display adapter only have the ability to use two?

It seems that "medium" mode, if it was available and descreet from the low and high modes, could be set to the same or higher GPU clock as the "low" mode while leaving the RAM clock the same as the low mode. Then there wouldn't be a RAM clock switch when doing Windows desktop graphics extensive stuff while still upclocking in high mode, yes/no?

 

There are 3. 3D, 2D and UVD. UVD only works if it detects video. But with Steam it only switches between 2D and 3D.

Problem also is that whenever the memory downclocks and overclocks, there is a flicker. That's why my taskbar flickers with Steam, constantly switching from 2D to 3D.
- Also why I have the memory fixed in A/C mode
- For some reason battery mode is unaffected though, no flickering.

I think its a combination of Steam being coded badly and Asus vBios PowerPlay still broken.

 

If I use your vBios, will the settings already be there? Or do I have to install Overdrive program and do the settings that you showed? I have no idea what overdrive actually does, so if your vBios has everything included, that would be great.

 

OverDrive is automatic OverClocking tied to PowerPlay. Meaning in 2D it will be in normal 2D clocks. But when you play a game, it will ramp up to those overclocked speeds.

Everything is all there, just flash and go. Once you do, in Catalyst there will be an option for OverDrive. When you click on it, you'll see a key. Click the key to unlock OverDrive.

I recommend flashing with WinFlash just in case it may fail. If it fails, just flash with the default vBios. Do not restart if you get fail. Flash with another vBios until you get success.

The reason why I modified it is because I wanted lower voltage and lower clock for 2D and I like OverDrive so I don't have to mess with MSI Afterburner or AMD GPU Tool.

 

Ok, could you link me to the version of winflash that you are using, thanks.

 

Where do you see 2D and 3D modes? Is that an OverDrive thing? I'm talking/asking about just PowerPlay here...

I'm asking about the three clock modes available for each PowerPlay state.



For example, on the beta VBIOS, state 1 (which I assume is AC optimal performance mode and the text is wrong in the VBIOS) uses clock info 1 for its "low" setting and clock info 0 for its "medium" and "high" settings. I would think "medium" is the mode reached when doing slightly graphics-intensive stuff like with Aero or the Steam client's UI, but since we're forced to use clock info 0 for "medium" mode, it's always going to use the "high" settings even when it's not necessary. So, in your case, if the "medium" mode clock info was configurable, I'd set it for a higher GPU clock but leave the mem clock - that way there wouldn't be any flickers in Steam - the mem clock would only be bumped for "high" mode.

 

There are 3 for A/C and 2 for Battery. There are 5 modes. There is only one setting for each PowerPlay state... That or what you are asking is very confusing. I thought what I said was pretty clear, that's how PowerPlay works...

 

In RBE, I see 8 states with three modes each. I edited my above post - is it more clear what I'm asking about now?

 

You can't change those. Only Asus/ATi can.

 

Thanks.

To me that makes PowerPlay crippled at best..."broken" is a good word too...

 

ziddy , does this vBIOS help you in OCing because your clocks are insane? Also does your battery life improve?

 

Thats a good way to describe it...
MSI vBios (the newer one) however is much better since it has all 3 clock settings available - low, medium and high instead of med and high using the same clock info... plus its more stable...
The overdrive feature is also a joke on all these mobile vBios since the memory clock gets stuck at the overclock you set, so powerplay cant downclock properly.
But since Gary said this is their final work (that isnt even official enough to be put on their support site) were stuck with this, still half broken patch work.
Its progress, but its still far from finished and i for one am still not happy with this.

 

Yup. The G73 had such potential. Sad and frustrating.
Just like my ROG Maximus Formula Mobo... it works but has met exactly what it should have been.

I used to be an MSI fan and an ASUS convert, now I'm an MSI fan. I realize sometimes this is about luck and which product you get, but all my MSI stuff has lived to expectations. No more no less. My ASUS gear is often less than advertised.

Just my personal experience.

 

umghh ziddy? Also can overdrive be disabled or is it enabled by default in your vBIOS as i don't need an OC now.. i need the Overdrive feature but not the 800/1100 OC yet...

 

You can enable or disable

 

I'm really happy with my current setup. My G73 is running very nicely and IMO better than an MSI.

 

I mean for all kinds of stuff. Not just this notebook. But it's good to know some people got luckier with the G73.

 

My G73 has worked perfectly with relativly few fixes (Except for Keyboard Lag, this is my only complaint)

 

link is down... can't access it..

 

If you mean MegaUpload? It's up right now. Didn't change anything either, maybe bad connection?

 

it doesn't seem to be downclocking properly... didn't hit 200/300 on video and now on AC, its stuck on 500/1000... althought there is 0 load.. flashing again... forget it.. no 3D under battery too.. i'm having too many problems... back to Chasity's one..

 

I made a post last week stating the vBios has been updated since the 200/300 on video etc was too unstable. PowerPlay is broken on Gary's vBios. Just read what I post, it's all there.

Everything is stock for A/C. I only modified the battery which downclocks to 100/150 on idle and 3D is 400/600 @ .9v. If you want to game on battery that's your choice, but I didn't want that, and don't think most people do either, so 400/600 works admirably.

This vBios is for those who want better battery clocks and with OD unlocked. That's it.

 

its ok..i'll use chasity's one which goes to 250/300.. its more stable for me... and seems to ramp clocks up or down quickly.. no offense intended ziddy.

 

If you mean this one: http://forum.notebookreview.com/6667334-post10.html
No it doesn't. Her A/C clocks are the same as Gary's. The battery does go down to 250/500. But mine goes down to 100/150.
- This is the vBios in her signature.

If her's work out better for you then fine. I'm not butt hurt over this. Mine works for me, and it's just there if others wanted to use it.

The main point of this thread was to show Gary and others, this vBios is still only half of what it should. Not necessarily promoting my modified vBios. It's just to show that OverDrive and PowerPlay is broken. Usable, but broken.

And my vBios does ramp up clocks quickly correctly.

 

Nice vbios modifications. If my card supports the voltages, I may go for it for thermal purposes.

 

I wonder what's up with Asus using highier boot voltage.I mean it's like 0,10V higier than Alienware and MSI. I wonder is we can use 1,05V for boot voltage or it will crash Asus 5870m?

Well if it is ustable with 1,05V that maybe Asus got the lower "bin" radeon chips for G73jh hence the price of it and the problems. Bin is used for leds,for chips to.

Lower bin = lower quality silicon.
Gives me sth to think about.
Regards

 

Ok I just tried this modded vbios and got my first ever gsod in mafia II. Weird, going back to gary's one to see if somehow this one is to blame.

 

Hey ziddy I am having problems with the flickering too, because i wanted my clocks in low 300/300 then mid high 700/100 but it flickers a lot.

i dont know if the link in your first page is the updated one can you give me your updated vbios so i could try it.

 

my clock sometimes get stuck on 500/1000 and dont go up or down... onlu way to set it back is using default clocks on AMD GPU Tool.. any clue on whats causing this? (ive reupdated vbios and drivers and problem still)

 

You probably have a video open in a browser tab, or Flash is running a video. Easist way to avoid this is to open up Flash's properties and disable hardware acceleration.

 

I've found the only way to get rid of flickering is to just force the GPU into either 3D mode or Battery Mode. Whenever memory changes clocks, it flickers.

So for me I just have balanced mode with PowerPlay set at battery mode. So when not gaming it change it to that.

When gaming change to high performance where the PowerPlay is set to maximum performance.

 

The poorly coded Asus vBios sometimes gets stuck on some profile and the only way to fix it is to either manually reset the clocks with AMD GPU Clock Tool or restart the laptop. To avoid this in the future you can disable Powerplay if youre fine with the new idle temperatures.

 

are you getting sometimes
The display driver has stopped working and has recovered?
and if yes what do you do about it ? just ignore it???

 

i do get this sometimes... specially if i set clocks higher than 700/1000 (not all games)

im not sure if its related to temperature (room temperature here pass easily 30C and gpu sometimes get on 97C). ive tried vbios and drivers and it still happens... my last hope is when i get back home and make a repaste myself