Recently I have built a 3D rendering station for a client of mine. The machine runs, but crashes about once or twice a day with a BSOD (watchdog violation 1x133. Blue Screen View mentions either nvlddmkm.sys or ntoskrnl.exe as culprit. Things I have tried so far: Clean install Windows 10 Clean install Windows 7 DDU removal of graphics drivers latest nVidia drivers older nVidia drivers extensive RAM testing Specs: Asus X99-WS 10G E Intel 6850K 7x Zotac 1080ti Blower Edition (transformed to water cooling) 64GB RAM Samsung 960 Pro 512GB (system drive) 3x WD Red in RAID 0 (data drive) 2x Cooler Master V1200 PSU Custom EK watercooling loop Obsidian 900D Speccy Snapshot: http://speccy.piriform.com/results/qchWoHD0m7mueWTEVccxFlD Any help or insight on this issue would be greatly appreciated, as this issue now causes great delays in my client's workflow.

Haven't seen that happen here yet, but could be unnoticed, because the machine is only being monitored remotely. One other thing we have noticed is that while rendering, some of the cards will intermittently be idle for a few seconds. My guess was this was being caused by the MSI-Utility. Might be the same thing as you seeing a frozen screen occasionally. But indeed, great that this is finally working properly (this is actually the first time in 8 months that this machine can be put to real use - quite a waste, considering it was kinda hard sourcing 8 GTX 1080ti's back in the Great GPU Drought of 2017 :)

Good news everyone! nVidia released drivers yesterday (411.63) that list this issue as fixed!

I confirm the system is stable with the new drivers (411.63), using ASUS X299 Sage WS motherboard and 4x GTX 1080 Ti GPUs. UPDATE (24/09/2018): I got a DPC_WATCHDOG_VIOLATION error (BSOD) twice today. Looks like the bug is still present :-(

Nice guys! Thanks for letting us know :)

PC crashing - BSOD Watchdog violation 1x133 (possibly nVidia issue)

Anonymous

Recently I have built a 3D rendering station for a client of mine. The machine runs, but crashes about once or twice a day with a BSOD (watchdog violation 1x133. Blue Screen View mentions either nvlddmkm.sys or ntoskrnl.exe as culprit.

Things I have tried so far:

Clean install Windows 10
Clean install Windows 7
DDU removal of graphics drivers
latest nVidia drivers
older nVidia drivers
extensive RAM testing

Specs:

Asus X99-WS 10G E
Intel 6850K
7x Zotac 1080ti Blower Edition (transformed to water cooling)
64GB RAM
Samsung 960 Pro 512GB (system drive)
3x WD Red in RAID 0 (data drive)
2x Cooler Master V1200 PSU
Custom EK watercooling loop
Obsidian 900D

Speccy Snapshot: http://speccy.piriform.com/results/qchWoHD0m7mueWTEVccxFlD

Any help or insight on this issue would be greatly appreciated, as this issue now causes great delays in my client's workflow.

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

87 answers

Anonymous

2018-08-10T12:22:04+00:00

Haven't seen that happen here yet, but could be unnoticed, because the machine is only being monitored remotely.

One other thing we have noticed is that while rendering, some of the cards will intermittently be idle for a few seconds. My guess was this was being caused by the MSI-Utility. Might be the same thing as you seeing a frozen screen occasionally.

But indeed, great that this is finally working properly (this is actually the first time in 8 months that this machine can be put to real use - quite a waste, considering it was kinda hard sourcing 8 GTX 1080ti's back in the Great GPU Drought of 2017 :)
Was this answer helpful?

0 comments No comments
Anonymous

2018-09-20T07:37:52+00:00

Good news everyone!

nVidia released drivers yesterday (411.63) that list this issue as fixed!
Was this answer helpful?

0 comments No comments
Anonymous

2018-09-21T23:31:47+00:00

I confirm the system is stable with the new drivers (411.63), using ASUS X299 Sage WS motherboard and 4x GTX 1080 Ti GPUs.

UPDATE (24/09/2018): I got a DPC_WATCHDOG_VIOLATION error (BSOD) twice today. Looks like the bug is still present :-(
Was this answer helpful?

0 comments No comments
Anonymous

2018-09-21T23:46:49+00:00

Nice guys! Thanks for letting us know :)
Was this answer helpful?

0 comments No comments
Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more