AMD Catalyst 14.9 WHQL Download
Click here to post a comment for AMD Catalyst 14.9 WHQL Download on our message forum
theoneofgod
Evildead666
Well got back home yesterday to find the main PC with a black screen, No DVI Input.
Rebooted the PC with the reset button, heard all the correct sounds for booting, windows startup, but I can't even see the Bios screen, which freaks me out.
Whats even stranger, is that my Nas, another PC, but on the same network, also has no video output, but its a Radeon 6670-LP, whose drivers haven't been updated in ages.
I finally got the Intel integrated drivers installed, but no Radeaon 290 detected at all in Device manager.
Will check tonight to see if in the Bios it hasn't switched to integarted only, but thats more of a prayer than anything else...
edit: Just to be clear, I'm pretty sure it had nothing to do with the drivers. I posted this here in case anyone else had the same sort of thing...(not that i'd wish it on anyone...)
theoneofgod
SpecChum
Rich_Guy
Looks like im going back to the good old 13.12s, as im playing Fear again at the minute, been running fine, but i just can't get past the Alice Wade level at the minute, as the bugger just keeps freezing.
First time was after about 20 minutes, second time was about a minute in, just freezes, and when i CTRL+ALT+DEL to get the Task Manager, it takes an absolute age, as rigs on a go slow, then when i eventually get there, and get the games process ended (even though it says its running ok), my GPUs stuck at 100% load, so i have to reboot, as whole things slow as hell.
Rich_Guy
Odd, just tried it again, but this time with my memory clock back to stock (was using 1300), but still keeping the same core clock of 1080, and i played it for over an hr fine, wtf :P
Can't see how an extra 50Mhz on the memorys to blame though, as Fear is hardly taxing, as i can play it on my low clocks profile (515/625), and still be locked at 144fps v-sync'd.
Actually, i should just play it on my low clocks profile 😀
lukas_1987_dion
kakarot
Weird you guys are having so many issues with the cards/drivers. I mean I had some black screens when I got the card at launch but after a couple of driver releases and a vga bios update from asus I have not seen one since.
I've used it on x58/z77/z97 and win7/8 with a nice oc (1100/1300), 24/7, without any issues. I do however always do a complete uninstall and use driver fusion pro for every update and also install as admin even tho I always am one
N0bodyOfTheGoat
Yet to work out a pattern, but sometimes I cannot get my pc to "wake up" after I have been away from it for a while, forcing me to either hard reset or power off then on.
xxela
This drivers are useless. Although I don't have any problem or bugs with them, in terms of performance 14.4 are superior in every game I tried(Crisys 3, Crisys 2-maldoHD, Metro last Light, B4, Watch Dogs and even that stupid port The Evil Within). So I suggest for the people who experienced issues with them to stick with 14.4 and don't worry, you wont lose anything.
Where is all those % increase listed in the release notes I don't know.:question:
yasamoka
xxela
Octopuss
OVer the last few days, I experienced a few weird freezes. The monitor turns black all of a sudden, and within like 10-20 seconds the entire PC freezes.
Is that the driver bug I've been hearing about or not?
Octopuss
Hm, no, it happens completely randomly while I am sitting at the PC doing things. Definitely not related to any power saving features at all.
Octopuss
I run Windows 7.
Normally I'd say I messed something up, but I haven't installed anything significant, and except for Catalyst, I haven't updated any drivers either.
Maybe I should reinstall the system anyway...
Octopuss
Of course. I installed the 14.9.1 beta today, but don't expect anything to change.
FunkyMike
Try this Eddie:
http://forums.guru3d.com/showpost.php?p=4952235&postcount=5
FunkyMike
Look above frezz
FunkyMike
Sorry pal I have been cracking this issue for 1 month now. Dell shares a wakeup issue with the Probook.
Removing CCC is the only way right now to make it go into standby and wakeup properly.
I have around 3 testers right now that are helping me with this.
I believe it is down to a dword conflict.
As you can imagine it is rather hard to solve but it is one of my goals for UnifL.
You could be of help if you are willing to tinker.
Btw I am not sure if AMD is aware of this bug and whilst AMD is supposed to support mobility themselfs there seems little chance as your device isn't old but fits into the behavior pattern of oldish 7xxxm cards.