Quote from: BingIt on October 26, 2022, 14:18:57Funny how biased the community is though. When AMD had driver issues three generations ago that led to artefact/tearing on screen, the community
- who largely never experienced it - holds onto it like a grudge even to this day. They still act as though it's a current reason to avoid AMD. It no longer applies to current or upcoming products, but the know-nothing lemmings online still cite it.

Nvidia's new cards are literally burning components, with video and photo evidence, due to something Nvidia did not alert the client base about. The response from the community? Shrug, ask about the release date for other 40-series in the lineup, instant and outright forgiveness while dropping far more money on them than they will ever be worth.

I am in a minority affected by AMD driver problems. I fully understand why majority avoids AMD GPUs even if majority is not affected.

The current working theory is there are cables out there that are substandard, using lower voltage wire in the construction of the SOME of the adapter cables and variations in the soldering into the 12v plug. Further testing needs to be done with a much larger sample of both cables and graphics cards. Gamersnexus gives a good explanation and a request for help with further testing. 

Quote from: zhoujianfeng on October 27, 2022, 11:16:30

Quote from: L on October 27, 2022, 04:53:03@Binglt

AMD is having bigger or smaller driver problems all the time, that is the problem and once someone experiences it they move away. Personally I want my PC to work and not have to tinker with something whoch Nvidia has working out of the box. This is over multiple gpu generations.
Having said so unless AIBs use the old power connectors or PSU manufacturers create proper cables I am skipping 40 series and reconsidering AMD as a potential gpu in the future.

This is actually not amd driver problem, as long as the computer unnatural key amd driver will prompt you to have this situation, this representative is caused by the driver, there may be a natural power failure, memory caused by the crash, amd driver this is a conscience move, instead of dyeing a lot of people think is caused by the driver, this I can not understand.

Quote from: zhoujianfeng on October 27, 2022, 11:16:30

Quote from: L on October 27, 2022, 04:53:03@Binglt

AMD is having bigger or smaller driver problems all the time, that is the problem and once someone experiences it they move away. Personally I want my PC to work and not have to tinker with something whoch Nvidia has working out of the box. This is over multiple gpu generations.
Having said so unless AIBs use the old power connectors or PSU manufacturers create proper cables I am skipping 40 series and reconsidering AMD as a potential gpu in the future.

This is actually not amd driver problem, as long as the computer unnatural key amd driver will prompt you to have this situation, this representative is caused by the driver, there may be a natural power failure, memory caused by the crash, amd driver this is a conscience move, instead of dyeing a lot of people think is caused by the driver, this I can not understand.

This is actually not amd driver problem, as long as the computer unnatural shutdown phenomenon amd driver will prompt you to have this situation and overclocking parameters to the default to prevent the boot, this representative is caused by the driver, there may be a natural power failure (including your own unplugged), or too much memory overclocking caused by the crash, amd driver this is a conscientious move, but many people think it is caused by the driver, this I can not understand.

Quote from: L on October 27, 2022, 04:53:03@Binglt

AMD is having bigger or smaller driver problems all the time, that is the problem and once someone experiences it they move away. Personally I want my PC to work and not have to tinker with something whoch Nvidia has working out of the box. This is over multiple gpu generations.
Having said so unless AIBs use the old power connectors or PSU manufacturers create proper cables I am skipping 40 series and reconsidering AMD as a potential gpu in the future.

This is actually not amd driver problem, as long as the computer unnatural key amd driver will prompt you to have this situation, this representative is caused by the driver, there may be a natural power failure, memory caused by the crash, amd driver this is a conscience move, instead of dyeing a lot of people think is caused by the driver, this I can not understand.

Quote from: L on October 27, 2022, 04:53:03AIBs use the old power connectors

We wish, however, so far Nvidia seems to impose the fire cause 12VHPWR on all RTX 4000 AIB models.

@Binglt

AMD is having bigger or smaller driver problems all the time, that is the problem and once someone experiences it they move away. Personally I want my PC to work and not have to tinker with something whoch Nvidia has working out of the box. This is over multiple gpu generations.
Having said so unless AIBs use the old power connectors or PSU manufacturers create proper cables I am skipping 40 series and reconsidering AMD as a potential gpu in the future.

Funny how biased the community is though. When AMD had driver issues three generations ago that led to artefact/tearing on screen, the community
- who largely never experienced it - holds onto it like a grudge even to this day. They still act as though it's a current reason to avoid AMD. It no longer applies to current or upcoming products, but the know-nothing lemmings online still cite it.

Nvidia's new cards are literally burning components, with video and photo evidence, due to something Nvidia did not alert the client base about. The response from the community? Shrug, ask about the release date for other 40-series in the lineup, instant and outright forgiveness while dropping far more money on them than they will ever be worth.

Almost as if old PCIe power cables didn't melt all the time since forever...