Nvlddmkm stopped responding/recovers

Driver issues associated with the Windows 10 roll-out

Moderators: Site Moderators, PandeGroup

Nvlddmkm stopped responding/recovers

Postby Kougar » Thu Nov 05, 2015 5:53 pm

I waited a few driver releases/months to see if NVIDIA would resolve this, but it is still occurring so I'll make a bug report about it.

This began on day one of a clean install of Windows 10. It only occurs when Folding@home is running and I launch another program. It never happens when Folding@home is paused or not running. No program, game, or application causes these errors on the system by itself, F@H must always be running for them to occur.

If the machine is folding on the GPU and any 3D accelerated program is started, they frequently cause a one-time "Display driver nvlddmkm stopped responding and has successfully recovered." error to occur. It can be as simple as opening a static JPEG in the old photo viewer (occurs 4 of 5 times I view any image), and less frequently when I launch a video in VLC or open Chrome. If I open GPU utilities such as Precision X, I will sometimes receive a chain of these errors until I close the program or kill F@H. Rarely the same programs run without a single occurrence.

Simple "Display driver nvlddmkm stopped responding and has successfully recovered" error in the event logs, no details given. I wonder if it is as simple as adjusting a timeout window in the drivers, but so far I've not had any luck.

7.4.4
Windows 10
NVIDIA Titan Black (358.50)
System is stock, no OCing.

I've yet to find any instability with the system using various utilities. I went as far as underclocking the GPU and even raised its voltage, but that did not change the frequency of these driver reset errors. I can therefore only conclude there is some kind of NVIDIA driver/Windows 10/F@H specific problem that is causing this. It reminds me a lot of the Windows Vista & fledgling GPU folding days all over again, just without the actual BSoDs this time. :mrgreen: If it matters, when this error occurs the display is not affected, video files are not interrupted, and F@H's WU is not affected. I wouldn't even know the driver had reset except for the error notification and chime announcing it.
Kougar
 
Posts: 171
Joined: Fri Apr 11, 2008 2:39 am
Location: Texas

Re: Nvlddmkm stopped responding/recovers

Postby bruce » Thu Nov 05, 2015 10:58 pm

There's an upcoming change to the FAHCore that is supposed to solve this problem. It's actually due to a combination of driver settings/OS settings/FahCore settings.

Yes, temporarily you can adjust the timeout window (aka TDR) until the fix is released. (soon™)
bruce
 
Posts: 20828
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: Nvlddmkm stopped responding/recovers

Postby Kougar » Fri Nov 06, 2015 2:46 am

I'm very relieved to hear it!

I had already modified several TDR settings, but nothing I've done had any effect. Could be I didn't modify the right one or Win 10 changed the options required https://msdn.microsoft.com/en-us/librar ... e/ff569918
Kougar
 
Posts: 171
Joined: Fri Apr 11, 2008 2:39 am
Location: Texas

Re: Nvlddmkm stopped responding/recovers

Postby toTOW » Fri Nov 06, 2015 4:05 pm

I think there are two ways of addressing this :

- setting TdrLevel to TdrLevelOff (0) to disable TDR feature.
- increasing the value of TdrDelay to something like 10 seconds.
Folding@Home beta tester since 2002. Folding Forum moderator since July 2008.

FAH-Addict : latest news, tests and reviews about Folding@Home project.

Image
User avatar
toTOW
Site Moderator
 
Posts: 8329
Joined: Sun Dec 02, 2007 10:38 am
Location: Bordeaux, France

Re: Nvlddmkm stopped responding/recovers

Postby ^w^ing » Thu Mar 31, 2016 5:16 am

what is the current status on this? I have the exact same sypmtoms as OP, fiddling with TDR delay does not help, turning TDR off results in complete desktop freeze needing a hard reset.
if the frozen system is left alone for long enough, current WU apparently finishes but does not upload - actual progress can be only found in the log in the WU's work folder, not in the global log. after reboot and client restart, the WU start folding from 0 despite wuresults.dat file being present in it's work folder. also simultaneously another WU is downloaded, resulting in 2 WUs at 0% queued for the 1 folding slot.
with the latest nvidia driver update (364.72), the display driver now crashes constantly if my monitors are turned off.

global log leading to a system freeze
Code: Select all
*********************** Log Started 2016-03-30T22:41:23Z ***********************
22:41:23:************************* Folding@home Client *************************
22:41:23:      Website: http://folding.stanford.edu/
22:41:23:    Copyright: (c) 2009-2014 Stanford University
22:41:23:       Author: Joseph Coffland <joseph@cauldrondevelopment.com>
22:41:23:         Args:
22:41:23:       Config: d:/$TEMP$/fah/config.xml
22:41:23:******************************** Build ********************************
22:41:23:      Version: 7.4.4
22:41:23:         Date: Mar 4 2014
22:41:23:         Time: 20:26:54
22:41:23:      SVN Rev: 4130
22:41:23:       Branch: fah/trunk/client
22:41:23:     Compiler: Intel(R) C++ MSVC 1500 mode 1200
22:41:23:      Options: /TP /nologo /EHa /Qdiag-disable:4297,4103,1786,279 /Ox -arch:SSE
22:41:23:               /QaxSSE2,SSE3,SSSE3,SSE4.1,SSE4.2 /Qopenmp /Qrestrict /MT /Qmkl
22:41:23:     Platform: win32 XP
22:41:23:         Bits: 32
22:41:23:         Mode: Release
22:41:23:******************************* System ********************************
22:41:23:          CPU: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz
22:41:23:       CPU ID: GenuineIntel Family 6 Model 94 Stepping 3
22:41:23:         CPUs: 8
22:41:23:       Memory: 31.92GiB
22:41:23:  Free Memory: 30.00GiB
22:41:23:      Threads: WINDOWS_THREADS
22:41:23:   OS Version: 6.2
22:41:23:  Has Battery: false
22:41:23:   On Battery: false
22:41:23:   UTC Offset: 2
22:41:23:          PID: 7052
22:41:23:          CWD: d:/$TEMP$/fah
22:41:23:           OS: Windows 10 Pro
22:41:23:      OS Arch: AMD64
22:41:23:         GPUs: 1
22:41:23:        GPU 0: NVIDIA:5 GM200 [GeForce GTX 980 Ti]
22:41:23:         CUDA: 5.2
22:41:23:  CUDA Driver: 8000
22:41:23:Win32 Service: false
22:41:23:***********************************************************************
22:41:23:<config>
22:41:23:  <!-- Folding Slot Configuration -->
22:41:23:  <extra-core-args v='-forceasm -verbose'/>
22:41:23:  <max-packet-size v='big'/>
22:41:23:
22:41:23:  <!-- HTTP Server -->
22:41:23:  <allow v='127.0.0.1 192.168.20.0/24'/>
22:41:23:
22:41:23:  <!-- Network -->
22:41:23:  <proxy v=':8080'/>
22:41:23:
22:41:23:  <!-- Remote Command Server -->
22:41:23:  <password v='*****'/>
22:41:23:
22:41:23:  <!-- Slot Control -->
22:41:23:  <power v='full'/>
22:41:23:
22:41:23:  <!-- User Information -->
22:41:23:  <passkey v='********************************'/>
22:41:23:  <team v='229610'/>
22:41:23:  <user v='^w^ing'/>
22:41:23:
22:41:23:  <!-- Work Unit Control -->
22:41:23:  <next-unit-percentage v='100'/>
22:41:23:
22:41:23:  <!-- Folding Slots -->
22:41:23:  <slot id='0' type='GPU'>
22:41:23:    <core-priority v='low'/>
22:41:23:  </slot>
22:41:23:</config>
22:41:23:Trying to access database...
22:41:23:Successfully acquired database lock
22:41:23:Enabled folding slot 00: READY gpu:0:GM200 [GeForce GTX 980 Ti]
22:41:23:WU00:FS00:Starting
22:41:23:WU00:FS00:Running FahCore: C:\FoldingAtHome\FAHClient/FAHCoreWrapper.exe d:/$TEMP$/fah/cores/web.stanford.edu/~pande/Win32/AMD64/NVIDIA/Fermi/Core_18.fah/FahCore_18.exe -dir 00 -suffix 01 -version 704 -lifeline 7052 -checkpoint 15 -gpu 0 -gpu-vendor nvidia -forceasm -verbose
22:41:23:WU00:FS00:Started FahCore on PID 6956
22:41:24:WU00:FS00:Core PID:6936
22:41:24:WU00:FS00:FahCore 0x18 started
22:41:25:WU00:FS00:0x18:*********************** Log Started 2016-03-30T22:41:24Z ***********************
22:41:25:WU00:FS00:0x18:Project: 9152 (Run 16, Clone 22, Gen 18)
22:41:25:WU00:FS00:0x18:Unit: 0x00000014ab436c9f56623c6016159528
22:41:25:WU00:FS00:0x18:CPU: 0x00000000000000000000000000000000
22:41:25:WU00:FS00:0x18:Machine: 0
22:41:25:WU00:FS00:0x18:Digital signatures verified
22:41:25:WU00:FS00:0x18:Folding@home GPU core18
22:41:25:WU00:FS00:0x18:Version 0.0.4
22:41:25:WU00:FS00:0x18:  Found a checkpoint file
22:41:34:WU00:FS00:0x18:Completed 500000 out of 2500000 steps (20%)
22:41:34:WU00:FS00:0x18:Temperature control disabled. Requirements: single Nvidia GPU, tmax must be < 110 and twait >= 900
22:42:29:WU00:FS00:0x18:Completed 525000 out of 2500000 steps (21%)
22:43:22:WU00:FS00:0x18:Completed 550000 out of 2500000 steps (22%)
22:44:15:WU00:FS00:0x18:Completed 575000 out of 2500000 steps (23%)
22:45:08:WU00:FS00:0x18:Completed 600000 out of 2500000 steps (24%)
22:46:05:WU00:FS00:0x18:Completed 625000 out of 2500000 steps (25%)
22:46:58:WU00:FS00:0x18:Completed 650000 out of 2500000 steps (26%)
22:47:51:WU00:FS00:0x18:Completed 675000 out of 2500000 steps (27%)
22:48:44:WU00:FS00:0x18:Completed 700000 out of 2500000 steps (28%)
22:49:40:WU00:FS00:0x18:Completed 725000 out of 2500000 steps (29%)
22:50:33:WU00:FS00:0x18:Completed 750000 out of 2500000 steps (30%)
22:51:26:WU00:FS00:0x18:Completed 775000 out of 2500000 steps (31%)
22:52:19:WU00:FS00:0x18:Completed 800000 out of 2500000 steps (32%)
22:53:16:WU00:FS00:0x18:Completed 825000 out of 2500000 steps (33%)
22:54:09:WU00:FS00:0x18:Completed 850000 out of 2500000 steps (34%)
22:55:02:WU00:FS00:0x18:Completed 875000 out of 2500000 steps (35%)
22:55:55:WU00:FS00:0x18:Completed 900000 out of 2500000 steps (36%)
22:56:51:WU00:FS00:0x18:Completed 925000 out of 2500000 steps (37%)
22:57:44:WU00:FS00:0x18:Completed 950000 out of 2500000 steps (38%)
22:58:37:WU00:FS00:0x18:Completed 975000 out of 2500000 steps (39%)
22:59:30:WU00:FS00:0x18:Completed 1000000 out of 2500000 steps (40%)
23:00:27:WU00:FS00:0x18:Completed 1025000 out of 2500000 steps (41%)
23:01:20:WU00:FS00:0x18:Completed 1050000 out of 2500000 steps (42%)
23:02:12:WU00:FS00:0x18:Completed 1075000 out of 2500000 steps (43%)
23:03:06:WU00:FS00:0x18:Completed 1100000 out of 2500000 steps (44%)
23:04:02:WU00:FS00:0x18:Completed 1125000 out of 2500000 steps (45%)
23:04:55:WU00:FS00:0x18:Completed 1150000 out of 2500000 steps (46%)
23:05:48:WU00:FS00:0x18:Completed 1175000 out of 2500000 steps (47%)
23:06:41:WU00:FS00:0x18:Completed 1200000 out of 2500000 steps (48%)
23:07:37:WU00:FS00:0x18:Completed 1225000 out of 2500000 steps (49%)
23:08:30:WU00:FS00:0x18:Completed 1250000 out of 2500000 steps (50%)
23:09:23:WU00:FS00:0x18:Completed 1275000 out of 2500000 steps (51%)
23:10:16:WU00:FS00:0x18:Completed 1300000 out of 2500000 steps (52%)
23:11:13:WU00:FS00:0x18:Completed 1325000 out of 2500000 steps (53%)
23:12:06:WU00:FS00:0x18:Completed 1350000 out of 2500000 steps (54%)
23:12:59:WU00:FS00:0x18:Completed 1375000 out of 2500000 steps (55%)
23:13:52:WU00:FS00:0x18:Completed 1400000 out of 2500000 steps (56%)
23:14:48:WU00:FS00:0x18:Completed 1425000 out of 2500000 steps (57%)
23:15:41:WU00:FS00:0x18:Completed 1450000 out of 2500000 steps (58%)
23:16:34:WU00:FS00:0x18:Completed 1475000 out of 2500000 steps (59%)
23:17:27:WU00:FS00:0x18:Completed 1500000 out of 2500000 steps (60%)
23:18:23:WU00:FS00:0x18:Completed 1525000 out of 2500000 steps (61%)
23:19:16:WU00:FS00:0x18:Completed 1550000 out of 2500000 steps (62%)
23:20:09:WU00:FS00:0x18:Completed 1575000 out of 2500000 steps (63%)
23:21:02:WU00:FS00:0x18:Completed 1600000 out of 2500000 steps (64%)
23:21:59:WU00:FS00:0x18:Completed 1625000 out of 2500000 steps (65%)
23:22:52:WU00:FS00:0x18:Completed 1650000 out of 2500000 steps (66%)
23:23:45:WU00:FS00:0x18:Completed 1675000 out of 2500000 steps (67%)
23:24:38:WU00:FS00:0x18:Completed 1700000 out of 2500000 steps (68%)
23:25:34:WU00:FS00:0x18:Completed 1725000 out of 2500000 steps (69%)
23:26:27:WU00:FS00:0x18:Completed 1750000 out of 2500000 steps (70%)
23:27:20:WU00:FS00:0x18:Completed 1775000 out of 2500000 steps (71%)
23:28:13:WU00:FS00:0x18:Completed 1800000 out of 2500000 steps (72%)
23:29:10:WU00:FS00:0x18:Completed 1825000 out of 2500000 steps (73%)
23:30:03:WU00:FS00:0x18:Completed 1850000 out of 2500000 steps (74%)
23:30:56:WU00:FS00:0x18:Completed 1875000 out of 2500000 steps (75%)
23:31:49:WU00:FS00:0x18:Completed 1900000 out of 2500000 steps (76%)
23:32:45:WU00:FS00:0x18:Completed 1925000 out of 2500000 steps (77%)
23:33:38:WU00:FS00:0x18:Completed 1950000 out of 2500000 steps (78%)
23:34:31:WU00:FS00:0x18:Completed 1975000 out of 2500000 steps (79%)
23:35:24:WU00:FS00:0x18:Completed 2000000 out of 2500000 steps (80%)
23:36:21:WU00:FS00:0x18:Completed 2025000 out of 2500000 steps (81%)
23:37:14:WU00:FS00:0x18:Completed 2050000 out of 2500000 steps (82%)
23:38:07:WU00:FS00:0x18:Completed 2075000 out of 2500000 steps (83%)
23:39:00:WU00:FS00:0x18:Completed 2100000 out of 2500000 steps (84%)
23:39:56:WU00:FS00:0x18:Completed 2125000 out of 2500000 steps (85%)
23:40:49:WU00:FS00:0x18:Completed 2150000 out of 2500000 steps (86%)


WU's work folder log
Code: Select all
*********************** Log Started 2016-03-30T22:41:24Z ***********************
Project: 9152 (Run 16, Clone 22, Gen 18)
Unit: 0x00000014ab436c9f56623c6016159528
CPU: 0x00000000000000000000000000000000
Machine: 0
Digital signatures verified
Folding@home GPU core18
Version 0.0.4
  Found a checkpoint file
Completed 500000 out of 2500000 steps (20%)
Temperature control disabled. Requirements: single Nvidia GPU, tmax must be < 110 and twait >= 900
Completed 525000 out of 2500000 steps (21%)
Completed 550000 out of 2500000 steps (22%)
Completed 575000 out of 2500000 steps (23%)
Completed 600000 out of 2500000 steps (24%)
Completed 625000 out of 2500000 steps (25%)
Completed 650000 out of 2500000 steps (26%)
Completed 675000 out of 2500000 steps (27%)
Completed 700000 out of 2500000 steps (28%)
Completed 725000 out of 2500000 steps (29%)
Completed 750000 out of 2500000 steps (30%)
Completed 775000 out of 2500000 steps (31%)
Completed 800000 out of 2500000 steps (32%)
Completed 825000 out of 2500000 steps (33%)
Completed 850000 out of 2500000 steps (34%)
Completed 875000 out of 2500000 steps (35%)
Completed 900000 out of 2500000 steps (36%)
Completed 925000 out of 2500000 steps (37%)
Completed 950000 out of 2500000 steps (38%)
Completed 975000 out of 2500000 steps (39%)
Completed 1000000 out of 2500000 steps (40%)
Completed 1025000 out of 2500000 steps (41%)
Completed 1050000 out of 2500000 steps (42%)
Completed 1075000 out of 2500000 steps (43%)
Completed 1100000 out of 2500000 steps (44%)
Completed 1125000 out of 2500000 steps (45%)
Completed 1150000 out of 2500000 steps (46%)
Completed 1175000 out of 2500000 steps (47%)
Completed 1200000 out of 2500000 steps (48%)
Completed 1225000 out of 2500000 steps (49%)
Completed 1250000 out of 2500000 steps (50%)
Completed 1275000 out of 2500000 steps (51%)
Completed 1300000 out of 2500000 steps (52%)
Completed 1325000 out of 2500000 steps (53%)
Completed 1350000 out of 2500000 steps (54%)
Completed 1375000 out of 2500000 steps (55%)
Completed 1400000 out of 2500000 steps (56%)
Completed 1425000 out of 2500000 steps (57%)
Completed 1450000 out of 2500000 steps (58%)
Completed 1475000 out of 2500000 steps (59%)
Completed 1500000 out of 2500000 steps (60%)
Completed 1525000 out of 2500000 steps (61%)
Completed 1550000 out of 2500000 steps (62%)
Completed 1575000 out of 2500000 steps (63%)
Completed 1600000 out of 2500000 steps (64%)
Completed 1625000 out of 2500000 steps (65%)
Completed 1650000 out of 2500000 steps (66%)
Completed 1675000 out of 2500000 steps (67%)
Completed 1700000 out of 2500000 steps (68%)
Completed 1725000 out of 2500000 steps (69%)
Completed 1750000 out of 2500000 steps (70%)
Completed 1775000 out of 2500000 steps (71%)
Completed 1800000 out of 2500000 steps (72%)
Completed 1825000 out of 2500000 steps (73%)
Completed 1850000 out of 2500000 steps (74%)
Completed 1875000 out of 2500000 steps (75%)
Completed 1900000 out of 2500000 steps (76%)
Completed 1925000 out of 2500000 steps (77%)
Completed 1950000 out of 2500000 steps (78%)
Completed 1975000 out of 2500000 steps (79%)
Completed 2000000 out of 2500000 steps (80%)
Completed 2025000 out of 2500000 steps (81%)
Completed 2050000 out of 2500000 steps (82%)
Completed 2075000 out of 2500000 steps (83%)
Completed 2100000 out of 2500000 steps (84%)
Completed 2125000 out of 2500000 steps (85%)
Completed 2150000 out of 2500000 steps (86%)
Completed 2175000 out of 2500000 steps (87%)
Completed 2200000 out of 2500000 steps (88%)
Completed 2225000 out of 2500000 steps (89%)
Completed 2250000 out of 2500000 steps (90%)
Completed 2275000 out of 2500000 steps (91%)
Completed 2300000 out of 2500000 steps (92%)
Completed 2325000 out of 2500000 steps (93%)
Completed 2350000 out of 2500000 steps (94%)
Completed 2375000 out of 2500000 steps (95%)
Completed 2400000 out of 2500000 steps (96%)
Completed 2425000 out of 2500000 steps (97%)
Completed 2450000 out of 2500000 steps (98%)
Completed 2475000 out of 2500000 steps (99%)
Completed 2500000 out of 2500000 steps (100%)
Saving result file logfile_01.txt
Saving result file checkpointState.xml
Saving result file checkpt.crc
Saving result file log.txt
Saving result file positions.xtc
Folding@home Core Shutdown: FINISHED_UNIT


global log after reboot and client restart
Code: Select all
*********************** Log Started 2016-03-31T04:57:42Z ***********************
04:57:42:************************* Folding@home Client *************************
04:57:42:      Website: http://folding.stanford.edu/
04:57:42:    Copyright: (c) 2009-2014 Stanford University
04:57:42:       Author: Joseph Coffland <joseph@cauldrondevelopment.com>
04:57:42:         Args:
04:57:42:       Config: d:/$TEMP$/fah/config.xml
04:57:42:******************************** Build ********************************
04:57:42:      Version: 7.4.4
04:57:42:         Date: Mar 4 2014
04:57:42:         Time: 20:26:54
04:57:42:      SVN Rev: 4130
04:57:42:       Branch: fah/trunk/client
04:57:42:     Compiler: Intel(R) C++ MSVC 1500 mode 1200
04:57:42:      Options: /TP /nologo /EHa /Qdiag-disable:4297,4103,1786,279 /Ox -arch:SSE
04:57:42:               /QaxSSE2,SSE3,SSSE3,SSE4.1,SSE4.2 /Qopenmp /Qrestrict /MT /Qmkl
04:57:42:     Platform: win32 XP
04:57:42:         Bits: 32
04:57:42:         Mode: Release
04:57:42:******************************* System ********************************
04:57:42:          CPU: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz
04:57:42:       CPU ID: GenuineIntel Family 6 Model 94 Stepping 3
04:57:42:         CPUs: 8
04:57:42:       Memory: 31.92GiB
04:57:42:  Free Memory: 29.85GiB
04:57:42:      Threads: WINDOWS_THREADS
04:57:42:   OS Version: 6.2
04:57:42:  Has Battery: false
04:57:42:   On Battery: false
04:57:42:   UTC Offset: 2
04:57:42:          PID: 5596
04:57:42:          CWD: d:/$TEMP$/fah
04:57:42:           OS: Windows 10 Pro
04:57:42:      OS Arch: AMD64
04:57:42:         GPUs: 1
04:57:42:        GPU 0: NVIDIA:5 GM200 [GeForce GTX 980 Ti]
04:57:42:         CUDA: 5.2
04:57:42:  CUDA Driver: 8000
04:57:42:Win32 Service: false
04:57:42:***********************************************************************
04:57:42:<config>
04:57:42:  <!-- Folding Slot Configuration -->
04:57:42:  <extra-core-args v='-forceasm -verbose'/>
04:57:42:  <max-packet-size v='big'/>
04:57:42:
04:57:42:  <!-- HTTP Server -->
04:57:42:  <allow v='127.0.0.1 192.168.20.0/24'/>
04:57:42:
04:57:42:  <!-- Network -->
04:57:42:  <proxy v=':8080'/>
04:57:42:
04:57:42:  <!-- Remote Command Server -->
04:57:42:  <password v='*****'/>
04:57:42:
04:57:42:  <!-- Slot Control -->
04:57:42:  <power v='full'/>
04:57:42:
04:57:42:  <!-- User Information -->
04:57:42:  <passkey v='********************************'/>
04:57:42:  <team v='229610'/>
04:57:42:  <user v='^w^ing'/>
04:57:42:
04:57:42:  <!-- Work Unit Control -->
04:57:42:  <next-unit-percentage v='100'/>
04:57:42:
04:57:42:  <!-- Folding Slots -->
04:57:42:  <slot id='0' type='GPU'>
04:57:42:    <core-priority v='low'/>
04:57:42:  </slot>
04:57:42:</config>
04:57:42:Trying to access database...
04:57:42:Successfully acquired database lock
04:57:42:Enabled folding slot 00: READY gpu:0:GM200 [GeForce GTX 980 Ti]
04:57:42:WU00:FS00:Starting
04:57:42:WU00:FS00:Running FahCore: C:\FoldingAtHome\FAHClient/FAHCoreWrapper.exe d:/$TEMP$/fah/cores/web.stanford.edu/~pande/Win32/AMD64/NVIDIA/Fermi/Core_18.fah/FahCore_18.exe -dir 00 -suffix 01 -version 704 -lifeline 5596 -checkpoint 15 -gpu 0 -gpu-vendor nvidia -forceasm -verbose
04:57:42:WU00:FS00:Started FahCore on PID 5820
04:57:42:WU00:FS00:Core PID:7016
04:57:42:WU00:FS00:FahCore 0x18 started
04:57:43:WU01:FS00:Connecting to 171.67.108.45:80
04:57:43:WU00:FS00:0x18:*********************** Log Started 2016-03-31T04:57:42Z ***********************
04:57:43:WU00:FS00:0x18:Project: 9152 (Run 16, Clone 22, Gen 18)
04:57:43:WU00:FS00:0x18:Unit: 0x00000014ab436c9f56623c6016159528
04:57:43:WU00:FS00:0x18:CPU: 0x00000000000000000000000000000000
04:57:43:WU00:FS00:0x18:Machine: 0
04:57:43:WU00:FS00:0x18:Digital signatures verified
04:57:43:WU00:FS00:0x18:Folding@home GPU core18
04:57:43:WU00:FS00:0x18:Version 0.0.4
04:57:44:WU01:FS00:Assigned to work server 171.67.108.155
04:57:44:WU01:FS00:Requesting new work unit for slot 00: RUNNING gpu:0:GM200 [GeForce GTX 980 Ti] from 171.67.108.155
04:57:44:WU01:FS00:Connecting to 171.67.108.155:8080
04:57:51:WU00:FS00:0x18:Completed 0 out of 2500000 steps (0%)
04:57:51:WU00:FS00:0x18:Temperature control disabled. Requirements: single Nvidia GPU, tmax must be < 110 and twait >= 900
04:57:52:WU01:FS00:Downloading 5.58MiB
04:57:58:WU01:FS00:Download 25.75%
04:58:04:WU01:FS00:Download 58.21%
04:58:10:WU01:FS00:Download 87.32%
04:58:12:WU01:FS00:Download complete
04:58:12:WU01:FS00:Received Unit: id:01 state:DOWNLOAD error:NO_ERROR project:9627 run:3 clone:2 gen:19 core:0x21 unit:0x0000001bab436c9b56ef7fef2cb06fba
04:58:56:WU00:FS00:0x18:Completed 25000 out of 2500000 steps (1%)
04:59:58:WU00:FS00:0x18:Completed 50000 out of 2500000 steps (2%)
05:00:59:WU00:FS00:0x18:Completed 75000 out of 2500000 steps (3%)
05:02:01:WU00:FS00:0x18:Completed 100000 out of 2500000 steps (4%)
05:03:06:WU00:FS00:0x18:Completed 125000 out of 2500000 steps (5%)
05:04:07:WU00:FS00:0x18:Completed 150000 out of 2500000 steps (6%)
05:05:09:WU00:FS00:0x18:Completed 175000 out of 2500000 steps (7%)
05:06:11:WU00:FS00:0x18:Completed 200000 out of 2500000 steps (8%)
05:07:15:WU00:FS00:0x18:Completed 225000 out of 2500000 steps (9%)


this now precludes me from contributing to the project.
^w^ing
 
Posts: 247
Joined: Fri Mar 07, 2008 7:29 pm
Location: Prague

Re: Nvlddmkm stopped responding/recovers

Postby toTOW » Thu Mar 31, 2016 2:16 pm

Something else is probably causing you issues :( ... did you run a complete stability check of the system ?

What other program could interfere with FAH when you encounter this behaviour ?
User avatar
toTOW
Site Moderator
 
Posts: 8329
Joined: Sun Dec 02, 2007 10:38 am
Location: Bordeaux, France

Re: Nvlddmkm stopped responding/recovers

Postby ^w^ing » Thu Mar 31, 2016 6:33 pm

this only happens with folding@home (gpu) running, does not happen otherwise, not even in heavy workloads. crashes on both core18 and core21 WUs. running overclock/stock/underclock has no effect on the issue. on windows 7 I did not have this issue. just to repeat what I said earlier more clearly - it got worse with the new drivers, it did not use to crash when not otherwise in use - it only crashed in cases described by the OP, but now it crashes precisely every hour when my monitors are turned off. by precisely i mean for example at 1:34:23, then 2:34:23 and so on according to event viewer... rather strange. I can't imagine what other program could interfere with it, already tried shutting down everything non essential and let it run for the night, but it did not help.
^w^ing
 
Posts: 247
Joined: Fri Mar 07, 2008 7:29 pm
Location: Prague

Re: Nvlddmkm stopped responding/recovers

Postby bruce » Thu Mar 31, 2016 6:47 pm

You're suggesting that the updated drivers are causing the problem. Reinstall the old drivers, disable OS's ability to replace them, and let us know what works correctly.
bruce
 
Posts: 20828
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: Nvlddmkm stopped responding/recovers

Postby ^w^ing » Thu Mar 31, 2016 11:00 pm

that is not really what I am suggesting, none of the old drivers worked correctly either - they behaved exactly as OP described, since day 1 of my windows 10 install and running fah. the new drivers just made it worse in a very specific way, that they now crash in the same situations as before + when my PC is running fah, otherwise not being used, and my monitors are off (but, interestingly, not when my PC is not being used and I don't actually turn off my monitors).

as this escalated the issues from inconvenient to unacceptable, I am seeking a definitive solution.

I'm not sure what rolling back to the previous driver will accomplish, I already know that they crashed too, they all do on windows 10 + fah.
^w^ing
 
Posts: 247
Joined: Fri Mar 07, 2008 7:29 pm
Location: Prague

Re: Nvlddmkm stopped responding/recovers

Postby Hunac » Sun Apr 24, 2016 5:36 am

Any news about this issue or a way of how to fix it ?
Hunac
 
Posts: 1
Joined: Sat Jul 06, 2013 10:29 am

Re: Nvlddmkm stopped responding/recovers

Postby toTOW » Mon Apr 25, 2016 1:21 pm

See my first post in this topic ... if changing the settings doesn't help, there is another issue.
User avatar
toTOW
Site Moderator
 
Posts: 8329
Joined: Sun Dec 02, 2007 10:38 am
Location: Bordeaux, France

Re: Nvlddmkm stopped responding/recovers

Postby bruce » Mon Apr 25, 2016 5:59 pm

If toTOW's fixs solve it, fine.
If not, what does the Windows event log say about this error?
bruce
 
Posts: 20828
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: Nvlddmkm stopped responding/recovers

Postby boolean » Fri May 06, 2016 6:48 am

There are a dozen of others who are experiencing the same issues. Mainly everyone who uses a resent OS and is folding. They are all W10/F@H/Nvidia related. Reverting back to drivers <=362.00 solves most of the crashes, but some might still occur.
Image
Image
boolean
 
Posts: 4
Joined: Wed Nov 26, 2008 11:47 pm
Location: The Netherlands

Re: Nvlddmkm stopped responding/recovers

Postby bruce » Fri May 06, 2016 3:58 pm

Either Windows or the drivers may have altered the setting for the abort timer that's supposed to detect a screen update that's taking "too long," If that's the issue, it can be "fixed" by a relatively easy change to the registry -- or FAH can reduce the amount computations that it sends to the GPU in a single block of work or wait until NV adjusts the setting.

See also viewtopic.php?f=80&t=28662
bruce
 
Posts: 20828
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.


Return to Windows 10 + NVidia

Who is online

Users browsing this forum: No registered users and 1 guest

cron