• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

The AMD Driver Thread

Martini1991 said:
It's not the OS that's the fault, it's the crap AMD are releasing that is! I'm not testing AMD's broken drivers!
Click to expand...

It is the OS fault for Auto installing Driver! I guess is conflicting with other driver!

If the early build of Windows 10 had other options on installing updates you wouldn't have this issue you having..

You beta testing, report the bugs with Microsoft!
 
It's not the OS's fault that AMD's driver is broken.
That's like blaming a car dealer for a car crash.

Your process of blame has blatantly shown your complete lack of objectivity for me. GG.
 
Martini1991 said:
It's not the OS's fault that AMD's driver is broken.
That's like blaming a car dealer for a car crash.

Your process of blame has blatantly shown your complete lack of objectivity for me. GG.
Click to expand...

It is the OS for installing a driver automatically, a driver that sounds like its conflicting..

Plus the fact you using a driver that isn't for Windows 10
The AMD Catalyst™ 15.4 Beta Driver can be downloaded from the following links:
AMD Catalyst™ 15.4 Beta Driver for Windows® 7 32-bit
AMD Catalyst™ 15.4 Beta Driver for Windows® 7 64-bit
AMD Catalyst™ 15.4 Beta Driver for Windows® 8.1 32-bit
AMD Catalyst™ 15.4 Beta Driver for Windows® 8.1 64-bit

So you using a driver for Windows 8.1 and coomplaing when Windows 10 is updating to a Windows 10 driver and conflicing..

User error and complaining :rolleyes::eek:

Learn to use your PC and you wont have these silly issues.
 
Oh, just forget it Shanks. Such a fanboy. You don't have a clue what you're on about. On the ignore list you go, I can't stand you anymore.
By that logic for the past year that W10's been previewing that no AMD owner should be using it.
 
Martini1991 said:
Oh, just forget it Shanks. Such a fanboy.
By that logic for the past year that W10's been previewing that no AMD owner should be using it.
Click to expand...

User error move along..
Dont complain when using a driver not designed for that OS!!

Simples!

No you should be using the Driver that comes with Windows update, not installing the Windows 8.1 driver...
 
humbug said:
I use it and don't get the problems you do, i accept that you do but Shankly is just trying help.
Click to expand...

Shanks isn't trying to help at all, he's just being himself.

And I know how to fix my problem. I just have to go onto my Intel IGP, uninstall AMD's driver.

Put card back in, install 15.4 and presto, no broken PC.

But then eventually it'll update to the broken driver again when I update the PC.

Rinse and repeat.

By broken driver, the performance with it is lacklustre. GTA 5 will go "out of signal" if you alt tab etc. I know it's AMD's driver because it happens to my brothers 7950 when the driver downloads too.
15.4 has no problem. But you can't just install over the W10 driver, or you'll get a "thread stuck in device driver" BSOD, and then you can't boot into W10 with the AMD card :p
 
Last edited:
Martini1991 said:
Shanks isn't trying to help at all, he's just being himself.

And I know how to fix my problem. I just have to go onto my Intel IGP, uninstall AMD's driver.

Put card back in, install 15.4 and presto, no broken PC.

But then eventually it'll update to the broken driver again when I update the PC.

Rinse and repeat.
Click to expand...

No I am helping! and have helped you figure out why you getting this issue..

The Problem
You using Windows 8.1 driver on Windows 10, An update is installing the correct Windows 10 driver and then conflicting.

The Fix
Remove Windows 8.1 driver and use the Windows 10 driver like you should be...

If that isn't helping I dont know what is..
 
Shanks, just stop. That doesn't fix anything, it's the driver that's the problem. I did a fresh flipping install of W10 and tried using AMD's borked driver, lacklustre performance etc.
Remove and whack on 15.4, hey presto, it works. There's no conflict. Only perhaps with you, logic and objectivity..

The fault is with what AMD has on the updater, the fix is for it to no longer be on the updater.
End of.
 
Last edited:
Martini1991 said:
Shanks, just stop. That doesn't fix anything, it's the driver that's the problem. I did a fresh flipping install of W10 and tried using AMD's borked driver, lacklustre performance etc.
Remove and whack on 15.4, hey presto, it works. There's no conflict. Only perhaps with you, logic and objectivity..

The fault is with what AMD has on the updater, the fix is for it to no longer be on the updater.
End of.
Click to expand...

"PIBKAC" Problem Is Between Keyboard And Chair
 
Using Windows 10 10074 myself and while it is annoying that the Microsoft Amd driver download's when updating it is one of the quirks of using a beta OS where Microsoft have disabled allowing users to pick and choose which drivers to install and which not to install until they release the final version.

I could not really blame Amd on that as if I was running Windows 8.1 instead of a beta OS I would not be experiencing these annoyances.

As a sort of a work around for this problem I turned off the Windows update service so it would not download any updates and install the offending Microsoft Amd driver instead of 15.4. It means having to manually install any updates/hotfixes after 10074 was released though.
 
You can't blame MS for the issue.
The blame lays with AMD only.

To make a case more "extreme" but relevant in how blame works.
A gunman is to blame for his actions, not the gun, nor the store who supplied him.

The store in this case would be MS's updater, the gunman would be AMD and their driver.

That's just how blame works.
 
Martini1991 said:
You can't blame MS for the issue.
The blame lays with AMD only.

To make a case more "extreme" but relevant in how blame works.
A gunman is to blame for his actions, not the gun, nor the store who supplied him.

The store in this case would be MS's updater, the gunman would be AMD and their driver.

That's just how blame works.
Click to expand...

Wow sounds like you really dont like AMD do you.
Also stop with the bad examples.

The gun was working fine with its ammo (Gun = gfx card, driver = ammo)
Then MS comes installs another driver and then messes things up
(dud ammo = MS driver)

= AMD fault... okay...

wait when you say your pc updates you mean AMD driver will update or a MS update? Now im confused.
 
You must log in or register to reply here.
Back
Top Bottom