Bitcoin Forum

I'm currently using Windows 10, and after several hours of mining my rig will usually go offline for some nvlddmkm related issue. It will either stops responding, recover and reboot itself, or just freeze up (not 100% sure if its nvlddmkm, event viewer just says it recovered from a BugCheck). I've tried reinstalling the drivers - version 385.69 .. Getting really frustrated as I stay up most of the night seeing if the fix i applied changes anything and then a few hours later it crashes but I wake up several hours after that.. Getting really annoyed, any suggestions would be appreciated.

What cards are you running?

5x 1080 ti on Windows 10

Changed the drivers to 385.28 and then this happened about 30 mins later

https://ibb.co/geT8tk

another nvlddmkm error that caused a reboot

This time I received a blue screen with CLOCK_WATCHDOG_TIMEOUT as the stop code

Change to 372.70 and see how you get on. Ive found those drivers the most stable.

Changing them now

Its telling me that those drivers are not compatible with the 1080 ti's

Trying 385.41

Are you overclocking your cpu by any chance? The only times I was having BSODs with clock watchdog timeouts was when I was trying to push my cpu too much.

nope, no oc on the cards either, just lowered TDP to 85% , it just went offline again after running for 2 hours with the 385.41 drivers, haven't seen the reason yet going to be home in a hour

Found this article, going to go through it when I get home... sounds like my issue https://forums.geforce.com/default/topic/413110/the-nvlddmkm-error-what-is-it-an-fyi-for-those-seeing-this-issue/

I'm using Win 10 also and occasionally I see the nvlddmkm error, but I've found either Claymore or EWBF miners seem the run the best for my rig.  EWBF I have a watchdog script for that will autorestart EWBF, and Claymore seems to behave.  CCMiner will eventually crash so I stay away from that.

What algos are you trying to mine?  I also found Awesome Miner to be a very nice program (free for 2 computers) as you can set whatever algo and it will restart the miner if it drops to 0 or crashes.  BSODs I don't think anything can help though.

Also what motherboard you have and did you configure the BIOS to use the correct PCI Gen, etc?

I mine Equihash with the latest EWBF, mobo is a ASRock H110 Pro BTC+ with 5 1080 ti's and 2 EVGA PSUs (1000W P2 and 850W G2)

It runs great, but then crashes after 2 hours... have mined up to 6 hours one time without crashing but that was once, it's usually only a couple hours and then it crashes. I'm thinking about going back to Windows 7

are you saying that Windows crashes or EWBF crashes and stops running?

Device manager shows my driver version at:  22.21.13.8494

Driver version filename is:  385.41-desktop-win10-64bit-international-whql.exe

Windows freezes, crashes, and or reboots itself

If you have all the latest Windows updates then I believe you will have to half-split the problem which is either the OS or the hardware.  Easiest way I can think of is to download the free nvOC software and give it a go.  See if things improve or not.  I just don't know a good way to figure out if you are dealing with software or hardware.

The nvOC the last time I checked, you hook your monitor to the GPU that's in the first x16 slot--apparently it doesn't like onboard video being used.

Perhaps you can remove the GPUs and start with one and isolate some sort of pattern to the crashing.  Like perhaps it works fine with 3, or maybe it crashes with one particular card in the mix?

yeah, I went from one problem to another.. I had everything working great on my last motherboard except that I could not get a fifth GPU working.. took days of troubleshooting to figure out it was the mobo... While troubleshooting the last problem I tried going from Windows 7 (which did work with the 4 GPUs) to Windows 10, which if I remember right I think I had it running with 4 GPUs with the last mobo until the new mobo came in..

Anyways, now I have a new mobo that recognizes and all 5 GPUs and they work but now they are crashing after running for so many hours (2-6). I installed a fresh copy of Windows 10 and that did not fix the problem. Right now I'm trying to go back to windows 7 but running some updates on the operating system (its an old copy)... Hopefully this works, if not theres an article of someone with a similar problem they were able to fix it, so I'll try that unless someone else has something else to suggest

the nvOC os looks cool, I don't have the time to set it up, leaving soon for a couple weeks.. Hoping I can get something working or at least 4 of the cards

Update: Windows 7 on the ASRock H110 with I7 CPU does not work lol, wouldn't let me update because of "hardware"

Alright, I finally finished putting Windows 10 Pro back on, but this time I followed these steps to prevent Windows Updates/Driver updates. (It was a gamer's post, not a miner but similar issues).

https://forums.geforce.com/default/topic/993738/-fix-tdr-errors-and-display-driver-nvlddmkm-stopped/

And I also applied the regedit for TDRDelay

EWBF is running now, hopefully it wont crash this time around and I wake up rich.

F****CK, it went stopped mining but this time it was a different error "Application miner.exe has been blocked from accessing Graphics hardware."


Edit: Looks like it might be a windows defender fix

Edit2 (no bump): looks like it was something to do with IGD / Intel Settings, switch the boot display to PCIe (PEG) and its been working since, almost an hour now as before it would stop working after 10 minutes.

Still having issues with nvlddmkm ... here's what I'm seeing from the memory.dmp file after BSOD ... On a positive note, the rig will run for 5-6 hours now instead of 3


Microsoft (R) Windows Debugger Version 10.0.15063.468 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 15063 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 15063.0.amd64fre.rs2_release.170317-1834
Machine Name:
Kernel base = 0xfffff801`88c93000 PsLoadedModuleList = 0xfffff801`88fdf5c0
Debug session time: Wed Sep 27 20:12:26.316 2017 (UTC - 7:00)
System Uptime: 0 days 1:37:09.016
Loading Kernel Symbols
..............................................................Page 1418d1 not present in the dump file. Type ".hh dbgerr004" for details
.
................................................................
........................
Loading User Symbols

Loading unloaded module list
.......
Page 1062cf not present in the dump file. Type ".hh dbgerr004" for details
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {ffffae0f9d391010, fffff8000b31f500, ffffffffc000009a, 4}

Page 141f7f not present in the dump file. Type ".hh dbgerr004" for details
Page 141f7f not present in the dump file. Type ".hh dbgerr004" for details
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+a0f500 )

Followup:     MachineOwner
---------

4: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffffae0f9d391010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8000b31f500, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.

Debugging Details:
------------------


DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING:  15063.0.amd64fre.rs2_release.170317-1834

SYSTEM_PRODUCT_NAME:  To Be Filled By O.E.M.

SYSTEM_SKU:  To Be Filled By O.E.M.

SYSTEM_VERSION:  To Be Filled By O.E.M.

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  P1.10

BIOS_DATE:  06/20/2017

BASEBOARD_MANUFACTURER:  ASRock

BASEBOARD_PRODUCT:  H110 Pro BTC+

BASEBOARD_VERSION:                       

DUMP_TYPE:  1

BUGCHECK_P1: ffffae0f9d391010

BUGCHECK_P2: fffff8000b31f500

BUGCHECK_P3: ffffffffc000009a

BUGCHECK_P4: 4

FAULTING_IP:
nvlddmkm+a0f500
fffff800`0b31f500 48ff2549ffe3ff  jmp     qword ptr [nvlddmkm+0x84f450 (fffff800`0b15f450)]

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CPU_COUNT: 8

CPU_MHZ: 1068

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: 9

CPU_MICROCODE: 6,9e,9,0 (F,M,S,R)  SIG: 42'00000000 (cache) 42'00000000 (init)

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  RIG1

ANALYSIS_SESSION_TIME:  09-27-2017 22:43:05.0557

ANALYSIS_VERSION: 10.0.15063.468 amd64fre

STACK_TEXT: 
ffffe681`16c1f9a8 fffff800`083d78f8 : 00000000`00000116 ffffae0f`9d391010 fffff800`0b31f500 ffffffff`c000009a : nt!KeBugCheckEx
ffffe681`16c1f9b0 fffff800`083b7db7 : fffff800`0b31f500 ffffae0f`a0fe3740 00000000`00002000 ffffae0f`a0fe37d8 : dxgkrnl!TdrBugcheckOnTimeout+0xec
ffffe681`16c1f9f0 fffff800`083b31f8 : ffffae0f`a0c700c0 00000000`04000000 00000000`00000000 00000000`00000000 : dxgkrnl!ADAPTER_RENDER::Reset+0x153
ffffe681`16c1fa20 fffff800`083d7095 : 00000002`00000100 ffffae0f`9fbc8040 00000000`00000000 ffffae0f`9fbc8040 : dxgkrnl!DXGADAPTER::Reset+0x430
ffffe681`16c1faa0 fffff800`083d71e7 : 00000000`00000000 fffff801`8908b380 ffffae0f`9c6b93d0 fffff801`88ce46a0 : dxgkrnl!TdrResetFromTimeout+0x15
ffffe681`16c1fad0 fffff801`88cd1158 : ffffae0f`9fbc8040 fffff800`083d71c0 ffffae0f`a20ce8b0 ffffae0f`a2ac2ac8 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x27
ffffe681`16c1fb00 fffff801`88d6ff77 : 40324057`5f40726f 00000000`00000080 ffffae0f`9c6b6040 ffffae0f`9fbc8040 : nt!ExpWorkerThread+0xd8
ffffe681`16c1fb90 fffff801`88e04a06 : ffffe681`15980180 ffffae0f`9fbc8040 fffff801`88d6ff30 40737469`6172745f : nt!PspSystemThreadStartup+0x47
ffffe681`16c1fbe0 00000000`00000000 : ffffe681`16c20000 ffffe681`16c19000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

THREAD_SHA1_HASH_MOD_FUNC:  56a150c818aff348d17e35fc9e822916b6c0190b

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  2b8e36420ad492fac55ee6ac7de8c9381dcb67f0

THREAD_SHA1_HASH_MOD:  3225689ea8bf23dca00cdfd517975e0703e07271

FOLLOWUP_IP:
nvlddmkm+a0f500
fffff800`0b31f500 48ff2549ffe3ff  jmp     qword ptr [nvlddmkm+0x84f450 (fffff800`0b15f450)]

FAULT_INSTR_CODE:  4925ff48

SYMBOL_NAME:  nvlddmkm+a0f500

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  599b590e

FAILURE_BUCKET_ID:  0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  0x116_IMAGE_nvlddmkm.sys

PRIMARY_PROBLEM_CLASS:  0x116_IMAGE_nvlddmkm.sys

TARGET_TIME:  2017-09-28T03:12:26.000Z

OSBUILD:  15063

OSSERVICEPACK:  0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE: 

USER_LCID:  0

OSBUILD_TIMESTAMP:  2017-09-04 21:09:34

BUILDDATESTAMP_STR:  170317-1834

BUILDLAB_STR:  rs2_release

BUILDOSVER_STR:  10.0.15063.0.amd64fre.rs2_release.170317-1834

ANALYSIS_SESSION_ELAPSED_TIME:  399

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x116_image_nvlddmkm.sys

FAILURE_ID_HASH:  {c89bfe8c-ed39-f658-ef27-f2898997fdbd}

Followup:     MachineOwner
---------

I no longer have physical access to the computer but can remote in periodically to check to see if miner is running. Any help would be very very much appreciated. Thank you guys

The cards I am using are

2x EVGA 1080 ti Hybrid SC2
3x PNY 1080 ti Blower Edition


May just split the rig and see if I can narrow the problem to maybe hardware or drivers? I don't know... clueless

Still having issues, its been running for a bit now waiting for the next set of errors to check them out. Any suggestions would be appreciated

No luck on the geforce bored either. When I get home I think I'll tryout the nvOC ubuntu modded os and see my luck. Wasted money by buying the Windows 10 Pro but wasting even more money not having these machines running stable

I heard some people getting this issue from not enough power, I have a 1000W EVGA Supernova P2 powering (mobo, risers, 2x 1080ti gpu's, sata hard drive) and the other 3x cards on a EVGA 850W PSU, minus their risers.