Computex is one of the biggest hardware events of the year and while we see both CPU and GPU vendors come up with new products - we actually ran into something quite funny this time. While visiting the ELSA Computex booth at the Nangang Exhibition Hall, we noticed something weird about an RTX 4090 model that was being displayed. It looked oddly familiar to a Gainward model - almost identical in fact and as it turns out - it looked identical because it actually was a Gainward GPU.
This ELSA GPU is actually a Gainward RTX 4090 Glare in disguise
The shroud was identical to the Gainward Glare RTX 4090 24 GB GPU (available here on Newegg) and the company seemed to have placed stickers on top of the existing ones on the fans. When you turned the GPU over to the side - ELSA had hot-glued an ELSA sticker on top of the still-visible Gainward logo - which you can see in the picture below.
Now we asked the staff there whether this was a Gainward GPU - and they denied that it was (even though it obviously is). Being unaware of any existing connection between ELSA and Gainward we also asked them if ELSA was related to Gainward in any way and they simply replied with a no as well. I am sure a very interesting explanation exists for this although I do not know what it is.
Maybe Gainward is selling off its excess RTX 4090 inventory and ELSA will buy it up and re-badge it or maybe they have the same OEM/ODM for the shroud and this was provided as a sample design to them. Of course, more malicious explanations may also be within the realm of possibly although I personally consider that to be very unlikely.
Whatever the case is, it is hilarious that the company thought they could simply put a sticker on a Gainward GPU and pass it off as entirely their own product at Computex. I look forward to finding out just what the exact explanation is behind this one. We did also check all of the other GPUs that they had on display and were actually ELSA GPUs and this seemed to be the only glaring anomaly in their booth.
from Wccftech https://ift.tt/PErIJln
0 Comments