What did you do and with what tool?
Upload it and post a link and the checksums. Ill take a look at it and flash it if ill feel comfortable with what im seeing.![]()
-
skygunner27 A Genuine Child of Zion
Some members thought it was funny when I said at this point Gary should be given unlimited resources to address this problem. I still don't understand why they don't just modify the working MSI bios. I also don't understand why Asus is leaving this up to just Gary and pals considering how big Asus is and how much money they've made off of the G73JH.
I feel so sorry for all you fellow G73 owners that have to go through all this BS to get a working "Gaming Computer". My hats off to you
-
Because the MSI vBIOS is the property of MSI! If Asus touches that without paying for license fee, they would get their a*s sued off.
-
no gsod on alien swarm and BC2
BIOS 209
Uninstall 10.1 and run driversweeper in safe mode
vbios beta
10.7a hotfix.
I will try l4d2 when steam finish to download it -
Check your P.M HellCry.
As said, its safe to flash. Im currently using it. but cant test the HDMI.
Awaiting your feedback -
Wait. What? How did you due that? I didn't know you know assembly
If you only copy pasted fragments with HEX editor, then testing that would be a suicide mission
update: I see you are using. Really interested now how did you do it
-
Ill explain what I did after HellCry report. I just have a theory of why HDMI wasnt working.
-
VGA port wasn't working neither
-
It will maybe be restored too.
Finger crossed. -
If you really managed to fix HDMI and VGA, then all of Gary and his team work, will seem like a waste of time and money
-
skygunner27 A Genuine Child of Zion
Insurance company's make back door deals all the time. I'm pretty sure that Asus can make this happend through compensation etc.... -
My guess is it wont work. But I do trust a bit my theory.
-
The flaw in this is that MSI did not create the vBIOS. This is actually AMD's vBIOS.
And considering Asus "CLAIMS" they are working with AMD for a solution, it is curious why ATi and AMD are unable to find a solution. ATi managed to do this for MSI, Clevo and Alienware, but not for Asus? -
I'VE GOT IT! It's all a major conspiracy to run Asus out of business! We should have seen this earlier. We could have SAVED THEM!!!
-
I have noticed this as well.All the time when windows was loading i notice the flickering lines on the bottom or top. I was on 10.7 for a week then back on 10.1 and no more flicker.
-
It isn't really a bug per se, SC2 just doesn't limit frame rates in excess of 500fps by default. It's really more of an oversight and fixable with a configuration file. This may completely saturate your GPU with work, but it's not like it's being told to destroy itself by the game. Same thing with FurMark, it just keeps your GPU 100% busy. I would argue that the same machines that were "broken by SC2" would have also died if they ran FurMark, and if a GPU fails because it was just at full load at stock speeds, then it was defective.
As for just modifying the MSI vBIOS, it's really not that simple imo. HDMI support is probably not just some flag in the software, it probably needs to be coded in on a card by card basis. From what I've gathered from Chastity's posts, Asus can't do a whole lot except change settings in the vBIOS. This probably means they do not have the assembly source and therefore can't do a whole lot. Likewise, they don't have the MSI vBIOS source, so they probably can't add HDMI support for it. Unfortunately, this may really be on ATI more than anyone to fix. Furthermore, this may also mean that Asus' 5870m card does not meet ATI's reference specifications. -
What i was told is that ATI makes the basic vBios - in RBE for example you can see the first Clevo and stock Asus vBios are both based on the same vBios from ATI - ATI VER012.017.000.004.035951, but then the manufacturers have to modify it to work with their machines - to get HDMI and VGA working for example...
-
skygunner27 A Genuine Child of Zion
I also notice this flicker on both of my working G73JH 05/A1 since 10.6. Both of my units have never GSODed. I hope this helps. -
Then if you put your car to 10000rpm in red zone 1 hour and it burn it mean that is a defective car...
you should know what is a normal use and a bad use forcing a GPU... -
The difference is that GPUs are made to handle full load for as long as you need em to so tha car analogy is really lame, but if you want to compare to cars - if you buy an expensive racing car will you say you mustnt race with it since it could harm it even though thats what its made for? Do some serious work on the GPU and it will be working at 100% for hours. People dont just use GPUs for games. But you know better dont you. Youll take care that your GPU doesnt overwork itself, poor thing.
-
And what about working sleep mode / hibernation? Did you manage to restore them too?
-
skygunner27 A Genuine Child of Zion
You seem to have a good insight on how these things work. Regardless of your past negativity(Justified), I think you represent a ton of energy/know how that this situation requires.
+1 rep!
Gary should have brought you on yesterday!! -
Sleep is working. But I think it did work even with unmodified MSI.
Correct me if im wrong. -
HellCry, were you able to test HDMI and VGA on the modified BIOS u got?
-
Err that's not an insight at all. That's what we have all been saying! We all already know the vBios is from ATi and that's why we are so curious why the vBios is failing for Asus and not for Clevo, MSI and Alienware.
Umm Gary even made a post stating this.
Why can't any number of you do this? Don't you all have a HDTV somewhere? Or a projector or another monitor in the office if you are at work? -
Well I just ran Furmark for 10 minutes no GSOD, but I did get a horizontal black line flicker.
-
I think I read it somewhere that some1 sad it did not work...but I might remember wrong.
-
We had Hash problem. But its solve now.
Chastity is on it too.
But guys dpnt expect too much. My modification was fairly simple and based on that the notebook was simply not allowing HDMI / VGA access is the Vbioswas not reconize as a Asus one.
WIth my modification G73 think its a pure Asus Vbios and so may unlock the HDMI .
Its only a guess. -
but GPU only overwork if you run furmark to overwork it, or if some company launch a buggy menu like blizzard and their SC2".
It is almost impossible for a gpu reaches at this load level with a normal use... it´s like intelburntest or linkpack in CPUs -
skygunner27 A Genuine Child of Zion
+1 rep.
same goes for you. -
This is something different. For example manufacturer tells you that you can go max 180kph. You usually don't go that fast, but when you do for 20 minutes, the engine just can't shutdown by itself.
-
Maybe the Asus panel is made of such a cheap and unstable parts, that only way to get it working is a very precise vBIOS tweaking...or a massive VGA recall and replace the VGA with a better designed one.
-
You managed to change the SubID for the vBios then? Did you use ATi bios editor or did you use a hex editor for this?
-
It's better then nothing...at least Asus reps can't spot it easily that it's an MSI vBIOS if some1 has to RMA lol
-
Nice theory but it doesn't explain why these MSI- or clevo-customized vbioses still work fully on a Asus G73jh with just some limitations (like hdmi, vga and sleepmodes). And they NEVER gsod.
-
From the first reply I got from HellCry, doesnt seem to work.
Sry guys. at least I tried.
Waiting for Chastity to confirm it failed too just in case... -
wagnard are you using the latest MSI vBios that was released or the older MSI vBios that was released by Xeven a few months ago?
-
DOnt know if its the oldest Xeven use But its not the Current latest.
-
Yeah I suspected that. I took the latest MSI vBios and tried to change the ID to match that with Asus with the ATi bios editor and that's how I managed to brick my vBios. The ID changing didn't seem to work.
The person to ask here is Xeven. Xeven managed to get a MSI, Clevo vBios to install on Asus. But that guy is elusive, never answered my PMs. I believe Xeven is a software engineer. -
I did it with A hex editor. so it didnt brick for us.
-
The redlining analogy is not really correct. GPU clocks can be thought of as engine RPMs, and by default they are left where stability and performance is around optimal. 700/1000 is the GPU's high cruising speed, but you can push it further by overclocking. Doing anything while at a nominal 700/1000MHz, including keeping your GPU at 100% load, should not cause the GPU damage aside from normal wear and tear.
-
This also should be noted to Gary - apart from the actual GSODs, using either 9.12/10.1 stock drivers or msi/clevo bios with any drivers don't show ANY flicker or artifacts either. It is just the gsod prone vbios/drivers combinations that do this. Might be the same with HellCry's observations with Windows loading screen.
-
so with all of the posts i think we lost sight of the new asus vbios beta...what is the verdict?
It sounds like its better but not perfect. is this acurate?
Im going to hold off on this or the MSI till i hear more from you guys... -
Can go back and forth. Fact matter is, the main supporters for running GPU at 100% are only from consumer overclockers. Manufacturers, not just Asus discourage the use of Furmark. ATi in general discourages the use of it also.
-
I do beleive Chasitity is a girl now (not to add blonde too
). Shes rather slow to answer
-
Sleep and hibernation both turned out not so reliable for me after upgarding with MSI vbios. The problem is usually seen when you try to come out of sleep mode /hibernation and the notebook will just crash or turn itself off.
I'm not 100% sure this has anything to do with vbios but I think it's possible (and probable) explanation because these were both functional with stock vbios/drivers. -
Well it's not entirely true. I suspect the thousands upon thousands who are not complaining on this forum do not have GSOD.
I can tell you I never had a GSOD, I know there are a few other G73 owners who used to post here back in February who no longer do, didn't have this problem either.
Gary said the problem with this issue is that the GSOD seems very random. Some units have it, some don't. This issue cannot be stated to be fact with all G73 units, but only the very few.
My issue with vBios has nothing to do with GSOD, I never had this problem. My issue is PowerPlay is not working and no OverDrive. So for Asus when testing to see how their units were working before release, it may be true, all the test units they had didn't have GSOD issue. But what is inexcuseable is the lack of PowerPlay and OverDrive, that they knew about from Day 1 and ignored. -
I heard that the later MSI vbioses really might have bricked G73's. But the older one from March posted in the beginning of that 'vbios update' thread is already version 012.020 and it works great, for me at least (don't need hdmi/vga).
-
does ati support OverDrive in their mobility drivers?
P.S:I have 2 Mx518 also
-
I hate it when people dont read my entire post.
I told you that every manufacturer edits/rebuilds the vBios themselves to make HDMI and such things work, so ATI doesnt make the entire vBios but only provides the basic frame which is than used by all manufacturers and its whatever Asus did with that basic frame provided by ATI that must have screwed it up. The end vBios is built/modified by the manufacturer so the MSI, Clevo and Asus vBios are by no means the same thing and its pretty clear whos at fault here and why its not working.
[GSOD Fix?] Beta vBIOS update for G73JH
Discussion in 'ASUS Gaming Notebook Forum' started by Chastity, Aug 25, 2010.