2019 Hardware Thread

paulpicks21 said:

I used it for overclocking. Seemed fine?

I OCd my 660 a long time ago with it, pretty much the same as AB

Sorry guys but FireStorm sucks to OC with.

For example:
It ask you if you are sure after every time max voltage change and gives stupid warnings.


Plus you need to unlock settings to make adjustments, and even when saved to a profile, voltage needs to be unlocked and reset(it's not saved).

GPU-Z v2.17.0 is available.

Download TechPowerUp GPU-Z | TechPowerUp

v2.17.0 (February 27th, 2019)

• Added support for NVIDIA GTX 1660 Ti, Titan RTX, RTX 2080 Mobile, RTX 2070 Mobile, RTX 2060 Mobile, Quadro RTX 4000, GTX 650 (GK106), Quadro P5200
• Added support for AMD Radeon VII, Radeon HD 8400E
• Added support for Intel Amber Lake GT2 (Core i7-8500Y)
• Added support for detection of Radeon Adrenalin 2019 version
• Simplified some sensor titles: "GPU Clock", "Memory Clock", "Shader Clock"
• Unified "Memory Used" / "Memory Usage" sensor titles to "Memory Used"
• Improved crash reporter to ask for problem description and optional email, so we can follow up
• Advanced Panel dropdown will show "Memory Timings" option only when memory timing details are available
• OpenCL "Max Packet Size" is now formatted as unsigned value
• Instead of empty value show "None" when no OpenCL Built-in Kernels supported
• Added support for "None" in OpenCL DP, SP, Half FP Capability
• Fixed "File creation failed" message during GPU-Z startup
• Fixed GPU and memory load monitoring on RX 580 2048 SP
• Fixed missing default boost clock on GTX 1660 Ti and some Pascal cards
• Fixed missing fan sensors on RTX cards with no monitor connected
• Fixed crash on startup (Windows XP)
• Fixed crash when opening DXVA 2.0 report (Windows XP)
• Fixed power limit reporting on older NVIDIA cards
• Fixed crash during BIOS save on older NVIDIA cards
• Fixed incorrect VRAM reporting on 16 GB Vega
• Fixed various crashes caused by physical memory access

I figured out what the problem with FireStorms RGB settings was.

One MUST click the default first to reset it, even if you nuked the program from your system first. It must have some hidden .ini file or registry entry under another name than FireStorm of ZOTAC, that causes a corruption.

I'm a happy camper again now.
FireStorm for Bling-Bling, and Afterburner for overclocking

You gotta be kidding Thermaltake
WaterRam RGB Liquid Cooling Memory

Cliff S said:

Sorry guys but FireStorm sucks to OC with.

For example:
It ask you if you are sure after every time max voltage change and gives stupid warnings.


Plus you need to unlock settings to make adjustments, and even when saved to a profile, voltage needs to be unlocked and reset(it's not saved).

I dont remember it doing that in the older version, it may be different now. It did save the unlock and profiles for me. At least its good for your RGB I use Mystic Light for my RGB

GPU Hierarchy 2019 - Graphics Card Rankings and Comparisons

CountMike said:

GPU Hierarchy 2019 - Graphics Card Rankings and Comparisons

They posted Wrong information for the Nvidia cards.....LoL Their Base/Boost speeds are incorrect. According to those posted specs, my GeForce RTX 2080 Ti FTW3 ULTRA is faster than the Nvidia Titian RTX .....Plus they posted my card speeds wrong too.

Wrong for my Rx 570 too but maybe because of the exact make and model, probably factory OC-ed.

CountMike said:

Wrong for my Rx 570 too but maybe because of the exact make and model, probably factory OC-ed.

Think they should have done a better job Mike......all of them look wrong.