Fury X Display Corruption under low load

[xkm1948]

Looks like this is a wide spread problem. I thought I was the only one affected. I also thought it may just be a BIOS problem. Now it seems more and more likely this is gonna be a major problem for all Fury X/ Fury and Nano users.

This problem only happens during low load. Once ULPS(Ultra Low Power State) is disabled the situation is greatly improved. My hypothesis is that AMD's implementation of ZeroCore is seriously bugged on the Fury/HBM chip.

Screenshot of my problem.

Link to youtube video:

Link to AMD official forum:

https://community.amd.com/thread/188642

Link to Sapphire forum:

https://www.sapphireforum.com/showt...creen-corruption-followed-by-bsod-at-low-load

Link to Rage3D:

http://www.rage3d.com/board/showthread.php?t=34024262

 

[OneMoar]

Heyyyyy guess what powerplay not working worth a shit as per usual
amd should have dumped there entire clock scaling architecture ages ago
its garbage and beyond fixing

 

[kiddagoat]

Yeah my Fury X was doing the same thing but with vertical lines across the screen. I moved to another DisplayPort and it seems to have resolved itself. At least it has not had any display corruption since switching ports..... been about 2 months or so now.

 

[Aquinus]

One more AMD's victim

Time to go NVIDIA.

The OP asked for help, not for people to be smart asses about their GPU preferences.

This probably has to do with the voltage at idle. HBM doesn't clock down at idle like GDDR5 did. Probably because HBM already sips power as it is. Does it get better if ULPS is on but with voltage bumped a little bit? Adjusting voltage should impact how the voltages scale since it's an offset. Reducing voltage in afterburner is also going to reduce idle voltages IIRC.

I'm assuming this is all happening with the card set to stock?

 

[buildzoid]

haven't had this happen to me yet.

@Aquinus there is still no voltage control support for the Fury or Fury X using software. I guess OP could try use: Force constant voltage. That'll keep the card running at minimum 3D voltage instead of 2D voltage.

 

[Athlon2K15]

Back on topic children....

 

[Aquinus]

haven't had this happen to me yet.

@Aquinus there is still no voltage control support for the Fury or Fury X using software. I guess OP could try use: Force constant voltage. That'll keep the card running at minimum 3D voltage instead of 2D voltage.

He did say that ULPS being disabled fixed it. I think he wanted a better solution. For some reason I was under the impression that core voltage was unlocked but HBM wasn't.

I'm not a smartass. I buy NVIDIA for a reason and that's not because I'm a fanboy. NVIDIA aren't perfect and I'm perfectly happy to criticize them when they deserve it eg GTX 970 memorygate, but they don't pull crap like this, especially with a flagship product. AMD have been putting out disappointing products for some time now and things like strong, hugely irritating, yet avoidable coil whine that TPU has been reporting on in the reviews and now this are the reasons that I avoid them, among others.

Yeah but, this isn't exactly the place to go on a rant about what you think about the two companies though. The OP asked for help, not your opinion on the company. If you have beef with AMD and want to rant, you should make a new thread for it.

 

[buildzoid]

He did say that ULPS being disabled fixed it. I think he wanted a better solution. For some reason I was under the impression that core voltage was unlocked but HBM wasn't.

Yeah but this isn't exactly the place to go on a rant about what you think about the two companies though. The OP asked for help not your opinion on the company. You have beef with AMD and want to rant? Make a new thread for it.

He said disabling ULPS improved the situation which AFAIK means that it still happens just less often.

I run my card with 2 monitors and I've yet to see it run at 2D clocks so I think OP needs to force the card to run 3D voltages all the time. It won't hurt the card since minimum 3D voltage is only a little bit above 2D voltage(which does not increase if you just raise core voltage). I also run permanent physical voltmods on my card so that might be part of the reason why mine doesn't crash.

The down side to forcing constant voltage is that power draw idle will be higher.

 

[RCoon]

Maybe we can spend our time helping the OP, instead of babbling on about other random bollocks?

I recommend RMA. Send the retailer that screenshot and ask for a replacement. If you're not happy with the Fury X and this problem is widespread, change card and go for a refund.

 

[INSTG8R]

Look at this ridiculous back patting going on here ^^^

With my "Vanilla Fury" I have noticed one thing in my case anyways. I don't see any idle corruption but I also have never seen it go into Zero Core either....

 

[newtekie1]

ZeroCore isn't active when the display is on, so this isn't a ZeroCore issue. It is an issue with the 2D clocks, and I'm guessing AMD picked voltages that are too low. I'd RMA the card, it shouldn't be doing this.

 

[Assimilator]

OP, I would suggest you RMA the card. Someone in the AMD thread said they did that and got back a card with a different serial that doesn't seem to exhibit the problem (https://community.amd.com/message/2676130#2676130). That, coupled with the fact that there has been no new BIOS released, would indicate a hardware issue to me.

Also please don't conflate ZeroCore with ULPS/2D clocks. ZeroCore is only applicable to the non-primary card(s) CrossFire configurations.

 

[OneMoar]

install msi-afterburner
1.enable unofficial overclocking mode without powerplay
2. config two profiles,one for 2d one for 3d
3.make sure the profiles are selected in AB's settings and ensure that global application detection level is set to LOW in rivatuner statistics server

Alternatively you can leave the global option on disabled, as I do ... but you will need to manually add profiles for every game or application where you want the card to clock up(better for power savings if you play less demanding games and don't want to throttle the gpu all the way up)

edit: like so: I recommend a minimum low clock of 300Mhz to 500mhz on the core and leave the ram at stock bring the vcore down as much as you can so it remains stable 0.800v should be plenty

 

[erocker]

Bunch of posts removed. Stay on topic, help out or stay out.

Thanks.

 

[xkm1948]

View attachment 68333 install msi-afterburner
1.enable unofficial overclocking mode without powerplay
2. config two profiles,one for 2d one for 3d
3.make sure the profiles are selected in AB's settings and ensure that global application detection level is set to LOW in rivatuner statistics server

Alternatively you can leave the global option on disabled, as I do ... but you will need to manually add profiles for every game or application where you want the card to clock up(better for power savings if you play less demanding games and don't want to throttle the gpu all the way up)

edit: like so: I recommend a minimum low clock of 300Mhz to 500mhz on the core and leave the ram at stock bring the vcore down as much as you can so it remains stable 0.800v should be plenty

If one can edit the BIOS of the card do you think it will be easier? In the good old days of my 4870 I can pull out the BIOS file, edit the frequency and flash it right back. I wish I can do the same.

Thanks for the software suggestion. I will try this method and report back.

Currently RMA is not an option. This is my main workstation. I need it on 24x7. Too bad I have sold my old 5870.

 

[OneMoar]

If one can edit the BIOS of the card do you think it will be easier? In the good old days of my 4870 I can pull out the BIOS file, edit the frequency and flash it right back. I wish I can do the same.

Thanks for the software suggestion. I will try this method and report back.

Currently RMA is not an option. This is my main workstation. I need it on 24x7. Too bad I have sold my old 5870.

bios editing is a bad idea no tool currently fully supports fury..;.

 

[xkm1948]

Maybe we can spend our time helping the OP, instead of babbling on about other random bollocks?

I recommend RMA. Send the retailer that screenshot and ask for a replacement. If you're not happy with the Fury X and this problem is widespread, change card and go for a refund.

I am very satisfied with the Fury X and this does not happen that frequently. I just don't like editing registry every single time after upgrading to new catalyst. I apologize for my ambiguous description earlier. After disabling ULPS the corruption completely stopped.

bios editing is a bad idea no tool currently fully supports fury..;.

That is a bummer. If disabling ULPS still lead to screen corruption I will try the Sapphire trixx to set the frequency profile. My card is sapphire and I think it functions the same as MSI AB. If AMD does not acknowledge this I will eventually RMA the card.

 

[OneMoar]

I am very satisfied with the Fury X and this does not happen that frequently. I just don't like editing registry every single time after upgrading to new catalyst. I apologize for my ambiguous description earlier. After disabling ULPS the corruption completely stopped.






That is a bummer. If disabling ULPS still lead to screen corruption I will try the Sapphire trixx to set the frequency profile. My card is sapphire and I think it functions the same as MSI AB. If AMD does not acknowledge this I will eventually RMA the card.

its likely a problem with the vbios combined with AMD's terrible clock scaling ....
its why I recommended to simply lock it to a two-step scaling untill a fix is released

 

[Countryside]

The OP asked for help, not for people to be smart asses about their GPU preferences.

This probably has to do with the voltage at idle. HBM doesn't clock down at idle like GDDR5 did. Probably because HBM already sips power as it is. Does it get better if ULPS is on but with voltage bumped a little bit? Adjusting voltage should impact how the voltages scale since it's an offset. Reducing voltage in afterburner is also going to reduce idle voltages IIRC.

I'm assuming this is all happening with the card set to stock?

 

[kiddagoat]

Have they released a new MSI AB since the Fury X launched?? The last version I had I when I purchased the card really couldn't do anything at all.....

 

[Aquinus]

@xkm1948 , given the situation I would just RMA it. It shouldn't be unstable at idle clocks, that's strange. I'm sure it's not perfect but, the manufacturer is the most capable to help you at this point. Whether that means providing you an updated BIOS or sending it in for RMA.

 

[newtekie1]

ZeroCore is only applicable to the non-primary card(s) CrossFire configurations.

It also applies to single GPUs, ZeroCore is activated on single GPUs when the monitor goes to sleep as well. But that, obviously, wouldn't lead to visible screen corruption. It could be a cause of the screen not waking up though. Just for an FYI.

If AMD does not acknowledge this I will eventually RMA the card.

I don't think there is much AMD can do, it really isn't anything they can do a broad fix on. The 2D voltages are set by the BIOS on the card, and that is the problem, they are so low they are causing instability. A driver fix likely isn't going to address this. Might as well bite the bullet and RMA the card now instead of later.

 

[kiddagoat]

@xkm1948 Does this happen randomly or just when sitting on the desktop? Mine would do it at random be it browsing the web, sitting on the desktop, or even sitting at the main menu of CS:GO.

 

[qubit]

I read them and chose not to reply because they're not on topic. Try a new thread, buddy.

What are you talking about? You did reply. You made some smartass critical comments to me and I replied to you. Then erocker deletes my comments but leaves yours, along with the deleted comments quoted, which isn't right. I was talking to him, not you. Now you get off your high horse and stop dragging this thread off topic. Thanks much.

 

[OneMoar]

I read them and chose not to reply because they're not on topic. Try a new thread, buddy.

@xkm1948 , given the situation I would just RMA it. It shouldn't be unstable at idle clocks, that's strange. I'm sure it's not perfect but, the manufacturer is the most capable to help you at this point. Whether that means providing you an updated BIOS or sending it in for RMA.

a rma is not going to fix anything the problem is a driver/vbios conflict they are just gonna send him another card and unless it had a newer vbios its going to have the same issue