14.8 WHQL's out

Hapatingjaky said:
Not that I know of. I think there was a 13.x driver that worked but I am not sure. This is a known issue and has existed for a very very long time.
Click to expand...

For several versions, acceleration didn't work with Firefox, either--but that has been fixed as of the last few versions. Never knew if it was a driver problem or a browser problem...
 
The official 14.4's do work nicely for me. I will be waiting for the next official set I guess. My days of benchmarking are over, I value the stability more. :D
 
Still waiting for official WHQL's or even new betas from AMD. I understand they are probably implementing fixes from their latest push for feedback, so I am being patient, but having to resort to single card in DX9 games blows.
 
WaltC said:
For several versions, acceleration didn't work with Firefox, either--but that has been fixed as of the last few versions. Never knew if it was a driver problem or a browser problem...
Click to expand...
My take is that it was an Adobe problem, since it appeared just after a Flash patch.
 
I have not got flash installed, I use html5 configured for youtube and don't bother with sites that use flash....and I still have had the occasional video lockup.
 
Korrigan said:
My take is that it was an Adobe problem, since it appeared just after a Flash patch.
Click to expand...

Could be...haven't had the problem in quite sometime, however (over the last several recent Catalyst driver/Ff browser releases.) But as I recall it was a problem that persisted over several Catalyst releases, and therefore several Flash version updates, as well. But, again, seems completely fixed for the last several versions of both the browser and the Catalysts--at least, it is for me, I'm happy to say.
 
caveman-jim said:
please submit this here - http://www.rage3d.com/board/showthread.php?t=34013403
Click to expand...


Thing is, this has been a complaint for months now on every tech forum in existence. Is there not someone in AMD's employ who's a liaison or something that looks at this stuff? It's like the black screen issue. The pixel clock issue. The dx9 issue. Monitors not waking up. etc...Those are the big hitters, and it only takes briefly looking at any enthusiasts forum (hard ocp, here, oc.net, overclockers.uk, guru3d, etc...) to see these are the issues with the most complaints.

Not knocking you, I am just saying these are well known issues. Shouldnt take a form when there is that kind of response just sitting there for anyone to look at.

hey look here as i type, lol:

TxZVuU.jpg


lol @ these cards.
 
t0adp1p3 said:
Thing is, this has been a complaint for months now on every tech forum in existence. Is there not someone in AMD's employ who's a liaison or something that looks at this stuff? It's like the black screen issue. The pixel clock issue. The dx9 issue. Monitors not waking up. etc...Those are the big hitters, and it only takes briefly looking at any enthusiasts forum (hard ocp, here, oc.net, overclockers.uk, guru3d, etc...) to see these are the issues with the most complaints.

Not knocking you, I am just saying these are well known issues. Shouldnt take a form when there is that kind of response just sitting there for anyone to look at.
Click to expand...

and that, Sir, is very well said :up:
 
Mine have the black screen issue as well. I had to disable monitor sleep, and just go with a blank screen save. :bleh:
 
Filled out feedback on my many issues "again".

While on the AMD site I was alsked to do a survey.

It asked a whole bunch of krap about brands and buying products , but not once asked if the level/competence of support will affect what I buy next.

Just a a whole bunch of krap fishing for gimicks to sell AMD stuff...so they think marketing is going to fix defecting customers...sad
 
Bitey said:
Filled out feedback on my many issues "again".

While on the AMD site I was alsked to do a survey.

It asked a whole bunch of krap about brands and buying products , but not once asked if the level/competence of support will affect what I buy next.

Just a a whole bunch of krap fishing for gimicks to sell AMD stuff...so they think marketing is going to fix defecting customers...sad
Click to expand...

The survey was a) voluntary and b) unrelated to your service issue (which is why it seemed unrelated.) Most of the time, web-site impromptu surveys are done by third-party companies the owner of the web site (AMD in this case) has hired to conduct the survey.

Long-distance tech diagnostics are among the most difficult of all technical problems to address, because when I as the "techie," let's say, say "tomate-o," you are thinking "tomah'to"...;) The number of variables in trouble-shooting is staggering and it is hard enough for me when I'm sitting right in front of the problem box...! If I'm doing trouble-shooting by email or telephone, and especially if the person with the problem is not terribly experienced himself, then often the cause may be completely hopeless--because the person with the problem usually fails to correctly define his problem; or barring that, he fails to correctly follow my instructions even though he *thinks he is following them to the letter*...;) Thankfully it has been many years since I've had to do that...

It's been a long time since I've seen the error Toad talks about above, but I *have* seen it, of course, just not in a while...;) The difficulty in discovering the source of the problem is that it may be caused by a local variable in the host system, or it may caused by an undiscovered bug in the gpu driver, or it may be caused by a third-party application bug, etc. One of my own past difficulties concerned a BSOD I kept inexplicably getting that identified my gpu driver as the culprit. Making a long story very short, at the end of everything it turned out that I had of all things an intermittently failing *hard drive* that, when it failed was setting up a cascade of device failures in the system that *ended* with gpu failure and the OS incorrectly identifying the gpu as the source of the problem when it was actually only the last component in the chain to fail prior to the BSOD appearing...!

That was a tough one to isolate, let me tell you! But I solved it by stripping everything down and going the install-each-component-one-by-one-until-the-problem-repeats method. Had a similar problem one other time with a bad RAM DIMM that only manifested as bad when certain software attempted to address corrupt ram addresses--otherwise there was no sign of a problem. Oddly enough, the OS also misidentified the problem as the gpu driver in that case as well--when replacing the DIMM fixed it.

More often than we might think, OS error messages misidentify the sources of the actual problems we may have. I learned that the hard way...;)
 
You must log in or register to reply here.
Back
Top