Yes why should I check if my existing board supports this new cpu? It's the same socket dammit I shouldn't need to check
If the CPU and motherboard manufacturers both say it should work I would believe them TBH
-
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.
Small problem with 4K monitor, loves Titans but hates 290Xs
- Thread starter Kaapstad
- Start date
If the CPU and motherboard manufacturers both say it should work I would believe them TBH
I reported it to AMD yesterday but I have not heard anything back, not that I was expecting to.
Have to wonder about all the issues with 4k and video cards, seen plenty of reviews with multiple cards on a variety of screens and only the odd issue encountered.
I think they get plenty of problems but they don't share them with us. A good giveaway is some of the bench figures they get are often way off what they should get where they have had problems.
Soldato
- Joined
- 28 May 2007
- Posts
- 10,226
Then you are in for some surprises. My old e6600 should have worked with my motherboard as it was compatible. Built the machine and it did not boot up. After a little googling the motherboard needed a bios update. Lesson learned and i am better for the experience. More reading required end of story. Just because it says it will work is no guarantee in the PC world.
+1
The monitor should not even see crossfire as it is done on the cards and there is only one output. My problem is something that is happening on the cards which lays the problem squarely at AMDs door. If 18 month old Titan's and two year old GTX 690s don't have a problem with the monitor that rules out the monitor.
Soldato
- Joined
- 28 May 2007
- Posts
- 10,226
No it's not. If i had read up i would have known. I believed what i read on the ocuk page and got bitten. It also relates in the fact that i was buying an early technology as well as the early conroe chips and motherboards had compatibility problems. 4k is relatively new so people should be even more careful. Had i done what i do now i would have been fully informed. You have to be 100% when it comes to hardware Rusty.
Last edited:
Associate
- Joined
- 7 Oct 2013
- Posts
- 32
I've run an Asus PB321Q 4k monitor @ 60hz on 3 x R9-290X cards since they first came out with no problems using the original drivers ( Titan GTX cards wouldn't boot in MST 60hz ), however I did experience similar issues to you since beta 14.1 drivers came out. I found that the catalyst control centre was not removing the old driver cleanly while installing the new driver, the simple workaround was to use DDU to first remove the driver before installing the new driver. I've only experienced this up to beta 14.5 since I've now gone back to NVidia cards.
Definitely the drivers.
I have just tried 13.12 which allows me to boot @30htz and then set 60htz no problem.
I then went back to 14.6 and the problems are back.
Definitely the drivers.
I have just tried 13.12 which allows me to boot @30htz and then set 60htz no problem.
I then went back to 14.6 and the problems are back.
At least that means it can be fixed. I will make sure this gets their attention Kaap.
Soldato
- Joined
- 5 Sep 2011
- Posts
- 12,888
- Location
- Surrey
As said earlier, a driver quirk, I'll be sure to mention it when I have a response RE SST issues
Oh Kaap, you and your PEBKAC issues.
You would discover this right after i sent a few emails wouldn't you. Oh well, at least we know the problem is not with the drivers on this occasion.
PEBKAC
PEBKACAK = Problem exists between keyboard and chair and Kaap.
Last edited:
Oh Kaap, you and your PEBKAC issues.
You would discover this right after i sent a few emails wouldn't you. Oh well, at least we know the problem is not with the drivers on this occasion.
PEBKACAK = Problem exists between keyboard and chair and Kaap.
The problem is very real with the drivers.
13.xx work
14.xx don't
And as TheRealDeal has gone to some length to point out it is not just me who is having the problem.
But 14.xx work after you install the monitor driver?
What about if you install the monitor driver first? I use a monitor driver through windows, but my monitor is old and will work without it. Perhaps it might be needed for a brand new monitor.
Last edited:
Oh Kaap, you and your PEBKAC issues.
You would discover this right after i sent a few emails wouldn't you. Oh well, at least we know the problem is not with the drivers on this occasion.
PEBKACAK = Problem exists between keyboard and chair and Kaap.
Nah, definitely a PIKNIC...
I am joking btw
Haha, tried working it out but failed.
Problem in Kaap not in computer...
We used to call it a PICNIC job where I used to work in support back in the day.
The first C equalling chair of course