Overclock.net › Forums › Graphics Cards › AMD/ATI › [Official] AMD R9 295X2 Owners Club
New Posts  All Forums:Forum Nav:

[Official] AMD R9 295X2 Owners Club - Page 522

post #5211 of 8948
Very unique issue. ..thinking.gif.

Would recommend to open a ticket with amd and sapphire. At least to get their take.

You have any one that can let you borrow another current card?
post #5212 of 8948
If you google hard enough you can find people who have experienced this with the R9 2XX series since late 2013. For some disabling the "driver signature enforcement" did the trick while for at least one person it required a video card swap.

I didn't find any instance in which a windows re-install helped at all so don't waste your time there.
Edited by xer0h0ur - 3/28/15 at 12:56pm
post #5213 of 8948
Hello overclock.net, for some time I had a R9 295X2 and Titan Z in my possession to run it with my LGA 1366 Dual Xeon Platform. However Windows (All versions) simply blue screen because it has to do with how 1st gen core i7/nehalem/westemere handles PCIe lanes. Nehalem/Westemere was the last Intel chipset to actually have a true Northbridge, as it contained PCIe lanes and not in the CPU and used QPI links to connect with CPUs and reduce latency. The problem kicks in on How windows OS handles PCIe lanes and the protocol following it with the Dual GPU cards. R9 295X2/Titan Z both use PLX8487, which doubles the PCIe lane taken in from the PCIe slot provided. However, this type of configuration has conflicting protocols since the PCIe lanes are located in Northbridge, not on CPU. Because of this, when windows loads drivers for the GPU, it becomes unstable and crashes 10 seconds after the driver has loaded since it cannot handle conflicting PCIe protocols. Unix Distributions, such as FreeBSD or Linux mint has no problems with the drivers because their way of handling PCIe protocol and data is significantly different from Windows. TL:DR, do not use R9 295X2 or Titan Z with Nehalem/Westemere Xeon 5520/5500 chipset in Windows, it will crash due to conflicting PCIe protocols.
post #5214 of 8948
Still doesn't explain at all why this happens with single GPU cards like the 290X/290/280X/280
post #5215 of 8948
Quote:
Originally Posted by xer0h0ur View Post

Still doesn't explain at all why this happens with single GPU cards like the 290X/290/280X/280

I agree. First thing I would do is when loading the video drivers, do a custom install and remove everything but display driver,CCC, install manager,and acp. Forget the drag and drop crap or even hdmi audio in my case I dont use. But his case is slightly different, I think its more a bios compatibility issue and maybe it is hardware somewhere but for me not having power states solved it. When I would be at desktop and gpu downclocked, which also reduced pcie speed at the same time I got BSOD. If had some patience I could try to find more information on my setup as we both have the same hawaii gpu and intel chipset.

If it was simply a pcie protocol issue then shouldn't it fail even without a driver loaded?
post #5216 of 8948
I was thinking the same thing myself. If it was a PCI-E protocol issue it shouldn't work no matter what. In my particular instance its only when the drivers are installed that the system fails to get past the 4 piece spinning windows logo. Other than that soon as I DDU the installation I can boot perfectly fine.
post #5217 of 8948
But R9 290X reference works on my computer perfectly, while R9 295X2 simply refuses to.
post #5218 of 8948
Quote:
Originally Posted by drchoi21 View Post

But R9 290X reference works on my computer perfectly, while R9 295X2 simply refuses to.

can you gpuz screenshot your 290x? Also do you have the available pcie slots to try 290x primary and 295x2 secondary and run trifire as a test? Funny though you never mentioned a 290x or I simply forgot.

Edit: I should specify I was curious about your gpuz shot of the 290x to see the stats like identifier, version etc. Not because I didn't think you had one.(if it sounded that way)
Edited by DividebyZERO - 3/28/15 at 1:59pm
post #5219 of 8948
it's kinda old, when I first got the R9 290X back in 2013

I also can't do Trifire since there is only 1 PCIe x16 slot
post #5220 of 8948
Your motherboard only has one full size PCI-E slot?
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: AMD/ATI
Overclock.net › Forums › Graphics Cards › AMD/ATI › [Official] AMD R9 295X2 Owners Club