I just got another GSOD on my G73JH and I know why.

A few weeks ago I got a few GSODs, at least I think that is what it is referred to as. The screen fills with vertical lines and the machine needs to be powered off to reset it. At this time one of the things I did was turn off Powerplay.

And yes I do have the latest vbios installed and I am running 11.2 version of Catalyst.

My machine has been running perfectly fine for a few weeks. This morning though I enabled the Powerplay setting in the Catalyst Control Center. Within 10 minutes I had a GSOD while browsing the web. I am sure Powerplay was the cause, or to be more precise the 405Mhz setting.

Also as others have posted, after a hard reset your machine will keep locking until you can do a normal shut down and restart.

So my advice is, if you are experiencing any GSODs, and you have done the vbios update already, turn off Powerplay, keep your GPU at 700Mhz.

Cheers

 

How do I keep the GPU at 700Mhz and turn off powerplay?

 

Right click the desktop and open the Catalyst Control Panel. Click on the power section.

 

I highly suggest you try my fix_od2 rom, because I don't have any issues like that at all, even using OverDrive.

 

I use PowerPlay regularly, and have zero GSOD events.

Been using all Catalyst versions since 10.6.

 

I'm running 11.3 and no such issues. If i am Ocing , got some minor lock ups in Crysis 2 or NFS Shift but otherwise no issues here. Powerplay is on.

 

Chas, where is this fix you speak of? Is it at the link in your sig, and that's this new updated VBios? Or is it somewhere else? Sorry, I've been MIA for awhile..

When I installed the new VBios right when it came out, I stupidly had MSI afterburner running at the same time with my 800/1100 clocks, and the VBios did something that with Powerplay, off or on, the clocks run at 405/1100 and then the usual 800/1100 in game.

Not that big of a deal, really as I've only experienced 2 GSOD's. But I am interested in this fix you're referring to..

Also, on these GSOD's how much is it possible that a GSOD can be attributed to a particular game and/or code and not exactly a fault of the machine?

 

http://pcaudio.ath.cx/stuff/fix_od2.rar

 

Sorry for the noob question, but now that I've got the file, how do I apply it? Does executing the Windows Batch do it?

 

No the file has to run out side of windows, on a win 98 bootable USB stick.
Extract the 2 files from the .rar to the USB stick , boot the computer from the USB stick, and at the command prompt type od2.bat

If you need more details see the 3rd link in Chastity's signature. BE CAREFUL to read as much as U can first.

 

Ahh, so essentially I have to reflash the VBios.

I don't know if I wanna go through all that again...

 

Exactly right! I never OC so I have not used this particular file, and I understand your hesitancy. I was praying when I did the initial Vbios update on mine!

 

If you are having GSOD problems and you have already flashed to the vbios issued by Gary Key, try turning off the Powerplay and see if your machine is better.

If you haven't flashed the bios at all yet, you have a choice, either use Chastity's or the Gary Key one.

Cheers

 

what is exactly doing fix od2 rom????

Is a vBios??

I'm interested because I started to suffer GSOD with 11.3 and 11.4 preview rc2. Never have GSOD before with 11.2 or earlier drivers. Sometimes happens with either normal clocks or OCs. Happens in both SC2 and Crysis 2 (the most played games). My BIOS is 213 and vBios is v93 from Gary's. My suspects now are going to chrome since it release the latest beta with gpu rendering I started experienced problems. Coincidently, all my GSOD are when chrome is in background (max or minimized) and the GSOD seems to be more than a driver reset than a hardware failure. Sometimes when they came, the screen goes black, the sound start (like) crackling and a couple a seconds later the screen game returns... but sometimes doesn't and the only solution is a hard restart.

 

Nekki you could be onto something regarding Chrome. I do use Chrome and I think it was on for each of my crashes. Having said that though it does not crash if the GPU is set at 700Mhz.

 

Yeah, pretty sure is chrome. Just now, I have a couple of driver restarts using chrome when open a youtube video on battery mode.

 

I already flashed the VBios to Chastity's, and unfortunately, I already have Powerplay off

Any other ideas is greatly appreciated

 

Simple. Stop OC'ing to 800/1100 when gaming.

I get GSODs at those clocks while gaming too, but synthetic benches allow me to go to 820/1150. Your gpu just wasn't blessed with the 800/1100 gaming ability. FWIW, mine tops out at 780/1100.

PS: I switched to Chrome and used it for the whole day with Powerplay on/off, no issues.

 

Nekki Fix od2 makes the over drive option become available in CCC. I am sure you know about using RBE but for anyone who want to look:

Not on point ,but battery clocks are set to 100/150

PS thanks for your help in the past!

THX5334 have U removed afterburner at this point? If not I would get rid of it... Also maybe a clean install of the video drivers would cure this??
Are you on 11.2 Catalyst or later BTW?
What is the version of your Vbios
Video BIOS Version: 012.020.000.032.038352
HWinfo32 indicates that is what I am running (I did not use Fix od2).

 

Or if you dont need any external monitors, use a vBios that actually works as it should (the MSI or Clevo one).
I had GSODs on all of Asus vBios (even the latest "beta" ones), powerplay didnt work right (sometimes just didnt clock up to 3D clocks in games or got stuck on 3D in idle), idle clocks were horrible - so were the temps, overdrive is broken (memory clock gets stuck in overclocked state), theres just too few clock profiles to manage things properly (also probably the cause of flicker when changing clocks without having a MED profile)...
With MSI the GPU works as it should. Idle clocks & temps are way lower as they should be (to the point when the fans turn off when the laptop is just being used to browse the web or minor work like that), powerplay never fails to clock up/down, overdrive actually works, no flicker or GSODs ever (ive been using it for almost a year now). Only downside is the external video ports (VGA, HDMI) dont work with it (since its not coded for our hardware specifically).
I know, people say not to encourage doing this, since its not the safest thing (and they do have a point, it can result in a failed flash - and you have to blind flash back then), but if you know what youre doing (you have to edit the hardware ID in a vBios editor at least) it actually makes the GPU work as its supposed to, unlike what you get with the half-broken Asus vBios (wheres that final fixed vBios Gary was promising? and the "final beta" we were given never made it on the official download site either...). Just some food for thought...

 

Why to modify the brand in vBIOS?
Just flashed a MSI vBIOS to the Asus card. No problems.
Wanted to know, if the "hardwired" voltage is really hardwired.
Seems so.
No temp decrease with 700/[email protected].

 

Changing ID is just my way to avoid the force flash method.
And yes, the voltage is hardwired i believe, also tried changing voltage when ziddy claimed it drastically reduced temps and it did squat for me. Clocks have the major impact on temps in my expirience. I did lower voltages back in my moddded vBios (before i used the MSI) just in case it did do something for others...

 

i am wondering if with the MSI vbios on the G73JH did the clocks jump for some applications?
can you answer this HellCry
like in this video
<param name="movie" value="http://www.youtube.com/v/a-bA3ug5sJo?fs=1&amp;hl=en_US&amp;rel=0"></param><param name="allowFullScreen" value="true"></param><param name="allowscriptaccess" value="always"></param><embed src="http://www.youtube.com/v/a-bA3ug5sJo?fs=1&amp;hl=en_US&amp;rel=0" type="application/x-shockwave-flash" allowscriptaccess="always" allowfullscreen="true" width='640' height="390"></embed></object>

also i don't want to change the ASUS vbios becouse finally i kept my clocks at 70/100 for videos on batery

 

I didn't include the ATIFLASH.exe in the 2nd package since I figured people had the first package.

@Hellcry: I can't exactly agree with your assessment of the Asus vBIOS. The only issue you list that I have is the memory clocks stay at the OC setting when on AC power. But then again, perhaps this was intentional to avoid screen flicker. When I switch to battery, Overdrive uses the proper battery settings. All of this is with PowerPlay enabled.

OTOH, I don't think I can be accused of having high temps. Plus my core clocks go up and down properly as needed.

 

chastity poke garry about the vbios if he is still in a repairing mood

 

I'm using the 11.4 preview drivers

My Video Bios is the same as the one above except I used Chastity's version.

The problem with removing Afterburner is that because I had it on when I updated the vBios somehow it's now tied in and if I remove it I end up with only the clocks for battery and can't even get the normal clock speeds

Also, the other thing I like about Afterburner or EVGA Precision is that I can monitor temps and clock speeds in my Logitech G13 gameboard window, thus keeping my primary screen free of any visual clutter not related to the game. If anyone has any ideas of another program that lets you monitor temps concurrently in a G13 or similar, I'd really appreciate any info.

I have had exactly 2 GSOD's since the new vBios. One was in DCU Online and the other in Crysis 2. I wonder if Crysis 2 may just not get along with the AMD/ATI drivers at this point?

And to the poster that mentioned it, you're right, the GPU might not be stable at those clocks, but I played BFBC2 for months on those clocks with no hiccups. Unless the wear and tear of running it at those speeds is catching up?

@HellCry

Unfortunately, I use external monitors and need that HDMI port, otherwise I'd be all over your modified vBios. If you can get that working, let us know.

Cheers

 

He really can't get that to work, as he would need to generate a matching BIOS for the G73JH.

Also, running Afterburner should not affect the system. Only thing I can think of is maybe a registry fubar?

To fix, strip out afterburner + drivers. Reinstall the video drivers with a clean install (ATI Crap Cleaner or DS 2.90 applied after uninstall) and see if the system works properly.

 

I'm sure you're right, and it's a registry issue.

I'll try this later when I get home.

Thanks, Chas!

 

@Chastity
Oh im not talking about powerplay not switching properly from AC to battery, as far as i know that always worked. As many others also reported the Asus Bios sometimes just doesnt clock up when you start a game and stays at those idle clocks (405 or what was it?) which turns a game into a slideshow unless you manually reset the clocks in ATI GPU Clock Tools (or just dont use powerplay which is just not a solution).
And i had flicker with the Asus clock settings when it was changing clocks, never with MSI (i cant say why, i just suspect after comparing the two that its the lack of MED load profiles like MSI has em so it can switch gradually, but i cant say for sure).
I know your temps are extremely low, but be honest - those temperatures are more of an exception with the Asus vBios, most people cant get anywhere near that (perhaps you have a much cooler card, cooler room, a freak amazing paste job - i dont know but its rare). I can just compare the temps i had on the Asus vBios vs. MSI vBios on the same laptop, with the same GPU, with the same paste job and theres a big difference...

I know you dont support the use of other manufacturers vBios since its a potential risk to brick the machine (actually its practically the same risk as flashing the Asus vBios as i see it, but the risk is still there), but when it works so nicely i just have to present it as an option (if you dont mind being without external video with it) .

@mite_jan
No ive never observed any problem with clocks on the MSI vBios. Ever.

@THX5334
I cant get HDMI/VGA out to work, nor can anyone but Asus, we just dont have the tools or the source AtomBIOS ATI hands to manufacturers who then tailor it to the specific harware used in their machines (so the specific hardware in this case that doesnt work is the HDMI & VGA out, as it turns out the use of different memory chips on the GPU doesnt matter much).

As a certain someone said im

so its my time to go again .

 

i don't know if you are familiar with this HellCry but there is a GX660 VBIOS and the GX740 (5870 mobility) date 2010 November
i haven't tried it , i've saw it on the official MSI site
MSI Europe ? Computer, Laptop, Notebook, Desktop, Mainboard, Graphics and more
http://global.msi.eu/index.php?func=downloaddetail&type=firmware&maincat_no=135&prod_no=1999

 

Never seen reports of this before. Never experienced it myself either so...

Also just wanted to put this out there. Something that's been repeated since the dawn of the JH. On the ASUS vBios, core clock changes do not result in flickers, but memory does.

And as for temps, its because of the voltage. Asus locks it at 1.15 at stock 700/1000 clocks, and 0.95 on idle clocks. 405/1000 ( or whatever you have it set at)

Just wanted to ask HellCry this though, can you alter the voltages properly on the MSI vBios? Isn't it hardlocked to the chip or something. If you can, that's probably the reason for the lower temperatures as the 5870m in the AWs run at lower voltages too, compared to the Asus G73s.

 

The voltage of MSI (all but Asus?) 5870m can be altered.
Imo there is a operating range between 0.8-1.15V.
It might also start from 0.85, IDK. The thing is, you even can set 100/[email protected] and the gpu still works. It's like a protection against to much undervolting.

With the exchange of the Asus card I wanted see, how much cooler would the gpu run with such undervolted settings. But there was the issue with the fans running at fullspeed. Cool but loud :|

 

@BumbleBoner
Dig up the old threads and youll find such reports. People ran games and had horrible framerates. The cause was the Asus vBios which just decided not to switch clocks to HIGH profile but stayed at LOW. The solution we suggested was to disable powerplay...

@mite_jan
Ive been using the MSI version BR35757.023 from 06/04/10 (ATOMBIOSBK-ATI VER012.020.000.032.035757) since it came out.

Voltage on these cards seams to be hardwired, becouse i can change it in vBios or with software and see no change in temperature. The MSI vBios is cooler becouse it has 3 clock settings for each profile (AC, Battery), and its idle clock as you can see here (the LOW - clock info 01) has 100/150 clocks vs Asus 405/1000 (this is also one of the risks of flashing to the MSI vBios - as Asus makes inferior cards, some cant handle to run at such low clocks as the MSI has, so if you want to flash to it, you should at least test prior to flashing if you card can indeed run at 100/150).

As you can see in the Asus vBios, MED & HIGH are the same profile (clock info 00). Just compare the two and you can see right away what the Asus vBios is lacking here. On both screenshots i highlighted the AC profile.


MSI vBios


Asus "final beta" vBios

This has been discussed before in length, but those threads got burried with time... There really isnt any doubt that Asus could have made a decent vBios if they wanted to, but as it stands its far inferior to what the competitors (MSI, Clevo) have. Most say the Asus vBios is still fine, id call it half-functional or crippled at best.

 

Alright.
Where do you use this MED setting?
Imo it's just a gimmick. The newer 027 vBIOS has only 6 clock settings too.
And you can alter the idle states. Currently i'm at 70/100 (clock 01).
There is just this damn voltage lock. The card could be much cooler and fanless while idleing.

 

This MED setting is used to gradually switch between clocks (and ive even seen it be used in some older games where the load isnt so high).
If you change the LOW clock on Asus as you have done, the fast switching of clocks can lead to flickering/instability as weve seen with my modded Asus vBios where i used the MSIs clocks (100/150 on LOW - worked fine for some, but flickered/was unstable for others).

Edit: And i checked the MSIs latest (027) vBios and it still has 3 profiles (LOW, MED, HIGH). They just merged 2 profiles (one profile before wasnt ever used), thats why it hass less clock infos.

Thats it from me... i really dont need to convince anyone anymore, ive finally fixed up my laptop so it works as it should and you do with yours as you want to, im not forcing anyone to use this .

 

i don't care about the overdrive on the Asus vbios becouse i don't use it (when i play game i use amd gpu tool to overclock and when i close the game i just pres restore defaults) and yes Overdrive doesn't work with the Asus vbios ...i don't know why some are telling that works for them

i care about the flickering and the jumping clocks which occur often (if that can be fixed with the MSI vbios) .... and also we all had at least 1 or 2 GSOD with the Asus vbios (so it is not GSOD free)

but still i won't experiment
not so big problem

 

@HellCry
I'm not a prayer. I just explain my experience.
I've been modding vBIOS's of 5870 since a year (on X7811). A french Medion X7811 was the first 5870m notebook with a working powerplay vBIOS.
MSI released this 1 month later. G73 users were still frustrated with the GSOD bug.

I tested the latest MSI vBIOS on G73 too. No difference.
Also I had never flickering. With or w/o overdrive. Overdrive is working as it should.
Switch from 70/100 to 825/1100 flawlessly.
Btw.: Never ever saw a GSOD.

 

i don't know of what kind of flickering you are talking about @tilla but we are talking about this one (actually it is not even like that ...there are on top of the screen showing horizontal line for a m/s when changing the memory clocks like in this video when he is playing youtube videos (even if you change 1MHZ higher or lower it will flicker)
width='640' height="390"><param name="movie" value="http://www.youtube.com/v/L9PMqcFBdO4?fs=1&amp;hl=en_US&amp;rel=0"></param><param name="allowFullScreen" value="true"></param><param name="allowscriptaccess" value="always"></param><embed src="http://www.youtube.com/v/L9PMqcFBdO4?fs=1&amp;hl=en_US&amp;rel=0" type="application/x-shockwave-flash" allowscriptaccess="always" allowfullscreen="true" width='640' height="390"></embed></object>
i believe that everyone is experiencing this but who knows maybe your graphic card is some prototype

and also overdrive doesn't work properly with the ASUS vbios (don't make me do a video about it
p.s that's why my signature looks like that

 

I'm not speaking about the movie "Flickering lights".

I only see this flickering when chanching clocks through AMD Clock Tool.
At the moment the "Set Clock" is pressed.

What driver you are using? ATM I'm at 11.4 preview. This is a bit weird, because the clocks here don't change to UVD setting anymore (youtube play etc.).

You can make a vid, my card with Asus vBIOS is working without such problems.

Edit: Just see the "Dual" thing. This is the point. The GPU reacts differently while plugged in an external display. But this is not my fault.

 

the clocks doesn't go to UVD when watching videos becouse you have batery clocks probably to 70/100
i have the same clock and it doesn't clock to UVD which is kind of nice and i don't know why they don't want to clock ...only hapens when the clocks are too low so if i set them to 100/150 they will probably go to the UVD clocks (yesterday i was able to watch a whole movie on baterry 1:40min yupiee)
so if the flickering happens when changing the memory clock with amd clock tool it must flicker when going from baterry to AC or 2D to UVD except if you don't have the memory clocks the same

the dual thing was just an example on what flickering i was reffering

 

In my OD2 vBIOS, I have AC idle and UVD at the same clocks, so you won't see a change either.

 

Ive been using powerplay for almost 6 months now with no bsod. But then again, I guess I got a lucky one cause I have never gotten a bsod even before the new vbios./

 

Try installing and running Google Chrome for a while and see what happens.

 

google chrome installed here with powerplay active and no BSOD (not that i use it very often)

do some formating man and call it a day