AMD Catalyst 13.6 BETA (13.101.0.0 May 23)

Ahh man i'm considering ditching Windows 8 here.

I cant uninstall 13.5 betas as the computer just shuts itself down and restarts when it gets to the point of uninstalling the display driver.

I tried also from device manger and the same, just shuts down and reboots.

Not touching that ATIman crap either as I remember on my last install it did something similar.

Guess I need a clean OS install to use these

 

Uninstall from safe mode.

 

oh yeah, what a noob I forgot about that !!!

i'll give it a try !!!!

 

Or use driver fusion.
http://treexy.com/products/driver-fusion
(free version is fine)

- run
- select AMD display driver
- remove any found entries
- reboot
- run again
- select AMD display driver
- remove any found remaining entries
- reboot
- install new version

Now, to get the old F8 option back in Windows 8, even for UEFI boot, from an elevated command prompt type:
bcdedit /set bootmenypolicy legacy

This should be the default. I can safely say that not making this option available was a stupid move for even a dumbass to make. You need safe mode because you can't enter Windows right? It's the whole point of it, yet by default, you need to enter Windows in normal mode, and navigate your way to finding the section where you can select to start in safe mode on the next boot. Completely useless!

 

Oh boy.

I managed to boot to safemode, obviously the uninstaller isn't supported, so I unistalled via device manager.

Rebooted and then when it tries to install the new driver.... system crashes and just restarts.

So no i'm stuck with the 1.2 WDM driver that comes with Windows8.

Just to clarify, its not an issue with these 13.6 drivers to anyone reading.
Its Windows8. I love it and hate it in equal measures.

Fresh OS install here we come, see you all in about 3 days...........

 

You don't need a fresh install, just use driver fusion as I outlined above. Worked perfectly for a friend that called up in a panicked state last night with the same issue (just thought it was him!).

 

Isn't the frame metering driver supposed to be coming in June or something?

 

Thanks....!

 

Hello all,

I'm unable to install this new set on my old switchable ATI card.
(PCI\VEN_1002&DEV_68C1&SUBSYS_1436103C&REV_00)

It was fine up to around 13.5 beta1 driver I think, then it fails from latest 13.5 beta and this one even though I clean the previous driver.

By setup or device manager the same error (hopefully correctly translated from FRE to ENG...):

Any idea pls ?

 

Thanks! :thumbup:, i've been searching for an updated version, but I couldnt find anything.. His site went down a while ago

 

These are absolutly WONDERFUL drivers.
13.5 were completly unstable for me no matter what, 13.4 were only just barely stable if I didn't overclock the cpu.
13.6, however are smooth and fine. Very good build, stable even overclocked to 4.8!
Couldn't be happier, upgrading the C++ base was huge for system stability, even gaming performance has increased for me in tombraider and metroLL. (Going from 13.4 to 13.6 that is, as 13.5 was such **** uke2

Thanks AMD/Asder.

 

Driver is fantastic so far for my 7970M!

 

If a CPU overclock was causing further instability in 13.4, wouldn't that mean your CPU overclock is unstable?

 

Finally think I've fixed the HDMI stutter when I'm watching a video on the TV and also have the PC running on DVI

----
GPU scaling on both displays
Disable Alternate DVI freq
Use scaling values

 

I get the same error. System specs on the left. Previous drivers I could always install using Device Manager. No go with these.

 

Installed on my HP Laptop Win8 with no issues.

 

Do these include CAP's or should we still be using 13.5 CAP1?

 

The server space used was kindly donated by a user on a different forum, who also had his stuff at another address (a complete and updated Windows hotfix repository). The site had been the victim of frequent DOS and DDOS attacks, as well as people trying to hack it from non-consistent IP addresses. As a result, he had to effectively 'close off' access to the server. The remote access that trusted users had, had to be removed as they posed a security risk.

Anyways, for now the stuff is accessed by:
https://www.dropbox.com/sh/yvo0u5lrac3whv2/j3Uhlqc9j8

but site forwarding may be an option later (in that it is hosted on dropbox but accessed through a more palatable web address).

A simple Directx mod will be available shortly that may or may not be of some benefit in Directx 10.x/11.x games. It will be able to be easily undone.

 

These drivers are smooth and everything installs fine for me unlike the leaked 12.105 13.x drivers where CCC simply would not work for me.

These all work fine, but I am getting extremely low GPU usage in BF3. In some areas its 40fps @ Ultra settings and 60% GPU usage. Whereas before it was 99% usage all the time and Ultra settings was around 70fps and 50fps min in extremely heavy battles.

Going to install 13.5 CAP1 and see if that helps. Also will install those Visual C++ updates Thanks for those.

 

About the various Visual C++ run times. A program is developed and tested with a given version. A newer or older version may lead to unexpected behavior, and unless a security patch is involved, it's not a good idea to use another than the tested version. Even a security update may screw things up.

This is how it goes: A version is installed to a central location. If the software requires (parts of) a specific version than it is installed in the folder containing the executable. That ensures that only that version is used, because a locally installed version has a higher priority than the global one. Simply put: Windows always looks for a required DLL in the folder of the executable and when it is not found there then it looks for the globally installed one.

In fact it is a bit more complicated than that. Here are the complete rules: Dynamic-Link Library Search Order.