Overclock.net › Forums › Graphics Cards › AMD/ATI › 290/290X Black Screen Poll
New Posts  All Forums:Forum Nav:

290/290X Black Screen Poll - Page 83

Poll Results: Do You Black Screen?

This is a multiple choice poll
  • 43% of voters (147)
    Stock Clock Elpdia UEFI?
  • 18% of voters (61)
    Stock Clock Elpdia LEGACY?
  • 14% of voters (48)
    Stock Clock Hynix UEFI?
  • 5% of voters (18)
    Stock Clock Hynix LEGACY?
  • 18% of voters (62)
    Over Clock Elpdia UEFI?
  • 8% of voters (27)
    Over Clock Elpdia LEGACY?
  • 7% of voters (26)
    Over Clock Hynix UEFI?
  • 5% of voters (20)
    Over Clock Hynix LEGACY?
337 Total Votes  
post #821 of 1600
Quote:
Originally Posted by acupalypse View Post

No i understand. That question was sort of rhetorical. True, this card is for benching, but you're not gonna go anywhere if you keep getting black screen. Hence, my post here on black screen poll, in a way that some readers would see that it also happens on lightning with samsung memory, not just hynix or elpida.

Whether i should RMA this now or not is another story.

i've posted here a bunch of times and have answered the same . . . if you can rma, then do so. don't waste your time trying to fix it.

edit: may i add, if bs happens AFTER a bios flash, overclocking, a change of cooler . . . then that's different. and then there are those whose psu are not up to snuff. i am only talking about normal use like unbox, install, bs.
Edited by rdr09 - 4/25/14 at 6:33am
Second Intel Rig
(16 items)
 
  
CPUMotherboardGraphicsRAM
2700 4.5/ 1.28 77 1050 16 / 1866 
Hard DriveCoolingOSMonitor
1000 212 10 64 32 1080 
PowerCase
700 912 
  hide details  
Reply
Second Intel Rig
(16 items)
 
  
CPUMotherboardGraphicsRAM
2700 4.5/ 1.28 77 1050 16 / 1866 
Hard DriveCoolingOSMonitor
1000 212 10 64 32 1080 
PowerCase
700 912 
  hide details  
Reply
post #822 of 1600
Quote:
Originally Posted by rdr09 View Post

i've posted here a bunch of time and have answered the same . . . if you can rma, then do so. don't waste your time trying to fix it.

I don't think you understood me.

Like i said i'm not even trying to fix it. I'm just giving out information to other readers that it happens on samsung memory, too. If you'd look at the poll, it doesn't have samsung on the list
post #823 of 1600
Quote:
Originally Posted by acupalypse View Post

I don't think you understood me.

Like i said i'm not even trying to fix it. I'm just giving out information to other readers that it happens on samsung memory, too. If you'd look at the poll, it doesn't have samsung on the list

i am sorry if i misunderstood you. i may have to go back a few pages and read up. lightnings are the only ones that use samsung. majority of these BS are those with elpida. so, yours happen at idle?

i re-read post #807. yours happened using 14 driver and everything is fine using whql. i don't think it has to do with the type of memory - the issue clearly was the driver.
Edited by rdr09 - 4/25/14 at 7:18am
Second Intel Rig
(16 items)
 
  
CPUMotherboardGraphicsRAM
2700 4.5/ 1.28 77 1050 16 / 1866 
Hard DriveCoolingOSMonitor
1000 212 10 64 32 1080 
PowerCase
700 912 
  hide details  
Reply
Second Intel Rig
(16 items)
 
  
CPUMotherboardGraphicsRAM
2700 4.5/ 1.28 77 1050 16 / 1866 
Hard DriveCoolingOSMonitor
1000 212 10 64 32 1080 
PowerCase
700 912 
  hide details  
Reply
post #824 of 1600
Quote:
Originally Posted by rdr09 View Post

i am sorry if i misunderstood you. i may have to go back a few pages and read up. lightnings are the only ones that use samsung. majority of these BS are those with elpida. so, yours happen at idle?

i re-read post #87. yours happened using 14 driver and everything is fine using whql. i don't think it has to do with the type of memory - the issue clearly was the driver.

oh no worries, my first post was i think #785, trying to throw in my experience.

Yes, only occurs during idle which MSI support has told me yesterday it could be the GPU going bad and consider RMA.

The only reason i'm not doing that - yet - because I don't want another Lightning. I believe it's plagued...and it'll be another hit or miss, but this time, it's the AMD GPU's quality is questionable, not MSI. Hence, i asked you what would you have instead (if you recall). I'm seriously considering it replaced by at least EVGA classified or Kingpin...not that i'm planning to go hardcore, but just so i can say I own one ...lol ...pls don't judge, that's just me.
post #825 of 1600
Quote:
Originally Posted by acupalypse View Post

oh no worries, my first post was i think #785, trying to throw in my experience.

Yes, only occurs during idle which MSI support has told me yesterday it could be the GPU going bad and consider RMA.

The only reason i'm not doing that - yet - because I don't want another Lightning. I believe it's plagued...and it'll be another hit or miss, but this time, it's the AMD GPU's quality is questionable, not MSI. Hence, i asked you what would you have instead (if you recall). I'm seriously considering it replaced by at least EVGA classified or Kingpin...not that i'm planning to go hardcore, but just so i can say I own one ...lol ...pls don't judge, that's just me.

the king will get you up there for sure.
Second Intel Rig
(16 items)
 
  
CPUMotherboardGraphicsRAM
2700 4.5/ 1.28 77 1050 16 / 1866 
Hard DriveCoolingOSMonitor
1000 212 10 64 32 1080 
PowerCase
700 912 
  hide details  
Reply
Second Intel Rig
(16 items)
 
  
CPUMotherboardGraphicsRAM
2700 4.5/ 1.28 77 1050 16 / 1866 
Hard DriveCoolingOSMonitor
1000 212 10 64 32 1080 
PowerCase
700 912 
  hide details  
Reply
post #826 of 1600
Quote:
Originally Posted by rdr09 View Post


i re-read post #807. yours happened using 14 driver and everything is fine using whql. i don't think it has to do with the type of memory - the issue clearly was the driver.

By the way, the driver is a totally separate issue. Using 14.x prohibits me to go more than 1130-1140Mhz. On 13.x, i can go beyond 1200 Mhz.

Black screen issue was my main point in posting here though.
post #827 of 1600
Quote:
Originally Posted by rdr09 View Post

the king will get you up there for sure.

100% agree...just having second thought because of its price. So i'm 'kind of' trying to get justification for myself why would i buy it or why not [60% = buy; 40% = go look for another card]
post #828 of 1600
Quote:
Originally Posted by acupalypse View Post

By the way, the driver is a totally separate issue. Using 14.x prohibits me to go more than 1130-1140Mhz. On 13.x, i can go beyond 1200 Mhz.

Black screen issue was my main point in posting here though.

so, it bs at idle, with no oc, and does not matter what driver?
Second Intel Rig
(16 items)
 
  
CPUMotherboardGraphicsRAM
2700 4.5/ 1.28 77 1050 16 / 1866 
Hard DriveCoolingOSMonitor
1000 212 10 64 32 1080 
PowerCase
700 912 
  hide details  
Reply
Second Intel Rig
(16 items)
 
  
CPUMotherboardGraphicsRAM
2700 4.5/ 1.28 77 1050 16 / 1866 
Hard DriveCoolingOSMonitor
1000 212 10 64 32 1080 
PowerCase
700 912 
  hide details  
Reply
post #829 of 1600
Quote:
Originally Posted by rdr09 View Post

so, it bs at idle, with no oc, and does not matter what driver?

due to being intermittent, it's really hard to say. It happened only 3x for that past week. The card was OC'd to 1115 and 1170 (that's what i can remember).

I just ate dinner and left the computer idle. When came back to my desk, i thought it was just the monitor in sleep mode (as I always set). Moved the mouse, monitor LED came back to ACTIVE state...BUT nothing is on my screen, just plain black and had to reboot to fix it.

That was on catalyst 13.12. Catalyst 14.x, crashes instantaneously when OC'd to at least 1150 MHz. (without me doing anything yet). Set 1130 MHz - ish, it would still work until GPU load reaches 100% and temp above 50C. Weird huh? thumb.gif
post #830 of 1600
was there the bing-bing noise like the monitor disconected, then reconected? i noticed 14.x does this on powersave. 13.12 and prior did not.
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: AMD/ATI
Overclock.net › Forums › Graphics Cards › AMD/ATI › 290/290X Black Screen Poll