I'm getting weird nvlddmkm errors when using T-Rex, every day, several times. They tend to break the miner, which then has to restart.
They all start with this in the event viewer:
The description for Event ID 13 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
the error could then be any of these:
\Device\UVMLiteProcess12
Graphics SM Warp Exception on (GPC 2, TPC 0): Misaligned Address
The message resource is present but the message was not found in the message table
\Device\UVMLiteProcess12
Graphics SM Global Exception on (GPC 2, TPC 0): Physical Multiple Warp Errors
The message resource is present but the message was not found in the message table
\Device\UVMLiteProcess12
Graphics Exception: ESR 0x514648=0x9000f 0x514650=0x24 0x514644=0xd3eff2 0x51464c=0x17f
The message resource is present but the message was not found in the message table
\Device\UVMLiteProcess13
Graphics SM Warp Exception on (GPC 2, TPC 0): Out Of Range Address
The message resource is present but the message was not found in the message table
\Device\UVMLiteProcess13
Graphics Exception: ESR 0x514648=0x108000e 0x514650=0x20 0x514644=0xd3eff2 0x51464c=0x17f
The message resource is present but the message was not found in the message table
Is anyone else experiencing this?
Is it a driver issue or is T-Rex messing something up?
Was just wondering if anybody else had been experiencing this at all.
@Trex, is that something the miner is causing, or is it overclock related?... if at all? I've tried to google it but can't seem to get a proper/decent solution (nor explanation for that matter).
