F5F Stay Refreshed Hardware Desktop Error encountered: GPU driver issue or not?

Error encountered: GPU driver issue or not?

Error encountered: GPU driver issue or not?

E
eliasxxx123
Junior Member
21
05-26-2016, 03:04 AM
#1
Hello, I'm operating a PC with an i5 4590 and a used mining board known as the P106, which is roughly comparable to a GTX 1060 with 6GB of memory. The card was purchased about two years ago and performed well until around August of this year when it suddenly stopped functioning. A BSOD occurred, displaying a message like VIDEO TDR FAILURE. I attempted to resolve the issue by changing drivers, but without success. The card refused to be detected by the system. This past week, out of curiosity, I tried it again and it functioned properly. The system recognized it and allowed me to play a few games with minimal problems. However, it then BSOD'd once more. Now it reports a DPC WATCHDOG VIOLATION, which, after some research online, appears to relate to problematic drivers.

To be clear, the driver in use is likely modified by developers since this type of card isn't standard and isn't officially recognized by Nvidia for gaming purposes. It lacks display output, so I'm using my integrated graphics as a workaround. This might seem unusual, but if anyone knows about similar cards, they'll understand that these are typical behaviors. The driver itself could be the cause. BUT, my main question is: why did it fail suddenly months ago? Why was it stable for nearly two years? Could another factor be responsible?
E
eliasxxx123
05-26-2016, 03:04 AM #1

Hello, I'm operating a PC with an i5 4590 and a used mining board known as the P106, which is roughly comparable to a GTX 1060 with 6GB of memory. The card was purchased about two years ago and performed well until around August of this year when it suddenly stopped functioning. A BSOD occurred, displaying a message like VIDEO TDR FAILURE. I attempted to resolve the issue by changing drivers, but without success. The card refused to be detected by the system. This past week, out of curiosity, I tried it again and it functioned properly. The system recognized it and allowed me to play a few games with minimal problems. However, it then BSOD'd once more. Now it reports a DPC WATCHDOG VIOLATION, which, after some research online, appears to relate to problematic drivers.

To be clear, the driver in use is likely modified by developers since this type of card isn't standard and isn't officially recognized by Nvidia for gaming purposes. It lacks display output, so I'm using my integrated graphics as a workaround. This might seem unusual, but if anyone knows about similar cards, they'll understand that these are typical behaviors. The driver itself could be the cause. BUT, my main question is: why did it fail suddenly months ago? Why was it stable for nearly two years? Could another factor be responsible?

H
HellNether
Senior Member
731
05-28-2016, 11:32 AM
#2
Device manager detects its presence when connected, yet it reports that Windows disabled it due to code 43. Run GPU-Z to check for any zero values in expected numeric fields. This used mining card is the P106; mining cards generally have inconsistent results, especially with losses.
H
HellNether
05-28-2016, 11:32 AM #2

Device manager detects its presence when connected, yet it reports that Windows disabled it due to code 43. Run GPU-Z to check for any zero values in expected numeric fields. This used mining card is the P106; mining cards generally have inconsistent results, especially with losses.

I
ISUCKAVGDIXK
Junior Member
15
05-28-2016, 03:07 PM
#3
They are indeed zeroes. Adding more details, I've experimented with various drivers and sometimes it works. GPUZ displays actual values instead of zeros. The Nvidia control panel could also be helpful. Until I attempt to play something and then it crashes. After the system restarts, the GPUZ appears filled with zeroes and the device manager again shows code 43. Mining cards is unpredictable, especially on the miss side. I was aware of the risks beforehand, but this was a surprise after a year and a half. The card didn't die completely, which is confusing.
I
ISUCKAVGDIXK
05-28-2016, 03:07 PM #3

They are indeed zeroes. Adding more details, I've experimented with various drivers and sometimes it works. GPUZ displays actual values instead of zeros. The Nvidia control panel could also be helpful. Until I attempt to play something and then it crashes. After the system restarts, the GPUZ appears filled with zeroes and the device manager again shows code 43. Mining cards is unpredictable, especially on the miss side. I was aware of the risks beforehand, but this was a surprise after a year and a half. The card didn't die completely, which is confusing.

P
Pradeep22
Junior Member
2
05-28-2016, 04:37 PM
#4
They are indeed zeroes.
After the system restarts, the GPUZ fills up with zeroes and the device manager once more displays code 43.
That GPU is definitely gone.
P
Pradeep22
05-28-2016, 04:37 PM #4

They are indeed zeroes.
After the system restarts, the GPUZ fills up with zeroes and the device manager once more displays code 43.
That GPU is definitely gone.