Nicehash / Windows 10 Crash

[NicerRolo]

Since a few days my Nicehash Crashs on both rigs.

One: Windows 10 2 x gtx 1060 2 x gtx 1070 newest Driver 1 AMD Ryzen

Two: Windows 7 2 x GTX 1060 1 x GTX 1080

The Miner is running for 4 to 5 hours straight, then it Crashs. Windows 10, doesnt restart just a bluescreen. How can i fix it? Nicehash 2 (Alpha)

[tcm5025]

Happening to me for the past couple days too.

Windows 10 2x GTX 1080 Ti SLI with newest drivers 384.76 1x i5 7600K

I haven't seen the crash, but I think it's similar. Seems to happen consistently after a few hours. I think it's probably a blue screen, and there is a MEMORY.DMP being created. Windows event logs are full of a lot of nvlddmkm errors. They come like 40 at a time in a couple flavors:

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:

\Device\00000250 NVRM: Graphics TEX Exception on (GPC 0, TPC 0): TEX NACK / Page Fault

the message resource is present but the message is not found in the string/message table

and

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:

\Device\00000250 Variable String too Large

the message resource is present but the message is not found in the string/message table

I do have some core clock overclock on both cards, but I tried turning the memory overclock down to 0 to see if that would help, and it didn't. I have the power limit increased to 120/117 and the temp limit set at 75° C. One of the cards is watercooled and doesn't get above 65° and the other is constantly getting throttled to stay under 75°.

I'm going to try testing with fan curve turned up more, and with overclock turned off altogether.

[tcm5025]

Still happening consistently without any overclock on. I don't seem to have trouble when just running claymore miner for ethereum/siacoin. Can't really use nicehash miner right now unfortunately. I'll try again if there is an update to nvidia drivers or nicehash miner because I really do prefer it.

[tcm5025]

Just noticed OP was running nicehash 2... My issues were encountered with 1.7.5.13.

[ScottYates]

I have the same/similar issue it appears. NiceHash is crashing my machine after a series of the following events:

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: 
\Device\UVMLiteProcess3
Variable String too Large

Is there a way to tell what miner was running at the time and disable it? I notice that the miner that starts up a console with the nvidia logo on it REALLY pulls the system to a crawl, so I am wondering if it could be that particular one.

System particulars and WAY more than you want to know about things are in the report in this zip file. SIW_BLACKMAX_20170712_235906.zip

This is all under 2.0.0.8 Alpha

[tcm5025]

I'm testing with the 2.0.0.8 alpha now, and I'm still getting the nvlddmkm errors in the event viewer logs right now. No crash yet though. I'll try to watch and see which algorithm it's associated with. I switched over to a bigger PSU too cause I was thinking NiceHash might be pushing things hard enough that I was overloading the PSU I had before. The cards run hotter and draw more power with NiceHash miner than using Claymore dual miner. So, I was thinking maybe this would solve it cause my other PSU was borderline for the load.

[OneOfMany07]

Does this help? Almost sounds like there is something using the system too much and that makes the OS think your computer is hung. So it reboots/crashes.

https://forums.geforce.com/default/topic/413110/the-nvlddmkm-error-what-is-it-an-fyi-for-those-seeing-this-issue/

"As a starting note, this is not an nVidia issue. It is not an ATI issue either. These errors are triggered by a Windows service called 'Timeout Detection and Recovery' (TDR). You will only see this error on Windows Vista and Windows 7, as TDR is a feature of the new WDDM driver model (implemented first in Windows Vista). TDR is supposed to be there to help stop BSOD's by resetting the GPU and/or driver when there is an issue or long delay. If the problem happens multiple times in a row, a BSOD can occur.

If you are having this problem frequently then you will probably find it very frustrating, however be reassured that the problem is normally perfectly solvable, although can take some troubleshooting to resolve. I personally have seen this issue on two separate nVidia builds, and an Intel onboard GPU."

[NicerRolo]

Thanks, i solved the problem otherwise. Since two week i´m just running Equihash. I found out, that the problem ist switching between the miners (ccminer etc.). So since im running just one miner, i dont have any crashing problems.

[tcm5025]

My issue was resolved by disabling SLI. Once I disabled that, no more nvrm errors or crashes. It would be nice to not have to switch back and forth between SLI like that though if there were a fix possible. I could provide more information on that if it helps.

[andrespaz9221]

Sorry what mean SLI and how can I disable it

[andrespaz9221]

I am a beginer

[tcm5025]

It's a setting you can use when you have two nvidia graphics cards connected together using a hardware bridge. If you don't know about it, then you probably don't have it as an option.