[GSOD Fix?] Beta vBIOS update for G73JH

Here's an update folks.

Ran Unigine Heaven and I received a Brown Screen of Death with dark vertical lines.
And like I said before, I got a solid Black Screen of Death in Combat Arms after a few minutes. I'm on the 10.7a driver, I'll run driver sweeper and go to 10.8.

 

I downgraded from BIOS 211 to 209 and installed the beta vBIOS. I don't know why? I've never had a GSOD. You guys are all doing it and it looked like fun so I did it too. I hope you guys aren't about to jump off a cliff because apparently I would be right behind you.

Anyway... no problems with updating it. I just noticed I'm missing keystrokes again. Then I realized that going back to 209 re-enabled the touch pad in BIOS so I'll have to reboot and fix that. It is a real pain to always HAVE to use an external mouse. I use one most of the time anyway, but I like two finger scrolling and wish I could use it. I sure hope that keyboard/missed keystroke fix is coming soon.

I'm about to run a Hairy Donut Test to verify that I still don't get GSODs but I guess that won't help anybody since I never had them to begin with.

 

i got gsod on call of duty mwf2 with 10.8 can anyone give me the 10.7 and see if that works plz

 

Here's an update, since the forums were down. I got SOD's of all sorts with the new vbios. 10.7a gave a black screen of death and a brown screen of death with vertical stripes. 10.8 was a little more stable, but got occasional horizontal black bars and screen jumps, eventually leading to another brown screen in FurMark and Unigine. Back down to 10.1 seems stable, but my Gpu sounds like a turbo charger when I run FurMark, which concerns me. Back to the drawing board.

 

guess Hellcry was right hours and hours ago after furmark crashed in 10 minutes

 

yeah i try all the 10.2 to 10.8 and get gsod so i went back to 10.1 and works fine but the beta vbios help a little bit and i hope the real one will come this week or next week

 

damm, just the right time to loose my pendrive...oh whell, gonna use a bootable DVD-RW, it's just as good...maybe better

 

mm new vbios + 10.7a = ffxiv bench full screen witouth GSOD

Later i will try 10.8.

 

Currently on 10.8 and the Unmodified *new* VBios and bios 209. Currently testing Furmark.
WIll keep informed of the result

Edit 1 = Got a screen flickering but no gsod yet.... not looking good. This never happened with the MSI / clevo Vbios

Edit 2: the bios still seem to be a bit more robust. Its would seem the g73 want to gsod with the flickering but did not after 6 min use.
Before I was flickering 1-2 time and bam.

Edit 3 = Just got my GSOD. this Vbios is a fail sorry. bios 211 has nothing to do with this apparently.

 

the beta vBios sucks, going back to msi vbios

 

can any1 post a link again to the 100% GSOD free MSI vBIOS please?

 

15:52min with furmark and beta vBIOS + 10.7a and no GSOD http://asusxperts.puchu.es/g73/furmark.jpg

i´m tired of see hairy donut, i go to try 3dmarks now

 

Msi Vbios for G73.rar - Windows Live


WIsh I could have the Asus tool for editing the MSI vbios and put the HDMI code in it....

Edit: ME want Rep + ;P

 

I ran benchmarks after the forums went down. No GSOD but I never had any before either. I'm just reporting back so interested parties have the data point. I don't know all the details on this one but t is apparently downclocking a little at idle when the GPU isn't needed because I'm a degree or two cooler. I'm running the versio where Chastity enabled Overdrive (bless her heart )

 

And you got 1

Wonder which 1 would be cheaper...paying the manpower for tweaking a defected Asus vBIOS or licensing a working MSI vBIOS?

 

3dmark vantage witouth GSOD in new vBIOS +10.7a, I go to try some games now

 

Go for Splinter Cell Conviction and Left 4 Dead 2. In L4D2 load up Heavy Rain, you should get GSOD in a few min after the map loads.

 

downloading l4d2 from steam .

 

Either way, cheaper than the fallout if they never manage to completely fix the Asus vBios.

 

the news isn't good... it was worse yesterday night but slightly better now.. my only issue is why are peopling running furmark instead of games? Run more games because furmark is useless! As long as it's stable in games , it shouldn't be a problem ... anyways , more waiting for me.. my payment hasn't cleared... i can't take it.

 

Nah, its not a fail but not ready to be released to public. With the stock vBIOS and 10.8 Drivers Crysis GSODs after about 10min. With the beta one i've playd it about 30min. without GSOD so its the right way but not finished yet.

 

So are there any issues with the MSI vbios? it would be nice to have an asus bios bu to be honest, as long as its working, i dont give a crap.....so who can give me some info on the MSI vbios.....dos it work with 211 bios? does it work with 10.8?

 

My biggest fear is a dead VRAM. Once, in my Clevo m570TU the 9800M GT's VRAM died in the the middle of a WoW raid (Anub'arak 25HC try) and I was wondering if God help me, my 5870's VRAM dies too, does Asus have the balls to claim it was because the MSI vBIOS and deny the RMA and blame me for it?

 

Others say it is working like a charm, absolutely no problem, except HDMI port does not work with it.

 

MSI BIOS works with all drivers but u loose HDMI and VGA.. also its in a way illegal to use it according to warranty and like DRevan said , if anything happens , Asus can deny RMA.

 

THe use of furmark is only to help producing the gsod faster.
For me, if furmark doesnt Gsod, game wont too.
Thats the reason I use it.

Furmark does a constant gpu usage and it stress the card more. I dont want to waste 1 hour of gaming and then gsod if I can make it happen in less than 10 minutes with Furmark.

 

so jsut to be clear...if i use the MSI bios, my GSOD death goes away buti will loose HDMI out (never used it) and VGA out (which i use for dual monitor).....hmmmmm tempting......

 

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".

 

Bios 209
Vbios unmodified beta
10.8 Official ATI driver (mobility)
DId not overclock / change CCC parameter.

Uninstall previos driver, cleaned files / service / reg entry that ATI uninstaller did not removed. And installed 10.8

Furmark gsod in less than 10 minutes. Cann see the screen bumping in +- 5 minutes

 

Just for the record...how much would Asus ask for a VGA if they deny RMA? A shop who sells Asus parts here in Hungary, have the VGA panel listed for $180 (converted from HUF).

 

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

 

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

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

 

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.

 

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.

 

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.

 

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...

 

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?

 

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.

 

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

 

Well with an HEX editor they are very different.
It would be great to have a tool to see/modify hdmi part

 

m8, this was not intended to be called beta because it can still give GSOD, it was because they planned to add more clock settings+enable Overdrive later...

 

Couldnt the non-HDMI part of the MSI vBIOS used to recode the non-HDMI part of ASUS vbIOS?

 

And how do you know without a proper tool which one is the HDMI part? MSI vBIOS has HDMI and VGA part too, but for MSI motherboard...

 

Yeah, but beta should still be a step in a right direction at least. As far it seems that this vbios is at least as prone to gsod if not more than Asus stock vbios. So all this waiting and testing so far seems to have accomplished nothing

It doesn't make it any better that most likely Gary and his team aren't even on the right track in solving the issue. If this beta vbios crashes as much as the original one when we end-users try it, it seems pointless in fact. IMHO the beta should already have the 'fix' at least, even if it could still have other problems (like hdmi, powerplay etc. not yet working).

There isn't a working fix in the current beta vbios and that's all that matters. Thanks for Gary and his team for trying, however, I hope you can still find a working solution.

It would be great if someone really had the skills to do a hex-level comparison of working 012.020 MSI vbios versus not-working 012.020 Asus beta vbios. If just the right HDMI and VGA addresses could be transferred from one bios to the other... Using other manufacturers' vbios there is also (a quite minor IMO) problem that sleep/hibernaton modes don't function correctly, at least for me with MSI vbios.

 

SO here is a whacky thought...

Dear Asus,

MSI vbios works...yours does not....why not have you engineers look at their vbios and see what they did different then you. Then take what you have learned and fix your god damned vbios..

sincerly,
Everyone who owns a G73 and actualy wants to play without GSOD.

 

One more thing ive noticed regarding testing for GSODs. Now im not saying this is surely accurate, but it has been with my machine.
If the windows logo (the one when windows is loading) flashes and gets kinda liny just before you enter the desktop (it flashes real fast but its clearly visible if youre looking at it) i will get GSODs (this always happens if im using the old or beta Asus vBios and newer drivers on wich i GSOD) and if it doesnt do that strange flicker it doesnt GSOD (i dont get it on 10.1 drivers or using MSI/Clevo vBios with any driver where i dont have problems). It isnt really something special, but when i see that logo flicker and distort a bit like that i already get that bad feeling...

 

It's like if Microsoft would use code from Linux for the Windows

 

I need someone who can test the HDMI with my custom Modified Vbios (msi)
I think I may have restore the HDMI on it.
I tested it and it is safe to flash. But cant test the HDMI at my job.

Hellcry? Chastity?

 

Its not exactly like that, since those are totally different and i doubt the code from linux could help do anything in windows, but the analogy is good enough (just imagine the lawsuits ).