[GSOD Fix?] Beta vBIOS update for G73JH

[dark_nerd]

The fastest way I could produce a GSOD without stressing the GPU is downclocking to 300/300 then back up to stock clocks, or downclocking to 100/200 from 300/300. This is test consistently GSODs on every driver except the stock and the 10.1, in my experience.

[wagnard]

The fastest way I could produce a GSOD without stressing the GPU is downclocking to 300/300 then back up to stock clocks, or downclocking to 100/200 from 300/300. This is test consistently GSODs on every driver except the stock and the 10.1, in my experience.

U did that with amd gpu tool?
Edit: im not gsoding with what u said on my system

[dark_nerd]

U did that with amd gpu tool?

YES. AMD GPU Tool onlyand results are consistent. My G73 only GSODs in this condition with ATI Reference Drivers

Edit: im not gsoding with what u said on my system

Well, it may vary on a case to case basis. Just like how others arent getting GSODs

[PulsatingQuasar]

The fastest way I could produce a GSOD without stressing the GPU is downclocking to 300/300 then back up to stock clocks, or downclocking to 100/200 from 300/300. This is test consistently GSODs on every driver except the stock and the 10.1, in my experience.

That happens for me too but I don't GSOD in games or Furmark. I doubt it has anything to do with the GSOD during games and it is not G73JH specific.

What you see there is a problem Ati already has for several years now on both desktop and mobile GPU's and I think it's drivers related.

[smile_gerard]

The fastest way I could produce a GSOD without stressing the GPU is downclocking to 300/300 then back up to stock clocks, or downclocking to 100/200 from 300/300. This is test consistently GSODs on every driver except the stock and the 10.1, in my experience.

Sad to say thats probably hardware related. I can go from 705/1100 down to 100/250 stable. Repeating it over and over makes no different. So i'd say thats not related to the vbios or drivers. Probably due to the rams on individual cards.

[jaolhe2]

To help things out, if you are reporting GSOD's, please include:

1) Your current BIOS
2) stock beta vBIOS or my modded one
3) driver package you are using, and if desktop or mobility
4) clock speeds
5) Driver installation method used

When I get a chance later, I am going to do a better driver cleanse and retry 10.8. I hate the fact that Gary has better results than me.

@ziddy: a vBIOS with proper & useful PowerPlay settings and Overdrive is the goal here for the final release. Based on feedback, 250/500 seems to get the best compatibility, which is why I snuck it into the mod vBIOS.

On stability: Generally speaking, so far I am getting more feedback that it's been successful than not, so it's definitely on the right track. I'm thinking of sending Hellcry's laptop to ATI with a note "FIX THIS".

You realize collecting and writing down all this information is very frustrating and might actually not even help. Why? Because MSI/Clevo vbioses are working GSOD free with every known combination of drivers, clock speeds and system bios! So it's not just any 'combination' that is problematic, it's the wholly and only the Asus vbios thingy that is failing.

[Carillo Gallardo]

That happens for me too but I don't GSOD in games or Furmark. I doubt it has anything to do with the GSOD during games and it is not G73JH specific.

What you see there is a problem Ati already has for several years now on both desktop and mobile GPU's and I think it's drivers related.

it's the same here... I never had any kind of sod, with any kind of game and any catalyst version, but if I do the steps described by dark_nerd I get a gsod... now I'm using my own modded vbios, catalyst 10.8 and bios 211...

[BKoolReturns]

Perhaps I'm oversimplifying the process, but isn't anyone capable of directly comparing the MSI/Clevo vBIOS code to the ASUS vBIOS code, enabling HDMI support, and calling it a day?

Or is that against corporate rules? Or maybe it just really hurts ASUS's pride?

[smile_gerard]

To be honest, the vbios is only a beta. Its acceptable for betas to not be ready right? I mean why else would it be a beta. And it was mentioned before hand that there was problems. This is like looking at the guru3d people shooting ati with every release of a driver.

[DRevan]

Or is that against corporate rules? Or maybe it just really hurts ASUS's pride?

I think both. They would have to license that vBIOS.