Upcoming NVIDIA RTX 3060 Purposely Cripples Mining Performance
NVIDIA is purposely crippling the Ethereum mining power of their upcoming GeForce RTX 3060 GPU by 50% to increase inventory for gamers.
Today, NVIDIA announced the upcoming launch of the GeForce RTX 3060 on February 25th for $329, and has made a drastic step to make sure miners do not steal all of the released inventory.
Instead of allowing the GPU to be used for any purpose, the RTX 3060 drivers will purposely reduce performance by 50% when it detects the card used for Ethereum cryptocurrency mining.
“With the launch of GeForce RTX 3060 on Feb. 25, we’re taking an important step to help ensure GeForce GPUs end up in the hands of gamers.”
“RTX 3060 software drivers are designed to detect specific attributes of the Ethereum cryptocurrency mining algorithm, and limit the hash rate, or cryptocurrency mining efficiency, by around 50 percent.”
“That only makes sense. Our GeForce RTX GPUs introduce cutting-edge technologies — such as RTX real-time ray-tracing, DLSS AI-accelerated image upscaling technology, Reflex super-fast response rendering for the best system latency, and many more — tailored to meet the needs of gamers and those who create digital experiences,” Nvidia announced today.
Also Read: Going Beyond DPO Meaning: Ever Heard of Outsourced DPO?
By purposely reducing the new RTX 3060’s performance, NVIDIA is hoping to push cryptocurrency miners towards its new line of CMP dedicated mining GPUs.
The new CMP GPUs do not include a display port and come in varying hash rates ranging from 26 MH/s to 86 MH/s.
30HX | 40HX | 50HX | 90HX | |
---|---|---|---|---|
Ethereum Hash Rate(1) | 26 MH/s | 36 MH/s | 45 MH/s | 86 MH/s |
Rated Power(2) | 125 W | 185 W | 250 W | 320 W |
Power Connectors(2) | 1x 8-pin | 1x 8-pin | 2x 8-pin | 2x 8-pin |
Memory Size | 6GB | 8GB | 10GB | 10GB |
Starting Availability | Q1 | Q1 | Q2 | Q2 |
As NVIDIA states that the software drivers will cripple the RTC 3060, it is not clear if it can be bypassed using third-party drivers or software.
Also Read: Limiting Location Data Exposure: 8 Best Practices
0 Comments